A multi-location flooring contractor
Barcode inventory that keeps working when the warehouse has no signal.
Client:
A multi-location flooring contractor
Year:
2026
Industry:
Home Services
Duration:
5 days, about 37 engineering hours
The Problem
Material stock for a multi-location floor-coating operation lived in a spreadsheet, reconciled by a monthly audit. In the client's own telling, everything ran right off an Excel sheet.
- No real-time count: the spreadsheet was only as fresh as the last audit
- No per-location view, so one city's surplus could not cover another city's shortage
- Reordering was reactive: a purchase order went out when someone noticed the rack was down to half a pallet
- Off-the-shelf inventory tools were rejected over lock-in: every missing feature would mean waiting on a vendor's roadmap
The fix had to work where crews actually are: warehouses and job sites with dead signal, on the phones already in their pockets.
Solution
An installable, offline-first app built for warehouse conditions, delivered as a working first version in five days.
Feature
How It Works
Camera barcode scanning
Scan pallets in as they arrive and out as crews load trailers, with a quantity keyed in per scan, so receiving a full pallet is one scan and one number. Pre-printed barcode sheets cover loose material like flake that carries no label. No scanner hardware was bought.
Offline scan queue
Scans queue on the device when a warehouse or job site has no signal and post automatically once a connection returns, so a dead zone never costs a stock movement.
Role-based access
Admin, manager, and crew roles, with crews seeing only the locations assigned to them.
Per-location stock, valuation, and alerts
Live counts across every location with low-stock thresholds, stock valuation, usage reports, CSV import and export, and label printing.
A full movement ledger
Every scan is recorded with who, what, where, and when, so any count can be traced back to the movements behind it.
Conclusion:
The first working version shipped in five days, about 37 engineering hours from a single developer, on the phones the crews already carry. It was built to retire the spreadsheet and the monthly audit as the source of stock truth, and it is part of the same account as the crew-availability build this client commissioned first.