QR Code Ordering for Restaurants: Build Your Own vs Third-Party (Toast, Square, Bopple)

A five-location group signs up for a QR ordering plan at $49 per month per location, files it under "solved," and moves on. Six months later the finance lead pulls the real number. The base subscription was only the entry fee. The kitchen display app bills separately, per device. The kiosk app bills separately, per device. And every online order carries a payment processing fee of roughly 2.9% plus 30¢. Add it across five locations and a busy season, and the "cheap" platform quietly costs more over two years than a custom build would have cost once.

That is the decision this article is about. Not whether QR code ordering belongs in your restaurant — you have already made that call — but whether you should rent a packaged platform or build your own. The answer turns on three things most owners underestimate: transaction volume, how much non-standard logic your business actually needs, and how far ahead you plan. We will compare Toast, Square, and Bopple against a custom build across cost, vendor lock-in, and ROI, and give you a framework for deciding.

We hit this exact wall on a real project. When we designed the user flow for the restaurant aggregator Foodclick, part of the in-venue ordering logic could not be satisfied by any off-the-shelf platform — and that gap turned out to be the deciding factor. More on that below.

"Free" and "$49/month" are never the final figure. The real cost of a packaged QR ordering system lives in three places: the base subscription, the add-on apps you need to actually run service (kitchen display, kiosk), and the percentage each platform takes from every transaction. Here is how the three vendors line up.

1. Square publishes its rate card openly. Its restaurant plans run Free at $0 per location, Plus at $49 per month per location, and Premium at $149 per month per location, with in-person processing of 2.6% + 15¢, 2.5% + 15¢, and 2.4% + 15¢ respectively (verified on squareup.com, July 2026). Online payments are billed higher — 3.3% + 30¢ on Free and 2.9% + 30¢ on paid plans — and the Kitchen Display and Kiosk apps are separate line items charged per device.
2. Bopple is equally transparent. Its Storefront plan is free, the Online ordering plan is $49 per month and includes QR Code Table Ordering, with white-label web at an extra $99 per month and a white-label app bundle at $399 per month, after a 14-day free trial (verified on bopple.com, July 2026).
3. Toast is the one to treat with care. Toast's public site does not display a static rate card, so the numbers here — Quick Start Bundle free, Core from $69/month, Growth from $165/month with Toast Online Ordering bundled in, and no commission on orders placed through Toast's own online ordering — come from independent reviews rather than a figure we could confirm directly on Toast's pricing page. Verify them against a live quote at the moment you decide, because plan structures shift.

Every packaged platform makes money from the same thing: your growth and your desire to stand out. The base plan is priced to feel painless. The costs that scale are the ones tied to adding locations, adding devices, and putting your own brand in front of the guest. Each vendor locks you in a different way.

1. Toast runs a closed hardware ecosystem — the software is designed to work on Toast-approved equipment. That keeps the experience consistent, and it also means switching later involves the hardware, not just a subscription cancellation.
2. Square scales cost linearly with locations. At $49 or $149 per month per location, every new site adds the full subscription again, and the Kitchen Display and Kiosk apps are billed per device on top. A single café barely notices. A growing group feels it directly, because the model rewards the vendor precisely as you expand.
3. Bopple monetizes your brand. On the $49/month plan the guest orders inside Bopple's shared marketplace app, not inside an experience that looks like your restaurant. To get a branded web presence you pay the extra $99/month; for fully branded native iOS and Android apps, the $399/month bundle. Data ownership and brand experience become a function of which tier you are willing to fund.

QSR Digital Transformation: A Step-by-Step Guide

You can see exactly where QR ordering fits and what has to be in place before it pays off.

Read the article

Packaged platforms handle the typical ordering flow cleanly. The ceiling appears the moment your business needs a rule the platform was never built to express. None of that reflects badly on the vendors; a one-size product behaves exactly this way.

On Foodclick, the custom logic lived in the in-venue payment and check-splitting flow. After a guest scans the QR code inside the restaurant, the app unlocks the in-venue functionality — and for a group, the first person to scan becomes the session admin, choosing how the bill is divided and paid while everyone else scans the same code to see their own share on their phone. The set of payment methods shown adapts to the region and to the restaurant's POS system, and a guest can add a cashless tip routed directly to a specific waiter. None of the three vendors exposes session logic like this as a setting — a QR flow that has to know who scanned first, what region the guest is in, and which POS sits behind the check is business logic that has to be built from the ground up.

If you want the wider picture, here's how modern restaurant automation looks end to end, and the same build-vs-buy logic applies to physical self-ordering kiosks too.

The decision comes down to arithmetic and to whether you need logic the platform can't express. Start with our own published estimate for what a custom QR menu costs to build: a simple SaaS-style digital menu runs from $500 to $2,000, while a fully branded, integrated system with analytics and upselling runs $10,000 to $30,000. Those are one-time development figures, plus hosting and support — with no percentage skimmed from each transaction.

Now compare that against the packaged cost accumulated over one to two years. A five-location Square Plus setup is $49 × 5 = $245/month in base subscriptions before add-ons, roughly $2,940 a year, before KDS and kiosk devices and before the 2.9% + 30¢ on every online order. Push meaningful online volume through that and the two-year total moves into the same territory as a mid-range custom build — except the custom build stops charging you per transaction once it ships. Below a certain order volume and location count, buying wins on both cost and speed. Above it, or the day you need a rule the platform can't support, custom starts paying for itself.

Buying can also be the right call — and it would be dishonest to pretend otherwise. The fast-casual chain Pei Wei replaced an underperforming in-house online ordering setup with Olo's platform and, in a case Olo published itself, saw a 36% lift in digital sales and digital checks running 57% higher than in-store walk-ins. The takeaway is not "always build." It is that a well-run packaged platform can beat a weak custom build. Custom wins when it is the thing standing between you and logic the platform genuinely cannot deliver — not as a matter of pride. If you want to pressure-test the numbers, here's how to think about ROI on POS-related changes.

What Businesses Lose When They Skip the Discovery Phase

This piece documents what a proper discovery phase catches, and what skipping it quietly costs

Read the article

A custom QR ordering system is a well-understood integration project rather than a moonshot. The part teams most often underestimate is the connection to POS and KDS; the front end is the easy part.

For work at this class, our stack is Laravel, Node.js, and Golang on the backend, PostgreSQL and Redis for data and caching, and Docker and Kubernetes for infrastructure — the same stack behind our foodtech projects. Foodclick is our proof that this holds up in production: the QR-driven bill-splitting flow, the region-aware payment methods, and cashless tipping were all custom-built rather than configured from a template. If you are mapping where a custom system has to plug in, this breakdown of the full restaurant tech stack shows the connection points, and it is worth revisiting why the QR channel earns its place before you commit budget.

Red Flags When Hiring a FoodTech Dev Agency

These five red flags identify the wrong partner before you sign

Read the article