One fictional store, simulated customer by customer for a year: trade at the desk and the timber yard before nine, DIY through the weekend, which aisles have gaps, whether click-and-collect orders are ready when promised, and what each change would be worth.
The pharmacy mode the research plan names (the fastest-growing large store segment, +11.7%) is not built here. Hardware is the only mode on this page.
All PROPOSED. Switch any on and the whole year runs again on the same customers. The figure on each is that change on its own against the store as it is, as store contribution: gross margin less wages and on-costs, shrink, stock holding, tool costs and write-offs.
Five levels of authority, set per job by the store. Nothing here is running in any store: every row is a PROPOSED assembl concept. The evidence column says who measured a result and whether anyone checked it independently. Where nothing was found, it says so.
Start with exports the store already has: POS line items, an inventory snapshot, click-and-collect orders, the roster, and a door counter if there is one. Files are read inside this browser tab. Nothing is uploaded or sent anywhere. Customer names, emails and phone numbers are ignored; trade account ids are hashed before anything is kept.
Generated in this page from one simulated week, so a demo never touches real data. Column names differ from the contract on purpose. The POS file has two broken rows and fake account-holder name, customer name, email and phone columns; the roster names staff. All of those are ignored on load, and the trade account numbers are hashed.
No live connection to any store's systems exists. Read-only by design: the connector reads sales, stock, orders and rosters and never writes an order, a price or a roster back. Placing a replenishment order, changing a promotion or publishing a roster needs a person's approval, set by the authority levels above.
| Kind | Named | What this research verified |
|---|---|---|
| POS, independents and small chains | Lightspeed Retail, Shopify POS | Not verified: API access, fields and fees to be checked per client and per vendor. |
| ERP, larger chains | Microsoft Dynamics, SAP | Named only; integration path to be verified per client. |
Until a vendor's API is confirmed, a scheduled export (the same CSVs, dropped nightly into a secure folder) is the realistic path.
This page declares data-feeds="fuel,weather,rts". When the assembl lab's shared feeds layer answers, the tiles switch from the snapshot to the latest published or live value. The Retail Trade Survey is quarterly (the September 2026 quarter is due 23 November 2026): the rts feed reads the latest release's zipped CSV, so the hardware benchmark follows each new quarter and names the quarter it shows.