Indian Restaurant Takeaway QR Code Not Working? Fix It Fast
Quick Diagnosis Table
Start here. Match your symptom to the most likely cause and jump to the relevant fix.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Phone camera opens but nothing happens | QR code too small or low contrast | Resize and reprint at minimum 3 cm x 3 cm |
| Scans but lands on a 404 or error page | URL changed or was entered incorrectly at generation | Regenerate with the correct live URL |
| Works in one lighting condition, not another | Printed on glossy paper causing glare | Reprint on matte stock |
| Scans fine but customers get lost after clicking | Landing page not mobile-optimised | Fix the destination page layout |
| Only some phones scan it | QR code too dense or distorted | Regenerate with more quiet zone margin |
| Customers say they can’t find it | Poor placement, not at eye level | Relocate the code on the counter or bag |
The Top 4 Causes (and Exactly How to Fix Them)
1. The URL You Encoded No Longer Works
This is the most common killer of a QR code for Indian restaurant takeaway ordering setups. A restaurant updates its online ordering platform, changes its domain, or switches from one delivery partner to another, and suddenly the QR code on 500 printed takeaway bags points nowhere useful.
Static QR codes encode the URL permanently at the moment of generation. That is not a flaw; it means they work forever with no subscription or monthly fee. But it does mean the URL itself must stay live. If you have moved your ordering page, even slightly (from /order to /order-online, for example), the old code is dead.
Fix: Test the URL in a fresh browser tab before you generate anything. Then generate a new QR code pointing to the updated address. QRapid’s free generator at qrapid.co takes about 30 seconds, so there is no reason to keep using a broken code. Print a fresh batch and replace the old ones immediately.
Check this monthly. Put a recurring reminder in your phone calendar. It takes two minutes and prevents the Friday-night chaos described above.
2. The Printed Code Is Too Small or Too Low in Contrast
Phone cameras need a certain amount of visual information to decode a QR code. Print it at less than 2.5 cm x 2.5 cm and most devices will simply fail to lock on. Print it in light grey on a white background and the contrast ratio drops below what the scanner expects.
Consider a takeaway that added QR codes to their flyers to drive customers toward their own ordering page instead of a third-party app. They printed the codes at a very small size on A5 flyers and got constant complaints that the code “didn’t work.” When they reprinted at a larger size with a white quiet zone on a dark background, scans became reliable and direct order volume increased in the weeks that followed. The fix was entirely physical, not technical.
Minimum size rule: 3 cm x 3 cm for a code placed on a flat surface at arm’s reach. For a wall-mounted sign or a window decal, go larger: 10 cm x 10 cm is a reasonable starting point. The same sizing logic applies when you use a QR code on a trade show display, where viewing distances can vary considerably.
Contrast rule: Dark code, light background. Black on white is the gold standard. If you are printing on coloured paper, test with three different phones before you commit to a full print run.
3. Glossy Surfaces and Bad Lighting Are Killing Your Scans
Laminated menus, glossy card stock, and shiny takeaway boxes all reflect light in ways that interfere with camera scanning. A customer standing at a brightly lit counter points their phone at a laminated QR code and the overhead strip light creates a white reflection directly across the centre of the code. The camera cannot read through it.
This is especially relevant for Indian restaurant takeaway environments, where counters are often well-lit for visibility and speed. The same lighting that helps staff work efficiently can make QR codes unreliable.
Fix: Switch to matte-finish printing for anything displayed at counter level. If you are printing on packaging, request a matte varnish from your printer. For window displays, position the QR code away from the direct path of natural light or use a matte laminate.
Also worth testing: print a simple test sheet on plain copy paper and see if that scans where the glossy version fails. If it does, the substrate is your problem, not the code itself.
4. The Destination Page Fails on Mobile
Technically the QR code works. Practically, it does not. Customers scan, land on the page, and then abandon because the ordering interface is not usable on a 6-inch screen. Buttons are too small, the menu does not load properly, or the page takes too long to appear over a slow mobile connection.
Smartphone users now have direct experience of how QR flows should feel. They know immediately when something is wrong, and they will not persevere through a clunky experience when they are hungry and in a hurry.
Fix: Open your ordering URL on your own phone before you print a single QR code. Scroll through the full menu. Try to place a test order. Check that the checkout button is tappable without zooming. If the page is hosted on a third-party platform, contact them about their mobile layout. If it is your own site, a developer can usually resolve basic mobile display issues in an afternoon.
Prevention: What to Do at Generation Time
Getting the generation step right removes most of the problems above before they start.
Use the exact final URL, not a redirect or a staging link. Copy it from your browser after the ordering page is fully loaded and confirmed live. Paste it into the generator, then click the generated link before downloading the image to confirm it opens correctly.
Download the QR code as an SVG or high-resolution PNG (at least 1000 x 1000 pixels). Low-resolution exports look fine on screen and terrible in print. This single choice prevents a significant number of “blurry QR code” complaints.
Add a short text instruction beneath the code. Something like “Point your camera here to order” removes the guesswork for customers who are less familiar with QR scanning. That extra line of copy matters more than it looks. The same principle applies in other contexts, such as when you use a QR code for a wedding seating chart, where guests of all ages and varying levels of tech confidence need to scan reliably on the day.
Keep a copy of the original download. If you need to reprint, you want the full-resolution file, not a screenshot someone grabbed off a WhatsApp group.
When to Start Over vs. When to Iterate
Not every problem needs a full regeneration. Here is how to decide.
Reprint the existing code if the issue is purely physical: wrong paper finish, wrong size, bad placement. The code itself is correct and the URL still works.
Regenerate from scratch if the URL has changed, if you suspect the original was exported at low resolution, or if you have no access to the original file. Regeneration is free and fast, so there is no cost argument for keeping a broken code alive.
Replace all copies when you regenerate. A common mistake is updating the digital version but leaving old printed copies in circulation on bags, menus, and flyers. One confused customer who scans an outdated code on a takeaway bag and hits a broken page is one too many.
Frequently Asked Questions
Q: Can I use one QR code across all my takeaway materials (bags, flyers, counter card)?
Yes, as long as all of them point to the same URL and you print each version at the appropriate size for its context. The counter card needs a different size than the small corner of a takeaway bag. Generate one code and resize the image file for each print application. Do not screenshot or stretch the image; export at high resolution and let the printer scale it correctly.
Q: My QR code scanned yesterday but stopped working today. What happened?
The code itself has not changed; something on the destination end has. Check whether your ordering page is still live, whether your domain has expired, or whether your ordering platform has gone offline temporarily. Scan the code with two different phones to rule out a device-specific issue. If the URL resolves on a desktop browser but not via the QR scan, there may be a mobile redirect problem on your hosting setup.
Q: How do I know if my QR code is good enough quality before I print 1,000 takeaway bags?
Print one copy on the actual material you plan to use, at the actual final size, and test it with four different phones including at least one older Android device. Older Android cameras are the strictest test of QR readability. If all four scan reliably in normal room lighting, you are good to go. If any fail, fix the size, contrast, or resolution before committing to the full print run.