Stock records that explain every difference

The monthly count across three warehouses and eleven vans took three days and still could not explain the write-offs. A movement ledger replaced the typed balances.

Length
12 weeks, one warehouse at a time

Shelf and system disagree every month

The client. A consumer electronics distributor in Bangladesh with three warehouses, eleven delivery vans and about 9,000 SKUs.

The count takes three days. Vans carry stock the system thinks is in the warehouse, and unexplained variance runs at about 2.4 percent of stock value.

Balances are typed in by hand, so a wrong number can be overwritten without a trace. Nobody can say which movement caused a difference.

How the engineers did it

  1. Record movements

    Every receipt, issue, transfer, van load and return becomes an event with a person and a time. The balance is their sum.

  2. Scan instead of typing

    An offline-first Android app scans barcodes in warehouses and vans, and syncs when the network returns.

  3. Count blind

    Counters do not see the system figure. A difference above the threshold creates an adjustment that waits for a supervisor.

  4. Treat vans as locations

    Loading and delivery are transfers, so van stock is always visible.

  5. Your supervisors sign off

    Variance reports link to the movements behind them, and a named supervisor approves every adjustment.

For your engineers

What was built

  • Movement ledger with derived balances and full history
  • Offline-first scanning app for warehouses and vans
  • Blind cycle counts with approval thresholds
  • Variance and write-off reports linked to the movements behind them
  • Low-stock alerts and reorder suggestions
  • Integration with the accounting system

Stack

Kotlin (Android), offline sync, PostgreSQL, Python, accounting integration

Length

12 weeks, one warehouse at a time

What changed

MeasureBeforeAfter
Monthly count3 days6 hours across three warehouses
Unexplained variance by valueabout 2.4%0.3% after two count cycles
Adjustments with a named approvernone recordedall of them

What we learned

  • A typed balance has no history. A ledger always does.
  • Offline-first is a requirement in a warehouse or a van.
  • Thresholds and approvals turn counting from an argument into a record.

Bring last month's stock count

The diagnostic follows one count from shelf to books, finds where the numbers part ways, and prices the ledger that would close the gap.