Product identifiers from 1 November 2026: What China sellers must prepare

The EU low-value consignment notice names 1 November 2026 as the date when Product Identifiers (PIDs) become mandatory. For sellers shipping from China, this is primarily a data-quality project: a marketplace SKU, customs code and description must refer to the same sold unit.

A PID does not replace a commodity code

The identifier complements customs data. Define which value uniquely identifies a variant, bundle or spare part.

Separate variants

Colour, size, set contents and material can affect classification or value. Do not use one catch-all SKU for variants treated differently at customs.

Confirm the carrier feed

Find out whether PID, value and origin come from your feed or the marketplace. A free-text fallback creates systematic errors at scale.

Practical checklist

1. Export the variant catalogue and give every sold unit a stable identifier.
2. Link the PID to code, origin, net weight and unit value.
3. Send test orders through marketplace, carrier and customs interfaces.
4. From 1 November, approve listing and bundle changes with a data check.

<!-- Longform expansion: research review 2026-09 -->

Decision frame for your import

From 1 November 2026, product identifiers (PIDs) become mandatory in the relevant low-value data sets. C127, C128 and C129 distinguish manufacturer, non-manufacturer and, where available, seller product IDs; Y081 records the exception where no seller PID exists. This is a data-quality obligation, not a new shop SKU.

Data and document pack per item

Keep GTIN or internal SKU, manufacturer, brand, model, variant, dimensions, material, image reference and any seller PID per item. The identifier must describe the same product on invoice, packing list, product page and customs message. Version changes: a new model or material packaging change must not silently remain under an old identity.

• Maintain one SKU/PID table with manufacturer and seller roles.
• Detect duplicates, typos and inconsistent spellings before export.
• Test C127/C128/C129 and Y081 with the broker in a sample message.
• Link ID changes to product approval, photos and the technical sheet.

A verification workflow from supplier to import

1. Merge all low-value SKUs from shop, ERP and supplier lists.
2. For each SKU, establish who is manufacturer, non-manufacturer and seller in the shipment.
3. Request missing IDs and reconcile identity with sample and data sheet.
4. Test a representative H7/H6/H1 scenario and log rejection errors.
5. Before November label printing, check that ID and goods description are current.

A worked decision example

A retailer sells under its own brand but uses two factories. The internal SKU is the same, but the manufacturer models are not. The PID table separates brand, manufacturer and model and assigns each plant correctly. A plant change creates a new approved mapping while the shop SKU can remain stable.

Common failure modes and countermeasures

• Reporting the shop SKU as the manufacturer ID — separate roles and fields.
• Using Y081 as a convenient default — record it only when no seller PID exists.
• Maintaining an ID only on the product page — synchronise invoice, packing list and customs message.
• Combining variants and plant changes under an uncheckable ID — define identity rules.

Message to send to the Chinese supplier

Request structured product identity data:

For each SKU, please provide manufacturer, model, brand, variant, internal item number and available GTIN/PID. Please state the actual manufacturing plant and notify us before shipment of model, material or packaging changes. Please use the same spelling on invoice, packing list and product label.

Release criteria for the file

A release is defensible only when four questions can be answered from the same record: What exactly was checked? Which SKU, batch, route or period does the statement cover? Which primary source or supplier document supports it? Who assessed the deviation and when is it reviewed again? Put those answers in the inspection report instead of marking a line only “passed”. Link the file to the order, sample and receipt. If evidence is missing, give the line an “open” status with an owner and due date. This keeps later corrections traceable and lets procurement distinguish evidence from assumptions.

Follow-up and recheck

Approval is not the end of the check. Set a trigger for the next review: a new batch, material or process change, an authority notice, a price or lead-time deviation, or the scheduled review date. A short monthly reconciliation of orders, supplier data and received goods catches drift earlier than an annual catch-up. When a deviation appears, hold the affected batch, obtain a written supplier response and reopen approval only after a documented corrective record.

<!-- Release template: research review 2026-09 -->

Internal release template

A check mark saying “reviewed” is not enough for this topic. In one short line, state that maintain one SKU/PID table with manufacturer and seller roles.. Add the exact scope (SKU, batch, plant, shipment or period), the primary source and document version. The second line records the open assumption or deviation, its owner and due date. The third line records the release decision and which shipment or version remains on hold. Another colleague should be able to reproduce the decision without searching an entire email thread.

Conclusion

Preparation is manageable if you start with the China SKUs that sell most. The key is an end-to-end test, not merely another PIM column.

Frequently asked questions

Does this apply only to large marketplaces?

The EU notice concerns e-commerce low-value consignments. Confirm your specific shipping model and implementation with the platform and carrier.

Can my SKU simply be the PID?

Only if it is stable, unique and passed through every system. An internal SKU without interface mapping is not a reliable process.

Does every small parcel need a new PID?

Not every parcel needs a new product identity. The ID must identify the actual product, model and responsible role unambiguously.

What if there is no seller product ID?

The EU instructions provide an exception code for that case. Record why no seller PID exists and confirm the format with the broker.

Sources

• EU Customs: Product Identifiers