Cloud-based restaurant POS: what it is, what it costs, what happens offline
What a cloud-based restaurant POS is, what works when the internet drops, who carries the risk on offline card payments, costs and 15 questions to ask.
By the TablePort teamFacts checked 11 min read
It is 8:15 on a Friday, every table is full, and the Wi-Fi drops. What happens next depends on how your POS was built, not on the word "cloud" in the brochure.
A cloud-based restaurant POS keeps your menu, sales and reports on the vendor's servers and runs on tablets, phones or a browser instead of a server in your back office. You can check sales from anywhere and add a device in minutes. The trade-off is that it leans on the internet, so before you buy, check what still works offline: taking orders, sending tickets to the kitchen, card payments and closing the day.
This guide explains cloud and local POS, what really happens in an outage, how offline card payments work and who carries the risk, what a cloud POS costs, and 15 questions to ask any vendor.
Last checked: 4 November 2026.
What is a cloud-based restaurant POS?
A cloud-based POS is a register that keeps its data on the vendor's servers and runs on tablets or phones, while a traditional POS keeps its data on a server in the building. With a cloud POS, the tablets on your floor are windows into the vendor's system. Many cloud systems are really hybrids: the app keeps a working copy of the menu and open orders on each device and syncs with the cloud when it can.
| Local server POS | Cloud POS (online only) | Cloud POS with offline mode | |
|---|---|---|---|
| Where your data lives | A server in the building | The vendor's servers | The vendor's servers, with a copy on devices |
| Devices | Fixed terminals | Tablets, phones, browsers | Tablets and phones |
| Sales and reports from home | Only with remote access set up | Yes | Yes |
| Updates | Installed on site | Automatic | Automatic |
| Internet drops | Keeps running | Stops | Keeps taking orders, syncs later |
| Server or hardware fails | Your problem to fix | The vendor's problem | The vendor's problem |
| Upfront cost | Higher (server, terminals, install) | Lower | Lower |
So the useful question is what keeps working when the connection, or the vendor, has a bad night.
What happens to a cloud POS when the internet goes down?
When the internet goes down, a cloud POS with a real offline mode keeps taking orders and pauses anything that needs the vendor's servers. One without offline mode stops. There are two kinds of outage, and they need different plans:
- Your connection fails. The router dies or your provider has a fault. A backup connection, such as a cellular hotspot, can cover this.
- The vendor's platform fails. Your internet is fine but the POS servers are not. Only the system's design and the vendor's contract terms help here.
Offline modes vary a lot between vendors, so check each line of this table with every system you look at.
| Function | Keeps working offline if... | Usually pauses? |
|---|---|---|
| Taking orders | The app stores the menu and open orders on the device | No, with a true offline mode |
| Kitchen tickets and KDS | Printers and screens are reached over your local network | No, if routing stays local |
| Card payments | The reader and processor support offline (store and forward) | Often, or with limits |
| Online and delivery orders | Never; they arrive over the internet | Yes |
| Gift cards and loyalty lookups | Rarely; balances live on the server | Usually |
| Reports and menu changes | Rarely | Usually |
| Closing the day | Every device has synced | Until devices reconnect |
For how kitchen screens route tickets and what to keep as a paper backup, see kitchen display systems.
One trap: offline mode relies on the local network. If the router itself loses power, the tablets may not reach the kitchen printer either. Put the router and the printers' network switch on a small backup power supply.
Can a cloud POS take card payments offline?
Sometimes, but the risk moves to you. Offline card payments work by store and forward. The reader takes the card and the POS stores the payment on the device. Nothing is checked with the guest's bank until the connection returns and the payment is forwarded. If the bank then declines it, the guest has already left.
Stripe's documentation shows how one processor handles this. These are Stripe's rules for its own readers, not an industry standard. In its guide to collecting card payments while offline, Stripe says that "authorization is only attempted after connectivity is restored and the payment is forwarded" and that "you, as the user, assume all decline and tamper-related risks associated with an offline transaction." The same page sets out these rules:
- An offline maximum of 10,000 USD per transaction, plus controls your POS can use to require online payment above an amount you choose, or to stop offline payments once the stored total passes a limit.
- No swiped cards while offline, because magnetic stripe data is easy to spoof.
- No canceling or refunding an offline payment until it has been forwarded.
- Stored payments are lost if the app is reinstalled or its storage is cleared before they are forwarded.
- A reader of the same type must have connected online at that location, and had its software updated, within the last 30 days.
Other processors set their own limits and rules, and some do not offer offline card payments at all. Ask yours, in writing.
Worked example: setting your exposure. Say your average check is $60 and you cap offline card payments at $1,500 in total and $250 per check. These are hypothetical round numbers for the example, not anyone's rule or limit. That allows about 25 average checks before offline cards stop. A single declined $240 party check after the guests have left costs you the full $240. With caps in place, your worst night is a known figure. Without them, it is not.
During an outage, a simple house rule helps: for checks above your cap, ask for cash or wait for the connection to return before the guest leaves.
Do you need a card reader, or can you use Tap to Pay?
You can take contactless payments on a phone with Tap to Pay, but most restaurants still want at least one card reader for chip cards.
Tap to Pay on iPhone lets an iPhone accept contactless cards and digital wallets with no extra hardware. Apple lists the United States among its supported regions, and you get it through a payment provider that supports it, not directly from Apple. Apple says that "over two thirds of all credit and debit cards in the U.S." are contactless-enabled, and notes that some contactless cards may not be accepted and transaction limits may apply.
That leaves guests whose card is chip-only. A card reader takes chip, contactless and wallets, so most restaurants want at least one reader per section even if servers also use phones.
Phone-based tap to pay can have narrower offline support than a dedicated reader. In Stripe's offline documentation, for example, offline mode for Tap to Pay on iPhone is in private preview in the United States and takes only Visa, Mastercard, Discover and American Express contactless cards, and Tap to Pay on Android does not support offline mode. Other providers set their own rules, so ask about both.
Security (PCI DSS). If card data never touches your tablet or your Wi-Fi, your compliance scope is smaller. The PCI Security Standards Council says a PCI-listed point-to-point encryption solution "can significantly reduce" the requirements that apply to you, but "does not completely remove" them, and that the card brands decide whether a small merchant must validate compliance. Ask your POS vendor which self-assessment questionnaire you will complete and whether its reader solution is PCI-listed.
How much does a cloud restaurant POS cost?
A cloud POS costs a monthly software fee, hardware, card processing on every payment, and add-ons. Processing is often the largest of the four, so get every one in writing.
| Bucket | What it covers | Questions to ask |
|---|---|---|
| Software | Monthly fee per location, per device or per module | What is included? What costs extra (KDS, online ordering, loyalty)? |
| Hardware | Tablets, card readers, printers, cash drawers, kitchen screens | Buy, rent or lease? What happens to it if I cancel? |
| Payment processing | A percentage plus a fixed fee per card payment | Flat rate or interchange-plus? Is the rate fixed in the contract? |
| Add-ons and terms | Setup, training, integrations, contract length, early exit fees | What is the total for 12 months on my numbers? |
Processing. A flat rate charges one blended price per card payment. An interchange-plus rate passes through the card network's interchange fee and adds the processor's markup. Neither is always cheaper; it depends on your card mix and ticket size. Judge it by your effective rate: total processing fees divided by total card sales, from three recent statements.
Worked example. These statement numbers are hypothetical and rounded to show the math. They are not a typical rate. $500 in fees on $20,000 of card sales is an effective rate of 2.5%. Now see why the rate matters more than the software price. On $20,000 a month in card sales, every 0.1 percentage point is $20 a month, or $240 a year. A rate that is 0.3 points lower saves $720 a year, more than many small differences in software fees.
Hardware leases. A lease that runs for years can outlast your use of the POS and can cost more in total than buying or renting. Read whether the lease continues if you cancel the software.
If you are building an opening budget, the cost to open a restaurant guide puts these lines in context. If you are also choosing reservations, stock and scheduling, see restaurant management software.
15 questions to ask any cloud POS vendor
Ask each vendor the same list, and ask for the answers in writing.
OFFLINE
1. If the internet drops, can we keep taking orders on every device?
2. Do kitchen tickets and the KDS keep working on the local network?
3. Can we take card payments offline? With which readers?
4. What are the offline limits: per payment, and in total?
5. Who carries the loss if an offline payment is declined later?
6. What happens to stored payments if a tablet dies or is reset?
7. What stops working offline: online orders, gift cards, loyalty,
reports, menu changes?
8. What happens if your platform, not our internet, goes down?
PAYMENTS
9. Flat rate or interchange-plus? Is the rate fixed, and for how long?
10. Which PCI questionnaire will we complete? Is your reader solution
PCI-listed?
11. Do you support Tap to Pay, and which card readers?
COST AND TERMS
12. What is the monthly fee per location, per device and per module?
13. Is hardware bought, rented or leased, and what happens to it if
we cancel?
14. What is the contract length, notice period and exit fee?
15. Can we export our menu, sales and guest data when we leave?
How do you test offline mode before you sign?
Test offline mode by unplugging the internet during a demo or trial and running a real order from start to finish. Do it on a quiet afternoon:
- Open two orders on two different devices.
- Unplug the internet line from the router but leave the router on, so the local network still runs.
- Add items and fire them. Check that tickets print or appear on the kitchen screen.
- Take a test card payment and note what the screen says.
- Close one check and try a refund on it.
- Plug the internet back in and check that every order, payment and ticket synced, with no duplicates.
- Repeat with the router switched off to see what happens when the local network goes too.
Can TablePort handle this for you?
TablePort is a cloud POS built offline-first.
- Run it on supported iPads, Android tablets and phones (iOS 15.1+, Android 10+), after a compatibility check.
- Keep taking orders when the internet drops. They sync when it is back, and tickets for a printer that went offline print when it returns.
- Take cards through Stripe Terminal readers (Chipper 2X and Stripe M2) or Tap to Pay. The reader is a $12 monthly rental, not a multi-year lease.
- Pay month to month in US dollars, from $59 a month per location before sales tax. Cancellation takes effect at the end of the paid month, with no cancellation fee.
One limit: card payments during an outage depend on the reader. The staff POS falls back to Stripe's offline mode where the reader supports it, the kiosk needs a connection, and an offline payment can still be declined later. See POS.
Frequently asked questions
- What is the difference between a cloud POS and a traditional POS?
A traditional POS stores its data on a server in your building and runs on fixed terminals. A cloud POS stores data on the vendor's servers and runs on tablets, phones or browsers, so you can see sales from anywhere and updates install themselves. A cloud POS with an offline mode also keeps a working copy on each device for when the internet drops.
- Does a cloud-based POS work without internet?
It depends on the system. One with a true offline mode keeps taking orders and can send tickets to the kitchen over your local network, then syncs when the connection returns. Online orders, gift card and loyalty lookups and reports usually pause. Test it by unplugging the internet line in a demo.
- Can I take card payments when the Wi-Fi is down?
Only if your reader and processor support offline payments. These are stored and sent to the bank when the connection returns, and if the bank declines one then, the loss is usually yours. Ask for the per-payment and total offline limits, and set your own caps.
- Is a cloud POS cheaper than a traditional POS?
Usually it costs less upfront, because there is no server to buy or install, but you pay a monthly fee instead. Compare the 12-month total: software, hardware, processing and add-ons. Processing is often the largest line, so check your effective rate, not just the software price.
- Is a cloud POS secure?
It can be. The main protection for card data is a reader solution where card details are encrypted and never touch your tablet or Wi-Fi. Ask your vendor which PCI questionnaire you will complete and whether its reader solution is PCI-listed, and use separate staff logins with the right permissions.
