EU Battery Passport 2027: What SMB Manufacturers Need to Do Right Now

GS1 Sunrise 2027 is the coordinated global deadline for retail POS systems to accept 2D barcodes — specifically QR codes built to the GS1 Digital Link standard. For grocery suppliers, this is not a marketing initiative. It is a vendor compliance requirement from the retailers that account for the majority of their revenue. We ran a test migration of a 500-SKU Dutch grocery supplier from 1D barcodes to GS1 Digital Link QR codes. Here are the eight things that broke — and what to do about each one before your transition.

---

Why grocery is the highest-urgency Sunrise 2027 category

Grocery is the first category most major retailers are targeting for Sunrise 2027 compliance because:

Short packaging cycles. High-volume grocery items reprint every 6–12 months. A supplier with a Q1 2026 print run can include GS1 Digital Link on packaging that will still be on shelves in 2027. You have repro opportunities now that you will not have if you wait until Q3 2027.

Active retailer compliance programs. Albert Heijn (Ahold Delhaize NL), Carrefour, and Tesco have published Sunrise 2027 roadmaps and are running active supplier engagement programs. New product submissions to some retailers already require 2D-capable packaging artwork to be submitted alongside the 1D barcode. By the time you get a formal compliance notice from your largest retail customer, you want to have already run a pilot.

GS1 data richness opportunity. Grocery products have the most to gain from the consumer-facing product page. Ingredients, allergens, origin, recipes, and promotions in a single scan create real consumer value. The 1D barcode was never designed for consumer interaction; the GS1 Digital Link QR code is.

Cross-regulation efficiency. For grocery suppliers with a pharmaceutical or nutraceutical portfolio, 2D serialization may already be required by FDA DSCSA or EU FMD. Sunrise 2027 becomes an extension of compliance infrastructure you already need to build, not a standalone project.

---

The 500-SKU migration: eight things that broke

We ran a mock migration of 500 grocery SKUs from a Dutch private-label food supplier (anonymized). The supplier had clean GS1 GTIN data, an existing ERP integration with their top three retail customers, and a cooperative packaging agency. They were better prepared than most. Here is what broke anyway.

Break 1 — GTIN check-digit errors in the master data. Of 500 SKUs, 23 had incorrect check digits in the ERP master data. The 1D barcode scanner had been silently correcting these for years — the error never surfaced because legacy scanners auto-correct single check-digit errors. The GS1 Digital Link URI validator rejected them immediately and with no auto-correction.

Lesson: audit every GTIN check digit before you build a single QR code. A GTIN with a wrong check digit encodes a code that points to the wrong product. At scale this is a food safety risk, not just a data quality issue.

Break 2 — Variable-weight items had no clean GS1 Digital Link path. Fresh produce with variable weight was tagged using price-embedded barcode formats. These have no direct GS1 Digital Link equivalent. Retailer POS systems handle variable-weight items differently; some use AI 30 (variable measure trade items), but implementation varies by retailer.

This required a separate workstream with each of the supplier's five retail customers to agree on the transition format for variable-weight SKUs. Three of the five had clear Sunrise 2027 guidance; two said "follow up in 2027." Do not assume all retailers have solved variable-weight before you start your transition planning.

Break 3 — Packaging agency artwork was not SVG-ready. The packaging agency had been delivering print-ready QR codes as raster images — PNG at 300 DPI. When printed at sub-3cm sizes, fine-detail loss caused scan failures on 8 of the 500 codes in the first press proof. The cause: rasterizing a QR code at 300 DPI and then scaling it down during plate making introduces module bleeding.

QR code artwork for packaging must be supplied as SVG (vector). The QR code scales perfectly at any size when the source is vector. We added this requirement to the packaging agency brief on day 1 of the next print run. Add it to yours now.

Break 4 — The consumer-facing resolver had no mobile optimization. When the 500 QR codes resolved to the existing product pages, 60% of those pages were not mobile-optimized. Desktop layouts, slow load times on 4G connections, and ingredient lists buried below the fold. Sunrise 2027 compliance technically requires a resolving URL — it does not specify mobile UX. But a non-mobile-optimized product page destroys the consumer engagement value that justifies the investment. If you are spending money on packaging reprints, spend another day mobile-optimizing your resolver pages.

Break 5 — Expiry date encoding format mismatch. The supplier encoded expiry dates as Application Identifier 17 in YYMMDD format (correct per GS1 specification). But the ERP exported dates in MM/DD/YYYY format. The encoding script had to transform every date field. A single date format inconsistency in a batch of 50,000 codes is a serious risk: a batch of yogurt where every QR code shows the wrong expiry date is a recall exposure, not just a compliance miss.

Build automated format validation into your generation pipeline before you run any production batch. Validate format, not just presence.

Break 6 — Batch number length exceeded what legacy scanners handle cleanly. The supplier used 20-character internal batch codes. GS1 Application Identifier 10 (batch/lot number) supports up to 20 characters — technically within specification. But several older POS scanners at their retail customers were truncating batch codes at 12 characters. The QR code was technically compliant; the scanner ecosystem was not.

Verify your batch code length against the scanner model specifications of your top five retailers — ask them directly which scanner hardware is deployed at their receiving docks and POS lanes. This information is not always public.

Break 7 — The resolver domain was tied to a marketing subdomain. Initial setup pointed QR codes at products.supplier.com/[GTIN]. Six months later the supplier rebranded their website and the subdomain changed. Every QR code on packaging already in market stopped resolving. This happened before Sunrise 2027 became a compliance topic — and it happened to a supplier with a professional IT team.

Use a dedicated resolver subdomain committed to long-term stability: id.company.com rather than products.company.com or any subdomain that sits under your marketing or e-commerce domain. Commit to maintaining it for the product shelf life plus 10 years minimum. This decision is harder to change than the QR code artwork.

Break 8 — No scan analytics per batch or SKU. The supplier had Google Analytics on the resolver pages but could not segment by QR code batch, SKU, or scan geography. When a spike in scans appeared on one product one Tuesday, they could not determine if it was in-store (organic scan from curious customer), e-commerce (package included with delivery), or PR coverage (journalist wrote something). First-party scan analytics per batch require a QR code platform with per-code scan tracking — not just URL-level analytics.

This matters for two reasons beyond curiosity. First, scan spikes that correlate with specific batch codes can be early indicators of a product quality issue. Second, if a retailer asks you for scan data to verify consumer engagement with a Sunrise 2027 implementation, URL analytics cannot give you what per-code tracking can.

---

The Sunrise 2027 supplier readiness checklist

Based on the 500-SKU migration, the practical readiness checklist for a grocery supplier:

• Audit all GTIN check digits in ERP master data — do not trust legacy scanner silence on errors
• Identify variable-weight and non-standard-format SKUs — escalate to each retailer's Sunrise working group individually
• Brief packaging agency: all QR code artwork as SVG, minimum size 2 × 2 cm, test at planned print size before press commitment
• Set up a dedicated resolver subdomain (id.yourcompany.com) — separate from marketing and e-commerce domains, committed for 10+ years
• Establish date format standards: confirm encoding format for AI 17 (expiry), AI 11 (manufacturing date), AI 15 (best before) in your ERP export
• Audit batch code lengths: GS1 AI 10 max is 20 characters, but verify against your top-retailer scanner hardware
• Mobile-optimize consumer-facing resolver pages — ingredients, allergens, origin, and promotions above the fold on a 390px viewport
• Set up per-code scan analytics (per SKU, per batch, per geography) — not just URL-level traffic analytics
• Validate with three test surfaces: iPhone native camera, Android native camera, Zebra DS3678 industrial 2D imager
• Check your retailer vendor manuals now — some major retailers have issued Sunrise 2027 compliance timelines that predate the December 31, 2027 public deadline

---

Timeline and cost estimate for a grocery supplier

For a 500-SKU grocery supplier with clean GTIN data and an existing ERP integration:

Platform cost: QR-Verse Business plan at €19/mo covers QR code generation, resolver hosting, and per-code scan analytics for your full SKU catalog.

Packaging agency cost: €50–150 per SKU for artwork adaptation (QR code placement, SVG generation, layout adjustment). For 500 SKUs this is €25,000–75,000 in agency fees — but you are not reprinting all 500 at once. Phase it by packaging reprint cycle.

GS1 membership: Most established grocery suppliers already hold GS1 membership. If not, annual fees range from €400–2,000 depending on revenue tier. GTIN registration is included in membership.

Timeline: 30–60 days for a pilot SKU end-to-end (GTIN audit through first compliant code live in retail). 6–12 months for full 500-SKU catalog conversion, assuming natural reprint cycle pacing.

The largest single cost is packaging agency time. Suppliers with shorter packaging refresh cycles (premium lines, seasonal products) can phase compliance naturally by converting each SKU at its next scheduled reprint with zero emergency-reprint cost.

---

Start with your fastest-reprinting SKU

The cheapest Sunrise 2027 path is to convert every SKU at its next scheduled packaging reprint, starting from the day you read this. You do not need a big-bang cutover. Pick the SKU with the shortest reprint cycle — typically a promotional or seasonal line — add the GS1 Digital Link QR code to its next artwork revision, validate against the checklist above, and run it live.

By the time the rest of your catalog cycles through, Sunrise 2027 compliance is complete. The alternative is a Q4 2027 emergency reprint of everything that missed the window — with premium agency fees, compressed timelines, and the risk of press-proof failures under deadline pressure.