European Commission guidance on low-value imports, published on June 8 and updated on July 20, states that a temporary flat customs duty of EUR 3 per item applies from July 1, 2026, to relevant low-value consignments up to EUR 150 imported from outside the EU. The same guidance says Product Identifiers may be declared voluntarily from July 1 and become mandatory from November 1, 2026.

For a cross-border seller, this is not simply another field in a shipping form. The operating requirement is to make the sales SKU, physical item, customs declaration line, and supporting product record refer to the same object. If those identities drift, a technically complete submission can still describe the wrong product.

A channel SKU is not always a customs item

Channel SKUs are often designed for merchandising. They may encode color, size, bundles, free accessories, packaging, or a regional version. A customs record concerns the actual items being imported. One platform SKU may contain several declarable components, while several channel SKUs may point to the same base product with different presentation.

Sellers need a hierarchy that separates the master product, variant, bundle components, packaging unit, and market version. Each shipped line should trace to the order, sales SKU, product identifier, quantity, value, origin, classification basis, and evidence record.

The mapping should not depend on a broker's private spreadsheet. It belongs in the product and order data model, with controlled ownership. The logistics provider can transform the data for its system, but the seller should retain the authoritative relationship and the record of what was transmitted.

Govern versions and exceptions

A product rename, package change, component substitution, or marketplace migration can break the mapping. Every change should have an effective date, predecessor relationship, and inactive state. Historical shipments must continue to resolve to the identity and evidence that applied when they were declared.

Exceptions deserve explicit workflows. Samples, replacements, returns, repaired goods, gifts, and bundles may require different treatment based on the applicable rules. The commercial description should not silently determine the customs structure. Qualified customs, tax, and legal professionals should confirm the correct approach for the actual product and transaction.

Transmission needs readback. An order platform can report that a payload was sent while the carrier or declaration intermediary received a truncated, reformatted, or rejected identifier. Teams should compare the submitted value, received value, rejection reason, correction, and final declaration record.

What this means for Chinese exporters

Product-data quality is moving closer to customs execution. Information that was previously completed manually at the logistics stage becomes harder to manage consistently as channels, warehouses, and parcel volume expand. Product, ecommerce, warehouse, logistics, finance, and compliance teams need one identity map rather than separate versions.

Bundle and promotional design also need review. A marketing page may present several objects as one offer, but the declaration still has to reflect the applicable customs treatment. The company should keep the customer-facing offer, warehouse pick list, invoice line, and customs line connected without assuming they are identical structures.

This article summarizes the cited Commission guidance and does not provide transaction-specific customs, tax, or legal advice. Exporters should confirm tariff classification, valuation, origin, product identification, and procedural obligations with qualified specialists and their declaration partners.

The readiness test should use real orders from several channels and product types. A clean master-data diagram is useful, but only an end-to-end rehearsal can expose field truncation, bundle ambiguity, stale identifiers, and ownership gaps.

Action checklist

1. Export every active sales SKU and separate base products, variants, bundles, accessories, and market versions. 2. Assign a stable product identifier to each physical item and retain effective, replacement, and retirement dates. 3. Map the SKU to the order line, customs line, product identifier, origin, classification basis, and evidence record. 4. Create exception paths for samples, replacements, returns, repairs, gifts, and bundles. 5. Complete a field mapping with carriers and declaration intermediaries before the November requirement. 6. Test both transmission and readback, including rejected, reformatted, and corrected values. 7. Trigger a customs-identity review whenever the product, component, package, or channel record changes. 8. Have qualified professionals confirm the treatment for the actual goods and transaction model.

Sources