English
Español
EU Product Identifiers From 1 November 2026: Which Field You Own
Product identifiers are a data task, not a labelling task. From 1 November 2026 European Union customs expects three product-identifier fields to accompany low-value parcels entering the bloc, and the field a seller already owns is not always the field a customs entry needs. The work before that date is mapping which identifier exists in your own system, which one has to come back from the factory, and which one a scanner at the shelf already reads.
Key facts
- Three fields, three owners. The merchant identifier is the code you sell under, the maker identifier is the code printed by whoever produced the goods, and the standard barcode is the globally registered number on the packaging. A fulfilment provider cannot invent the second or the third.
- The effective date is fixed. The European Commission's customs-reform track puts the identifier requirement on entry declarations for parcels from 1 November 2026, ahead of the wider reform milestones that follow it.
- A missing field is a declaration problem, not a paperwork nicety. An entry that cannot state the identifiers is exposed to hold, return, or an infringement finding against the declarant, which in practice is the importer of record named on the shipment.
- Our side of it is captured at receiving. Intake at the Shenzhen, Dongguan and Suzhou warehouses records the three fields against each stock-keeping unit, so the value travels with the unit instead of being re-typed per order.
Which identifier means what
The three fields describe the same object from three different seats. The merchant-side identifier is whatever a seller lists the item as — an internal code, a variant code, a model string on the listing. The maker-side identifier is what the producer attaches to the article: its own product code, model reference, or type designation in the specifications. The standardised barcode is the registered global number, the one a retail scanner reads and the one that resolves ambiguity when two sellers use the same internal name for different goods.
Customs wants the article described in a form it can match against a risk list. A seller code that exists only inside one storefront does not, which is why the requirement reads as a set of fields rather than one field.
| Field | Who originates it | Where it normally lives | What we can do with it |
|---|---|---|---|
| Merchant-side identifier | The seller | Storefront catalogue, ERP line, channel feed | Carry it through the order and print it on the pick document |
| Maker-side identifier | The producer | Packing list, product spec sheet, carton stencil | Capture at receiving and bind it to the stock unit |
| Standardised barcode | The producer or its registration body | Retail packaging, GTIN registry | Scan-verify at the pick face and pass it into the entry data |
| Commodity code | Declarant or customs broker | Commercial invoice, classification note | Reuse the stored value per unit; classification itself stays with the broker |
What the 2026 sequence actually changes
Two separate 2026 measures are easy to conflate, and they arrive on different dates. One changes how low-value consignments are treated on duty; the other, dated 1 November 2026, requires the identifier fields on the declaration itself. A seller who adjusted only for the first can still be short on the second, because product identifiers are not derived from a tariff line.
The practical consequence is that a parcel lane is only as good as the data behind each unit on it. An operator with no stored maker identifier is not delayed by the border in the abstract; it is delayed one consignment at a time, and the delay lands on the customer who was told the lane was estimated at five to nine working days.
How intake at our three China warehouses handles it
Identifier capture is a receiving step, because that is the only moment the physical article, the carton paperwork and the supplier are in the same room. When a carton reaches Shenzhen, Dongguan or Suzhou, the receiving record for that stock unit is expected to carry the merchant code, the maker reference and, where the packaging shows one, the standardised barcode. Stock arriving without the maker reference is held as an incomplete unit rather than shelved as clean stock, which keeps the gap visible to the person who can close it instead of surfacing it at a border three weeks later.
None of this moves responsibility. On a delivered-duty-paid lane the importer of record and the declarant are named positions, and a declaration is judged against the documents the shipment carries. What a fulfilment floor controls is whether the data is present, stored and reproduced on every outbound unit — the same logic behind our published mis-pick rate below 0.01 percent, measured per order line rather than per order.
What to ask your supplier before November
Three questions close most of the gap. Which identifier do you print on the article or its packaging, and is it stable across production runs? Do you hold a registered global number for this model, and does it change when the model is re-versioned? Can the packing list carry the maker reference in its own column rather than in a free-text remark? A supplier who answers all three in writing is usually structured for it already.
Three questions buyers ask us about the identifier fields
Can you create a maker-side product identifier for my goods if the factory does not have one?
No, and a provider who offers to is worth questioning. The maker identifier is an assertion about who produced the article and under which internal reference it is defined; it is issued by the producer, and no warehouse service legitimately substitutes for it. What our receiving team can do is record the value printed on the carton stencil or spec sheet, flag a unit that arrives without one, and hold that unit as incomplete so it never reaches a declaration as if the field were clean. What we cannot do is invent a code and let an entry go out under it, because the consequence of a bad declaration falls on the importer of record named on the paperwork.
Do you re-key these fields for every order, or store them once?
Once, at the unit level. Re-typing product data at pick time is how a clean lane acquires a wrong commodity code, so the identifier fields are bound to the stock-keeping unit on receipt at Shenzhen, Dongguan or Suzhou and reproduced on each outbound record without manual entry. That is also why an order line traces backwards: the code that shipped is the code that was recorded, with the same receiving document behind it. For a catalogue that changes often the storage is versioned, so a re-versioned model does not inherit the barcode of the run before it.
What happens to my parcels if a field is still missing on 1 November 2026?
The realistic outcomes are a held entry, a return of the consignment, or an infringement finding against the declarant — and none is resolved by a warehouse, because the missing value is not in the warehouse either. The exposure concentrates where a seller has many small units from many suppliers, since each incomplete unit is its own gap. Close the data on the slowest supplier first rather than the largest: the tail of small factories is where a maker reference is genuinely absent.
Data reviewed on 2026-10-30 against the Commission's customs reform file and carrier guidance published this quarter; the rule set is dated from official sources rather than from carrier marketing. Transit figures quoted on this page are typical estimates, not a promise of delivery.
Published under SBT FulfillDock by Shenzhen Shibotong International Logistics Co., Ltd.
Related: the full question list, how our fulfilment services are set up, and the European Commission customs reform file for the dates behind this summary.
