| Wrong table | Table mixed up, or direct sale confused with table service. | Confirm the table while taking the order and compare it with the guest request before sending; keep direct sale without a table on its own path. | The selected table assignment in the cart; table 41 on the station monitor. | The app does not check whether the guest is actually sitting at that table. That remains a team agreement. |
|---|
| Wrong variant or quantity | Similar names, rushed selection or unclear abbreviations. | Use unique product names and variants; check product, variant and quantity before sending. | Position and quantity in the cart; the sent item appears with product details on the monitor. | The app does not replace clear product setup or a final check before sending. |
|---|
| Wrong station | The product is assigned to the wrong station, or the station is not staffed. | Test station routing before the festival; name a responsible person and a question route for each station. | After sending, the item appears only at its assigned station; Grill and Kellnertheke show separate tickets. | A wrong setup is not detected automatically; the rehearsal must reveal it. |
|---|
| Unclear status | The status was not advanced, or the handover between helpers is unclear. | Agree who maintains Open, In progress and Ready, and who takes over open orders at a shift change. | The monitor shows three processing states per station. | “Ready” means processing is complete, not collected or paid. |
|---|
| Duplicate entry after an interruption | An order waits locally and is not visible on the monitor; someone enters it again. | First check the local queue on the submitting device; during a longer outage keep paper notes separately and reconcile after reconnection. | Locally waiting orders become visible on the monitor only after transmission. | There is no automatic duplicate lock and no guaranteed transmission time. |
|---|