Quick answer
What should EU sellers check before China parcels ship?
Treat customs duty and product identifiers as separate checks. Confirm the applicable duty route with the EU declarant, then agree how each product identifier (PID) will be sent in the customs data. Before dispatch, match the identifier to the actual goods, listing, labels, invoice and safety file. Hold release if the carrier cannot accept the data or the identifier points to a different product.
China-side evidence module
EU low-value parcel duty checklist
The check is practical: connect each product type to the parcel, listing, label, invoice, product identifier, safety file, and seller handoff before the supplier or warehouse releases the shipment.
Before stock is packed
- Freeze the SKU-to-manufacturer reference map and record supplier aliases, product variants and approved changes
- Ask for original product and package photos, label files and the source of each identifier
Before the carrier handoff
- Compare the warehouse export and carrier input with the controlled product file; check truncation, blank fields and lost leading zeroes
- Obtain the declarant response for missing codes, bundles and special product circumstances before dispatch
Before payment or pickup
- Inspect buyer-approved sample scope and document mixed models, stale labels, carton identity and correction evidence
- Keep product safety evidence and customs data review separate; a matched code does not clear a safety defect
Release record
- Name the exact order, version, checked quantity, cleared lots, held cartons, responsible owner and outstanding conditions
- Reopen the review if the supplier changes the product, pack, identifier or dispatch data after approval
Why review the parcel file before November?
The Commission guidance sets November 1, 2026 as the mandatory PID date after the voluntary period that began in July. DHL confirms the operational scope includes qualifying online B2C imports of any value, while B2B transactions that are not distance sales are outside that requirement.
This is also an active implementation task: EasyPost published carrier-integration guidance on October 2. Its documentation exposes separate merchant, manufacturer and standardized identifier fields. A shipping platform accepting an order today does not show that the November data handoff is ready.
Use the remaining preparation window to resolve supplier identity gaps while stock is accessible. Build the identifier map before packing, then test the same records through the actual fulfillment channel. Do not wait for a customs query to discover that a factory code was omitted from the export file.
Sources: Commission guidance, section 3.5: PID timing and scope; DHL: B2C scope and line-item identifiers; EasyPost, October 2: carrier implementation update; EasyPost: electronic identifier fields
Separate the EUR 3 duty, the handling fee and product IDs
The EUR 3 temporary duty has applied since July 1, 2026 to qualifying consignments up to EUR 150. The Commission explains its item grouping by tariff classification rather than unit count: five identical T-shirts can attract one EUR 3 charge, while a T-shirt and a watch can attract two. Have the declarant confirm the grouping for the actual goods.
The Union handling fee is a different measure. The Commission adopted C(2026) 6694 on September 21 with EUR 2 per item; its text provides for application on the tenth day after entry into force following Official Journal publication. EU communications point to November implementation. Confirm the operative publication and collection date with the declarant before activating customer charges; the adopted amount does not mean it is already being collected.
Keep separate fields for duty, handling fee, VAT and carrier or broker charges in the commercial handoff. Identify the payer, calculation basis and applicable date for each. Do not describe every low-value parcel as costing a universal EUR 5: item groupings, tax treatment, service charges and the transaction itself still need review.
Sources: Commission Q&A: EUR 3 duty and item examples; Commission adopted act C(2026) 6694, Articles 1–2; Commission customs reform: implementation timetable
What if the factory code or barcode is missing?
Treat a missing manufacturer reference as a supplier-data issue to resolve before dispatch. The Commission guidance expects the manufacturer, producer or product supplier to assign a non-standardized identifier if one does not exist. A standardized identifier is reported where it exists; its absence is handled through the applicable declaration process, not by buying or inventing a barcode solely to fill the field.
The references do not need to be identical strings. A retailer SKU and a factory model can legitimately differ, but the evidence must show they identify the same product version. Ask the supplier to explain aliases in writing and retain the original reference. Do not silently replace a factory code with a warehouse code.
For a mixed carton, separate the physical stock by the approved variant and record which references belong to each line. If the pack quantity, size, colour, manufacturer or product changes, review the mapping before the corrected order file is reused. A parcel tracking number identifies a movement, not the product sold.
Sources: Commission guidance, section 3.5.4: missing manufacturer IDs and standard IDs
Test what reaches the declarant, not just the spreadsheet
Choose representative order lines from the actual fulfillment flow: a normal SKU, a variant, a bundle if sold, and a product without a standardized identifier if applicable. Ask the carrier or broker how each must be transmitted for the booked service. Keep the outbound record and the values received at the next step; a screenshot showing three empty field names is insufficient.
Compare seller export, warehouse record, shipping-system input and declarant receipt. Look for truncation, reordered columns, lost leading zeroes, merged variants and old cached product data. Ask how the service represents an absent standard identifier and which document or exception codes the declarant will use. Do not insert a guessed code into live declarations.
Fix the source record first, then repeat the transfer and inspect affected stock if labels or product versions were wrong. Record the test date, route, service, system version and responsible owner. Obtain the carrier operational cutoff for parcels arriving near November 1; a booking date in October does not by itself settle the import requirement.
Sources: DHL: provide product IDs electronically during shipment creation; EasyPost implementation reference: separate customs-item fields
- Require the seller to approve the product map, the supplier to confirm its references and the declarant to approve the customs data path
- Keep tariff codes in their classification fields; product identifiers are additional identity data
- Archive the accepted version with order, batch and carton evidence so corrections can be traced
A matching product ID does not establish product safety
Use the identity map to connect the goods with the buyer-approved safety file, warnings, instructions, responsible-party details and relevant test records. It is useful for finding mismatches; it cannot turn an unrelated report or incorrect label into evidence for the shipped model.
A China-side check can document what was accessible: sampled product identity, visible labels, package configuration, carton scope and correction photos. Technical testing, legal applicability and EU market access require the responsible specialists. Keep a safety hold in place even if the electronic shipment record passes validation.
Sources: Commission public control operation: product compliance findings

