Simple Order Ready Notification: a QR Code and a Screen

🎯 What simple actually means here

Simple is not a feeling, it is a list of things that are absent. No purchase order. No installation. No app for the customer to download. No account for them to create. No integration with your till. No training beyond a sentence.

Measured that way, most paging setups are not simple at all. A coaster kit needs a purchase, a plug, a rack, a charging habit and a cleaning routine. Waitlist software needs an account, a subscription and a configuration afternoon.

The smallest thing that works is a printed code, a screen, and a phone that already exists.

• Nothing to buy before the first order.
• Nothing to install, on either side of the counter.
• No app store, and no account for the customer.
• No till integration, and no engineer visit.

⏱️ The whole setup, in ten minutes

Create the page with your business name and logo, and the QR code is generated. Print it, put it at eye level where orders are taken, and run one test order on a staff phone before service.

That is the entire process. If it takes longer than a coffee break, something has gone wrong.

1. 1Name and logoTwo fields. The customer sees your name when they scan, not a generic page.
2. 2Print the codeA4 at the ordering point, at eye level, not flat where a tray will cover it.
3. 3Test it yourselfScan, take a number, tap Ready, listen for the ring. Once is enough.
4. 4OpenOffer the scan first. Hand out a number by hand when someone prefers it.

📱 What the customer experiences

They point the camera at a code they have seen the shape of a hundred times, on menus, parking meters and tickets. A page opens with your name on it. They type a phone number and get a number back.

Then they put the phone away and forget about it, which is the best possible outcome. When the food is up, it rings and vibrates in their pocket. No notification to enable, no app asking for permissions.

• A familiar gesture, already learned elsewhere.
• Your name on the page, not a generic screen.
• A number on screen, so they know where they are in the queue.
• A ring and a vibration, wherever they chose to wait.

⚠️ The three ways simple goes wrong

Almost every failure comes from one of three places, and all three are fixed in a minute.

The poster is in the wrong place, usually flat on the counter where a tray covers it by mid-morning. The script is too long, so it gets dropped at the busiest time. Or the team has not been told they can hand out a number by hand, so somebody ends up in a pointless negotiation with a customer.

✨ Simple does not mean bare

Removing the hardware does not remove the useful parts. The counter screen still shows what is in progress and who has been called. Customers with no phone still get a number in one tap.

And because the customer typed their own number, a few things come free that a coaster could never do: a regular flagged on sight, a customer list you can export to CSV, a Google review request offered at the right moment, and a promo wheel to fill the wait.

None of it needs configuring. It is there when you want it and ignorable when you do not.

• A live order board, in the order things came in.
• A manual number for anyone without a phone.
• Regulars flagged with their visit count.
• A CSV export of the customer list.
• A review request and a promo wheel, both optional.

🏪 Who this is the right answer for

It suits anybody who wants the problem solved this week rather than after a procurement cycle: a bakery at lunch, a coffee shop, a food truck, a market stall, a staff canteen, a seasonal site that would rather not buy a fleet for ten weeks.

It is less of a fit where mobile reception is genuinely poor, or where most customers do not carry a smartphone. In both cases the fallback still works, but you will be handing out more numbers by hand than the system is designed for.

• A single counter with a short, sharp rush.
• A site with no space for a charging rack.
• A seasonal or pop-up operation.
• Anyone who wants to test paging before spending.

💪 Why simple survives a busy Saturday

Anything complicated gets abandoned at the peak, and the peak is the only time it mattered. That is the real test of a system, not whether it works on a quiet Tuesday when somebody has time to think about it.

A setup with one poster and one button passes that test because there is nothing in it to skip. There is no basket to keep stocked, no rack to keep loaded, no wipe to fit between customers, no count to do at the end. Under pressure, a system with four steps loses two of them. A system with one step keeps it.

The same logic applies to staffing. A new starter on their first Saturday can be told the whole thing in one sentence, and the worst mistake they can make is to hand out a number by hand, which is exactly what the fallback is for. Nothing they do can break the queue or lose an order.

That is worth more than any feature. A system that is used every time, by everyone, in the same way, beats a better system that gets used when the room is calm.

• One poster and one button, with nothing in it to skip.
• No basket to stock, no rack to load, no count at closing.
• A new starter is briefed in one sentence.
• The worst mistake available is the fallback itself.
• Used every time beats clever and used sometimes.

Frequently asked questions