GS1 UK reports that 11% of its members are already live with 2D barcodes, and another 33% plan to join them within twelve months. Behind each of those migrations sits an unglamorous piece of infrastructure: the resolver, the service that turns a scanned GS1 Digital Link URI into a destination. And behind the resolver sits a build-or-buy decision that lands on someone’s desk in every single programme.<\/p>\n
This guide sets that decision out honestly. Self-hosting is a legitimate route with real advantages for certain organisations. A managed resolver is the faster and cheaper route for most others. The useful work is knowing which kind of organisation yours is before the first purchase order, and the four questions in the middle of this article usually settle it. If you want the standard itself explained first, start with our GS1 Digital Link guide<\/a>.<\/p>\n\n Unitag tracks 2.4 million scans daily<\/strong> across 189 countries. Over 40 million QR codes generated for brands including Bonduelle, Schneider Electric, and L’Or\u00e9al.<\/p>\n<\/div><\/div>\n\n On paper, a resolver redirects. A scan arrives as an HTTPS request for a URI such as In production, the job description is longer:<\/p>\n No single item on that list is exotic engineering. The list as a whole, kept running reliably for years while printed packaging depends on it, is where the real cost lives. That is the decision in one sentence.<\/p>\n Some organisations should run their own resolver, and it is worth being specific about which ones.<\/p>\n Self-hosting gives you full-stack control. The redirect logic, the data model, the logging pipeline and the release calendar are all yours. If your products feed regulated traceability systems with unusual requirements, or your security policy rules out any third-party processing of scan traffic, that control can be decisive on its own.<\/p>\n It also suits organisations that already operate customer-facing web infrastructure at scale. If you have a platform team with an on-call rota, edge capacity in place and room on the roadmap, a resolver is one more service on infrastructure you already run, and the marginal cost is genuinely low.<\/p>\n The honest bill for that control looks like this:<\/p>\n Self-hosting remains the right answer for teams that can absorb that list as routine work. It is an expensive answer for everyone else.<\/p>\n A managed resolver moves the operations, the conformance upkeep and the tooling onto a vendor, while the identifiers and the domain stay yours.<\/p>\n Unitag’s Digital Link Resolver, certified by GS1, works this way:<\/p>\n What you give up is bespoke control. If a requirement sits far outside standard resolver behaviour, you are negotiating a vendor roadmap rather than writing code that afternoon. For most packaging programmes that trade is comfortable; for a minority it is a dealbreaker, and those teams should self-host with a clear conscience.<\/p>\n A resolver sees every scan: timestamp, rough location, device type, which product. That makes it customer behaviour data, and it deserves a line of its own in this decision.<\/p>\n Self-hosted, the raw logs never leave your infrastructure, which is the cleanest possible answer to a data protection officer. The follow-up questions are then yours as well: retention periods, anonymisation, who inside the business can query what, and how the logs become reports that packaging and marketing teams can actually use. The redirect is a weekend project next to the reporting pipeline behind it.<\/p>\n Managed, the vendor processes scan data on your behalf, so the same questions move into the contract. Ask where the data is hosted and under which law, how anonymisation is handled, who at the vendor can access raw logs, and what you can export if you ever leave. Unitag’s Digital Link Resolver is EU-hosted and GDPR-compliant, and scan reporting is part of the product rather than a build item on your roadmap.<\/p>\n Neither answer wins by default. A pharmaceutical company with strict data boundaries may treat in-house logs as non-negotiable, while a consumer brand usually cares more about usable reports this quarter than log custody in principle. Decide which of those companies you are, in writing, before the procurement conversation starts.<\/p>\n 1. Control: do you need to own every layer, or to direct it?<\/strong> If regulation or internal security policy requires the redirect logic and the scan data to stay entirely in-house, self-host; the decision is made for you. If what you actually need is authority over destinations, rules and data access, a managed resolver on your own domain provides that authority without the infrastructure underneath it.<\/p>\n 2. Compliance scope: how many rulebooks apply to you?<\/strong> A single-market brand with one product family faces a manageable conformance surface. A multi-market catalogue touching the ESPR (Ecodesign for Sustainable Products Regulation, EU 2024\/1781), the battery passport obligation arriving in February 2027 (EU 2023\/1542) or the EU wine e-label requirement (EU 2021\/2117) is signing up to track several moving standards at once. The wider the scope, the stronger the case for making conformance a vendor’s problem rather than a quarterly internal review.<\/p>\n 3. Engineering cost: what would the assigned team otherwise build?<\/strong> The realistic self-hosted commitment is a build phase followed by a permanent operational slice of a platform team. For a company whose product is infrastructure, that slice is business as usual. For a food, cosmetics or retail business, the same engineers usually have work that moves revenue more directly, and the resolver becomes the project that is always second priority. Under-maintained infrastructure with your brand printed on millions of packs is the worst of both routes.<\/p>\n 4. Uptime accountability: who answers when a printed code fails?<\/strong> Carrefour’s May 2026 rollout put GS1-powered QR codes on 148 million water bottles and 50 private-label products. At that kind of scale a resolver outage is a shop-floor incident, and the printed code cannot be patched; only the service behind it can be fixed. Before deciding, write down who gets paged at 3 a.m., what the recovery target is, and where the redundancy sits. If the honest answer today is a shrug, buy the accountability with an SLA.<\/p>\n Whichever route you choose, one decision keeps you free to change your mind later: own the resolver domain, and print nothing else. Because every URI on your packs lives at your own domain, the service answering that domain can change without touching a single label. You can start managed and insource once volume justifies a platform team, or start self-hosted and hand over operations when the bill comes due. Printed packaging pointing at a vendor’s hostname is the one version of this decision you cannot walk back, so refuse it in either scenario.<\/p>\n\n Compare Digital Link Resolver plans<\/strong><\/p>\n Managed resolver on your own domain, EU-hosted, with scan analytics included.<\/p>\n <\/div>\n See pricing \u2192<\/a><\/p>\n<\/div><\/div>\n\n None of this needs to happen in a rush. GS1 Sunrise 2027 means retailers will need to be able to accept QR codes carrying GS1 Digital Link<\/a> at point of sale by the end of 2027, and during the transition 2D codes are read in addition to the barcode, so nothing on shelf breaks while you decide. The direction of travel is settled all the same: 48 countries covering 88% of world GDP are piloting 2D migration, and GS1 UK already counts one member in ten live.<\/p>\n What the timeline rewards is sequencing. A managed pilot can put conformant QR codes on a product line within a quarter. A self-hosted build wants a year or more of runway before packs reach print, because the operational muscle has to exist before the first artwork is signed off. Work backwards from your first target print run, and the pace of each route tells you a lot about which one fits.<\/p>\n The decision is rarely urgent, and it is never trivial. Made deliberately, either answer can carry you through Sunrise 2027 and well beyond it.<\/p>\n Talk through your resolver decision<\/p>\n Tell us where you are with GS1 Digital Link and we will map the shortest route to production.<\/p>\n Book a demo \u2192<\/a><\/p>\n<\/div>\n\n GS1 UK reports that 11% of its members are already live with 2D barcodes, and another 33% plan to join them within twelve months. Behind each of those migrations sits an unglamorous piece of infrastructure: the resolver, the service that turns a scanned GS1 Digital Link URI into a destination. And behind the resolver sits…<\/p>\n","protected":false},"author":6,"featured_media":472,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[21,22],"tags":[],"class_list":["post-469","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-packaging"],"_links":{"self":[{"href":"https:\/\/www.unitag.io\/blog\/wp-json\/wp\/v2\/posts\/469","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.unitag.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.unitag.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.unitag.io\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.unitag.io\/blog\/wp-json\/wp\/v2\/comments?post=469"}],"version-history":[{"count":2,"href":"https:\/\/www.unitag.io\/blog\/wp-json\/wp\/v2\/posts\/469\/revisions"}],"predecessor-version":[{"id":519,"href":"https:\/\/www.unitag.io\/blog\/wp-json\/wp\/v2\/posts\/469\/revisions\/519"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.unitag.io\/blog\/wp-json\/wp\/v2\/media\/472"}],"wp:attachment":[{"href":"https:\/\/www.unitag.io\/blog\/wp-json\/wp\/v2\/media?parent=469"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.unitag.io\/blog\/wp-json\/wp\/v2\/categories?post=469"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.unitag.io\/blog\/wp-json\/wp\/v2\/tags?post=469"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What a resolver actually does<\/h2>\n
https:\/\/id.yourbrand.com\/01\/09506000134352\/10\/LOT2748<\/code>, and the resolver answers with a destination.<\/p>\n\n
The case for self-hosting<\/h2>\n
\n
The case for a managed resolver<\/h2>\n
\n
Who sees the scan data<\/h2>\n
Four questions that settle the decision<\/h2>\n
The domain is your exit strategy<\/h2>\n
Sunrise 2027 sets the pace, calmly<\/h2>\n
What to do now<\/h2>\n
\n
Related articles<\/h2>\n
\n