Incidents
When something goes badly wrong for a restaurant (a payment defect, an ordering defect, or a QR code problem), operations opens an incident and switches off the affected feature in one step:
| Switched off | Guests see |
|---|---|
| Ordering | The menu, without ordering. Paying still works |
| Payments | The bill, without paying. Staff take payment at the till |
| Service | 4u Check is unavailable at the restaurant |
Each incident has a severity (P0, P1 or P2) and moves from open to retrying to resolved.
Switching back on
Section titled “Switching back on”Restoring a feature needs a second check: the technical side (operations) and the restaurant side (the manager) each confirm, so a feature never comes back on by mistake. Managers can also switch ordering or payments off and on themselves from settings, for example during a till outage.

