When Do You Need a New GTIN, and When Do You Need a Variant?
Supply chain wants a stable GTIN. E-commerce and EPR want data on every change. The GS1 Consumer Product Variant (CPV) and the 2D barcode let you have both.
Short answer: For fifteen years, supply chain teams and digital and compliance teams have been locked in an unwinnable argument about when a product change deserves a new GTIN. The linear barcode forced a single answer, and there is no single right answer. The 2D barcode removes that constraint. By combining a stable GTIN with the GS1 Consumer Product Variant (CPV, Application Identifier 22) inside a GS1 Digital Link, you can keep one commercial identifier while publishing a distinct data set for every physical specification behind it.
The problem: one identifier, three incompatible demands
Anyone who manages product data in consumer goods has received some version of these three messages, often from the same retailer, in the same quarter.
From supply chain: Please do not change the GTIN when only the recipe or packaging material has been updated. These changes create unnecessary cost and disruption.
From QA and sustainability: Please assign a new GTIN whenever the formulation or packaging composition changes. This is essential for tracking sustainability progress and accurate EPR reporting.
From digital commerce: Please update the GTIN for every new pack design or label update. The digital twin must match what consumers see online.
These are not the result of a badly run organisation. Each request is correct on its own terms, and they cannot all be satisfied by a single number.
Why the supply chain is right
A GTIN change is not a data edit. It is a commercial event. It triggers re-listing, new shelf and rack plans, phase-in and phase-out logistics across distribution centres, updated planograms, fresh listing fees, and a window where the old and new items compete for the same slot. Retailers absorb real cost every time it happens. When the change is a marginally different foil or a slightly reformulated marinade, and the product on the shelf is functionally identical to the consumer, that cost buys nothing.
Why e-commerce, sustainability and compliance are right
The digital shelf has no tolerance for approximation. If the pack in the warehouse contains 34% more post-consumer recycled content than the pack described on the product page, the product page is wrong. Under PPWR, EPR schemes, ESPR and the Digital Product Passport, that inaccuracy stops being a customer experience problem and becomes a reporting problem. You cannot report on a material change you never recorded, and you cannot record it if every version of the product shares one identifier and one data record that simply overwrites itself.
The word that causes the argument
The GS1 GTIN Management Standard requires a new GTIN for any substantial change to a trade item. The entire conflict lives in that one word.
Substantial for whom? For a distribution centre, substantial means the pallet pattern changed. For a compliance officer, substantial means the recyclability declaration changed. For an e-commerce manager, substantial means the on-pack claim changed. Those are three different thresholds, and no amount of rule-writing reconciles them, which is why fifteen years of increasingly detailed GTIN allocation guidance has not settled the question.
The real constraint was the barcode
The linear barcode carries one number. One number means one answer. As long as the GTIN was the only identifier the physical pack could express at point of sale, the industry had to choose a winner, and whichever side won, the other side operated on inaccurate data.
That constraint is now lifting. GS1's Sunrise 2027 initiative is moving retail point of sale toward 2D barcodes carrying a GS1 Digital Link. A Digital Link URI can carry the GTIN and additional qualifiers in a single symbol. The question stops being which team wins and becomes how do we structure the second layer.
The solution: two layers, one QR code
Layer 1: the GTIN stays stable
The GTIN remains what it has always been, the globally unique identifier of the Sales Unit and the number that transacts. Orders, invoices, EDI messages, point of sale scans and warehouse movements all continue to run on it, unchanged. Supply chain stability is preserved by leaving the supply chain alone.
Layer 2: the CPV carries the change
The Consumer Product Variant (CPV) is an existing GS1 identifier, Application Identifier 22, holding 1 to 20 alphanumeric characters. GS1 defines it as an element string used to distinguish one variant of a retail consumer trade item from another when the change does not require a different GTIN, but partners still need to communicate about it.
Critically, CPV is a key qualifier in the GS1 Digital Link standard. Under a GTIN, only three qualifiers are permitted: 22 (CPV), 10 (batch/lot) and 21 (serial), in that fixed order. So this is already valid syntax:
https://example.com/01/8765438765434/22/V004R003 The GTIN is globally unique. The CPV is unique within its GTIN. Together they form a unique key for a specific physical specification.
CPV is not theoretical. It has been supported in the Global Data Synchronisation Network (GDSN) since 2018, with a ratified implementation guideline (Consumer Product Variant in GDSN, Release 1.1, November 2024) defining five attributes and thirteen reason codes covering minor formulation changes, packaging changes with minor impact, artwork changes, marketing declarations, added languages, production in different locations, vintage, and time-critical promotions.
The missing piece: a format
GS1 specifies what the CPV field is. It does not specify what should go in it. The published examples are values like 123, 126, 128. In practice this means every company invents its own scheme, such as ABC-2024-Q3-rev2, NL-PLANT2-v4 or 2025-03-REFORM, and none of them mean anything to a trading partner.
A free-format field is not interoperability. It is a private note in a shared envelope.
A proposed convention: V###R###
We propose a single, self-explanatory structure for the CPV value, built on two dimensions.
V001R001
V = VARIANT, what is different at the same time. Variants run in parallel. Same GTIN, same commercial proposition to the shopper, different physical execution or origin. A second contract manufacturer. A different plant. A promotional pack running alongside the standard pack.
R = REVISION, what changed over time. Revisions replace one another within their own variant. Each R represents a new Manufacturing Bill of Materials. A recipe reformulation. A packaging material change. An assembly change.
Read it as: V004R003 is variant 4, in its third Bill of Materials revision.
Five rules
| Rule | Why it matters |
|---|---|
| Fixed 8 characters: V plus 3 digits, R plus 3 digits, zero-padded | Human-readable, machine-sortable, no parsing logic required |
| Numbered per GTIN | GTIN is globally unique; CPV is unique within it. GTIN + CPV is the key |
| V001R001 is the Primary Version | GS1's own term for the baseline the item reverts to |
| V is concurrent, R is transitional | Multiple variants live at once; within a variant, the higher revision supersedes |
| Never reused, never renumbered | A retired variant number stays retired, so history stays readable |
Worked example: private-label tilapia
A private-label frozen fish product, tilapia with Thai marinade. One Sales Unit. One GTIN. The brand owner sources it through a contract manufacturer who buys from seven suppliers in seven countries.
Today, that is one GTIN and one data record, and six of those seven specifications are invisible.
With the convention:
| Reality | CPV |
|---|---|
| Seven sources, all live in parallel | V001 to V007 |
| Each source reformulates on its own cycle | R increments within its own variant |
| Source 4, third recipe revision | V004R003 |
Country of origin, allergen detail, nutritional values and packaging composition can now differ per variant, and be published per variant, without a single re-listing.
A different manufacturer might use the same structure for a different purpose: V001 for the standard pack and V002 for the promotional pack, with R tracking formulation revisions in each. The convention does not prescribe what a variant means to your business. It prescribes only that variants are parallel and revisions are sequential.
Concurrent and transitional
This distinction matters more than it first appears, because it maps onto a distinction GS1 already draws.
- A transitional CPV represents a change where the new version replaces the old one. This is what GDSN documents today, and the assumed behaviour is serial: the newer data set overwrites the previous record.
- A concurrent CPV represents variants that exist in the supply chain simultaneously. GS1's own cited example is different production facilities.
Concurrent CPV is defined in the standard, but guidance for it is still in development. That is precisely the gap the seven-supplier case falls into, and precisely where an industry convention would do the most good.
In the proposed structure, V is concurrent and R is transitional. Nothing new is invented. The thirteen existing reason codes already sort naturally into these two groups. PRODUCED_IN_DIFFERENT_LOCATIONS and TIME_CRITICAL_PROMOTION describe variants. MINOR_FORMULATION_CHANGE, PACKAGING_WITH_MINOR_IMPACT, MINOR_ARTWORK_CHANGES and MARKETING_DECLARATIONS describe revisions.
What this does not break
The most common objection is the most easily answered.
Point of sale and warehouse systems read only /01/. They scan the GTIN and beep exactly as they do today. They neither see nor need the CPV.
EDI, ordering and invoicing are untouched. Those transact on GTIN. A CPV never appears on an order line.
Partners who are not ready keep working. If a retailer's systems do not support CPV, a new data set published for an existing GTIN simply overwrites the previous record, which is today's behaviour. Nothing fails. The benefit of versioning is unavailable until their systems are updated, but operations continue.
One symbol. Two audiences. Granularity without operational impact.
What it does require
Honesty about the remaining work is more useful than a clean story.
- The GTIN Management Rules still set the boundary. CPV is defined for changes considered insignificant to supply chain processes. Some sustainability-relevant changes may sit above that line today. Moving that boundary is an industry policy question, not something a format convention resolves on its own.
- CPV attributes are not yet in the Global Data Model (GDM), the harmonised attribute set most trading partners exchange by default.
- Concurrent CPV guidance is still being developed.
- The CPV becomes part of the artwork. Each variant and each revision carries its own QR code, and therefore its own artwork version. In practice this is far less disruptive than it sounds, for the reason set out in the FAQ below.
How SyncForce supports this
SyncForce is the Operating System for bringing packaged goods to market, the system of record where Sales Units, Products, Packaging, specifications and compliance data live together rather than in separate silos. That architecture matters here, because a variant is not a marketing attribute. It is a different Bill of Materials with different compliance consequences.
Available today
- Multiple Sales Units can share a single GTIN. The data model does not assume one GTIN equals one record, which is the structural prerequisite for everything below.
- Product, Packaging and Sales Unit are modelled as distinct objects. A packaging material change is captured as a change to Packaging, linked to the Sales Unit, not buried in a free-text description.
- Full specification and Bill of Materials management, so the thing a revision refers to actually exists as structured data.
Coming in H2 2026 (roadmap)
CPV support is on the SyncForce roadmap for the second half of 2026. Planned capability:
Guided variant and revision assignment. When a user creates a Sales Unit with a GTIN that already exists, SyncForce will ask a single question:
This GTIN already exists.
- Is this a new Variant? Existing variants are listed on screen, and the system assigns the next V.
- Or a new Revision of an existing variant? Select the variant, and the system sets R = R + 1.
Two clicks. The V###R### code is assigned automatically, and nobody has to memorise the convention.
One GTIN, many CPVs. Each variant and revision carries its own data set: specifications, images, claims, declarations and effective dates, all under one stable GTIN.
GS1 Digital Link generation, producing the resolvable /01/{gtin}/22/{cpv} URI for the on-pack 2D barcode.
CPV-aware publication, so the correct data set reaches the correct channel, with the CPV reason code mapped to GS1's existing values.
We are building this because for a large number of our customers it resolves a GTIN allocation problem they are living with today, and because Sunrise 2027 gives the industry a real deadline to align against.
What to do now
You do not need to wait for a finished standard to start.
1. Count your hidden variants. How many of your GTINs currently have more than one live specification, whether that is multiple plants, multiple co-manufacturers, or a promo pack alongside the standard? That number is your variant backlog, and it is usually larger than people expect.
2. Decide your revision threshold. Which changes will you version rather than renumber? Write it down and agree it across supply chain, quality and digital before a regulator or a retailer forces the question.
3. Check your PIM. Can it hold one GTIN with many variants, each with its own data set and effective dates? If not, that is the gap to close first, before artwork, before resolvers, before anything on-pack.
Frequently asked questions
What is a GTIN? The Global Trade Item Number, the GS1 identifier for a trade item and the number encoded in the barcode on a retail pack. It identifies the Sales Unit: the combination of Product and Packaging that a customer buys.
What is a Consumer Product Variant (CPV)? A GS1 identifier, Application Identifier 22, of 1 to 20 alphanumeric characters. It distinguishes variants of a retail consumer trade item when the difference does not warrant a new GTIN but trading partners still need to communicate about it. The brand owner assigns it.
Is CPV part of the GS1 standard, or is this a proposal? CPV is a ratified part of the GS1 General Specifications, a key qualifier in GS1 Digital Link, and supported in GDSN with a ratified implementation guideline. What is proposed here is a format convention for the CPV value, V###R###, because GS1 does not specify one.
Does adding a CPV break point of sale scanning? No. Point of sale and warehouse systems read the GTIN (/01/) only. The CPV is ignored by systems that do not need it.
When should I change the GTIN instead of the CPV? The GS1 GTIN Management Standard remains the authority. As a working principle: if the change alters what the customer is buying, such as a different net content, a different product, or a change to declared information that materially changes the offer, it is a new GTIN. If the customer is buying the same thing, made or presented differently, it is a candidate for a CPV.
How does CPV help with EPR and PPWR reporting? Packaging composition changes such as recycled content, material source and recyclability can be recorded and published against a specific variant and revision, with effective dates, instead of overwriting a single record. That produces a traceable history of what was actually placed on the market and when.
Do I need a different QR code for each variant? Yes, and this costs far less than it first appears. A new variant or revision almost always arrives with an artwork change already in progress: a different country of origin, a different manufacturer address, a changed ingredient declaration, a new claim. The QR code is regenerated as part of an artwork revision you were making anyway. In the seven-supplier example, each supplier already prints its own packaging with its own country of origin and manufacturer details, so the CPV adds no separate print event at all.
It is sometimes suggested that encoding batch/lot in the QR instead, and resolving the variant from it, would avoid this. It does the opposite. Batch and lot codes change with every production run, so the QR would have to be printed as variable data inline on the packing line rather than in the artwork. That is a real capability, and lines already running serialisation have it, but it is a substantially larger investment than versioning your artwork. The CPV changes when the specification changes, which is exactly when the artwork changes. That alignment is the point.
What is Sunrise 2027? A GS1 initiative to prepare retail point of sale systems to accept 2D barcodes carrying GS1 Digital Link, alongside existing linear barcodes. It is the enabler that makes a second identifier layer practical on-pack.
SyncForce is the Operating System for Bringing Packaged Goods to Market: commerce, customer and compliance data in one system of record. To discuss how variant and revision management would apply to your portfolio, get in touch.