QR menu and POS integration: how it works

A guest at table 9 orders two shawarma plates, one with no garlic sauce, and a mango juice from their phone. In a well-connected setup that order appears on the kitchen screen and on the cashier's bill for table 9 at the same moment, and at the end of the night it shows up in your sales report without anyone typing it. In a disconnected setup, a waiter reads it off a tablet and re-enters it into the POS, and "no garlic" has a decent chance of getting lost on the way.

"POS integration" is the name for the difference between those two nights. Vendors use it loosely, so this guide explains what it really means, the three setups you will find in practice, where each one breaks, and the questions to ask before you pay for anything.

1The three levels of "integrated"

When a sales page says its QR menu "integrates with your POS", it could mean any of these:

Level	How a QR order reaches the POS	Who maintains the menu	Typical pain
1. Side by side	Staff re-enter it by hand	Twice: once in the QR menu, once in the POS	Typing errors, missed items, prices out of sync
2. Connected	Pushed automatically through a connector or API	Usually the POS, synced to the menu	Mapping errors on modifiers, sync delays, two vendors blaming each other
3. One system	There is no transfer; the menu, orders and POS share one database	Once	You are tied to one vendor's POS features

Level 1 is not integration at all, but it is how a lot of restaurants actually run. It is acceptable if QR orders are a small share of your sales and you have spare hands at the till. Once QR orders are a real part of a busy night, the re-keying becomes a job in itself.

2Follow one order through the system

The quickest way to judge any setup is to trace a single order and ask what happens at each step.

1. Scan. The QR code on the table should tell the system which table the guest is at. If it is one generic code for the whole restaurant, the guest has to type a table number, and some will get it wrong.
2. Build the order. The guest picks items and modifiers (size, extra cheese, no onions). Those modifiers must exist in the POS in the same shape, or the kitchen gets a ticket that says "Burger" with the important part missing.
3. Send. The order goes to the kitchen and to the table's open bill. If the guest orders a second round later, it should add to the same bill, not open a new one.
4. Cook. The kitchen marks it preparing and ready. Ideally the guest sees that status too, which cuts "where is my food?" questions.
5. Pay. The cashier closes the bill with tax, service charge and payment method, whether cash, card or a wallet transfer.
6. Report. The sale lands in your end-of-day numbers, tagged as a QR order, so you can see how much the channel actually brings in.

Every hand-off between two systems is a place for something to go wrong. In a Level 2 setup there are usually three hand-offs to test: menu sync, order push and payment status back to the menu.

3Where connected setups usually break

These are the failure points to test in a demo, not take on trust.

Modifiers and combos

A POS might model "Meal: burger + fries + drink" as one item with choices, while the QR menu treats it as three items. If the two do not map cleanly, you get wrong prices or kitchen tickets that lose the choices. Ask the vendor to show a real item from your menu with its modifiers going end to end.

Price changes

With food costs moving often, you may update prices every few weeks. In a connected setup, check which system is the master and how fast a change reaches the other. If a guest sees EGP 180 on the QR menu and the POS charges EGP 210, the argument happens at your table, not the vendor's.

Sold-out items

When the kitchen runs out of something, it has to disappear from the QR menu straight away. If marking it out in the POS does not update the menu, you will keep taking orders you cannot cook. The guide to handling 86'd items covers the service side of this.

Internet drops

Ask what happens to an order placed while the restaurant's connection is down for five minutes. Does it queue and arrive late, get lost, or duplicate when the connection returns?

4Taxes, service charge and receipts

Egyptian bills usually carry VAT and often a service charge, and they need to be calculated the same way whether the order came from a waiter or a QR code. Check three things:

• The QR menu shows prices the way you want guests to read them (inclusive or with charges added at the end), and the POS bill matches.
• Service charge applies only where you intend it to, for example dine-in but not takeaway.
• Your receipt meets your obligations. If your business falls under the Egyptian Tax Authority's e-receipt requirements, confirm with your accountant which system must issue the receipt and whether your POS supports it. A QR menu on its own is not a fiscal receipt system.

5Standalone QR menu or integrated setup: how to decide

Integration is not always worth the cost or the lock-in. Use these rules of thumb:

• Menu only, no ordering from the table? You do not need POS integration. A display menu with good analytics is enough.
• Table ordering but a small room, and you are happy for staff to confirm each order? An orders dashboard where staff accept QR orders and ring them up can work for a while.
• Busy dine-in service with QR ordering? Pay for Level 2 or Level 3. The labour and error cost of re-keying grows with every order.
• Already locked into a POS you cannot leave (hotel property systems, a chain-wide contract)? Look for a QR menu with a tested connector to that exact POS, and ask for another restaurant using it that you can call.
• Choosing a POS from scratch? A single system that includes both usually costs less to run and has fewer failure points, as long as its POS features cover what you need.

If you are replacing an older till, this POS migration guide covers the practical steps, and this overview of POS alternatives compares the broader options.

6What Menyo does and does not do

Menyo is a Level 3 setup: the menu, table QR orders, POS and kitchen display share one system. On the Growth plan ($49/month) guests can order from the table and staff see and manage those orders. The staff POS and the kitchen display system are on Professional ($99/month) and above. There, QR orders and orders rung up at the till land on the same kitchen board, staff can add items to an open table bill, tax and service charges are applied from your settings, and sales reports split revenue by source (POS or guest QR) with CSV export.

What it does not do: it does not advertise ready-made connectors to other POS brands. API access is on the Enterprise plan ($199/month) if you have a developer who wants to build a link to another system. Guest orders are paid at the till or in cash rather than by online card payment in the ordering flow. If you have to keep an existing POS, weigh that honestly.

7Questions to ask before you buy

• Show me one of my real items with modifiers going from the QR menu to the kitchen and the bill.
• Which system is the master for items and prices, and how fast do changes sync?
• Does a second round from the same table add to the same bill?
• What happens to an order placed during an internet outage?
• Can I see QR orders separately from staff orders in sales reports?
• How are VAT and service charge calculated, and does the receipt meet my obligations?
• Who do I call when an order goes missing, and what are their hours?
• Can I export my menu and sales data if I leave?

8Frequently asked questions

Can a QR menu work without any POS?

Yes. Many cafés and small restaurants use a QR menu for display only and take payment at the counter as before. Integration only matters once guests order from the table.

Is an API the same as an integration?

No. An API means a developer can build a connection. An integration means someone already has, tested it and supports it. If a vendor says "we have an API", ask who will build and maintain the link to your POS, and at whose cost.

Will POS integration stop all order errors?

It removes re-keying errors and lost tickets. It does not stop a guest choosing the wrong item or a cook misreading a ticket. Clear item names and well-built modifiers still matter; see how to set up modifiers.

Do I need a kitchen display to benefit from integration?

Not strictly, since orders can print to a kitchen printer. But a screen shows order status in both directions, which is where much of the time saving comes from.

9The short version

Integration means an order is entered once and flows to the kitchen, the bill and the report without being retyped. Know which level you are buying, test modifiers, price sync and sold-out items in a demo, and get clear answers on support before you sign.

If you want the menu, table orders, POS and kitchen screen as one system, start with Menyo and compare plans on the pricing page.