From 1 November 2026, businesses selling goods into the European Union must transmit product identifiers at the point of import. The obligation comes from Regulation (EU) 2026/382, the same instrument that abolished the 150 euro customs exemption and replaced it with a flat 3 euro per item tariff. Voluntary filing opened on 1 July 2026.
The codes themselves those already in use them for internal systems. But they will service as a shared reference point between a business and customs.
C127, C128, C129, and Y081 for exceptionsProduct identifiers are simply alphanumeric codes used internally by businesses. Effective November 2026 those codes are a necessary part of the data set transmitted systematically to customs.
That distinction matters more than it first appears, and it is worth being precise about why.
The June 2026 EU Guidance explicit goal is to improve the traceability of individual products. Once customs identifies a non-compliant product, it can extend the outcome of that single inspection cross referenced with the importer's internal records.
Inspectors are finite and the traditional answer for parcels was sampling. Product identifiers break that constraint by decoupling the finding from the inspection. One examination can yield a result that propagates across an entire product inventory.
Under sampling, a defect had a low probability of being caught and a contained consequence when it was. Under identifier-linked enforcement, the probability of exposure rises.
Since 8 July, roughly 600 products have had to be declared in advance to United States Customs and Border Protection, covering the content of the certificates of conformity required by the Consumer Product Safety Commission, with the product identifier among the required elements.
Two major customs authorities converging on item level identification within four months of each other is not coincidence. It is the same recognition arriving in two places: that parcel volumes have outrun physical inspection capacity, and that the only scalable answer is to make the data do the work.
The source material and much of the early commentary uses these three abbreviations without expanding them, which is where most readers stall. The distinction is about who owns the code and what it points to.
| Identifier | Owned by | What it anchors | Where it breaks |
|---|---|---|---|
| M-PID | Marketplace or platform | The listing as the platform knows it, linking the offer to the seller and the consignment | Platform feed does not reach the declarant, or reaches it after the declaration is filed |
| NS-PID | Manufacturer | The product at model or series level, guaranteed by the party that made it | Supplier will not or cannot supply it, common with private label and multi-tier sourcing |
| S-PID | Manufacturer | A more specific production level reference tying goods to a defined run | Exists in the factory system but never crosses into the seller's master data |
Supplying a code is not compliance. Where more than one identifier exists, the rule is to prioritize the identifier that maximizes control. That is a judgement standard, not a data entry standard. Document your selection logic down so that it is consistent, defensible and repeatable.
Compliance splits across three parties who do not report to each other:
| Party | Obligation | Practical exposure |
|---|---|---|
| Platforms | Manage the M-PID | Feed integrity, and delivering the code to the declarant in time to be filed |
| Manufacturers | Guarantee the NS-PID and S-PID | Accuracy at source, and willingness to release production level references downstream |
| Customs declarants IOSS holders or indirect representatives |
Formal declaration using TARIC document codes | Carries the filing liability while originating almost none of the data |
That last row deserves emphasis, because it is the structural tension in the whole design. The declarant is accountable for the accuracy of a field that the platform or the manufacturer controls. If you are an indirect representative, you are jointly liable on a declaration built from data you did not create and frequently cannot verify.
The mitigation is contractual rather than technical. Before 1 November, the data supply obligation should be written into your terms with platforms and suppliers: which identifier, in what format, on what refresh cycle, with what warranty of accuracy, and who bears the cost when it is wrong. Distributed responsibility has a well known failure mode, which is that every party assumes another party owns the field.
| Code | Use |
|---|---|
C127 |
Product identifier document code |
C128 |
Product identifier document code |
C129 |
Product identifier document code |
Y081 |
Declared where an exception applies and no product identifier is provided |
Confirm the exact mapping of C127, C128 and C129 to identifier type against the current TARIC publication and the 2 June 2026 guidance before configuring your declaration system. Document codes are the kind of detail that moves between draft and implementation, and a mapping error is silent until it is a rejection. Your broker or indirect representative should confirm the field mapping in writing.
Note also what Y081 represents an exception code. Every Y081 declaration is a documented assertion that no identifier was required, which means it is a queryable population. Patterns of use run the risk analytics of greater oversight by customs.
A Canadian merchant shipping direct to consumer parcels into the EU is in scope, whether selling through its own storefront or through a marketplace.
Three points that matter specifically on this side of the Atlantic:
Use the test period before November to review potential identifier error messages. It is the the most useful testing environment available.
November 2026 is a waypoint to the the new Union Customs Code in July 2028.
The pattern is clear: De minimis removal, product identifiers, greater oversight. Information transparency becomes structural to how goods move in the single market.
An alphanumeric code that uniquely identifies a specific product or model within a business What is new under Regulation (EU) 2026/382 is that the code must be transmitted to EU customs at the point of import on distance sales, converting a private inventory reference into a regulatory data element.
Mandatory from 1 November 2026. Voluntary compliance opened on 1 July 2026, allowing operators to test data flows.
They differ by who owns the code and what it points to. The M-PID is the marketplace or platform level identifier, managed by the platform. The NS-PID and S-PID are manufacturer side identifiers.
Declarants use C127, C128 and C129 to transmit product identifiers on the declaration. Y081 is used where an exception applies and no identifier is provided. Confirm the exact mapping against the current TARIC publication before configuring your system.
Responsibility is distributed. Platforms manage the M-PID. Manufacturers guarantee the NS-PID and S-PID. The customs declarant, in practice the IOSS holder or indirect representative, makes the formal declaration using the TARIC document codes. The declarant carries the filing exposure despite rarely originating the data, which is why the data supply obligation belongs in your contracts.
Yes.
Both come from Regulation (EU) 2026/382, which removed the exemption for consignments up to 150 euros and replaced it with a flat 3 euro per item tariff. The identifier obligation is a separate requirement but part of the overall effort of greater oversight.
A missing identifier where no exception applies is a declaration error, exposing the consignment to a hold, request for information and possible rejection.
The PID is the on ramp. The reform runs to July 2028 with the new Union Customs Code and the EU Customs Data Hub.
For most operators with meaningful EU parcel volume, yes. Voluntary filing is a low risk way to surface master data and revealing coding errors without a rejected declaration (until November).
Jet Worldwide has supported Canadian exporters through EU customs reform. Contact our team for support with building compliant programs.
This article summarizes Regulation (EU) 2026/382, the EU Guidance of 2 June 2026 and related reporting. Document codes, dates and scope should be confirmed against the current official publications before you configure systems or file. Nothing here is legal advice.