Last updated: 2026-11-15 · By the ZhiShuYun Research Team
One-product-one-code (also called unit-level serialization) assigns a unique identifier to every individual product unit rather than to a batch or SKU. The identifier is printed as a QR or Data Matrix code and registered in a platform, so each scan proves which specific unit it was, when and where. It is the foundation for authentication, traceability, anti-diversion and consumer engagement.
| Granularity | One identifier per unit, versus batch-level or SKU-level coding |
| Carrier | QR code or Data Matrix, usually GS1 Digital Link-compatible |
| Core uses | Anti-counterfeiting, traceability, channel control, consumer marketing |
| Platform need | A registry that issues codes and records scan events |
| Production requirement | Marking on the line or pre-printed labels with verification |
Batch codes tell you which production run a product came from. Unit codes tell you which individual product it is — which matters when a counterfeit reuses a valid batch code, when a diversion case needs evidence of the specific unit, or when a consumer scans a product and you want to know whether it has been scanned before.
The second scan of the same code is itself information: legitimate resale, a duplicated label, or a copied code all produce different patterns. Batch codes cannot support that analysis.
A serialization platform issues codes in ranges, associates them with product and batch data, records scans as events, and exposes query and reporting interfaces. The association step — unit to carton to pallet — is what makes logistics traceability possible.
For regulated markets the same identifier can carry the additional payload: a DPP record in the EU, a Chestny ZNAK registration in Russia. One identifier layer, multiple compliance outputs.
Cost has two parts: per-code cost (typically fractions of a cent to a few cents depending on the carrier and platform) and the production change (pre-printed labels are cheap to start; inline coding requires equipment and integration).
The common mistake is to budget only for printing. Verification, exception handling and the data platform are where the operational value — and the operational cost — actually sit.
Unit codes alone are impractical in a warehouse: a pallet can hold thousands of units. Aggregation binds unit codes to carton codes and carton codes to pallet or shipment identifiers, so receiving and dispatch operate on packages while the system still knows exactly which units are inside.
Aggregation is also what makes recall precise. If a defect is traced to a production window, the association record identifies the affected units and the cartons and shipments they travelled in — without opening every pallet to scan each item.
Three outcomes justify the investment in most programmes. First, recall scope: the ability to name the affected units instead of a whole production period. Second, channel evidence: proof of where a specific consignment went, which is what diversion cases need. Third, consumer trust: a verification result the consumer can obtain without an app.
Everything else — dashboards, engagement campaigns, analytics — sits on top of those three. A programme that cannot produce the recall scope and the channel evidence is not yet a traceability system, whatever else it displays.
A batch-level recall forces a choice between recalling more than necessary and defending the decision to recall less. Unit-level records replace that judgement with a list: which serials were produced in the affected window, which cartons they went into, and which shipments carried those cartons.
The operational gain is not only the scope. It is the evidence trail for the regulator and the customer: you can show what was affected, what was quarantined and when. That record is also what makes a post-incident review useful, because the timeline of the defect is reconstructable rather than remembered.
Ask what the platform records at issuance, because a code that cannot be traced to a code order is a code anyone could have generated. Ask how the production association is captured, because a manual step at the line is where most programmes quietly lose the unit-to-carton link.
Ask what happens on the second scan of a code, because the answer reveals whether there is an exception process or only a consumer page. And ask for the export, in the format, before you sign — that single artefact tells you whether you own the record or are renting access to it.
No. The QR code is the carrier. One-product-one-code is the principle that each unit has a unique identifier, plus the platform that records it.
Not necessarily. Pre-printed labels can be applied to existing packaging with minimal changes; inline printing may require a packaging or equipment adjustment.
Yes, and that is usually the point: the same scan verifies authenticity, returns traceability data and can trigger a marketing action.
GS1 provides the identifier structure (GTIN plus serial) and the Digital Link resolution format; serialization is how you apply and record those identifiers per unit.
The platform records both scans. Whether that is a problem depends on context — resale, a duplicate label, or a copied code produce distinguishable patterns.
Start with one line, prove the record
The value appears when the record is complete, not when the code is printed. Pilot a single product line, measure first-read rate and association completeness, and extend only after those numbers hold.