Home Dynamic QR Geo Routing
Geo Routing
One artwork ships to every market and each one opens its own page.
Quinta do Vale prints one back label for the whole run. Bottles sold into the EU need the e-label with ingredients, nutrition and the health warning. The same bottle sold elsewhere does not, and the estate would rather those visitors landed somewhere useful.
The rule engine
What the scanner gets
Inside the EU, so the code opens the e-label: ingredients, nutrition per 100ml, and the health warning the regulation requires on the label or behind it.
Country is resolved by the edge network from the connecting address on the scan itself. It is not asked for, not stored against a person, and never a cookie. Groups are matched in order, so an ungrouped country is predictable rather than approximated.
Get this wrong and a bottle on a shelf in Lyon carries no e-label. The back label is already printed; the rule is the only part still editable.
no subscription · pay per scan · nothing to cancel
Six markets, one artwork, and each regulator wants a different page
Packaging and print runs cross borders; storefronts, support pages and mandatory consumer information do not. The usual workarounds each cost something a printed code cannot afford.
- A separate code per market means a separate print run per market.
- A country picker on a landing page adds a click and loses the readers who do not take it.
- A third-party geo service in the middle adds a hop and a dependency to every scan.
- The nearest competitor most people reach for has geo switched off outside the United States by design.
What Dal Giardino set up in one afternoon
Group the markets that share a page
A group is a name and a list of ISO 3166-1 alpha-2 codes. Groups are ordered, and the first group containing the scanner country wins.
[{ "name": "DACH", "values": ["DE", "AT", "CH"] }]The scan arrives already knowing where it is
Country is resolved by the edge network from the connecting address on the request that carries the scan. It is not asked for, not stored against a person, and never a cookie.
Everything else lands on a page you chose
Anything outside every group falls through to your default destination. There is no guessing and no nearest-neighbour matching, so a scan from an unlisted country is predictable.
What one sleeve buys you in four markets
- One rule for DACH, not three
geoA trade bloc is one group. You are not writing twenty-seven near-identical rules to cover the EU.
- A market you never considered still works
Every unmatched scan lands on your default, so a shopper in a country nobody planned for still reaches something deliberate.
- Regional pages can move after the print run
Importers change and storefronts migrate. Repoint the group and every code already in that market follows, with no reprint.
- Evidence of where the stock actually went
Scans by country are recorded first-party and cookie-free, which is the input to the next print run.
- Stacks with language
Country picks the storefront and the legal text; language picks the words. They are separate rules because they answer separate questions.
- Priced per rule, not per market
A custom routing rule is 5 credits, every change · add, edit or remove · a save that changes nothing is free, and scans are 1 credit each wherever they come from.
Questions
Where does the country come from?
From the edge network, derived from the connecting address of the request that carries the scan. It arrives as a signal on the redirect itself, which is why there is no extra round trip and nothing for the reader to answer.
How accurate is country routing?
Country level is the reliable tier and the one to build on. City is available in analytics and as a condition, but it is best-effort and a VPN or a carrier gateway will move it, so it is the wrong basis for anything a reader must not miss.
What happens if someone scans from a country I did not list?
They take your default destination. Groups are matched in order and there is no fuzzy fallback, so an unlisted country behaves the same way every time.
Does geo routing make my pack compliant?
No. It routes; it does not make the destination correct. Getting the right page in front of the right market is your job and a regulatory question, and a routing rule is only the delivery mechanism for it.
Does this work on packaging that is already printed?
If the printed code is dynamic, yes · add the rule and every code in the field follows it immediately. A printed static code cannot be given routing after the fact by us or by anyone, because its destination is the pattern.