Industry
Retail software.
Retail technology spans a physical till and a national inventory picture. The unforgiving requirement is that a store cannot stop taking money because a connection failed, which forces genuinely offline-capable design at the point of sale.
What shapes the architecture
Constraints that are specific to this sector.
These are the things that would be wrong or meaningless if written about a different industry. They are design inputs, not compliance paperwork added at the end.
- 01
The till must transact offline
A store with no connectivity still has customers in a queue. POS needs local persistence, local tax and pricing rules, and deterministic reconciliation when the link returns.
- 02
One stock pool, many fulfilment promises
Ship-from-store, click-and-collect and in-store sale all draw on the same units. Without a reservation model the same item is promised twice, and the customer discovers it, not you.
- 03
Cycle counts never match the system
Shrinkage and mis-scans mean recorded stock drifts from physical stock permanently. Systems need a correction workflow with an audit trail, not an assumption of accuracy.
- 04
Promotions compose in unexpected ways
Multibuy, coupons, loyalty tiers and markdowns stack. A pricing engine needs deterministic precedence and a way to explain a computed price, or staff cannot resolve a dispute at the counter.
Typical work in retail.
- Point of sale and offline-capable tills
- Omnichannel order management
- Inventory and stock visibility
- Loyalty and promotions engines
- Click-and-collect fulfilment
- Store operations and workforce tools
What it has to talk to.
- Payment terminals
- ERP connectors
- Barcode / RFID
- Loyalty platforms
- Tax engines
Integration surfaces are where most sector projects actually fail. We treat each one as a boundary with its own translation layer, rather than letting an external format leak into the domain model.
Other sectors
Explore the rest.
Start here
Tell us the problem.
We'll be honest about the fit.
A first conversation costs nothing and is useful even if you go elsewhere — you'll leave with an architecture opinion and a realistic sense of scope.
- Reply within 24 hours
- No sales sequence