Français
Español
GS1 Sunrise 2027: Which Code Goes on Your Carton, and Who Owns It
A retail barcode has one job, which is to carry a product identifier to a till. From 2027 the same packaging is expected to carry that identifier in two symbol families at once, and the transition is an industry commitment rather than a law. Consequences for goods shipped from a China warehouse are concrete and narrow: which code sits on which unit, who owns the artwork, and what a prep line can fix without touching a registration.
Key facts
- The goal date. GS1's retail-2D guideline states that point-of-sale scanning should be globally capable of reading the GTIN from both linear and 2D barcodes by the end of 2027; the text read here is release 1.1.0, ratified December 2025.
- Dual marking, not replacement. Until an adoption threshold across scanning estates is met, any product using a retail 2D symbol must also carry a linear barcode.
- Padded, not new. A 2D symbol encodes the same GTIN as the linear code, written in a zero-padded 14-digit form whether the item is GTIN-8, GTIN-12 or GTIN-13.
- Ownership does not move. A floor can print, place and verify; it cannot assign a prefix, change a GTIN or re-issue artwork.
What the transition is, in one page
A linear barcode carries an identifier and nothing else. A 2D symbol to the GS1 Digital Link syntax carries that identifier plus a web URI, so one scan can price an item at a till and then resolve to batch data, ingredients or a manufacturer page. The retail interest is one symbol serving checkout, provenance and consumer information; the brand-owner interest is a package with a data address that can be updated without reprinting the box. The guideline states a capability goal for scanning estates rather than a deadline imposed on a seller, and it distinguishes what scanners must handle from what packaging must show.
What changes on a prep and labelling floor
Four items move, and one is a trap. Placement matters more: a 2D code printed on a curve, under a seam or beside a dark border fails to resolve even when the linear code scans cleanly, so a floor that checked one code now checks two. Quiet-zone rules apply to both. The readable string is another: the guideline requires the 14-digit GTIN beside a 2D symbol when it is the only barcode on an object, and no second string when it sits next to a linear code that already carries one. Batch and date fields can ride in the 2D, which tempts local printing of variable data - a brand-owner decision, not the printer-holder's. And the trap: putting a logistics-level identifier on a retail unit.
The difference between a retail unit and a shipping carton
A consumer unit sold across a counter is identified by a GTIN-8, GTIN-12 or GTIN-13, and that number must be the payload of a retail 2D symbol. A case or pallet is identified at a different level, commonly a GTIN-14 built from an indicator digit plus the base number, and that is what a receiving centre or wholesaler scans. Both are legitimate; neither replaces the other. Where a line relabels returned or repackaged stock, the failure to watch for is a case-level number printed onto a sellable unit: it clears an inbound scan and fails at a till. A 2D transition changes nothing here; the extra symbol only hides the mistake better.
| Object | Identifier level | What a fulfilment line can do |
|---|---|---|
| Consumer unit sold at a till | GTIN-8, GTIN-12 or GTIN-13, padded to 14 digits inside a 2D symbol | Print and place a conforming symbol, check quiet zones, verify the readable string |
| Case of those units | Logistics-level GTIN built with an indicator digit | Label, re-label and scan against a packing list |
| Marketplace inbound label | A platform-scoped item number, not a GTIN | Applied over or beside the retail code per your instruction |
Who owns artwork, and what nobody can own for you
A GTIN comes from a company prefix, and a prefix is registered, not delegated. That one fact draws the boundary of this transition for a seller working through a third party. A warehouse can place a symbol on a carton you approve, report when a printed code fails verification, and hold which batch was packed on which date. It cannot choose your identifier, re-issue packaging carrying a code it did not receive, or certify the data behind a web address. Updating what a code resolves to is a content decision on your side. The cheapest control is procedural: one owner for the code register, a log of every change, and no labelling instruction arriving as a screenshot in a chat.
What a seller should ask a fulfilment partner this year
Four questions, and the answers are either documentary or they are not. Which identifier is printed on a retail unit today, and where the register of those numbers is held. Whether a partner applies two symbols to one object, and how it stops a case number reaching a consumer unit. What verification exists after printing - a scan against the artwork file, or nothing. And what record survives a complaint in twelve months: batch, date, the file used, the operator who ran it. A mis-pick below 0.01 per cent, measured per order line, is what our floors report, because a code printed on the wrong unit is a picking failure rather than a barcode one, and is counted as such.
Frequently asked questions
Do I have to reprint packaging before the end of 2027?
Not on the strength of the guideline, which is a capability goal for scanning estates rather than a rule binding on a seller. The real driver is commercial: a retailer or marketplace may set its own inbound date for requiring 2D symbols, and packaging then follows that timetable. Dual marking exists precisely so a brand can add a symbol without withdrawing the linear code. Ask each account for its stated requirement and treat the guideline as the ceiling of a schedule, not the trigger.
My 2D code holds fourteen digits and the box says thirteen. Is one wrong?
Neither. The 2D payload is the same identifier written in a zero-padded 14-digit form, which is why a GTIN-13 shows as fourteen characters and a GTIN-8 does too. The readable string beside the linear code does not change. What would be wrong is a symbol holding a logistics-level number while the linear code carries the retail number, because those identify two different trade items and a till would be reading a case.
Can your floor add a 2D symbol to cartons I send you?
Where you supply artwork, identifier and placement instruction, a label is printed and applied like any prep task, and quoted as its own named task rather than folded into base handling. We do not choose the number, alter artwork, or print variable data nobody authorised. Before a first run we ask which register entry the code belongs to and verify the printed symbol against the file, because a symbol that scans only on the machine that made it proves nothing to a till in another country.
Reviewed 4 November 2026 (2026-11-04). The goal date, the dual-marking condition, the padded 14-digit encoding and the exclusion of GTIN-14 from retail points of sale were read that day from the GS1 retail-2D implementation guideline, release 1.1.0 ratified December 2025, published on ref.gs1.org; the adoption threshold is quoted there as a percentage of scanning solutions and is not repeated as a figure in this article. Retailers and marketplaces set their own inbound dates. Issued under the FulfillDock by SBT brand, a Shenzhen Shibotong International Logistics Co., Ltd. name since 2011, with labelling lines at Dongguan, Shenzhen and Suzhou. Related: the FAQ page, the prep and first-leg service page and the contact page.
