Two independent operators can reduce misrouted QR orders by making the merchant choice clear before checkout and checking that every order stays tied to that merchant, its menu, payment account and kitchen. A table number alone is not enough: both businesses may serve the same physical table.
Before buying, map the full order path and ask the vendor to demonstrate it for both operators. Decide who owns the signs, who can change the setup and what staff will do when a guest chooses the wrong business.
Map each table to the right merchant and kitchen
Start with the physical dining area, not the software screen. List the tables guests can use and give each one an identifier that staff can find. A physical table may seat several guest parties; the table identifier tells staff where to go, but it does not necessarily distinguish one party from another.
For each operator, record four separate things: the merchant taking the order, the menu shown to the guest, the fulfillment point that should receive it, and the identifier staff will use to find the guest. Also record where payment is collected and how staff can see its status. Do not assume two independent merchants can share a payment account or a kitchen screen in the way you need; ask how the proposed setup handles each one.
For example, a vendor might show that scanning a sign at table B4 opens a particular menu. That is only the first step. The operator also needs to see what happens when the guest selects an item, checks out and the order appears for preparation. A correct menu followed by an order at the wrong fulfillment point is still a failed setup.
Fleksa's QR ordering lets guests scan, order and pay at the table in a browser without downloading an app. Ask whether the specific arrangement you need for independent merchants and shared tables can be configured and demonstrated. A QR menu alone does not establish that orders or payments can be handled.
Choose between separate signs and a venue selection step
There are two useful starting designs. With merchant-specific signs, each operator has a distinct code and branding at a shared table. With a venue selection step, the guest scans an entry code and then chooses an operator. Ask vendors which design they can support and how they preserve the choice through checkout and fulfillment.
Separate signs put the merchant choice on the table. They can work well when each sign clearly names the business and shows its logo or menu cues. The tradeoff is physical clutter: guests must pick the right code, and staff must keep multiple signs in place. If signs move between tables, a guest can submit an otherwise valid order with the wrong location.
A selection step can leave fewer signs to maintain, but it adds a decision on the screen. The merchant name needs to remain visible after the guest chooses, including before payment. Ask what happens if a guest goes back, changes operators or wants food from both businesses. Do not assume that one checkout can split an order or payment between independent merchants.
Use this hypothetical worksheet for a venue with two independent businesses, Noodle Counter and Bread Stall, serving four physical shared tables. The four tables are locations, not a limit of four guest parties. Each business has its own menu and preparation point. The owners want each business to receive only its own orders and to know the table for delivery. They have not yet chosen a sign design.
| Decision | Vendor evidence to request | Owners' acceptance criteria |
|---|---|---|
| Entry and merchant choice | Show both proposed sign or selection flows, including the merchant name before checkout. | A guest can identify Noodle Counter or Bread Stall before placing an order. |
| Table identity | Show the table identifier on the guest flow and on the order received by staff. | An order from each of the four tables carries the correct identifier. |
| Routing and payment | Trace an order for each merchant to its preparation point and show payment status and account assignment. | Each order reaches only its intended preparation point and is assigned to the intended merchant. |
| Mixed or mistaken choices | Show what a guest must do to order from both businesses and how staff handle a wrong selection. | The flow does not imply a combined checkout unless the vendor demonstrates one; staff have an agreed correction procedure. |
| Sign upkeep | Explain how codes are created, replaced and checked after a table change. | A named person can replace and verify each sign before it returns to service. |
The worksheet separates a vendor's demonstration from the owners' decision. Use it for both sign designs if both are available. Add any requirement specific to your venue, such as how a runner distinguishes two parties at one table. Ask whether the guest enters a name or another identifier, and whether that information appears where the runner needs it.
Trace both orders before live service
Ask for a guided simulation using a safe practice environment. It should not take a real card payment, send a guest message or dispatch a courier. If a vendor cannot provide a safe way to demonstrate a step, ask for another form of evidence before treating that step as accepted.
For the hypothetical venue, start at one table with Noodle Counter. Follow the path from scan to merchant name, item selection, table identifier, checkout display and the order as the kitchen would see it. Repeat for Bread Stall at the same table. Then repeat at the other three physical tables, or agree on a documented check that covers every table-to-code assignment as well as both merchant paths.
Include deliberate mistakes. What does the guest see if they select Bread Stall but intended to order noodles? Can they return and choose Noodle Counter before submitting? What happens if they have already submitted? Ask the vendor to show the available correction path rather than assuming staff can transfer an order between merchants.
Check the staff handoff as carefully as the guest screen. The preparation point needs enough information to make the right food; the person taking it out needs the table and, where necessary, a way to identify the party. Ask whether the order shows payment status and how staff should handle an unpaid or unclear status. Also agree on a non-phone fallback, such as ordering with a staff member, and establish how that order reaches the correct kitchen.
A simulation is different from a live service pilot. Once the owners accept the practice checks, they can plan a limited live pilot with staff briefed on the workflow and a clear way to stop using the signs if routing is wrong. Live orders and payments are real; use the normal guest-facing process and tell staff how to report errors. Review each issue before expanding to more tables.
If the order has to appear in a restaurant POS system or another kitchen workflow, include that handoff in the demonstration. Ask which devices and connections are required, what staff will see, and what happens if a device or connection fails.
Assign ownership, correction and ongoing checks
Write down who may create or change codes, menus, table identifiers and fulfillment destinations. Independent operators should know which settings they control and which require the venue or vendor. Ask how access is separated so that a change for one business does not accidentally alter the other's setup.
Give each physical sign an owner. That person should check that it is readable, branded correctly and attached to the intended table. After cleaning, rearranging furniture or replacing a damaged sign, verify the code and location before guests use it. Keep a simple record of the table identifier, merchant or entry point, and date of the last check.
Agree on the guest-error procedure before opening. If a guest orders from the wrong merchant, staff need to know who speaks to the guest, who checks payment status, who stops or prepares the food, and who can authorize a correction or refund under the businesses' own policies. Do not promise an automatic transfer or refund without seeing how it works. If contract terms need interpretation, ask a qualified adviser.
Compare written quotes alongside the operational requirements. Ask each vendor to separate fixed charges, per-order or processing charges, and exception costs such as replacement signs, extra devices or support. Quoted processing fees alone are not the all-in operating cost. Fleksa states that table QR orders have no Fleksa commission; payment processing and applicable tax still apply. Check Fleksa's plans and request a current quote for the proposed setup; pricing information was checked in November 2026.
Use the worksheet to compare your requirements with Fleksa QR ordering. Bring the table map and both merchant paths to the conversation, and confirm the relevant workflow before buying.
Frequently asked questions
Can two restaurants use the same table numbers?
They can identify the same physical tables that way, but a table number does not identify the merchant or guest party. Confirm that the order also carries the right merchant and reaches its intended preparation point.
Should each restaurant have its own QR sign?
Separate signs make the merchant choice visible on the table, but they require upkeep and can be moved. Compare them with a venue selection step and choose the flow your vendor can demonstrate against your acceptance criteria.
What if a guest orders from the wrong operator?
Staff should follow an agreed correction procedure that covers the guest, food preparation and payment status. Ask the vendor what can be changed or refunded, and do not assume an order can be transferred between merchants.
