Square for Restaurants: The 5 Things They Don't Tell You

November 19, 2026
Square for Restaurants: The 5 Things They Don't Tell You

Square for Restaurants: The 5 Things They Don't Tell You

The first time I sat through a Square for Restaurants demo, I was sold. The rep was sharp, the dashboard was clean, and the pitch was exactly what a tired operator wants to hear: one system, one rate, everything connected. Eighteen months and one very bad Friday later, I understood why three of my friends had quietly moved off it.

This is not a hit piece. Square is a real company with a real product, and for some businesses — a coffee counter doing 200 tickets a day, a single-location retail shop — it is genuinely fine. But if you run a full-service restaurant with a floor plan, a weekend rush and a staff that turns over twice a year, the gap between the demo and the invoice gets wide. Here are five things that never made it into the slide deck.

1. The "simple" pricing has layers

Square advertises 2.6% + 10¢ per transaction. That number is real — for swiped, dipped and tapped cards on a standard plan. Everything else lives in the footnotes.

Keyed-in payments — the ones your staff types when a chip will not read, or when a guest calls in a takeout order — run 3.5% + 15¢. International cards run closer to 4%. A chargeback costs $15 whether you win it or not. And if you want same-day access to your own money instead of waiting one to three business days for an ACH transfer, instant transfers cost 1.5%.

On $80,000 a month in card volume, with a normal 12% of tickets keyed in, that spread is roughly $105 a month in card fees alone — before chargebacks and before the 1.5% you would pay to get your money a day sooner. It is not a scandal. It is just not the number on the poster.

2. Customer support is email-first

Ask any operator what actually breaks the relationship and you will hear the same story. The terminal freezes at 7:40 on a Saturday. The card reader will not pair. The kitchen printer stops mid-service. You open a ticket. A template reply asks you to restart the device. You reply. Somebody answers on Monday.

Square's support model is built for scale, and scale means email queues and community forums for most accounts, with phone support reserved for narrow situations and higher tiers. For a retail shop, that is an inconvenience. For a restaurant, it is a line at the door and a dining room watching you apologize. Four hours of downtime on a Friday does not cost four hours of labor — it costs the covers you did not turn and the reviews you will read on Monday.

One Austin operator I know keeps a backup terminal in the trunk of his car. Not because he is paranoid. Because he has been through a Saturday.

3. Table management is basic

The product is literally called Square for Restaurants, so you would expect the floor to be the center of it. In practice you can assign a table to an order, and that is roughly where the native capability stops. Floor plan customization is limited. Waitlist management is not built in. Server rotation, sections, coursing, and the ability to see at a glance which of your 22 tables is on dessert and which is waiting for a check — those require third-party add-ons or a workaround your manager invents at 6 p.m. on a Friday.

If your model is counter service, this does not matter. If you seat people and expect them to stay 70 minutes, it matters every single night.

4. Offline mode is unreliable

Every cloud POS advertises offline mode, and what that means varies wildly. Square's version lets you keep swiping cards when the connection drops — but chip and contactless stop working. In 2026, that is most of your transactions. The practical result is that an internet outage turns a modern restaurant into a cash-only restaurant, and half your guests no longer carry cash.

At one Denver concept, a 40-minute ISP outage during a Friday dinner service cost the bar about $2,100 in card sales that simply walked out the door. The POS did exactly what it was designed to do. It just was not designed for that.

5. Upgrade paths cost more than starting over

This is the one that stings longest. The base product is affordable. Then the features you actually need to run a real restaurant arrive as separate line items. Multi-location reporting? That is Square for Restaurants Plus, about $60 a month per location on top of processing. Loyalty that is more than a punch card? Add-on. Advanced inventory and recipe costing? Different tier. Scheduling and tip pooling? Another module.

Three locations, loyalty, inventory and scheduling later, the free software you signed up for is a $300-plus monthly line item — and you still pay the processing spread on top. The pricing page is not dishonest. It is simply organized around the entry price instead of the steady state.

What the demo never shows: three years of it

Here is the version of the math I wish someone had shown me. One restaurant, $85,000 a month in card volume, 4,000 tickets, 22 tables.

Card processing at the headline rate: about $2,210 a month, or roughly $26,500 a year. Add keyed-in volume, a handful of chargebacks, and the 1.5% instant transfer fee in the weeks you needed cash before payroll, and realistic annual processing lands nearer $29,000.

Software: base plan free, Plus for multi-location reporting at $60, add-ons for loyalty and inventory — roughly $1,800 to $2,400 a year. Hardware: two terminals, a kitchen display, a reader and a stand, amortized over three years, another $1,500 a year.

Total cost of ownership: somewhere between $32,000 and $33,000 a year. None of those numbers is outrageous on its own. Together they are the reason "cheap POS" and "cheap to run" are two different sentences.

Where a focused tool wins

QRfood does not do everything Square does, and I would be lying if I said otherwise. We do not process your payments, we do not run payroll, and we are not trying to be your business bank.

What we do is the part that touches the guest: a QR menu that opens in the browser with no app to download, updates in real time across every language and every location, and lets a table order and reorder without flagging down a server. Pricing is flat and published, and it does not move when you add a second location. Onboarding is one afternoon, not a project plan. And when something breaks at 7:40 on a Saturday, a human answers.

For 500+ restaurants in Japan and a growing number in the US, that focus is the point. You keep your POS for money. You use QRfood for the menu, the guest experience, and the 40 seconds between "we are ready" and "the order is in the kitchen."

A checklist before you sign anything

• Ask for the all-in rate, not the headline rate — including keyed-in, international, chargebacks and instant transfers.

• Ask what happens when your internet dies at 7 p.m., and get the answer in writing.

• Ask which features require an add-on, and price the version of the product you will need in year two, not year one.

• Ask how support works on a Saturday night, and whether you get an actual phone number.

• Ask whether the software charges per location, and what the bill looks like at location three.

The honest bottom line

Square for Restaurants is a competent product built for the middle of the market, priced to win the first comparison. That is a legitimate strategy. It is just not the same thing as being cheap to own.

If you are signing a POS contract this quarter, do the three-year math, write down the five things that would ruin a Friday, and ask about each one. The answers you get in the demo are the cheapest part of the decision. The invoice is what you live with.

Get the features you actually need without the surprises. Try QRfood free at qrfood.ai — no card required, no per-location fee, and a real person on the other end.