Replace a restaurant QR code by confirming the table’s identity first, then verifying the code’s destination before you print or install it. Remove the old sign, check the replacement at the physical table, and record who approved the change. A readable code is not enough: it must identify the right table for the way your staff receives and fulfills orders.
Treat a damaged sign differently from a sign found in the wrong place. A worn sign may only need a verified reprint. A misplaced sign calls for a pause while someone checks both its intended table and the table where it was found. The goal is to prevent a guest at one physical table from being identified as another.
Keep a replacement register, not just a pile of artwork
Give each physical table a stable identifier that staff can recognize, such as P-03 for patio table 3. A table identifier is not a guest party number: several parties may use the same table over a shift, and one party may occupy more than one table. Your replacement record should identify the furniture location, not the people currently sitting there.
Keep a register that a shift manager can reach when a sign goes missing. For each table, record:
- The table identifier and a plain-language location, such as “patio, beside the north door.”
- Where the sign belongs: tabletop, holder, wall, or another fixed location.
- The current approved artwork or file location, including a version or date.
- The destination or table association the code is supposed to produce.
- The person responsible for approving a replacement and the date it was checked.
- The status of any removed sign: destroyed, held for investigation, or otherwise retired.
Control access to the artwork. A printer-friendly folder is useful, but an old file saved on a personal phone can put a retired code back into service months later. Mark approved files clearly and move superseded versions out of the normal print folder. If your system generates codes, ask the vendor how to identify the current code for a table and whether an older code can still be used.
Assign a backup owner as well as a primary owner. The person who notices a damaged sign should be able to remove it, but a trained manager should verify the destination and approve the replacement. During a busy shift, use a temporary non-phone ordering method rather than letting an unverified sign remain on a table.
Choose the replacement path before printing
The following worksheet uses hypothetical inputs for a restaurant with individually labeled physical tables. It shows how the condition and location of a sign change the next step. It does not assume a particular vendor can deactivate or regenerate a code; confirm those controls before relying on them.
| Finding | What is known | Decision before printing | Release check |
|---|---|---|---|
| P-03 sign is worn but remains in its holder | The location matches the register; the code no longer scans reliably. | Use the approved P-03 file only after confirming its table association. | Scan the installed copy and confirm P-03 in the ordering flow. |
| A P-04 sign is found on P-05 | The printed label and physical location disagree. | Remove the sign. Check the registered associations for both tables before choosing either replacement. | Check each table separately; document where the removed sign went. |
| P-06 holder is empty after a layout change | The sign is missing and the furniture may have moved. | Confirm which physical table is now P-06 and whether the missing code needs to be retired. | Approve the updated location, then check the installed sign at P-06. |
In the first row, the location supports a straightforward reprint, but it does not prove the saved file still has the right association. In the second, reprinting immediately could preserve the wrong placement. In the third, the missing sign is a separate risk: someone may find and reuse it. Ask the vendor whether it can be invalidated and what happens if a guest scans it afterward.
Replace a sign when damage makes scanning unreliable, the destination is wrong, the table association has changed, or the printed instructions no longer match the service offered. A sign that has moved needs verification even if it looks perfect. If you cannot establish its intended destination, remove it from guest use until the question is resolved.
For any new or regenerated code, ask whether the table identifier is embedded in the code, assigned through a destination link, or managed another way. Also ask whether a replacement can use the existing association and whether changing it affects previously printed copies. Those answers determine whether you can safely reprint an approved file or need a new code and a retirement step.
Verify the destination, then retire the old sign
Before printing a batch, inspect the candidate code in a safe preview or test flow. Confirm the destination belongs to the restaurant and that the ordering screen or staff-facing view identifies the intended table. A code that merely opens the menu has passed only the first check. If the service takes orders or payments, the table association and staff handoff matter too.
Ask your provider how to check that association without creating a live order. If there is no suitable preview, agree on a safe verification method before a guest uses the sign. A practice scenario must not trigger a real card payment, guest message, or courier dispatch. Do not assume a scan alone proves that an order would reach the right staff member.
Then install and verify the physical copy:
- Remove the old sign from its holder and collect any duplicate copies kept nearby.
- Compare the printed table label, physical location, and replacement register.
- Scan the installed sign from a normal guest position. Check readability and the expected destination.
- Use the agreed safe check to confirm the table association and the staff-facing handoff.
- Record the checker, approver, date, and outcome. Release the table for QR use only after the check passes.
If a check fails, remove or cover the replacement and route guests to staff for ordering. Record what failed rather than repeatedly printing the same file. The problem might be the artwork, the association, the placement, or the way the table was renamed. Resolve the cause and repeat the check before putting the sign back.
Retiring paper and retiring a digital destination are different jobs. Destroying a printed sign stops that copy from being reused; it does not necessarily disable the code. Where a code may have been photographed, lost, or duplicated, ask whether the vendor can disable it and what guests and staff would see if it were scanned. Record the answer and the action taken. Do not mark a code digitally retired merely because the paper is gone.
Keep the service model in view. Fleksa’s QR ordering lets guests scan, order, and pay at the table in a browser. A QR menu alone does not necessarily provide ordering or payment. Before choosing a workflow, check what staff sees, how payment status is presented, and how a guest without a phone can order.
Recheck after furniture and service changes
Make QR signs part of the opening check and any planned furniture reset. A quick visual pass can spot a missing holder or an obviously wrong label. A deeper association check belongs after a table move, a rename, a replacement, or a change to the ordering setup. Decide who performs each check and who can approve a table’s return to QR service.
When combining tables, distinguish the physical tables from the party using them. For example, if one party sits across P-03 and P-04, decide which table identifier staff should use for that service and what should happen to the other sign. Do not assume the software combines the two. Ask the vendor how combined tables, split parties, and table transfers appear to both guests and staff. If the workflow cannot represent the arrangement clearly, remove the extra sign and use the staff ordering fallback until the tables are separated.
When furniture moves permanently, update the register before installing signs in their new locations. Record the old and new locations, the reason for the change, and the approving manager. Remove the old sign from the prior location, including a wall-mounted copy that could be overlooked. Then verify the new placement at the physical table, not from the office.
A live service pilot is different from a simulation. After safe checks pass, a manager can observe normal service at a limited number of tables, watch for confusion in the staff handoff, and collect issues for correction. Do not promise that a changeover will be uninterrupted. Keep the fallback ready, and pause QR use at a table if its identity is in doubt.
Include the handoff in your buying questions. Ask how table identity appears in the restaurant POS, whether staff can recognize a moved or combined table, and how they distinguish an unpaid order from a paid one. Your answers may also affect where QR ordering fits alongside table service; use the table-service buying guide to work through that choice.
Next step: Pick one damaged or missing sign, complete the register and verification steps above, and compare the resulting workflow with your operating requirements using Fleksa QR ordering.
Frequently asked questions
Can I reprint the same QR code for a damaged sign?
Possibly. First confirm that the approved file still points to the correct table and that the provider permits reuse. Scan and verify the installed copy before returning it to service.
What should I do if a QR sign is found on the wrong table?
Remove it and check both the printed label and the physical locations against the register. Verify each affected table separately, and use staff ordering while the association is uncertain.
Does destroying a sign deactivate its QR code?
Not necessarily. Destroying the physical copy prevents its reuse, but a photo or another copy may still work. Ask the provider how to disable the destination and what a scan of the old code will show.
