PROJECT CASE STUDY
Trace stock ownership through five movement categories.
An inventory ownership model connecting head-office storage, branch purchases, and order fulfilment for a cross-border cookware distributor.
KEY NUMBERS
Problem
Goods sit together at head office, but ownership lives in separate branch spreadsheets. Sales, reservations, and dispatches require manual reconciliation.
Approach
Separate physical storage from inventory ownership. Confirmed payment creates a branch allocation, and each sale draws on that branch’s stock.
What changed
Head office can see total warehouse stock and each branch’s allocation.
Retail distributor
Inventory ownership · Order flow · Product traceability
Earlier work by the Ordiva founding team, delivered under Story Light Studio. The three feature stories cover the same operations system.
Executive Summary
This cookware distributor stores goods centrally, while individual branches pay for and own their allocations. Separate spreadsheets blurred location, ownership, and dispatch status. We built an ownership ledger connecting payment confirmation, branch sales, reservations, dispatch, and warranty records. Head office can see the warehouse and branch allocations together; branches work within their own stock.
The client is a Vancouver-based premium cookware distributor with operations in China. Stock stays in a central warehouse, while individual branches pay for and sell their own allocation. Storage is shared; ownership is not.
The Problem
A conventional stock sheet can show what is in the warehouse without showing who owns it. When purchases, customer payments, and dispatches are recorded separately, head office and branches must reconcile allocations, borrowed stock, and unshipped orders by hand.
Before
Goods sit together at head office, but ownership lives in separate branch spreadsheets. Sales, reservations, and dispatches require manual reconciliation.
The implemented workflow
Separate physical storage from inventory ownership. Confirmed payment creates a branch allocation, and each sale draws on that branch’s stock.
The Vision
Give head office and branches a consistent answer for each item: who owns it, how much remains available, what has sold but not shipped, and how to trace it after dispatch.
The Solution
Separate physical storage from branch ownership
Two views describe the same stock: where it sits and which branch owns it. Head office confirms a branch purchase before its allocation is recorded. Sales, bundle deductions, and reservations follow that allocation. Five agreed movement categories provide a recording framework, and an individual warranty identifier links each dispatched item to its order.
Included in the build
- Branch ownership ledgers and a head-office stock view
- Payment confirmation, reservations, and bundle deductions
- Inventory movements and exception-handling records
- Per-item warranty identifiers linked to orders
How the System Works
How the team uses the inventory workflow
- 01
Establish ownership before changing quantities
Head office confirms a branch payment before the system adds its allocation. Goods remain centrally stored, with ownership tracked independently of location.
- 02
Keep each sale within its branch allocation
Branch orders draw only on that branch’s stock. Bundles are handled by component, while paid but unshipped quantities appear separately as reserved stock.
- 03
Give exceptions a traceable route
Damaged returns, shortages in transit, write-offs, and recovered items retain their records. Key quantities on settled write-offs are protected from later changes.
- 04
Connect after-sales service to the individual product
Dispatch generates a warranty identifier for each item, linked to its product and order. Head office and branches can trace the movement through shared records.
What Makes This System Different
A model that matches the trading relationship
Head office holds the goods; branches own their paid allocations. Separating those facts prevents total warehouse quantity from being treated as stock every branch can sell.
Payment confirmation is a workflow event
Confirmed branch purchases create ownership. Branch orders draw on that allocation, giving payment records and stock changes an explicit sequence.
Exceptions remain connected to normal fulfilment
Bundle components, reserved stock, damaged goods, transit shortages, and write-offs have defined paths. Settled quantities are protected, and warranty identifiers connect after-sales work to the original transaction.
Measurable Results
The following are functional and verification results from the project record.
Movement categories recorded
The contract-defined categories create a shared recording basis for branch and head-office reconciliation.
Product linked to its order
Each dispatched item receives its own warranty identifier. Bundles are handled by component, allowing after-sales checks against the related order.
Project-wide automated tests
The project record describes more than 700 tests across orders, payments, dispatch, damaged goods, permissions, and other areas. This is coverage for the whole system, not a stock-module test count.
Figure definitions and verification notes
Figures are drawn from the project introduction and sections A1, A5, A12, and A16. Counts describe implemented recording rules and project-wide verification.
Business Impact
Head office: less reconstruction of ownership
Managers can start with warehouse totals and branch allocations before investigating a difference. Reconciliation time still needs measurement after launch.
Branches: distinguish sellable stock from pending dispatch
Paid but unshipped quantities are shown separately as reservations, providing a clearer basis for taking orders and planning replenishment.
After-sales teams: trace the item back to the transaction
Warranty identifiers link products and orders, giving service staff a record to follow when checking purchase and dispatch information.
Ongoing operating metrics
- Manual minutes spent on each reconciliation
- Differences between reserved quantities and physical checks
- Time to retrieve a full order from a warranty identifier
Why This Matters
A warehouse total cannot explain responsibility when goods are stored together but sold by different branches. As the network grows, ownership differences become harder to resolve from memory. Connecting payment, ownership, and dispatch gives new branches a consistent way to keep records.
The Takeaway
Define ownership first, then automate stock movements. Head office and branches gain a common, traceable record; live reconciliation time and stock variance can then show how much the process improves.
LET’S TALK
Where does your workflow lose its thread?
Start with a problem your team handles repeatedly. Share the context by email, or arrange a remote video conversation.