What runs where
| App | Who uses it | Where it runs |
|---|---|---|
| POS Terminal | Floor staff, bartenders, cashiers | Android, iOS, desktop, or any browser at /pos/ |
| Kitchen Display (KDS) | Kitchen & bar | Any terminal device — the Kitchen tab |
| Customer display | Guests at the counter | The Customer tab on a guest-facing screen |
| Back Office | Owners, managers | Desktop app (Windows/Mac/Linux) or any browser at /admin/ |
| QR Menu / guest ordering | Your guests | Their own phones — no app install (also served at /order/) |
| Sign-in hub | Anyone opening Aura in a browser | https://<your-server>/app/ — one page with the links to the till, the Back Office and guest ordering |
| Help centre | Everyone | https://<your-server>/help |
| API & sandbox | Developers/integrators | https://<your-server>/docs |
All of these talk to one server (your Aura backend). The terminals keep working when the server is unreachable and catch up automatically — see Offline and load shedding.
The POS terminal is one app with tabs for every job: Sale, Floor, Kitchen, Tabs, Orders, Checklists, Reports, Cash, Customer, and Settings. On tablets and desktops these live in a collapsible left rail (the ☰ button shrinks it to icons); on phones the ☰ opens a slide-in drawer. The top bar always shows who is signed in, a low-stock badge when items run low, and the sync badge (see §19).
More in Getting started
- 2Quick starts
- 3Setting up your restaurant
- 4Signing in, roles and permissions
- 25Running a shop (retail mode)
- 44Products and licensing
Still stuck? Mail support@aurapos.co.za or use the support page — include your venue name and what you were doing.