A general-purpose guide for restaurant staff — not specific to any POS brand or system
Contain & Communicate
The moment your POS goes down, your first job is to stop the panic — not fix the system.
Action | Who | Script |
Announce the issue to staff | Manager/Shift Lead | "Team, our POS is temporarily down — switch to manual mode now." |
Notify waiting customers | Front of house staff | "We're experiencing a brief system issue. We'll continue serving you manually — thank you for your patience." |
Assign emergency roles | Manager | See the role table below |
Note the exact time the system went down | Anyone | Write it down immediately |
Emergency Role Assignment:
Role | Responsibility |
Order Taker | Takes orders using pen and paper / physical tickets |
Payment Handler | Manages manual/offline payments |
System Monitor | Attempts basic reboot steps and contacts support |
Customer Handler | Keeps the queue calm, manages complaints |
If you have fewer than 4 staff, the manager covers the System Monitor and Customer Handler roles.
Quick Triage (In This Order)
Do not skip steps or go out of sequence. 60–90% of failures resolve in this phase.
Step 1 — Basic Power & Hardware Checks
[ ] Check that the terminal is properly plugged in and powered on
[ ] Confirm the power outlet/surge protector/UPS has not tripped
[ ] Reboot the terminal: power off → wait 15–30 seconds → power on → wait for full boot
[ ] Check all cables: power cable, ethernet cable, USB connections to printer, cash drawer, and card reader
[ ] Confirm the receipt printer is online — check paper level, send a test print
[ ] Check the Kitchen Display System (KDS) is on and communicating
Step 2 — Network & Connectivity Checks
[ ] Check if the router/modem lights are normal (refer to your router's indicator guide)
[ ] Test internet connectivity: open a browser on a staff phone connected to the same Wi-Fi — can it reach a website?
[ ] If using wired ethernet, trace the cable back to the router — reseat both ends
[ ] Restart the router/modem if the internet is down: unplug → wait 30 seconds → plug back in
[ ] Wait 2 minutes for the network to restore fully, then recheck the POS
Step 3 — Software Restart
[ ] Fully close the POS application (do not just minimise it)
[ ] On Windows: use Task Manager → Force End Task if frozen
[ ] On Mac: use Force Quit (⌘ + Option + Esc)
[ ] On tablet/iPad: swipe the app closed fully
[ ] Wait 30 seconds, reopen the POS app, and attempt a test transaction
[ ] If it responds normally → system is back, proceed to post-recovery steps
[ ] If it freezes again → confirmed software issue, escalate immediately
Rule: If no fix within 5 minutes of triage, do not continue deep troubleshooting. Escalate and switch to full manual mode.
Manual Operations Mode (While System is Down)
Do not stop service. Switch to manual immediately.
Taking Orders
Method | What to Use |
Primary | Pre-printed paper order pads or triplicate ticket books |
Backup | Any pen and paper |
Record | Table number, seat number, item name, quantity, any modifications |
Kitchen | Walk physical tickets directly to the kitchen and call station |
Accepting Payments
Payment Type | How to Handle |
Cash | Accept normally — use a manual till/cash box with float; record every transaction |
Card (contactless/chip) | If your card machine operates independently of the POS, use it as a standalone device |
Card (no standalone terminal) | Inform customers politely; offer a cash alternative or request they return to pay once the system is restored |
Manual card imprint | If available, use a physical card imprinter (knuckle-buster) with carbon slips for later processing |
Mobile payments (QR, etc.) | Only if the payment method is entirely separate from your POS software |
Important: Record every manual transaction as it happens. Do not rely on memory for reconciliation later.
Escalating to Support
Before you call your POS provider, gather this information first — it will significantly reduce your support call time.
Pre-Call Data Checklist
[ ] Terminal ID or device serial number
[ ] POS software version (found in Settings > About, if accessible)
[ ] Exact error message or error code (photograph the screen if possible)
[ ] Exact time the issue started (use 24-hour format)
[ ] What the staff member was doing when it failed (e.g., processing a refund, printing a receipt, closing a table)
[ ] Whether the issue is recurring or has happened once
[ ] Any recent changes: software update, new menu items added, network provider changed, new hardware installed
[ ] User account that encountered the error (cashier, manager, specific employee)
[ ] Payment processor in use (if the issue involves payments)
During the Support Call
Lead with data, not a story — state the error code, time, and action immediately
Follow the agent's steps exactly — do not skip ahead
Do not hang up without a ticket/reference number and a clear statement of next steps
Write down the ticket number and promised callback time
If they do not call back within the stated window, call back with your ticket number
If Vendor Support Cannot Help in Time
Option | When to Use |
Contact a local IT/tech partner | Always the fastest on-site resolution — can often arrive within 60 minutes |
Call your hardware supplier | For physical device failures (terminals, printers, card readers) |
Contact your internet provider | If the outage is a network/connectivity issue |
Post-Recovery: When the System Comes Back Online
Do not skip this phase — this is where most restaurants lose revenue silently.
Immediate Steps
[ ] Verify the system loads fully and test a dummy transaction before resuming normal operation
[ ] Monitor the backend/dashboard to confirm all offline transactions have synced correctly
[ ] Cross-check any cloud-based offline queue to confirm no transactions were lost
Manual Reconciliation
[ ] Manually enter or ring up all handwritten paper tickets that were processed during downtime
[ ] Balance the cash drawer against all manual cash records
[ ] Match physical credit card terminal batch totals against POS software records
[ ] Flag any discrepancies to the manager immediately for investigation
Incident Documentation
Complete a short incident report immediately while details are fresh:
Field | What to Record |
Date & Time of failure | — |
Duration of downtime | — |
Error message/code | — |
Root cause (if confirmed) | — |
Steps taken to resolve. | — |
Who resolved it | — |
Estimated revenue impact | — |
Notes/follow-up needed | — |
Keep a running log of all POS incidents in a simple spreadsheet. Patterns (same error every Friday peak, same terminal always failing) reveal whether you have a hardware issue, a software bug, a network capacity problem, or a staff training gap — and let you fix it before the next crisis.
Prevention: Reduce the Chance of It Happening Again
Action | Frequency | Why It Matters |
Run staff "manual mode" drills | Monthly | Staff who have never done manual service panic under pressure |
Test your standalone card terminal | Weekly | Confirm it works independently of the POS before you need it |
Check router/modem firmware updates | Quarterly | Outdated firmware causes unexpected dropouts |
Confirm offline mode is enabled on your POS | Monthly | Many cloud POS systems require offline mode to be pre-activated |
Test the receipt printer paper levels | Daily pre-shift | Printer failures during downtime are entirely preventable |
Keep printed menu and price lists on hand | Always | Staff cannot quote prices confidently if everything lives only in the POS |
Maintain a UPS (uninterruptible power supply) | Install and inspect annually | Protects against power surges and short outages |
Schedule automatic data backups | Per your POS settings | Offline mode entries must sync — verify this happens automatically |
Review the incident log for patterns | Monthly | Recurring errors are the system warning you before a major failure |
Keep the vendor support number printed and posted | Always | Do not rely on staff to find it during a crisis |
Quick Reference Card — Post at Every Terminal
Print and laminate this section.
POS is down? Do this:
Stay calm. Announce manual mode.
Assign roles — orders/payments/system/customers.
Reboot terminal — unplug, wait 30 sec, restart
Check the internet — router lights, test on phone
Restart software — fully close, wait 30 sec, reopen
No fix in 5 minutes? → Go full manual, call support
Before calling support: note error code, time, and what triggered it
Support number: ____________________
Local tech partner: ____________________
When the system returns,: reconcile all manual tickets before the next service
This checklist is system-agnostic and applies to any cloud-based or locally-hosted POS environment. Adapt the payment handling section to match the specific card terminals and offline capabilities available at your location.