M-PID & NS-PID: The Hands-On Guide to EU Product Identifiers (Nov 1 Deadline)

Your November 1 deadline just got more concrete. The €2 handling fee is a cost you can feel — but Product Identifiers (PIDs) are a compliance requirement: declare the wrong way, and your parcels sit at customs while carriers chase you (or your customer) for missing data.

The good news: PIDs are not hard to source once you know who's responsible for which one. This guide walks through both identifier types, exactly where each one comes from, and the checklist to complete before your first November shipment.

The two identifiers, and who issues them

Customs declarations for distance sales need a product identifier under data elements F48 / F49 / F53. There are two types, and the split is simpler than it sounds:

Type	What it is	Who issues it
M-PID	Merchant Product Identifier	The seller, marketplace or platform — whoever "merchandises" the product
NS-PID	Non-standardised Manufacturer Product Identifier	The manufacturer or supplier, for products without a standardised identifier

During July–October 2026, PIDs could be declared voluntarily. From November 1, they are mandatory in all cases. If a parcel arrives without them, expect clearance delays and follow-up charges — not a rejection notice weeks later, but a "fix this now" from your carrier while the parcel sits.

Step 1: Get your M-PID from your platform

The M-PID is the merchant side — the identifier that says "this product, as sold by this seller." That's the side you (or your marketplace/platform) control.

• Check whether your platform generates it automatically. Many order systems, marketplaces and shipping platforms can generate a merchant product identifier from your existing product data — often it's a system-assigned code tied to your product listing.
• Ask your app/ERP developer (or check your integration docs): "Do we emit a merchant product identifier for customs declarations (F48/F49/F53)?" If yes, find out whether it's per-SKU or per-listing — and make sure it maps to the product your customer actually receives.
• If nothing exists yet, set a simple convention — e.g. your product's unique ID in your store. What matters for customs is that the identifier is consistent between your declaration and the goods, not that it's a specific format.

Step 2: Source NS-PIDs from your suppliers

The NS-PID is the manufacturer side: the identifier the manufacturer or supplier would use on a customs declaration for that product. This is the one most sellers haven't asked for yet — and the one that becomes a real problem in November.

Here's the workflow:

2a. Check for a standardised identifier first

If your product already has a standardised identifier like a GTIN / EAN / UPC, you're partly there — the manufacturer side has something on file. Confirm with your supplier that the identifier they hold matches the product you're shipping, and record it in your product data.

2b. Ask your supplier for the NS-PID

For products without a standardised identifier, you need the supplier's own product identifier. Send this — it takes them two minutes to answer:

Hi [supplier],

We ship to the EU, and from Nov 1, customs declarations require a Product Identifier for each product. Do you have a manufacturer product identifier (NS-PID) you'd use on a customs declaration for [product name / SKU]? If the product has a GTIN/EAN, that works too — just confirm it's the right one for this item.

Thanks!

2c. If a supplier can't provide one

Flag it now, don't wait. A supplier without any identifier for their product is a clearance risk in November. Options:

• Ask for a photo of the product label/packaging — the identifier is often printed there even when the supplier doesn't know the term "NS-PID."
• If there's genuinely nothing, decide whether that product stays in your EU catalogue — because every unit you ship is a delay risk until an identifier exists.
• Record the gap in a simple spreadsheet (product → supplier → identifier status), and re-run it before your first November shipment.

Step 3: Make sure PIDs actually reach customs

Having identifiers in your product data only helps if they travel with the declaration. This step is a conversation, not a build:

• Ask your carrier or broker: "Does your integration transmit PID fields (F48/F49/F53)? What happens for orders where PIDs are missing?"
• Some integrations already support PID fields; some don't yet. You want the answer before your first November shipment, not after a parcel is stuck.
• If you use a third-party fulfillment or 3PL, ask the same question there — and check whether their system pulls PIDs from your store or needs them supplied separately.

Your November-readiness checklist

When	Action
This week	Confirm your platform emits an M-PID (or set your own consistent convention)
This week	Send every supplier the NS-PID question; log answers in a spreadsheet
Next week	Chase suppliers who haven't replied; fill gaps for products without any identifier
Before Nov 1	Confirm with your carrier/3PL that PID fields are transmitted (F48/F49/F53)
Before Nov 1	Re-check HS codes + country of origin — PIDs sit on top of correct item declarations, not instead of them

The trap most sellers will hit

Most stores will do the platform side (M-PID) and stop there — because it's a setting, not a conversation. The supplier side (NS-PID) is where the delays live: a supplier with no identifier, or a product whose GTIN doesn't match what's actually shipped. That's the gap that turns into "your parcel is on hold — which product is this?" emails in November.

Treat the NS-PID as an inventory question, like stock levels: you don't wait until an order arrives to discover you can't ship it. You check it before you list.

How DutyRight helps

DutyRight is a Shopify app that audits your products' HS codes, flags missing or incorrect codes and origins, and shows exactly how many declaration items you could legally consolidate. It won't issue your PIDs for you — but it makes the declaration data around them correct, which is where the costs and delays actually come from.

Key takeaways

• M-PID is the merchant side — from your platform/system; check it's emitted and consistent
• NS-PID is the manufacturer side — ask your suppliers now; it's the most common gap
• Products with GTIN/EAN: confirm the identifier matches what you ship; no standardised ID at all = flag and fix before November
• Confirm your carrier transmits PID fields (F48/F49/F53) before your first November shipment
• PIDs sit on top of correct HS codes and origins — fix the declaration data while you fix the identifiers

November 1 is two weeks out. The sellers who ask their suppliers this one question this week are the ones whose parcels sail through customs next month.