Restaurant Menu QR Code Not Working? Here's Why (and How to Fix It Without Reprinting)

Before assuming the physical code itself is damaged, check the four most common causes in order: whether the code was deactivated or deleted from your dashboard, whether an expiry date or scan limit has quietly kicked in, whether the destination page (not the code) is actually the thing that's broken, and only then whether the physical print itself has a design or damage problem. Most "QR code not working" complaints trace back to one of the first three — not the printed pattern at all.

SMLLR supports instant deactivation of a QR code — a genuinely useful control, but one that's easy to trigger by accident when staff are managing dozens of table codes across a busy menu redesign. Check your dashboard first: a deactivated code will show as inactive rather than throwing a generic error, and reactivating it takes seconds. If the code was deleted outright rather than deactivated, that's not recoverable — the printed pattern encoded a specific link that no longer exists, and the table card needs a new code.

Two features that are useful when set deliberately can look like a bug when forgotten: an expiry date (available from the Basic plan, ₹1,999/month) that quietly stops the code once a set date passes, and a scan-limit redirect (same plan) that switches the destination once a set number of scans is hit — useful for a limited-run promotion, confusing on a permanent table menu if it was configured with a cap in mind for a different purpose. Check whether either was set intentionally for a past promotion and simply never removed.

A dynamic QR code redirecting correctly to a destination that's itself broken looks identical to a broken code from the customer's side — but the fix is completely different. If the menu is a PDF hosted elsewhere, check that the file wasn't moved or deleted at the source. If it's a page on your own website, check that the site itself is up and that specific URL still resolves. SMLLR's Landing Page builder (Pro plan, ₹4,999/month) removes this specific failure mode by hosting the menu page directly rather than depending on a separate, externally-hosted file that can be moved or deleted without anyone updating the QR code's destination to match.

If the dashboard shows the code active with no expiry or limit issue, and the destination loads fine when you visit it directly, the problem is likely physical: lamination glare under table lighting, a faded or low-contrast print after repeated wiping down, a code sized too small for the distance a seated diner actually holds their phone at, or physical damage to a corner of the pattern beyond what its error-correction level can recover from. Our error correction levels guide covers how much physical damage a code can tolerate before it stops scanning.

This is where a dynamic QR code earns its keep: if the underlying issue is deactivation, expiry, a scan limit, or a broken destination link, every one of those is fixed from your SMLLR dashboard in under a minute, with zero impact on the already-printed table cards — reactivate the code, remove or extend the expiry/limit, or simply update the destination URL. Only a genuinely physical problem (a damaged, faded, or badly lit printed code) requires touching the print itself, and even then only that specific card needs replacing, not the whole batch.

A few habits that stop this from recurring: use a dynamic QR code (available from the Starter plan, ₹499/month) rather than a static one for anything on a table, since a static code has no dashboard to check or fix at all. Avoid setting an expiry date or scan limit on a permanent menu code unless you have a specific reason to, and if you do, put a reminder to review it. Host the actual menu on SMLLR's Landing Page builder rather than a separate file host you don't control directly. And do a real phone-camera scan test on a handful of table cards periodically, rather than assuming a code that worked on day one still works months later.

Create your dynamic QR code on SMLLR for your table menus, and fix any future issue from your dashboard instead of a reprint.