Support
DineStack is early and deliberately small. When you write to us, somebody who works on the product reads it.
If a till is down and you are mid-service, say so in the subject line and we will jump it.
Getting started
It reads back what is and is not configured, so you can leave and come back without losing where you were.
Sign in to the owner dashboard. It tells you what is still outstanding.
Name, currency, time zone and tax. Rates are entered as percentages, and DineStack refuses one that looks like a decimal-point mistake.
Categories, items, prices, modifiers.
People, roles and PINs.
Add a POS terminal in People → Devices, read out the setup code, and type it into the tablet.
Fire it and take one payment end to end. The setup screen watches for that and will not call you ready without it.
Device troubleshooting
It has no credential yet, or it has never reached DineStack. Add a terminal in the dashboard and type the setup code in. If it says the tablet is registered under a different device, stop and write to us — enrolling it again would strand the orders it already recorded.
They last fifteen minutes and work once. Generate another. If a second one is also refused, check the tablet can reach the internet at all.
The tablet refuses to sign anybody new in if its authorised staff list has gone stale — which is correct, because otherwise switching somebody off would never reach the counter. Get it back online and it recovers by itself.
Revoke it in People → Devices. It stops syncing immediately. Everything it already recorded is unchanged — revoking is not a reason to unwrite last Tuesday.
A ticket appears when it is fired, not when it is rung up. If the kitchen screen says it is offline, it is showing you what it already has and will catch up on its own.
The till says which it was: nothing printed and you can retry, or the printer never answered and it may be on paper. In the second case check the paper first — that is what stops a guest getting two receipts for one sale.
Offline
The tablet keeps its own copy of the staff list, the menu, the prices, the tax rates and the order log. When the connection drops it keeps trading.
Payment continuity
When the card route is unavailable, the Card button stays on screen, greyed, with the reason on it — and cash and your backup terminal are offered instead.
A backup terminal payment is recorded as somebody’s confirmation that a charge was approved, labelled as exactly that, and counted separately in reconciliation until the terminal’s own batch confirms it.
The same rule runs through the product. A labour cost with no pay rate behind it reads “not known”, not zero. An order whose history cannot be read is quarantined and named rather than counted as a free meal. Where DineStack does not know something, it says so.