Fo-Mart

A custom device buyback platform where fraud prevention went from a policy to a system. Customer trade-in interface, SICKW IMEI verification integrated as a mandatory pre-purchase step, staff management system, and multi-location inventory tracking. MERN stack. 3 months.

Timeline
3 months
Fraud
Prevented
Locations
2 stores
Acquisition
Structured

What We Delivered

Frontend (React.js) Backend (Node.js/Express.js) MongoDB SICKW API Integration Multi-Location Inventory Staff Management System Fraud Prevention Architecture

The Situation

The store manager gets the call. A customer sold an iPhone an hour ago. Clean condition, they said. No issues. The IMEI check was supposed to happen, but it was busy, the system was slow, the manual lookup got skipped. The device has already been purchased. The payment has been made. The IMEI check runs now. The device is reported stolen.

This is not an unusual scenario. It is a predictable consequence of operating a verification-dependent workflow without verification-integrated infrastructure. The check that was supposed to happen as a condition of purchase became optional under operational pressure. And the fraud exposure that was always there became a fraud loss.

  1. Fraud exposure without infrastructure

    Customers submitting stolen or activation-locked devices, relying on the store's manual verification being skipped under pressure. The protection was a policy. Under pressure, policies become optional. Systems do not.

  2. No structured customer acquisition channel

    No digital channel for customers to submit device information and receive quotes. Enquiries arrived as messages and emails that staff processed manually. Volume limited to physical proximity.

  3. Inventory chaos across locations

    Two stores buying devices independently, maintaining separate records. No consolidated view of combined inventory, purchase activity, or buying patterns. The store manager who did not know what the other location paid for the same model last week was making buying decisions without context.

  4. Manual processes at every stage

    Customer submission, device assessment, pricing, purchase, inventory entry. Each requiring manual data entry and coordination. Each a point where errors accumulate and information gets lost.

  5. No workflow enforcement

    Verification was a manual step that could be skipped. Under pressure, it was skipped. The gap between policy and system is where fraud lives.

The buyback business was growing. The manual processes were not scaling with it. Every workaround accumulated in the gap between the workflow and the system was a point where revenue could be lost.

The Approach

Phase 1

Workflow Architecture and Verification Design

Before building, Empyreal mapped the complete buyback workflow from customer submission through to inventory record. Every stage identified as a dependency on the previous one. Every stage assessed for fraud exposure.

Three-layer problem analysis

Layer one: customer acquisition without structure. Layer two: fraud exposure without infrastructure. Layer three: inventory chaos across locations. Each layer addressed as a distinct problem with a specific architectural solution. All three integrated into a single platform.

SICKW integration placement

The most critical architectural decision. The IMEI verification check placed as a mandatory pre-purchase step in the workflow. Not a manual step that could be skipped. A system requirement that the purchase could not proceed without. The device that was reported stolen now produces a mandatory resolution step before any payment is made.

Customer-facing trade-in design

Structured device submission interface guiding customers through model identification, condition assessment, and quote generation. Every submission arriving in the staff system in a format ready for immediate processing.

Phase 2

MERN Stack Build and SICKW Integration

MongoDB, Express.js, React.js, Node.js. Two interconnected systems on shared data infrastructure.

Customer trade-in interface

Device selection, condition questionnaire, indicative quote generation, and customer information capture. Speed and clarity designed for the customer who wants to know what their device is worth before committing to a visit. The submission is the structured beginning of a workflow, not an enquiry into a void.

Staff management system

Buyback request queue, IMEI verification triggered from within the workflow, purchase processing with condition confirmation, and automatic inventory creation. The staff member who processes a buyback request follows a system. The system enforces the verification the manual process could not.

SICKW IMEI verification

Integrated as a mandatory workflow step. Clean status, flagged issues, and specific detail determining required action. Flagged devices produce a mandatory resolution step with an audit trail. The verification logic is not a feature. It is the fraud protection infrastructure.

Multi-location inventory

Single source of truth across both store locations. Every device purchased at any location immediately visible to all authorised staff. Purchase price, condition, and location tracked. Buying decisions informed by what the other location paid last week.

The Numbers

Timeline
3 months
Concept to live platform.
Fraud
Prevented
IMEI verification as mandatory pre-purchase system step.
Locations
2 locations
Consolidated inventory and purchase visibility.
Acquisition
Structured
Customer acquisition replacing manual email processing.

The scene that opened this case study is now structurally prevented. The IMEI check runs before the purchase. The flag is visible before the payment. The fraud protection is in the system, not in the staff's attention. For a buyback business scaling across locations, the platform provides the operational infrastructure that makes scaling manageable.

Mohit's Take

"The most critical component was placing the SICKW integration correctly in the workflow. A verification check after the purchase is not verification. It is a post-mortem. We built it as a mandatory pre-purchase step with an audit trail that protects the business in any dispute. That architectural decision is the fraud protection. Everything else, the customer interface, the inventory system, the multi-location visibility, serves the business. The SICKW placement protects it."

— Mohit Ramani, Founder & Lead Architect, Empyreal Infotech

Tech Stack

The toolchain behind the Fo-Mart platform.

MongoDB Express.js React.js Node.js SICKW API

Start a Conversation About Your Product

You have a device buyback operation that works and a digital infrastructure that is not keeping pace. The question is how much the gap between the two is costing you in fraud losses you cannot fully see, inventory inaccuracy you cannot fully measure, and operational overhead you cannot fully eliminate.

A discovery call with Empyreal is thirty minutes. You describe the buyback workflow. Empyreal listens, identifies where verification, inventory, and acquisition are failing, and tells you honestly what the platform architecture would require.