Start with the service you can actually deliver
A direct ordering channel should make your existing service easier to understand, not create a second restaurant inside the first one. Decide whether guests will order drinks, complete meals, or additional items after a server greets them. Write down when ordering is available and who answers questions. A small, well-supported rollout is more useful than opening every possible channel during your busiest dinner service without anyone assigned to watch it.
Think about the guest's entire journey: finding the menu, selecting food, submitting a request, receiving confirmation, and paying. Those are separate moments. A QR scan does not mean an order exists, and a submitted request does not mean the kitchen has accepted it. Explain that distinction in everyday language so guests know when to wait, when to ask a server, and what happens next.
Understand what commission-free means
Commission-free ordering describes a different commercial arrangement from a marketplace that takes a percentage of each sale. It does not mean operating a restaurant costs nothing. You still have software subscriptions, staff time, food costs, printing, and whatever charges apply to your own payment arrangements. Compare those categories separately rather than treating every expense as a commission or promising that a new channel will automatically increase profit.
QR Code + Pages offers restaurant ordering through its Pro and Tables packages, billed annually per restaurant. Pro is $199 USD per year; Tables is $299 USD per year. Guests pay in person at the restaurant, not through an online checkout in QRP. The software subscription is separate from the guest's food bill. Build your decision around the workflow you need, and confirm the package details before purchasing.
Choose WhatsApp or panel orders deliberately
WhatsApp can suit a team that already handles guest messages reliably. The important part is assigning responsibility to a person on each shift, not assuming everyone will notice a notification. Check that the restaurant's configured number is correct and that the staff responsible for responding can access it. Run a complete test with a guest phone rather than relying only on what the menu looks like in your own account.
Pro and Tables also support orders through the account's orders panel. Choose a process staff can monitor consistently and explain how requests reach the person preparing food. Do not assume the panel replaces your existing point-of-sale or kitchen workflow. Restaurant ordering starts disabled until the restaurant enables and configures it. Finish the operational decisions before switching it on, and avoid leaving an unattended ordering channel available to guests.
Make WhatsApp submission unmistakable
A prepared WhatsApp message is not a delivered order. The guest must send that message inside WhatsApp. Opening the app, reading the draft, or returning to the menu does not complete that step. Teach servers to explain it briefly, especially when helping someone who does not use WhatsApp often. Guests should also understand that sending a request is not the same as receiving the restaurant's confirmation.
Agree on a short confirmation routine: review the requested items, verify availability, clarify any questions, and tell the guest whether the restaurant accepts the order. Resolve substitutions before preparation rather than silently changing the request. If a guest sends a second message, determine whether it adds items or replaces the first request. The goal is a reliable conversation, not a pile of messages that different employees interpret differently during a rush.
Match table identification to your plan
A shared menu QR can sit on every table without identifying any particular table. If your workflow needs individual table QR codes, Tables is the relevant package; Pro includes ordering but not individual table identification. Keep that difference clear when deciding what to print. A server should not assume that a shared QR has told the restaurant where a guest is sitting simply because the sticker is attached to a table.
With individual table codes, label the physical signs clearly and verify each one at its actual location. Move the correct sign with the table only if your operating convention keeps the identification accurate. Table codes identify the table for an order; they are not a reservation or occupancy system. Staff still need to manage seating, changes of table, and conversations with guests using a procedure everyone on the floor understands.
Keep menu information and payment accurate
Start with a menu that matches what the kitchen can serve. Review dish names, prices, availability, and Spanish and English descriptions together. In QRP, dishes can have bilingual text and one photo of up to 5 MB. Useful descriptions explain what arrives on the plate; attractive photos do not replace information about ingredients. Direct allergy questions to staff, and do not treat a digital request as proof that every dietary concern has been resolved.
Payment remains in person whether an order arrives through WhatsApp or the panel. Tell guests when and where to pay, and have staff verify the final bill through the restaurant's normal process. The restaurant remains responsible for prices, taxes, allergens, preparation, service, cancellations, and refunds. Keep a human route available for guests without a suitable phone, anyone having connection problems, or a customer who simply prefers to speak with a server.
Pilot one shift before expanding
Rehearse a normal request, an unavailable dish, an unsent WhatsApp draft, and a guest changing tables. Include the people who actually work the shift, not only the manager configuring the menu. Watch for unclear responsibilities: who notices a request, who confirms it, and who tells the kitchen? Record those answers in a short shift checklist. If an employee has to guess during rehearsal, the process needs another pass before guests depend on it.
After a limited launch, ask staff where the process became confusing and review guest questions. Improve the instructions before adding more tables or menu options. Pro and Tables include up to five menus for the licensed restaurant, not licenses for five separate restaurants. Compare the restaurant packages when you are ready, choosing Pro for supported direct ordering or Tables when identifying individual tables is genuinely part of your service plan.