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.

Four months later, they have not reprinted a single insert. But the analytics they collected along the way changed how they run their entire operation. Here is their story.

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.

"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."

Setting up across three locations

Spice Route created a separate QR code 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 accounts, generate three codes, 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.

What the scan data revealed

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

Peak scan times: 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 at that time slot.

Device split: 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, bounce rates on the menu page dropped significantly.

Location comparison: The Andheri location had 40% more daily scans than the Worli location despite similar table counts. The team identified that the Andheri table cards had better visibility placement, and updated the Worli card design accordingly.

The financial outcome

Four months in, Spice Route has saved 100% of their historical menu reprint costs — approximately ₹13,000 across three 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."

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.
• 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.