EU Customs 2026: The Shopify Merchant's Essential Guide to Product Identifiers

Alright, folks, let's talk about something that might seem a little far off, but trust me, you'll want to get ahead of this: the new EU customs requirements for product identifiers coming into full effect on November 1, 2026. If you ship physical goods from outside the EU to consumers within it, this is for you. The good news? Our Shopify community has been digging into it, and we've got some solid insights to share to help you prepare.

As migration experts at Shopping Cart Mover, we understand that data integrity is paramount, especially when facing evolving international trade regulations. This isn't just about avoiding penalties; it's about ensuring smooth, uninterrupted delivery for your EU customers and maintaining your brand's reputation.

I recently followed a really insightful discussion started by Jamelight in the Shopify forums, where they broke down what's needed and what Shopify's current export capabilities offer. It’s a vital topic because getting this wrong could mean delays, issues at the border, or even returned shipments – all of which impact your bottom line.

The "Big Three" Product Identifiers You'll Need by November 2026

From November 2026 (though voluntary compliance started July 2023, with no penalties during the voluntary period), EU customs declarations will require three specific product identifiers for each item. Jamelight laid these out clearly, using the names from the Commission's customs guidance:

• M-PID (Merchant Product Identifier): This is your own internal product code. For most Shopify stores, your SKU (Stock Keeping Unit) will serve this purpose. The key here is that every variant must have a unique SKU. Repeated or blank SKUs are a red flag you'll need to address.
• NS-PID (Manufacturer/Supplier Product Identifier): This is the manufacturer's or supplier's own model or part number for the item. This is where things get a bit tricky with Shopify's default setup, as there isn't a dedicated, standard column for this in your product exports.
• S-PID (Standardized Identifier): This refers to a globally recognized identifier like a GTIN, EAN, UPC, or ISBN. If an item truly has no such identifier, an exception code (Y081) is used. It's crucial not to confuse "blank in my export" with "doesn't exist."

Shopify's CSV Export: What It Has and What It Doesn't

When Jamelight dove into Shopify's product CSV export, they highlighted a few key points that every merchant needs to understand:

1. M-PID (SKU): Your SKU works great as an M-PID, but only if every product variant has its own unique SKU. If you have products with multiple variants (e.g., different sizes or colors), each variant must have a distinct SKU.
2. S-PID (Barcodes): Since September 2023, Shopify's product export includes a "Barcodes" column. This column is quite versatile, capable of holding up to 20 typed values per variant (e.g., gtin:00012345678905; upc:012345678905). For customs, you'll typically need to provide *one* standardized value per item. Internal codes or ASINs do not count as standardized identifiers for this purpose.
3. NS-PID (Manufacturer Code): This is the biggest gap in Shopify's default export. There is no standard column for the manufacturer's or supplier's own code. This means you'll need to collect this data from your suppliers and find a way to store it within Shopify so it can be exported.

The Solution for NS-PID: Shopify Metafields

This is where Shopify's custom data capabilities come to the rescue. As highlighted by One-Sun1995 in the forum, you can define a product metafield to capture the NS-PID:

1. Go to Settings > Custom data > Products in your Shopify admin.
2. Define a new product metafield, perhaps named "Manufacturer Code" with a namespace like custom.mfr_code.
3. Once defined, this product metafield will automatically appear as a header (e.g., "Manufacturer code (product.metafields.custom.mfr_code)") in your product CSV exports. You can then fill in this data directly in the CSV.

A Critical Distinction: Product vs. Variant Metafields

It's vital to understand that while product metafields are included in CSV exports, variant metafields are not. If your manufacturer's part numbers differ per variant (which is often the case), you'll need to use the variant bulk editor within Shopify to manage these. This means a two-pronged approach might be necessary if your NS-PIDs vary at the variant level. Always test by exporting a single product after defining your metafield to ensure the header appears as expected before committing to a large data entry project.

Beware of Placeholder Values:

Many merchants use placeholders like "N/A," "0," "-", or simply repeat the SKU as the barcode when data is missing. Global-e's guidance, for example, explicitly warns against this. These placeholders will likely cause issues with customs declarations, leading to delays.

Your Action Plan: Preparing Your Shopify Store for 2026

As migration experts, we at Shopping Cart Mover recommend starting this process sooner rather than later. Here's a step-by-step guide:

1. Audit Your Current Product Data: Export your entire product catalog as a CSV. This is your baseline.
2. Identify Gaps:
   • Check for unique SKUs for every variant (M-PID).
   • Review the "Barcodes" column for valid S-PIDs. Flag any missing, invalid, or placeholder values.
   • Identify products or variants for which you lack an NS-PID.
3. Define Your NS-PID Metafield: Implement a product metafield in Shopify for your manufacturer/supplier codes as described above.
4. Collect NS-PIDs: This is often the most time-consuming step. Reach out to your suppliers for their official model or part numbers. A templated request can streamline this process.
5. Populate Data:
   • Update SKUs to be unique for all variants.
   • Fill in the new NS-PID metafields. For variant-level NS-PIDs, use the variant bulk editor.
   • Clean up your "Barcodes" column, ensuring valid S-PIDs or identifying items that genuinely have none (for the Y081 exception).
6. Leverage Third-Party Providers (Wisely): Services like Managed Markets/Global-e, Zonos, Passport, FlavorCloud, or Shipmate can help file declarations. However, their own documentation emphasizes that the merchant is responsible for providing accurate and complete catalog data. They can't fix data that isn't there.
7. Test Your Export: Regularly export your products and use a data validation tool (or manual checks) to ensure your data is clean and compliant.

For merchants looking to start a new e-commerce venture or migrate an existing store, choosing Shopify as your platform offers robust tools and flexibility, especially with its metafield capabilities, to adapt to such evolving requirements. It's a powerful foundation for global sales.

Why This Matters for Your Shopify Store

Ignoring these upcoming EU customs requirements is not an option. Non-compliance can lead to:

• Shipping Delays: Parcels held at customs due to incomplete or incorrect data.
• Increased Costs: Potential fines, storage fees, or return shipping costs.
• Customer Dissatisfaction: Delayed orders and poor delivery experiences erode trust.
• Operational Headaches: Manual intervention to fix customs issues is time-consuming and inefficient.

At Shopping Cart Mover, we specialize in ensuring your e-commerce data is not just migrated smoothly but also optimized for future compliance and operational efficiency. Don't wait until the last minute to address these critical updates. Start preparing your Shopify store's product data now to ensure a seamless transition and continued success in the European market.

If you have questions about your export format, identifier definitions, or need assistance with data migration and cleanup to meet these new standards, our team is here to help.