Case Study: How a 3-Location Restaurant Cut Menu Reprint Costs by 100%

When Spice Route, a three-location restaurant group in Mumbai, switched from static to dynamic QR codes in January 2026, they had one goal: stop reprinting menu inserts every time prices or dishes changed.

Six months later, they have not reprinted a single insert. But the analytics they collected along the way changed how they run their entire operation — staffing, menu design, even which branch got a layout refresh. Here is their story in detail: the numbers before and after, the exact setup, what the data revealed month by month, and the playbook any restaurant can copy.

The situation: three locations, one recurring cost

Spice Route runs three full-service locations across Mumbai — Bandra, Andheri, and Worli — with a shared seasonal menu and roughly 180 tables in total. Like most restaurant groups, they had adopted QR menus during the pandemic and never looked back. Unlike most, they were still running the original static codes printed in 2021. Every menu revision meant a physical print cycle across all three sites. The QR codes worked. The economics around them didn't.

The problem: reprinting was bleeding money

Spice Route prints table cards with QR codes at all three locations — roughly 180 tables total. Before switching to dynamic QR codes, any menu change meant a full reprint run at approximately ₹12 per card. With seasonal menu updates every 6–8 weeks, the annual reprint cost was exceeding ₹40,000 — for a piece of cardboard nobody thinks about.

The hidden costs were worse than the printing itself. Each update cycle meant a design hand-off, a print-shop turnaround of 3–5 days, staff time swapping cards across three sites, and an awkward window where tables showed prices that no longer matched the kitchen. Twice a year, a rushed update shipped with an error — one typo in a QR URL once sent a week of scanners to a dead page before anyone noticed.

"We updated the menu in February for the summer season," says the operations manager. "Under the old system, that would have triggered a full reprint across three locations. This time we changed the URL in QRPulse, and it was done in about 30 seconds."

The setup: three locations, one hour

Spice Route created a separate QR code for restaurants for each location in QRPulse — three codes on the free plan initially, then upgrading to Pro once they saw the analytics value. Each location's code points to the same menu URL, but tracks independently.

Setup took under an hour: create the account, generate three codes named by branch ("Menu — Bandra", "Menu — Andheri", "Menu — Worli"), hand the SVG files to their regular print supplier. The new table cards were printed with the dynamic codes for the same cost as a standard print run — the switch itself added zero print cost, because the cards were due for a reprint anyway.

That last detail is the practical lesson for any restaurant considering the move: time the switch to your next scheduled reprint, and the migration is free.

What the scan data revealed

The first week of data surfaced insights none of them expected.

Peak scan times — and a hidden demand window

78% of menu scans happened between 12:00–13:30 and 19:30–21:00 — which matched their kitchen's busy periods. But the Bandra location had a secondary peak at 15:30–16:30 that the other two locations lacked. Investigation revealed it was driven by office workers from a nearby tech park having late lunches.

The team responded by adding an "afternoon specials" section to the Bandra menu, promoted in that time slot — lighter dishes, faster service, priced for the office crowd. Because the menu is behind a dynamic QR code, the specials section appears only on the Bandra menu, and updating it costs nothing. Within six weeks, the 15:30–16:30 window went from an accidental discovery to a deliberately staffed and stocked service period.

Device split — a menu format problem made visible

91% of scans were on mobile — 68% iOS, 23% Android. This confirmed that their menu PDF (which rendered poorly on Android) needed fixing. After switching to a mobile-optimised web menu, guests stopped flagging down servers to ask about items the PDF made hard to find, and the repeat-scan rate — guests re-opening the menu mid-meal because navigation was frustrating — dropped noticeably.

No survey would have caught this. Diners don't report "your PDF renders badly on my phone" — they just squint, give up, and order less.

Location comparison — a 40% gap with a physical cause

The Andheri location had 40% more daily scans than the Worli location despite similar table counts and covers. The obvious hypothesis — different customer demographics — turned out to be wrong. A side-by-side photo comparison showed the difference: Andheri's cards stood upright next to the condiments at eye level; Worli's lay flat on the table, where glare and clutter buried them. The team updated the Worli card design to the upright format, and the gap closed to under 10% within a month.

This is the core value of per-location codes: without independent tracking per branch, the gap would have been invisible — and the fix cost almost nothing.

The financial outcome

Six months in, Spice Route has saved 100% of their historical menu reprint costs — approximately ₹20,000 across update cycles that would previously have triggered full reprints. The QRPulse Pro plan costs $2/month.

"The saving on reprints alone paid for years of Pro in the first month," the operations manager notes. "But honestly, the more valuable thing is knowing which locations are performing and being able to act on it. That's not something we had before."

What they would do differently

Asked what they'd change with hindsight, the Spice Route team named three things. First, they would have started with per-section codes rather than per-location — indoor vs terrace vs bar scan patterns turned out to differ enough that they added section codes in month four anyway. Second, they would have fixed the mobile menu before launch instead of discovering the Android rendering problem through the device data; the fix was a day of work that had been silently costing orders for years. Third, they would have set up the weekly five-minute dashboard review as a named responsibility from day one — for the first month, everyone looked at the data and no one owned it.

None of these are QR problems; they're the standard lessons of adding measurement to a process that never had any. The data surfaces issues in the order of how visible they are, not how important — the discipline is acting on them.

The playbook: replicate this in your restaurant

1. Time the switch to your next scheduled reprint — the migration then costs nothing extra.
2. Create one dynamic QR code per location (minimum), named clearly by branch. Larger operations: one per section or per table zone.
3. Point all codes at the same menu URL — they track independently anyway.
4. Print upright tent cards at eye level, at least 5×5 cm, with a "Scan for menu" CTA.
5. Check the dashboard daily for the first two weeks — the anomalies (hidden peaks, branch gaps, device issues) show up fast.
6. Fix the menu format before anything else if your device split shows 90%+ mobile and you're serving a PDF.
7. Review weekly thereafter — five minutes: scans per branch, hourly curve, repeat rate.

Does this scale down to a single-location restaurant?

Yes — arguably better. A single location doesn't get the branch-comparison insights, but every other finding in this case study came from data any one-site operation collects from day one: the hourly demand curve, the device split, the repeat-scan rate, and the before/after signal on every menu change. The economics are also simpler: one location's table cards fit comfortably in QRPulse's free plan (2 dynamic codes — one for tables, one for the window or receipts), so the experiment costs literally nothing.

The single-location version of the playbook: one code for tables, one for a second placement you want to compare (counter, window, or receipt), two weeks of daily dashboard checks, then the weekly five-minute review. If the data changes even one staffing or menu decision per quarter, it has outperformed most paid market research — and unlike a consultant's report, it keeps updating itself every service.

Key takeaways for restaurant operators

• Create one QR code per location, not one for the whole business — per-location data is where the insights are.
• Check your device split early. If your menu is PDF-only and most diners are on mobile, you have a conversion problem to fix.
• Look for secondary scan peaks outside your obvious meal times — they often indicate an audience segment you can serve better.
• When two similar branches diverge in scans, look for a physical cause first — placement, height, glare — before assuming customer behaviour.
• The reprinting cost saving is real, but the operational intelligence is the longer-term value.

Want to replicate this setup for your restaurant? Create a free QRPulse account and have your first location tracking in under 5 minutes.