Start here: one database per machine
Every AlphaTill install keeps your business data in a database file on that computer. That is what makes the till keep working when the internet does not — and it is also the fact that decides everything below. There is no AlphaTill server holding a master copy of your shop.
So the question is not “does AlphaTill do multi-location?”. It is: are your extra tills on the same local network as the first one, or not?
Several tills in one shop — this works today
On one network, one PC runs in server mode and the others connect to it over the LAN. They share one database in real time: a sale on till 2 shows on till 1, and stock comes down once. This is the Multi-device LAN sync line on pricing, and it needs the LAN plus a firewall rule — not the internet.
The mobile companion app joins the same way, over your own network.
Two shops on different networks — read this before you buy
Two shops on separate networks keep separate databases. Nothing syncs between sites automatically today — you move data between them with an export, an import or a backup file, and a chain-wide live total is not something AlphaTill produces yet.
A second shop means a second AlphaTill install with its own database. The two do not talk to each other over the internet, because nothing in AlphaTill sends your business data anywhere. Head-office totals, transfers that debit one shop and credit another, and a single stock figure across sites are all things AlphaTill does not do yet.
What a “location” is inside AlphaTill
A location is a label on a product and on a sale, held in the one database on that machine. Stock is a single quantity per product, so a location tells you where something is recorded — it is not a separate stock pool.
That is genuinely useful for one site with several storage areas — shop floor, stockroom, van — and it is what the location features are built around. It is not two shops sharing a ledger.
- Sites included
- 10 sites on Business, 1 site on Professional and below, Custom on Enterprise.
- Areas inside a site
- Unlimited on every tier — they do not count against the cap.
- Transfer requests
- Business and Enterprise.
- Stock report grouped by location
- Every tier, including Solo.
Transfer requests: what they do and what they do not
Transfer requests between locations, with a pending → approved → completed trail and who approved each one. This is record-keeping: completing a transfer does not move stock quantities by itself, so you still adjust stock where you count it.
Do not use a completed transfer as your record that stock has physically moved and been counted. The request is the paperwork — the approval trail of who asked, who approved and when. Adjust the stock figures where you actually count them.
Reporting across locations
Stock reports grouped by location label, so you can see value and counts per location inside that database.
There is no chain-wide roll-up that combines two shops’ databases into one figure. If you need that today, export from each site and combine the exports — which is honest work, not a feature we are going to pretend is automatic.
If you need real multi-site sync
Talk to us before you buy rather than after. Enterprise includes a self-hosted option, and cross-site sync is the kind of thing we would rather scope with you than sell you a tier and hope. Contact us and say how many sites and what you need to see across them.
Up to 10 sites, counted as top-level sites — areas inside a site, like a stockroom or a shelf, do not count against it on any tier.