How a cafe chain replaced 240 menu prints with 8 dynamic QRs.

Bend Coffee Co runs 12 locations across Portland and the Eastside. Every quarter we rotated seasonal menus — and every quarter, our store managers spent half a day making sure the new menus had been updated, printed, and laminated at every location. Some quarters we had stragglers running old menus for weeks.

Then we switched to 8 dynamic QR codes. Now I update one URL and all 12 locations have the new menu in under five minutes.

Here are the numbers, the implementation, and the things we'd do differently.

Photo: cottonbro studio on Pexels

The math

Before:

After:

• 12 dynamic QRs (one per location-customizable per location)
• $0/yr in software
• 0 weekly manager time

The implementation

The setup was actually trickier than a single-location restaurant. We wanted:

1. Each location to have its own QR (so we could see scan rates per store)
2. All locations to share a baseline menu but allow per-location specials (Fairhaven has a different cold brew lineup than Bend)
3. The ability to update prices uniformly across all locations when wholesale changes

We used QRBliss's smart redirect feature for this. Each location has a unique QR — but they all resolve through the same dynamic code with location-specific URL fragments. From the customer's perspective, scanning the Fairhaven location's QR sends them to bendcoffeeco.com/menu?loc=fairhaven, and our website serves the right content.

This took 30 minutes to set up across all 12 locations. The hardest part was getting all 12 store managers to scan their respective QRs to verify they worked.

The unexpected wins

A few things we didn't expect:

Manager satisfaction went up. Store managers used to dread the quarterly menu update — it meant a Saturday morning of laminating, distributing, and pulling old menus. Now they don't think about it. The menus just update.

Customer scan rates revealed location preferences. The Bend (downtown) location has a 38% scan rate. The suburban locations are at 20-25%. Same menu, same QR design — the difference is foot-traffic demographics. Bend gets more out-of-towners who want to scan menus before ordering. We're now using this data for things like staffing during high-scan periods.

Updates can be A/B tested. When we rolled out the spring menu, we changed prices on the matcha lineup to test elasticity. Within a week the data was clear: a $0.50 increase reduced order volume by 6% but increased revenue by 11%. We kept the new prices.

What we'd do differently

Add the QR to drive-thru menu boards from day one. We initially only put QRs on the in-store menus. Our drive-thru customers couldn't access them. We added them six weeks in — they now drive 22% of all our scans because drivers want to see the menu before pulling up to the window.

Train staff on what to do when a customer scans. Some baristas got confused when customers were "looking at their phones for too long" before ordering. We had to explain that the QR menu is part of the experience, not a distraction. Two minutes of training would've saved a week of confused interactions.

Pick a category-tinted QR template. We initially used a black-and-white QR. It worked, but it didn't match our brand. A simple swap to our forest-green template made the QR feel like part of the menu, not a tech afterthought.

Should you do this?

If you have 3+ locations and any kind of menu rotation, yes. The break-even is somewhere around 3-4 locations.

If you have 1-2 locations, dynamic QRs are still useful (for seasonal updates, A/B testing prices), but the case is less obvious. Sarah at Maple Diner uses 8 dynamic QRs in a single location, mostly for the price-update flexibility.

If you don't update your menu more than once or twice a year, static QRs are fine. The dynamic value is in the changeability.

For us, the answer was an obvious yes. Three months in, we wouldn't go back.