The EU PID Checklist: A Six-Step Walkthrough to a Painless Border Crossing

Many brands shipping into the EU have still not sorted their Product IDs yet. The deadline is November 1, and every product needs three identifiers by then. This post walks you through each of the steps you need to take leading up to November 1^st, and helps you get started today.

EU Product Identifiers have been optional since July 1, 2026 and become mandatory on November 1, 2026. For the time being, there’s no penalty for getting it wrong, so now is the time to find any gaps in your catalog or process and get them resolved before November.

The checklist

• Step 1: Pull your EU-bound catalog and check all three fields on every SKU
• Step 2: File a no-barcode declaration for any product without an EAN
• Step 3: Send NS-PID requests to every supplier that owes you one
• Step 4: Run test declarations now, while there's no penalty for errors
• Step 5: Add all three fields to new SKUs as you launch them
• Step 6: Name one owner for the November 1 cutover

Step 1: Pull your catalog and check all three fields

Export your full EU-bound catalog and confirm each SKU carries an M-PID (your platform SKU), an NS-PID (the manufacturer reference), and an S-PID (the standardized barcode, usually a 13-digit EAN). The M-PID is almost always already in your storefront. The other two are where the work is, so this export is how you see the size of the job.

Keep in mind that a single blank field is enough to stop a shipment at the border. Don’t stop at 98% or 99% coverage. Ensure that all of your products have an entry in these three fields.

Step 2: File a declaration for anything without a barcode

Where a product genuinely has no standardized barcode, you cannot leave the S-PID empty. You have to declare that none exists, which the European Commission guidance (PDF) treats as a deliberate exception.

Go through the SKUs from Step 1 that have no EAN and confirm each one has an active declaration in your data.

Step 3: Get NS-PID requests out to suppliers

The manufacturer reference has no required format. If a supplier has never assigned one, they are expected to create it, and that request sits in their queue on their timeline.

This is the step outside your control, which makes it the one most likely to slip past the deadline. Build your list of missing NS-PIDs from Step 1 and send the requests now. If you wait and plan to chase suppliers in October, you might end up sliding past the deadline with no NS-PIDs and getting shipments stopped at the border.

Step 4: Run test declarations while it’s free

Start feeding PID data through real customs declarations today. That will surface the mismatches, blank fields, and broken mappings now, while getting it wrong costs you nothing.

The voluntary window is the only time a rejected declaration is free. After November 1, the same error results in a stopped shipment. Send live PID data through a few declarations, watch what comes back, and fix the mappings before they matter.

Step 5: Cover new SKUs as you add them

Your catalog keeps moving. Any product you add to the EU catalog from here on needs the same three fields, and new arrivals are the easiest to miss because they were not in the export you started with.

A one-time cleanup goes stale the moment you launch a new product or product line. Build the three-field check into how you onboard products so you're prepared going forward.

Step 6: Name the owner for November 1

Name a point person to watch the switch to mandatory and define the steps they take if a shipment stops.

Give one person the cutover and the escalation path, so a shipment that holds on November 3 is caught by your team and not by the shopper.

More on this before November

PIDs are three data fields with a hard deadline, and they are one line item on a calendar that keeps filling up. We are staying on this topic as the date gets closer: the supplier NS-PID problem on its own, what actually happens to a shipment that stops at the border, and the wider pattern of EU rules landing in the same window. Watch Commerce Intelligence Alerts for each one.

Where FlavorCloud fits

That steady drip of new customs requirements is what makes international feel harder than a domestic market, and it is what FlavorCloud's platform is built to absorb. FlavorCloud is the AI-native Cross-Border Commerce OS, compliance-ready by design. Changes like PIDs flow through customs documentation and declarations without landing on your operations team, so your shipments keep clearing while the rules tighten around slower competitors.

That is the difference between treating international as a liability and treating it as compounding growth. Most brands generate 10 to 20% of revenue internationally. The leaders reach 40 to 60%, and that is the most defensible growth there is. The gap is not demand. It is risk, and every new customs rule is part of that risk. We remove it.

Selling into Europe and want PIDs handled before the November deadline? Talk to FlavorCloud.