When the POS cannot accept orders or payments, staff can use numbered paper tickets, an order log, a current printed menu, and management-approved payment methods. The manager should decide which services can continue, how many orders the kitchen can handle, and when to stop accepting new ones.
Prepare those decisions before an outage. A manual fallback does not depend on an offline feature working, and it should not assume a card terminal, online ordering channel, or kitchen display is available. Keep the plan with the supplies, and make sure each shift knows who is in charge.
Choose what stays open
Start with the failure, not the device. A screen may be on while payments fail, kitchen tickets stop printing, or orders from another channel no longer reach staff. Ask the manager to identify what is affected before choosing a response. If the situation is unclear, use the more limited plan until someone can verify the affected channels.
Write down management's approved choices for dine-in, pickup, delivery, and new online orders. For each, state whether staff may continue, must pause, or need manager approval. Include a capacity limit the kitchen can actually track on paper, such as a maximum number of open manual tickets. An open ticket is one that has been accepted but not yet handed to the guest or otherwise closed. It is not a count of physical tables or guest parties.
Hypothetical decision: A small restaurant approves dine-in and walk-in pickup during an outage, with no more than eight open manual tickets at once. It pauses new delivery orders and does not accept new online orders until a manager can verify where those orders are going. If eight tickets are open, the host asks the next party to wait; staff do not promise a pickup time until a slot is free. The manager may lower the limit if the kitchen falls behind.
List payment methods separately from service channels. For example, management might approve cash with a written receipt and a secure place for the cash. A separate card device should be used only if management has approved it and staff have confirmed it can process payments. If no approved method is available, tell guests before accepting an order. Do not write down card numbers, security codes, or other card credentials on a ticket.
Also decide who can authorize discounts, refunds, voids, and orders already in progress. If staff cannot confirm whether a guest has paid, they should ask the manager to investigate rather than charge again. Keep a way to contact the payment provider and other relevant support teams without relying on the affected POS.
Review the wider setup, too. Your restaurant POS hardware may include several devices with different failure points. Ask your provider what each device and order channel does when connectivity or power fails, and what staff must do when it returns. The paper plan should still work when those answers do not cover the actual outage.
Make a numbered order log staff can follow
Keep a bound log or a pre-numbered packet, duplicate tickets if available, pens, a printed menu, and a calculator in an accessible outage kit. Assign a number to every accepted manual order. Use that number on the kitchen copy, the front-of-house record, and any paper receipt so the pieces can be matched later.
Each entry should capture the time, staff identifier, service type, items, quantities, modifiers, approved prices, and order status. Record the amount due and payment status separately: unpaid, paid by an approved method, or needing manager review. Note an approved discount or change and who authorized it. Cross out an error with a single line and add the correction; do not make a ticket disappear.
Use the least guest information needed to hand over the order. A table number or pickup name may be enough. Avoid collecting contact details just because a paper form has a space for them. Keep completed records away from the public and follow the restaurant's established retention and secure-disposal rules.
Give the kitchen a clear copy rather than passing a verbal order through several people. Mark allergies and other critical preparation instructions prominently, then use the restaurant's normal confirmation procedure. If an instruction is unclear, the kitchen should stop and ask the server before preparing that item.
A change after the first ticket needs its own trail. Write the change and time on the log, mark the kitchen copy, and confirm that the cook received it. If food is already being prepared, the manager decides how to handle the change. Do not reuse a canceled ticket number; mark it canceled and retain it for reconciliation.
Put a one-page role card in the outage kit
The following role card uses the hypothetical restaurant and eight-open-ticket limit above. Adapt the roles to the people actually on each shift. One person may hold more than one role, but someone must own each handoff.
| Role | At the start | During service | Before recovery |
|---|---|---|---|
| Manager | Confirm affected functions; announce approved services and payments. | Track the eight-ticket limit; resolve exceptions and pause intake if needed. | Collect records and assign one person to reconcile. |
| Order taker | Get the numbered packet and printed menu. | Tell guests the limits; log each order and send the matching ticket to the kitchen. | Mark open, canceled, and handed-over orders. |
| Kitchen lead | Confirm how paper tickets will arrive. | Check ticket numbers and modifiers; report missing or unclear tickets. | Return tickets and flag food still in progress. |
| Payment lead | Confirm which approved payment methods work. | Record payment status against the ticket; refer uncertain payments to the manager. | Separate receipts and payment records for matching. |
The card gives each role a start, service, and recovery action. Put actual staff names or shift positions on the printed copy, along with the kit location and support contacts. The manager should announce when the plan begins and when it changes. A kitchen lead who notices missing tickets should notify the manager immediately, not wait for the system to return.
Use a short guest explanation at the door and before an order is taken: which services are open, which payment methods are accepted, and whether there is a wait. Give a realistic estimate only when the kitchen can support it. For orders placed before the outage, check the available records and ask the manager to resolve uncertainty; do not assume the guest's order or payment was captured.
Run a practice exercise before a busy shift using clearly marked fictional tickets and a mock payment record. The simulation must not send a guest message, take a real card payment, or dispatch a courier. Practice a modifier change, a canceled ticket, and a payment whose status is unknown. Separately, if management chooses a live service pilot, use the approved real-service process and monitor it; do not treat a simulation as proof that live payments or outside channels work.
Reconcile before returning to normal
When screens come back, do not immediately enter every paper ticket. First, the manager confirms which functions and channels have returned, tells the team who is responsible for recovery, and decides whether manual intake should continue briefly. Keep the two workflows clearly separated until staff can identify where each new order belongs.
- Collect and count. Gather the log, kitchen copies, paper receipts, cash records, and any approved payment-device records. Account for every ticket number, including canceled orders.
- Check open work. Match food still being prepared or awaiting pickup to its ticket. Tell the kitchen and front of house which orders remain active.
- Match before entering. Compare each manual ticket with available POS and channel records. Look for an existing entry or a payment that arrived after the initial failure. Flag uncertain matches for the manager.
- Enter only what is needed. Follow the provider's recovery instructions for orders that need to be recorded. Keep the manual number with the entry where the workflow allows, and mark the paper log once the match is complete.
- Resolve exceptions. Investigate duplicate entries, missing tickets, refunds, and uncertain payments. Do not charge a guest again simply to make records balance.
- Close the fallback. Confirm the count of unresolved items, secure the records, and tell staff when normal intake resumes. Assign an owner and follow-up time to anything still open.
Keep payment reconciliation distinct from order entry. A sale recorded in the POS, cash received, and a card payment record are different pieces of evidence. A matching order total alone does not prove that a card payment went through. If the payment status is unclear, use the provider's support process and the restaurant's approved guest-contact procedure.
Afterward, note where the plan slowed down: perhaps tickets reached the kitchen but changes did not, or the manager had no reliable count of open orders. Replace used supplies and revise the role card before the next shift. Consider how your restaurant management software and other order channels fit the procedure, including who checks each source during recovery.
Next step: Bring your service limits, payment choices, and recovery questions to a POS provider. Ask how its system handles interrupted orders and what records staff can use afterward. You can also discuss the plan with Fleksa through its restaurant POS team.
Frequently asked questions
Can a restaurant take card payments during a POS outage?
Only use a method management has approved and staff have confirmed is working. A POS outage does not establish whether a separate card device can process a payment. If payment status is uncertain, ask the manager to investigate before charging again.
What should a manual order ticket include?
Include a unique number, time, staff identifier, service type, items, quantities, modifiers, prices, and order status. Record payment status separately and collect only the guest information needed to complete the order.
When should staff stop taking manual orders?
Stop or pause when the approved open-ticket limit is reached, the kitchen cannot track orders safely, or no approved payment method is available. The manager should communicate the decision to both staff and guests.
