A practical step-by-step guide for restaurant managers and staff when the point of sale system goes down during service
Overview
A POS system failure during service is one of the most disruptive operational emergencies a restaurant can face. This SOP gives every team member a clear, confident action plan to keep service running, protect revenue, maintain guest satisfaction, and recover quickly — with or without technical support.
This document applies to all restaurant types and sizes, across all markets globally.
Section 1: Immediate Response — First 2 Minutes
Speed and calm leadership in the first two minutes determine how well your team and guests handle the rest of the outage. Do not wait to confirm the cause before activating this SOP.
Manager / Shift Leader: First Actions
Priority | Action | Notes |
1 | Stay calm — your team takes its cue from you | Visible panic spreads instantly |
2 | Announce to all staff: "POS is down — switching to manual procedures now." | Use a clear, confident tone |
3 | Assign emergency roles immediately (see Section 2) | Do not delay role assignment |
4 | Brief each team area with their specific instruction | FOH, BOH, and Host separately |
5 | Begin the outage master log — note exact time of failure | Critical for reconciliation later |
6 | Attempt basic technical restart while manual procedures begin | Do not halt service to troubleshoot |
Team Briefing by Area
Team | What to Say | What to Do |
Front of House | "We are handling this professionally — guests come first, keep serving." | Switch to manual order pads immediately |
Back of House / Kitchen | "Continue as normal — handwritten tickets are coming." | Acknowledge each ticket verbally |
Host Stand | "Seat guests normally, but let them know there may be a slight delay." | Do not stop seating guests |
Bar | "Continue making drinks — note all orders manually on your pad." | Start a manual drinks log by table number |
Section 2: Emergency Role Assignments
Assign these roles within the first two minutes. In smaller teams, one person may cover more than one role.
Role | Assigned To | Responsibilities |
Overall Coordinator | Manager / Shift Leader | Coordinates all teams, handles escalated guest concerns, monitors cash security, and contacts POS support |
Order Coordinator | Senior FOH staff member | Collects all handwritten orders, assigns sequential order numbers, distributes to the kitchen, and maintains the master order log |
Kitchen Expediter | Head chef or senior cook | Confirms receipt of each ticket, ensures clarity with cooks, and communicates hold and completion times to FOH |
Payment Handler | Trusted senior staff member | Processes all cash and mobile payments, maintains the payment log, and secures card details if collected |
Guest Relations | Floor manager or senior server | Proactively communicates with guests, manages expectations, and delivers complimentary offerings where appropriate. |
Section 3: Manual Order Taking Procedures
Required Emergency Materials — Keep These Stocked at All Times
Item | Location | Quantity Recommended |
Pre-printed manual order pads | Every server station | Minimum 50 pads per station |
Carbon copy / duplicate order books | Manager's office backup | 2 books per station |
Calculators | Each station and bar | 1 per station + 2 spares |
Pens | Every station | Minimum 10 per station |
Guest check presenters | Server stations | 1 per table in the venue |
Table number cards | Host stand | Full set always available |
Stapler and spare staples | Order coordinator station | For attaching order copies |
Printed menu with prices | Every station and bar | Current version, updated for each service |
Manual Order Form — Required Information
Every order taken during a POS outage must include all of the following:
Field | Example | Why It Matters |
Sequential order number | #0047 | Tracks all orders; prevents loss |
Table number | Table 12 | Links to payment |
Server name or initials | JM | Accountability and tip tracking |
Time order was taken | 19:42 | Supports reconciliation |
Guest count | 4 guests | Helps kitchen plan covers |
Each item ordered | Grilled salmon, medium | Accuracy for the kitchen |
Modifications | No cream sauce | Allergy and preference management |
Estimated bill total | ±$85 | Prepares guests for payment |
Order Copy Distribution
Copy | Goes To | Purpose |
Original (white) | Kitchen | Cooking instruction |
Duplicate (yellow) | Server | Personal tracking and billing reference |
Triplicate (pink) | Order Coordinator | Master log and reconciliation |
Section 4: Kitchen Communication During Outage
Ticket Handoff Protocol
Step | Action | Responsible |
1 | Server writes order clearly — print, do not use cursive | Server |
2 | The server calls out the order number verbally when handing it to the expo | Server |
3 | Expo reads back the order to confirm accuracy | Expediter |
4 | Any unclear items are clarified immediately — never assumed | Expediter / Server |
5 | Estimated cook times are communicated back to the server | Expediter |
6 | Kitchen calls out when order is ready — use order number, not table name | Kitchen |
Kitchen Workflow Adjustments
Situation | Action |
The ticket is illegible | Return immediately to the server for rewrite — do not guess |
Two orders arrive simultaneously | Process in sequential number order |
Hold is needed | Expediter communicates hold time to FOH within 2 minutes |
Order error discovered after cooking | Manager is notified immediately — do not serve the incorrect dish |
Section 5: Payment Processing During Outage
Payment Method Priority Order
Priority | Method | When to Use | Notes |
1st | Mobile payment apps on cellular data | Always try first | Square, iZettle, SumUp, Yoco, or equivalent in your market |
2nd | Staff smartphones with payment apps | If dedicated readers unavailable | Ensure staff devices are charged pre-service |
3rd | Cash | Reliable fallback in all markets | Ensure adequate change in the cash drawer before every service |
4th | Card detail collection | Last resort only | Only with secure storage, explicit guest consent, and immediate processing on recovery |
Payment Security Rules — Non-Negotiable
Rule | Detail |
All large cash transactions require a witness | Minimum two staff members present |
A written receipt must be given for every transaction | Handwritten is acceptable |
Card details must never be left unattended | Store in a sealed envelope in the safe |
The manager must approve any complimentary adjustments | No unauthorized comps |
All payment logs must match order logs | Cross-check before the end of service |
Payment Log — Required Fields
Field | Example |
Order number | #0047 |
Table number | Table 12 |
Bill total | $87.50 |
Payment method | Cash |
Amount received | $100.00 |
Change given | $12.50 |
Server name | J. Mokoena |
Time processed | 20:15 |
Manager initials | RM |
Section 6: Guest Communication Scripts
Adapt the language below to suit your restaurant's tone and the local culture of your market. The goal is to be warm, transparent, and reassuring — never defensive or dismissive.
Situation | Suggested Script |
Initial announcement at the table | "Good evening. I wanted to let you know that we're experiencing a brief technical issue with our ordering system. We're handling everything manually tonight, which may add a few minutes to your experience, but our kitchen is fully operational, and we're committed to taking great care of you. Thank you for your patience." |
The guest asks how long it will take. | "We're working to resolve it as quickly as possible. In the meantime, your meal is being prepared exactly as normal, and we will have your bill ready when you're finished." |
The guest is frustrated about the wait. | "I completely understand, and I apologize for the inconvenience. We'd like to offer you [a complimentary drink / a discount on your bill tonight] as a thank-you for your patience." |
At the bill presentation | "For payment this evening, we can accept cash or process your card through our mobile system. As a thank-you for bearing with us, we'd like to offer you [specific comp]." |
The guest asks if their order is correct. | "Absolutely — let me read back your order to you to confirm everything is right before I send it to the kitchen." |
Section 7: Technical Recovery Steps
Run these steps in parallel with manual service — do not halt the dining room to troubleshoot.
Step-by-Step Restart Sequence
Step | Action | Time Target |
1 | Check all physical cable connections to the POS terminals and the router | 1 minute |
2 | Power cycle the POS terminals — switch off, wait 30 seconds, restart | 2 minutes |
3 | Restart the network router and modem | 3 minutes |
4 | Test internet connectivity on a mobile device | 1 minute |
5 | Test one POS terminal before declaring recovery | 2 minutes |
6 | If no recovery, call the POS provider's emergency support line | Within 10 minutes of failure |
7 | Document all error codes and messages shown on screen | Ongoing |
Support Contact Protocol
Contact | Information Needed | When to Call |
POS provider emergency line | Account number, site ID, error codes | Within 10 minutes of failure |
IT support | Network details, error messages, router model | If the network is the cause |
Internet/network provider | Account number, location details | If the internet outage is confirmed |
General Manager / Owner | Brief update on the situation | If the outage exceeds 20 minutes |
Emergency Contacts — Complete Before Posting This SOP
Contact | Name | Phone Number |
POS System Emergency Support | ||
IT Support | ||
Network / Internet Provider | ||
General Manager | ||
Owner / Director | ||
Nearest equipment supplier |
Section 8: System Recovery Procedure
When the system comes back online, do not rush. A disorganized recovery creates more errors than the outage itself.
Recovery Checklist
Step | Action | Completed |
1 | Test all functions on a single terminal before announcing recovery | ☐ |
2 | Process a test transaction to verify payment connectivity | ☐ |
3 | Confirm the kitchen printer is connected and printing | ☐ |
4 | Confirm all stations are synchronized and showing correct data | ☐ |
5 | Announce system recovery clearly to all staff | ☐ |
6 | Enter all manual orders into the POS immediately | ☐ |
7 | Process any deferred card payments with guest permission | ☐ |
8 | Cross-reference the manual payment log against POS totals | ☐ |
9 | Identify and resolve any discrepancies before the end of service | ☐ |
10 | Update the daily sales report to reflect the outage period | ☐ |
Section 9: Documentation And Logging
Outage Master Log — Complete in Real Time
Field | Record |
Outage start time | |
Outage end time | |
Total duration | |
Number of tables affected | |
Total manual orders taken | |
Total revenue processed manually. | |
Payment methods used | |
Comps offered and value | |
Guest complaints received | |
Staff on duty | |
Manager on duty |
Post-Incident Report — Complete Within 24 Hours
Section | Detail to Include |
Timeline of events | Exact times from failure to full recovery |
Root cause (if known) | Technical fault, network outage, hardware failure, etc. |
Actions taken | What worked, what did not |
Guest impact | Complaints, comps, lost covers |
Revenue impact | Estimated loss or delay |
Staff performance | Who performed well, who needs additional training |
Preventative recommendation | What should change to avoid recurrence |
Follow-up required | Outstanding tasks, equipment replacements, and retraining |
Section 10: Prevention And Preparedness
Daily Pre-Service Checklist
Item | Check | Notes |
Manual order pads are stocked at all stations | ☐ | |
Calculators are present, and batteries are working. | ☐ | |
Minimum 10 pens per station | ☐ | |
Mobile payment devices are fully charged. | ☐ | |
Cash drawer stocked with adequate change | ☐ | |
Emergency contact list posted at the manager's station | ☐ | |
Printed menus with current prices available | ☐ | |
The POS system is functioning and synchronized. | ☐ |
Weekly Maintenance Checklist
Task | Responsible | Completed |
Test all backup payment systems | Manager | ☐ |
Review emergency procedures at the team briefing | Manager | ☐ |
Check that mobile payment app accounts are active | Manager | ☐ |
Update the emergency contact list if any changes | Manager | ☐ |
Verify the network backup or mobile data solution is working | IT / Manager | ☐ |
Monthly Review Checklist
Task | Responsible | Completed |
Full review of this SOP — update if needed | General Manager | ☐ |
Staff roles are reviewed and reassigned if the team has changed | Manager | ☐ |
All backup equipment tested | Manager / IT | ☐ |
Previous incidents reviewed for lessons learned | General Manager | ☐ |
Training materials updated | Manager | ☐ |
Section 11: Staff Training Requirements
Monthly Training Topics
Topic | Format | Duration |
Manual order taking — handwriting speed and accuracy | Timed practice drill | 15 minutes |
Bill calculation without POS | Calculator exercise with real menu prices | 10 minutes |
Guest communication during outage | Role-play scenarios | 15 minutes |
Emergency role assignments | Role review and confirmation | 5 minutes |
Mobile payment device operation | Hands-on practice | 10 minutes |
Quarterly Full Simulation Drill
Run a complete POS-down simulation during a quiet service or pre-service period once every quarter. The goal is muscle memory — when it happens for real, your team should not have to think.
Drill Element | Success Measure |
Full manual order taking for 10 tables | All orders accurate, legible, and correctly distributed |
Bill calculation under time pressure | No errors on final guest totals |
Guest communication role play | Guests express satisfaction despite the situation |
Mobile and cash payment processing | All transactions logged correctly |
Recovery and reconciliation | Manual log matches simulated POS data |
Section 12: Success Metrics
Service Standards to Maintain During Any Outage
Metric | Target |
Order accuracy | Above 95% |
Increase in guest wait time | Less than 15 minutes above normal |
Payment security | 100% — no exceptions |
Guest satisfaction | Maintained at normal levels through proactive communication |
Staff composure | Calm and professional throughout |
Recovery Time Benchmarks
Milestone | Target Time |
Initial diagnosis attempted | Within 5 minutes of failure |
POS support contacted | Within 10 minutes of failure |
Full system recovery | Target within 30 minutes |
All manual orders entered into the POS | Within 1 hour of recovery |
Post-incident report completed | Within 24 hours |
Document Version: 2.0 | Last Updated: _____________ | Next Review: _____________ | Approved By: _____________
This SOP should be reviewed monthly, updated after every incident, and adapted to reflect your specific market, payment environment, and team structure. Print and laminate a condensed version for posting at each manager station.