One Stock Record Across Three Locations
How a multi-location retail operation replaced end-of-day reconciliation with a shared inventory workflow for warehouses, POS, suppliers, and reporting.
The Situation
The retail operation held stock in multiple locations, while sales, transfers, supplier receipts, and returns all changed the same catalog. Teams needed a consolidated view without waiting for an end-of-day count or manually comparing separate records.
The case-study evidence describes the core issue as coordination: the business needed location-level detail and a dependable total at the same time.
The Reconciliation Problem
Stock moved faster than reports
Sales and transfers could make a location report stale before the next manual reconciliation.
Reorders depended on memory
Low stock needed a configurable threshold instead of a purchasing manager discovering it after the fact.
Systems disagreed
POS, ERP, e-commerce, accounting, and supplier records needed an integration layer around one inventory model.
What We Built
The documented architecture centers on one inventory database with location-level stock pools. Sales deduct stock, transfers move reservations between locations, and receiving updates the same shared catalog. The system exposes consolidated totals while preserving per-location drill-down.
A reorder engine watches configurable thresholds, drafts a purchase order to the preferred supplier, and routes it to a purchasing manager for approval.
How the System Works
Record the stock event
A sale, transfer, receipt, return, or write-off updates the relevant location.
Recalculate the shared view
The central record makes the new location balance and total available to connected systems.
Check the reorder point
When a SKU crosses its configured threshold, the system identifies the preferred supplier and quantity.
Draft and approve the purchase order
A draft PO is generated and sent to the purchasing manager for review rather than silently placing an order.
Before → After
- End-of-day reconciliation
- Separate location views
- Manual reorder discovery
- Conflicting system totals
- Shared real-time stock record
- Location-level drill-down
- Configurable reorder triggers
- Integration layer for existing systems
Implementation Details
The integration boundary is important: the inventory application connects to ERP, accounting, e-commerce, POS, and supplier systems rather than attempting to replace every system the business already uses.
Stock reservations, inter-warehouse transfers, preferred suppliers, expected arrival dates, and reorder history are treated as explicit records. That makes the workflow reviewable when an exception needs human judgment.
What Changed Operationally
The documented outcome is that end-of-day reconciliation was eliminated and stock discrepancies were reduced to zero across the three locations. The more durable change is that the team can act on the same stock picture regardless of which location or system generated the event.
The Broader Point
Multi-location inventory is not just a dashboard problem. It is an event and integration problem. A useful system preserves the detail needed by each location while maintaining a shared model that purchasing, sales, and operations can trust.
Start with the inventory model.
Solvevare designs inventory systems around catalogs, locations, integrations, and approval rules.
Book a Technical Discovery