Aantar POS
What is proved and what is not
Exactly what the chain test has proved about one company with many stores on one store server, what is not proved yet, and what a chain should check before go-live.
A chain on one store server has been proved by an automated test that runs a whole chain against a real store server over HTTPS: the set-up page, the company, the stores, the users, the tills, a day of sales, an outage, returns and every lane's close, then the books checked to the cent. This page says exactly what that test covers, and what it does not.
What is proved
With one store server, one company, and every till and the head office reaching it over HTTPS through their own line, as to a cloud server:
- The set-up page opened by name from away: the set-up code, the admin password, one BC liquor company.
- A location per store; a store manager role that does not reach every store; one manager per store; a manager of one store cannot sell at another.
- Every till paired from the set-up page's pairing link, with the server's fingerprint pinned; the link carries the public name.
- Store prices: the same item sells at each store's own price. A promotion for store 1 is sent to store 1 only and applied there only.
- A transfer from store 1 to store 2: stock moved, ledger balanced.
- Every lane of every store selling at the same time; one answer lost on the way back and the sale booked once.
- One store offline: its tills queue their sales while the other stores sell on; the line comes back; nothing lost, nothing twice.
- A return at every store, found by the store's own receipt number.
- X read, Close shift and Z on every lane; each Z holds its own sales.
- The books to the cent: every sale's total is the till's, every sale and return balanced, the ledger balanced, the ledger's tax the receipts' tax, stock at every store right, each store's Sales summary the sum of its lanes' Zs, and the stores adding up to the chain.
It passed at 3 stores of 2 lanes, 10 stores of 2 lanes, and 20 stores of 2 lanes (280 sales).
How fast
The store server writes one sale at a time. With all 40 lanes of 20 stores sending sales back to back with no pause, a sale waited 11 to 18 seconds for its answer (the median, depending on the run, on a shared test PC). Sales that waited longer than the till's live wait were queued and sent in order, as offline sales are: the customer was served and nothing was lost. A real store rings a sale every minute or two per lane, far below this.
What is not proved
- The Docker image on a real cloud computer over the real internet. The test runs the server in its own process.
- The speed on the cloud computer the chain will use.
- The till's screens. The test drives the till's own queue, pricing, sale and receipt numbering, not the screens a cashier touches.
- The head office's pages driven as screens: Stores side by side, transfers and reports. The test calls the same paths those pages call.
- A licence key for 40 lanes, and the lane limit at 40.
- Backups and a restore with 20 stores' tills paired.
- Stores in different time zones; store prices on items priced with tax included; stores in more than one province.
Not finished: The published plans stop at five lanes. A chain needs a key issued by Aantar One Inc. for all its lanes. See Chains over five lanes.
Important: Before a chain goes live, run one store for a full day on the real cloud server, with every lane, card terminal and printer, and compare its Zs with the books.
The chain requirements, at a glance
| Asked for | In Aantar POS today |
|---|---|
| One back office for every store | Yes: the back office on a head office computer paired with the server |
| One product catalogue for every store | Yes |
| Store prices and store promotions | Yes: Stores side by side |
| Changes to selected stores or all stores at once | Central prices and promotions: yes. Store prices: one item and store at a time |
| Stock by store, with transfers | Yes; transfers and the stock-by-store report are in Aantar Books |
| Reports per store and for the chain | Yes: a till's reports for its store, the back office's for the chain |
| Roles for owners, managers and cashiers, per store | Yes |
| Changes without visiting each store | Yes |
| New stores without rebuilding the catalogue | Yes: add a location |
| A cloud dashboard on the web | Not finished: the Aantar Cloud reports page is not deployed |
| Two-step sign-in for administrators | The Aantar account only, not the store's users or the store server |
| Backups and restore | Yes, on the store server; see Automatic backups |
| A request log | Yes: the store server logs every request with its device and user |
| A published API for other systems, webhooks, alerts by e-mail or text | No |
| A mobile-friendly admin dashboard | No: the back office runs in the app; the set-up page is a plain web page |
| Different suppliers and costs for one item at different stores | Not covered in this chapter; see Several suppliers and supplier SKUs |
Related articles
Something unclear or out of date? Write to support@aantar.com and name this page.