.jpg?width=1024&name=social-asset-1(2).jpg)
Of the three EU Product Identifiers you need on every SKU by November 1, 2026, two are within your control. The merchant PID lives in your storefront and the standardized PID is typically the EAN barcode associated with the product (the 13-digit number you may already have in your product catalog). If your product does not have one, that also needs to be explicitly confirmed (i.e. handmade, artisanal, or niche manufactured goods). In reality, you'll still needs to locate that EAN, capture it at the SKU level, and transmit for import customs purposes. Even if the barcode physically exists, it is not automatically available in your product data.
The third one is a non-standardized manufacturer PID and that’s managed by the manufacturer of the product. It also happens to be required in all cases, with no exception starting November 1st, and it’s the one field on your catalog you cannot fill in yourself.
That means you need to coordinate with your suppliers ahead of November 1, or you’ll be on the hook for the liability.
What the rule actually says
The NS-PID is assigned by the manufacturer, producer, or product supplier and does not rely on any international standard. There is no required structure. In practice it is the model number, style code, or production reference your supplier already uses internally, something like MX-2024-BLK-L.
The EC guidance assumes most products already have one, because manufacturers generally need a reference to track warehousing and sales. Where none exists, the manufacturer is expected to assign one. And the supplier carries an implicit responsibility to pass that identifier down the chain to whoever files the customs declaration. While the obligation may be the supplier’s, you’ll be the one facing a stopped shipment if you don’t report the NS-PID with it.
Why this is the riskiest step
The other two PIDs move on your timeline. This one moves on your supplier's. A request to assign or surface an NS-PID lands in their queue behind everything else they are doing, and you have no lever to speed it up. If you wait too long, you might not be able to get NS-PIDs for your full catalog before the deadline.
How to approach the requests
Rank by exposure, not alphabetically. Sort your missing-NS-PID list by EU shipment volume. The supplier behind your top ten EU sellers matters more than the one behind a long-tail SKU that moves twice a quarter.
Ask a specific question. Don't ask whether they support EU PIDs. Ask for the non-standardized manufacturer product identifier for each SKU, name the field, and reference the November 1 EU customs requirement. Give them the exact list of SKUs and a date.
Offer the shortcut the guidance allows. The manufacturer chooses whether to use the standardized barcode (S-PID) as the NS-PID to simplify their side. This decision is entirely up to the manufacturer and the merchant is not able to determine this.
Have a plan in case you don’t hear back. For a supplier who goes quiet, escalate through your account manager, and if a product genuinely has no barcode and no manufacturer reference, be ready to limit shipments of that item into the EU until you get one.
Where this leaves you
A blank NS-PID behaves exactly like a blank anything else on this rule: an empty field stops the shipment at the border. This particular field depends on a party outside your four walls, which is why it needs to be the first one you start.
The steady drip of requirements like this is what makes international feel harder than a domestic market, and it’s what FlavorCloud's Cross-Border Commerce OS is built to absorb. AI-native and compliance-ready, it routes new customs data through declarations without landing on your ops team. That is the difference between treating international as a liability and treating it as compounding growth. Most brands sit at 10 to 20% of revenue internationally. The leaders reach 40 to 60%. Every rule you clear cleanly is part of closing that gap.
Selling into Europe and want your PIDs handled before November? Talk to FlavorCloud.
