EU Product Identifiers Go Live Today - What Shopify Exports Miss
EU product identifiers are mandatory from today. Shopify's export has two of the three codes. Here is how to source the third before you ship.

Every EU customs declaration for a sub-EUR 150 parcel to a consumer now needs three codes per item: your SKU, a retail barcode, and the manufacturer's own part number. Shopify's product export carries two of them. The third one - the manufacturer code - is why most solo stores are not ready for EU product identifiers today.
Open Products in your Shopify admin. Pick any variant that has ever been sold to an EU customer. Open the Barcodes section on that variant. If you see one typed entry labeled ns-pid, you are in better shape than most readers of this post. If you see a blank, a dash, the word TBC, or your own SKU typed back in the barcode field, your next EU label booking fails, and you were meant to fix it before this morning. The wall has a name: EU product identifiers.
The three codes, and the one Shopify never had a field for
Three codes. One SKU, one retail barcode, one manufacturer reference. That is EU product identifiers in a sentence.
The Commission's guidance calls them M-PID, NS-PID, and S-PID. M-PID is your own code. In Shopify this is the Variant SKU, which has lived on the product record forever. S-PID is the standardized retail identifier: GTIN, EAN, UPC, or ISBN. In Shopify this is the Variant Barcode, also an old field. Both are easy to find in the admin and both export cleanly to CSV.
NS-PID is where the trouble starts. It is the manufacturer's or supplier's own internal part number for the item - the factory's reference. If you resell goods, it is the number the maker uses, not the number you use. If you make the goods yourself, it is a code you invent and apply consistently. Until October 2026 Shopify had no dedicated field anywhere in the product admin for this value. If you looked, you did not find one. If you looked carefully you found a workaround involving a variant metafield, which the CSV export then refused to include.
Shopify shipped a native NS-PID barcode type on variants in October 2026. The Barcodes section on a variant now accepts multiple typed entries - you can store a GTIN and an NS-PID side by side, each with its own type tag. The field finally exists. The policy question is whether you have the manufacturer codes to put in it.
What does your Shopify export actually have today?
Export your products CSV. You get Variant SKU and Variant Barcode columns. The SKU satisfies M-PID. The Barcode column satisfies S-PID when it is populated with a real GTIN - not when it holds a placeholder, your SKU typed back in, or the word UNKNOWN.
As of October 2026, the Barcode column also exports NS-PID values when they are stored in the native NS-PID barcode type. A merchant's test export dated October 21 wrote them in a ns-pid:CODE shape inside the same column, next to the GTIN. The practical implication: if you populate NS-PID through the admin UI, it travels in your CSV. If you still store it in a variant metafield, it does not - variant metafields have never been included in CSV import or export, and that limit has not changed with the barcode-type update.
Two caveats on the new native path. First, reimporting a CSV that contains ns-pid:CODE entries has not been publicly tested as of late October 2026. If you plan to bulk-edit a hundred variants in a spreadsheet and reimport the whole catalog at once, test with one row before you commit the rest. Second, the order inside the Barcodes section matters. NS-PID has to go after the standard retail barcode, not before it. Shopify sales channels read the first barcode slot as the primary GTIN. Put the NS-PID in position one and your Google Shopping feed will treat the manufacturer code as your EAN, which is a different compliance problem on top of this one.
If you want a mechanical check that catches these mistakes across a whole catalog, PIDReady is a free Shopify app that scans every variant, flags blank or placeholder barcodes, and bulk-fills NS-PIDs. I am not involved with the project. It is the first tool in the Shopify ecosystem built specifically for this requirement, and it does the thing it says on the tin. The free plan covers unlimited one-by-one fixes and 25 bulk fixes per month; the USD 9.99 tier raises the limits for the duration of catch-up work.
Where does the manufacturer code come from if you did not collect it?
Email your suppliers. There is no shortcut.
You want the manufacturer's or supplier's own internal part number per variant: model code, style code, factory reference. The format does not matter to EU customs. Consistency does. If you resell goods from three suppliers, you may end up with three different format conventions coexisting in your catalog, and that is fine. What EU customs will not accept is a blank field where a code should live.
If you make the goods yourself - handmade candles, print-on-demand apparel, custom embroidery, small-batch anything - you create your own code and use it. The Commission's guidance treats a self-assigned manufacturer reference as a valid NS-PID so long as you apply it consistently across variants. A reasonable rule for a solo maker: use the SKU as both M-PID and NS-PID, document that you did it on purpose, and move on. For products with a genuinely non-existent retail barcode (handmade, custom, unbranded bulk), customs accepts exception code Y081 - but Y081 is a positive declaration, not an absence. A blank Barcode cell is not Y081. Some carriers auto-apply Y081 when they see a blank. Others do not. Confirm with yours before you rely on it.
The honest unknown here is the time cost of the supplier emails. I underestimated it the first weekend I spent on this. For a small catalog with eight suppliers I lost most of a Saturday to a thread of "do you mean the code on the inner carton or the one on the invoice line," and still finished with two blanks that needed a follow-up on Monday. If your catalog has 500 variants spread across 30 suppliers and you have not started, the work is more than one weekend. If your situation looks like that and you want a second pair of eyes on the data model before you commit, the first chat with a help1 expert runs free for the opening fifteen minutes and a good use of that quarter-hour.
What breaks first if you ship an EU parcel today without these codes?
The label booking.
UPS began checking for EU product identifiers on October 25 for some API-connected customers. FedEx started October 26. FedEx has stated that from today, labels will not be created via Ship Manager or the API for B2C EU shipments without the codes present. The failure mode is not "parcel shipped and then held at the border" first. It is "shipping software refuses to generate a label." For merchants connected through FedEx or UPS APIs, enforcement already began last week.
A specific wrinkle for FedEx: Ship Manager and the legacy FedEx WebServices API will not support the typed PID fields themselves until March 2027. Even once you have the codes in Shopify, you will still have to type them onto the commercial invoice or packing list manually, and FedEx staff transfer them at their end. That four-month gap is public and acknowledged. UPS, DHL Express UK, Royal Mail, and Parcelforce all have dedicated declaration fields that your shipping integration needs to populate correctly. Zenstores and ShipTheory updated their Shopify integrations to read the native NS-PID barcode type. Shipmate historically defaults NS-PID to the merchant's SKU, which is correct only when the SKU happens to be the manufacturer's code - wrong for most stores that buy wholesale, so audit the mapping in whatever shipping tool you use.
The second thing that breaks today is unrelated to identifiers but hits the same parcels: Regulation EU 2026/2108, published in the Official Journal on September 19, introduces a Union handling fee of EUR 2 per item type per parcel from today. It stacks on top of the EUR 3 flat customs duty for sub-EUR 150 orders. For a parcel containing a t-shirt and a mug (two tariff lines, two item types) that is EUR 6 in duty plus EUR 4 in handling, so EUR 10 of fixed charges on a EUR 40 basket. The handling fee has no EUR 150 ceiling. Even your high-value EU orders owe it. If you have been quoting EU landed cost at the old numbers, your margin math is wrong as of this morning. Our earlier post on what EU compliance costs a solo UK store covered the earlier layers of this stack; the handling fee is the newest piece on top.
September 2027 is the date to watch for the next escalation. The new EU customs fines regime for sellers who repeatedly file incorrect customs information takes effect then. Between now and September 2027, non-compliance mostly produces held or returned parcels and friction with carriers. After September 2027 it means money. Nothing in the November 1 regulation itself writes a grace period into the deadline; the practical grace comes only from carriers like FedEx whose own software is not ready for the typed fields yet.
A 20-minute version of the compliance checklist
If you are reading this on November 1 and have done none of the above, this is the order to work in:
- Export your products CSV. Scan the Variant SKU column. If any row is blank, assign a code. Shared SKUs across sizes or colors are also invalid for M-PID; a t-shirt in three colors and four sizes needs twelve distinct SKUs, not one.
- In the same CSV, scan the Variant Barcode column. Blank cells are blank. Placeholder values (TBC, UNKNOWN, 0, the SKU repeated) also count as blank. For products that actually have a GTIN, fill it in. For products that genuinely do not, note them so you can declare the Y081 exception when you ship them.
- In the Shopify admin, open a representative variant and look at the Barcodes section. If you see only one single Barcode field and no typed-barcode interface, your store has not received the October barcode-type update yet. In that case the fallback is a product metafield definition for NS-PID; FlavorCloud and Zenstores both document the setup.
- Install PIDReady or an equivalent tool and run a catalog scan. The scan tells you how many rows are missing which identifier. The number is usually larger than the merchant expected. Mine was.
- Email your top five suppliers today for their part numbers. The remaining suppliers can wait a day, because the parcels going out this week are almost certainly from those five anyway.
- In Shopify Flow or Shopify Automations, create a hold rule for EU-destined orders where a variant has a blank NS-PID or a blank Barcode. That is the safety net Zenstores recommended on October 15 and it is cheap to put in place while you catch up on the data.
The rule covers consignments with an intrinsic value of EUR 150 or less. Higher-value orders follow the standard H1 customs procedure and sit outside the PID scope for now. The EUR 2 handling fee has no value ceiling, so it applies regardless. Managed Markets merchants should verify their exposure directly with Global-e - the public guidance is silent on whether Global-e absorbs the identifier obligation on behalf of the merchant, and no Shopify staff reply has clarified this yet.
One honest caveat about the regulation reading. On October 3, a merchant on the Shopify Community pointed out that the TARIC code mapping used by some vendor guides (C127 for M-PID, C128 for NS-PID, C129 for S-PID) does not appear verbatim in the regulation text. A separate practitioner source confirms the mapping is correct for the specific declaration procedures used on low-value B2C parcels, but if you are building an automated declaration pipeline, verify the exact codes against your carrier's documentation. For a merchant doing the data entry by hand, this does not change the three fields you need to populate; the carrier handles the mapping on the other side.
So here is the question for the next hour. Of the three EU product identifiers - M-PID, NS-PID, S-PID - which one can you not name right now for every variant your store has ever sold to an EU customer? That is the one to spend the next hour on. The others can wait until Monday.
Still stuck? Talk to an expert.
Our vetted Shopify experts can fix this issue for you in a live session. $39 per session. Your first 15 minutes are free.