Loading...
Menu
Loading...
Architecture, specification and acceptance of a multi-store retail system, from stock to till
NYS runs a network of stores in Morocco alongside an online shop. Growth made spreadsheet-based stock tracking untenable, since the same item moves between points of sale and every movement must stay traceable. Our role covers the system architecture, its specification and the acceptance of each delivered block, with development carried out by a contractor on the client side.
A retail system is judged on its edge cases, not its happy path. An interrupted inter-store transfer must leave stock neither duplicated nor missing, a discount combined with a promo code must yield a commission calculable to the unit, and a till close must reconcile even after an incident. Specifying that means writing the rules before the code, then having a way to verify the code actually honours them.
Where the friction lived before we started.
How we removed the friction.
We first built a reference prototype covering the whole scope, which let the rules be settled against running code rather than intentions. That prototype became a stack-neutral specification, split into domains, with named rules and acceptance criteria verifiable one by one. Each block delivered by the contractor then goes through an acceptance run executed against the real system, with the result recorded.
Reference prototype built across the entire functional scope
Specification split into 16 domains, stack-neutral
185 named rules and 121 verifiable acceptance criteria
Acceptance run block by block against the real system, results recorded
GS1 barcodes encoding item and lot, printing included
Two-step inter-store transfers, backed by a printed note
Let's discuss your vision. We guide you from strategy to launch.