EU Citizen · Open to Relocation
Since 1 November, an EU customs declaration for an e-commerce import is incomplete without product identifiers. Missing data is no longer a paperwork gap. It is a reason for the parcel to sit.
The European Commission confirmed it on 3 November: for goods sold in distance sales to EU buyers, every product on the declaration must carry three identifiers.
- Merchant product identifier (M-PID): the seller's or marketplace's own reference for that listing, unique on that platform.
- Manufacturer product identifier (NS-PID): the maker's model, part or style number.
- Standardised identifier (S-PID): an EAN, UPC, ISBN or similar barcode number. If the product has none, the declaration must say so with a specific exemption code.
Identifiers could be supplied voluntarily from 1 July 2026. From 1 November they are mandatory and enforced. The purpose is risk analysis at scale: when customs finds one unsafe or non-compliant product, it can extend that result to every identical item, even when other sellers list it on other platforms. And this is only the first step. The Commission says more comprehensive product data requirements will follow in July 2028, once the EU Customs Data Hub for e-commerce is live.
Carriers are already building it into booking. SingPost, for example, moved its commercial EU shipments to a DDP model from 1 November and added dedicated identifier fields, 6-digit HS codes and precise descriptions to its shipping portal so the data is complete before parcels leave.
The Commission's point is that the data usually already exists in listings, invoices and packaging. In practice, the problem is that it lives in three different systems and nobody owns it end to end. From the operations side, that is what I would fix this month:
1. Audit the catalog. Every SKU sold into the EU needs a merchant ID, a manufacturer reference and either a barcode number or a documented reason it has none.
2. Make it flow. The declarant, whether your IOSS holder or customs representative, can only report what your order feed sends them. Check the fields actually reach the declaration.
3. Fix supplier data at source. Ask manufacturers for model numbers and barcodes in the purchase order and on the packing list, not after a shipment is held.
4. Treat descriptions and HS codes as part of the same clean-up. Vague lines and wrong codes undo good identifiers.
5. Build for 2028 now. If your product master is messy today, the next wave of data requirements will cost more.
Clean product data is now a clearance asset. Sellers who fix the catalog before booking will move goods; the rest will be explaining delays to customers in peak season.
Is your product master ready to answer customs, or does it still live in spreadsheets?
#CrossBorderTrade #Customs #Ecommerce #EU #Operations #SupplyChain
