Guides

When the POS is down: a café's paper backup, offline mode and downtime checklist

Mays cover card: When the POS is down: a café's paper backup, offline mode and downtime checklist — Offline mode, a paper kit and a checklist the whole team knows

It happens on a Saturday at 9 a.m. The register spins, the card reader says it can't connect, and there are twelve people in line. What happens next depends on whether someone decided it in advance.

This is the sixth post in our series on setting up the tech for a new café. The POS post listed the questions to ask about offline mode, and the network post covered a backup internet connection. This one turns them into a plan your team can follow. For a power cut or a boil-water notice, see our power outage checklist; this post is about the systems.

CISA's advice for small businesses puts the goal in one line: "Consider including the ability to execute mission essential functions without access to critical assets or even internet access (e.g., shift to paper-based operations, radio communications, etc.)" (CISA: Secure your business).

Know which kind of "down" it is

Different failures need different responses:

What failed

What still works, usually

First step

Your internet

The POS in offline mode, if it's set up

Switch to the backup connection, if you have one

The POS company's service

Offline mode, if your POS supports it for this case

Check the vendor's status page

One device (a register or reader)

The other devices

Move to a spare

Card processing only

Cash, maybe offline card payments

Decide: offline cards or cash only

Power

Nothing without a battery

Follow the power outage checklist

Square's support center, for example, separates "Internet outage: Your Wi-Fi stops working or your ISP has a service issue" from "Square service disruption: Square's services are deprecated or down," and lets you choose how to take payments in each case (Square: Process offline payments). Toast's platform guide says that "After 40 seconds of offline activity, an offline banner appears on the Toast POS app and provides information on the cause of the disruption, what actions you can and cannot do, and resolution steps" (Toast: Offline mode overview). Teach your team to read that screen.

Before it happens: set up offline mode

Offline mode is a setting, and the defaults may not be what you want. Using Square as an example, its support center says:

  • "Offline payments will be automatically allowed on all your devices unless you opt out."
  • You can "Set your preferred max amount allowed per transaction for offline payments (between $1 and $50,000)."
  • Some payment types don't work offline: "EBT/SNAP, Afterpay, Cash App Pay, Square Gift Cards, Tap to Pay on iPhone and Android, and manually entered card numbers are not available with offline payments."
  • "You will not receive notifications for declined payments while processing offline payments," and "You're responsible for any expired, declined, or disputed payments accepted while taking offline payments."
  • Square suggests you "download the offline payments guide and share it with your employees."

Whatever your POS, find its offline settings and decide, on purpose:

  1. Do we take cards offline, or cash only? Offline cards keep the line moving, but you carry the risk of declines.
  2. What's the most we'll take on one offline card? A low limit caps your loss on a declined payment.
  3. Which devices can go offline? Check that every register and reader you use is supported.

The paper backup kit

Put these in one labeled box in the office, and check it every quarter:

  • A printed menu with prices, including modifiers, updated whenever prices change.
  • A calculator and your sales tax rate written on the lid.
  • Numbered order tickets or a duplicate pad, so the bar and the kitchen each get a copy.
  • Pens, a marker and tape.
  • A sign for the door and the counter: "Cash only for now" or "Card payments may be delayed".
  • The cash drawer key and a note of where the spare float is.
  • This week's schedule and the team's phone numbers, printed.
  • Support numbers: internet provider, POS company, card processor, with your account numbers.
  • The one-page network sheet from the network post.
  • A printed copy of the downtime checklist below.

One thing that never goes in the kit: a way to write down card numbers. Our card security post explains why. If cards can't be taken, it's cash only.

The downtime checklist

Print it, tape it inside the kit's lid, and walk the team through it once before opening.

  1. Confirm what's down. One device, the internet, or the POS service? Try a second device and the backup connection.
  2. The shift lead decides offline cards or cash only, within the limits you set in advance.
  3. Put the sign up and tell the line, calmly and once.
  4. Pause online ordering and delivery apps, so a pile of orders doesn't land all at once when the connection comes back.
  5. Write every sale on a numbered ticket: items, total, cash or offline card.
  6. Keep cash in the drawer, and don't make change from tips.
  7. Call the POS company or the internet provider, and write down the ticket number.
  8. Note the time it went down and the time it came back.

After it comes back

The cleanup matters as much as the outage:

  • Upload offline payments right away. Square, for example, says offline payments process when the device reconnects "within 24 hours (no later than 72 hours)," and that "uploading your offline payments within 24 hours is highly recommended to reduce your risk of chargebacks or card declines."
  • Check for declined offline payments in your POS reports.
  • Ring the paper tickets into the POS as cash sales, or record them the way your accountant prefers, so daily sales and inventory match.
  • Count and reconcile the drawer as usual. See cash handling and till reconciliation and the daily sales and cash report.
  • Turn online ordering back on.
  • Write down what happened and what you'd change in the plan.

Back up the files you can't lose

Most café data lives in cloud services now, but not all of it, and the cloud service isn't the only copy you should have. The FTC's basics: "Make it a habit to back up important files regularly. Save your backups in the cloud or on an external hard drive." Its advice on phishing adds: "Regularly back up your data and make sure those backups are not connected to the network" (FTC: Cybersecurity for Small Business). CISA's business guidance: "Have backups ready and test them regularly" (CISA: Secure your business).

What to back up in a café:

  • Recipes, SOPs and training material, if they live in documents on one computer.
  • An export of your POS menu and items, so you can rebuild them if you ever switch.
  • Employee files and contracts (kept private).
  • Accounting files and the documents your accountant needs.
  • Photos and brand files: logo, menu designs, social media photos.

Test one backup every few months: open a file from it and check it's the one you expect.

Practice once

Run a ten-minute drill before you open, and again a couple of times a year: "The register just went down. Go." Time how long it takes the team to find the kit, put the sign up and take the first paper order. Fix whatever slowed them down.

Where Mays fits

The Mays apps need an internet connection to clock in, complete tasks and send messages; there's no offline mode. If the café's internet is down, phones on mobile data can still use Mays, but a kiosk tablet that only has the café Wi-Fi can't. Plan for it:

  • Clock-ins on paper, then fixed in one place. Have staff write their start time on the paper sheet. Afterwards, a manager adds each missing punch under Scheduling → Time Clock with Add punch. It shows as Web (manual), and the employee gets a notification. See Timesheets and pay periods.
  • The schedule on paper. Print is in the schedule's tools menu, so the week's schedule can go in the kit every Monday. See Building the schedule.
  • The checklist in the app, too. Build the downtime checklist as a checklist template, so it's on everyone's phone once the connection is back (or on mobile data), and walk through it in training. See Creating a checklist template.
  • A record of the outage. Post it in the location's Logbook under Incidents, with the times and the support ticket number, and flag it for follow-up. See Manager logbook.
  • Sales catch up on their own. Mays's Square sync looks back two days, so offline payments uploaded within that window come into Mays by themselves. If they upload later, an admin can bring them in with Backfill payments on the Square card. See Connecting Square.

Decide it on a quiet day

Every decision on this page is easier on a Tuesday afternoon than with twelve people in line. Set up offline mode, pack the kit, print the checklist and practice once.

Start your free trial: 30 days, every module, no card needed. Want help building your downtime checklist? Book a walkthrough.