If you run more than one physical location — restaurants, retail branches, service franchises — you already know the headache: printed materials go out the door and then your hours change, your menu updates, or a new promo launches at only three of your six sites. With static codes, you're reprinting. With dynamic routing tied to geography, you're updating a spreadsheet.
This post covers four concrete routing setups for multi-location businesses, what each one requires technically, and where each breaks down so you don't walk into it blind.
Why Geography Alone Isn't Enough
Most articles on geo-routing stop at "detect the scanner's location, redirect to the nearest store page." That works when your stores are 50 km apart. It breaks when two branches are in the same shopping mall or when a customer scans your code at home before driving in.
Effective multi-location routing usually layers two signals: a location identifier baked into the code itself (one unique code per location), plus dynamic destination control so you can change where each code points without reprinting. Understanding the difference between a truly dynamic code and a static one is foundational — the Static vs Dynamic QR Codes breakdown explains the mechanics if you need a refresher before diving into these setups.
Scenario 1: One Code Per Branch, Centralised Destination Control
The setup: Each location gets its own dynamic QR code. All codes live under one dashboard. When you need to update the destination URL — say, to swap a lunch-special page for a dinner-special page — you change it once per location, or in bulk if the same page applies everywhere.
Best for: Restaurant groups, salon chains, gym franchises.
What it solves: A manager at your Westside branch can't accidentally break the Eastside code. You also get per-location scan analytics without any extra tagging effort.
Watch out for: If you create one code and try to share it across branches to "save codes," you lose per-location data entirely. One code = one location is the non-negotiable rule here.
Scenario 2: Shared Promo Code, Location Detected at the Landing Page
The setup: You print one QR code on a national flyer or mailer. The code points to a landing page that asks the scanner to choose their nearest branch, or — if you have location permission — auto-detects and redirects.
Best for: Franchise systems where the franchisor controls printed collateral and can't produce location-specific versions.
What it solves: You get one print run, one design, one URL to manage.
Watch out for: Conversion drops sharply when users have to take an extra step. A/B tests on multi-step landing pages consistently show higher drop-off than direct-to-destination routing. If you can print location-specific codes, do it. Reserve this scenario for cases where you genuinely cannot.
Scenario 3: Time + Location Routing Combined
The setup: Each branch code routes to different destinations depending on the time of day. Branch A's breakfast menu from 7–11 am, the lunch menu from 11 am–3 pm, the dinner menu after 3 pm — all without reprinting. This is a natural extension of time-based routing applied at the branch level.
Best for: Food and beverage businesses with distinct day-part menus; gyms with class schedules that vary by location.
Implementation note: Your dynamic QR platform needs to support multiple routing rules per code (time and destination), not just a single redirect. Check this before committing to a platform — some tools only allow one active redirect at a time.
What it solves: A customer scans the table tent at 2 pm and lands on the lunch menu, not a generic homepage. Staff don't need to swap printed menus.
Watch out for: Time zone handling. If your platform operates on UTC and your branches are in multiple time zones, verify that each code's schedule accounts for local time. A routing rule set to "after 3 pm" should mean 3 pm local, not 3 pm server time.
Scenario 4: Stock or Availability Routing Per Location
The setup: A product is stocked at some branches and not others. Each branch's code for that product routes either to a buy-now page (if in stock locally) or to a "find it nearby / join the waitlist" page (if out of stock).
Best for: Boutique retailers, specialty food shops, hardware stores with uneven inventory distribution.
This is closely related to inventory-level routing — the QR Code Routing by Stock Level post covers the mechanics of connecting your QR platform to live inventory data.
What it solves: A customer scans a shelf tag for a product that sold out this morning and gets a useful page instead of a dead listing.
Watch out for: This requires an API or webhook connection between your inventory system and your QR routing platform. If you're managing stock manually or in a spreadsheet, you'll need to update routing rules manually too — which is workable for slow-moving products, but impractical for anything that turns over daily.
What to Track Across All Four Scenarios
Per-location scan analytics are the primary payoff of this entire architecture. At minimum, track:
- Scans per location per day — surfaces which branches generate the most engagement from printed materials
- Destination reached — confirms routing rules are firing correctly (a scan that hits the wrong page tells you a rule is broken)
- Scan-to-conversion rate per branch — identifies whether a location's landing page is underperforming relative to its scan volume
The QR Code Analytics: 6 Metrics That Actually Drive Decisions post walks through how to interpret these numbers once you have them flowing in.
Choosing the Right Platform Features
Before you commit to any of the four scenarios above, confirm your QR platform supports:
| Feature | Needed for |
|---|---|
| Multiple active rules per code | Scenarios 3 and 4 |
| Per-code analytics dashboard | All scenarios |
| Bulk destination updates | Scenarios 1 and 3 |
| API / webhook integration | Scenario 4 |
| Local time zone scheduling | Scenario 3 |
Most mid-tier dynamic QR platforms handle Scenarios 1 and 2 without issues. Scenarios 3 and 4 require checking the feature list before signing up — and you can use our QR Code Finder to narrow down which code type and platform tier fits your specific setup.
Key Takeaways
- One code per location is the baseline rule for multi-location routing — sharing codes destroys per-branch analytics.
- Layered routing (location + time, or location + stock) is more powerful than geo-routing alone, but requires platforms that support multiple rules per code.
- The shared-flyer scenario (one code, branch chosen at landing page) is a fallback, not a best practice — it adds friction and reduces conversion.
- Time zone handling is the most common technical failure point in time-based multi-location setups — verify it before going live.
- Per-location scan-to-conversion data is the primary long-term value of this architecture; set up tracking from day one.