Offline mode
No-duplicate sync: one order stays one order
How each order carries a unique ID so that a reconnect does not send the same order twice.
No-duplicate sync gives each order a unique ID when it is created, so if the same order is sent twice after a reconnect it is recognized and counted once. A cook never sees a repeat ticket for one order, and your sales are never counted twice.
When you would use it
“After an outage, the kitchen prints two tickets for one order.”
“A manager worries that reconnecting will double sales.”
“A device retries when the connection flickers.”
How it goes, step by step
1
Order gets an ID
On the device, when it is created.
2
Order is sent
Maybe more than once.
3
Server de-duplicates
The same ID is kept once.
Settings and edge cases
| Topic | What to know |
|---|---|
| Example counts | Sync counts shown on this site are examples. |
| What staff see | A held order is marked as waiting, then as sent, so a cook can tell a repeat from a new ticket. |
| Why the ID matters | A counter that simply counts orders cannot tell a resend from a new order. A unique ID can. |
Questions about this feature
What if two devices make the same order?
They get different IDs, and staff can merge.
Do I need to do anything?
No. It works in the background.
See it on your own menu.
Bring your menu. We will show how Zorveta One fits your restaurant.