DOCS

Add EU product identifiers (PIDs)

Add the product identifiers the EU requires on low-value B2C shipments, for each Zonos integration.

From November 1, 2026, the EU requires product identifiers (PIDs) on every item in business-to-consumer shipments entering the EU worth €150 or less. Shipments missing them may be held or rejected by customs. This guide shows where to add the identifiers for each Zonos integration.

The €150 is measured per consignment — what you send to one customer under a single transport contract, meaning one waybill — and counts the goods only, excluding shipping and insurance. A shipment of several cartons on one waybill is a single consignment, so those cartons are valued together. An order you dispatch as two separate shipments is two consignments, each judged on its own value. Because that depends on how an order is packed and dispatched, the simplest approach is to fill in the identifiers for everything you sell into the EU.

For background on the regulation, including TARIC codes and exceptions, see the EU Product Identifiers (PID) guide.

What's required 

Each product needs up to three identifiers. Two are always required; the S-PID is required only when the product has one.

Identifier↕Also called↕Required?↕Example↕
Merchant Product Identifier (M-PID)SKU or product IDAlwaysTSHIRT-BLU-M
Non-Standardised Manufacturer Product Identifier (NS-PID)Manufacturer number; model or part numberAlwaysMX-500-BLK
Standardised Manufacturer Product Identifier (S-PID)Often referred to as the barcode or GTIN; includes UPC, EAN and ISBNOnly if the product has one012345678905

For the merchant product ID (M-PID), you can use either the product's SKU or its product ID. You only need one.

If you make the product yourself, your own model or part number is the manufacturer number.

Where to add them 

Shopify merchants add the identifiers in Shopify, and Zonos picks them up automatically. For every other integration, add them in Zonos Catalog, or map them from your store's own fields if your plugin's settings offer custom mapping.

Integration↕Where to add the identifiers↕
Shopify (Zonos Duty and Tax)On each product variant in Shopify admin
MagentoZonos Catalog, or attribute mapping in the Zonos plugin settings (steps below)
WooCommerceBuilt-in GTIN field (auto-detected) and Manufacturer Product ID mapping in plugin settings (steps below), or Zonos Catalog
BigCommerceNative GTIN (or UPC/EAN) and Manufacturer Product ID fields on each product, or Zonos Catalog
MivaZonos Catalog, or custom field mapping in the Zonos module settings (Miva mapping guide)
Any other integrationZonos Catalog, or custom mapping

Shopify 

Add all three identifiers on each variant in Shopify admin. The Zonos app picks them up.

  1. In Shopify admin, open Products and select a product.
  2. Open the variant you want to update.
  3. For the merchant product ID (M-PID), the Zonos app uses the Shopify product ID automatically. To use your SKU instead, every product needs a SKU and each SKU must be unique: make sure the SKU field is filled in and the SKU isn't used on any other variant.
  4. Add the manufacturer number as a barcode with the type NS-PID (non-standardised manufacturer product identifier).
  5. If the product has a UPC, EAN, GTIN or ISBN, add it as a second barcode with the matching type.
  6. Save, and repeat for each variant.

Shopify product Barcodes field with a GTIN barcode and an NS-PID barcode added

Tips:

  • Put the manufacturer number in its own NS-PID barcode, not in the SKU or UPC field. Zonos sends each barcode type to customs as a different identifier.
  • A variant can hold several barcodes, but Zonos reads the first five. Keep the NS-PID and the product's main barcode among them.
  • Barcodes you entered before this change still work as the UPC/EAN. Only the manufacturer number is new.

Any integration: Zonos Catalog or plugin mapping 

Magento, WooCommerce, BigCommerce, Miva and any other integration can add the identifiers in Zonos Catalog. Some plugins can also map them from your store's own fields. Use whichever fits how you already manage product data.

Use the S-PID as the NS-PID 

If a product doesn't have its own manufacturer number (NS-PID), you can have Zonos send its S-PID (GTIN) as the NS-PID instead. The setting applies to every integration, is off by default, and never replaces a manufacturer number you've already added.

  1. In Dashboard, go to Settings > Landed cost > Catalog.
  2. Under Product identifiers, select Use S-PID as NS-PID.
  3. Read the acknowledgement that appears below the checkbox, then click Save.

Catalog settings in Dashboard with the Use S-PID as NS-PID checkbox selected under Product identifiers and the manufacturer acknowledgement shown below it

A product needs an S-PID for the setting to help. If a product has neither a manufacturer number nor an S-PID, you still need to add a manufacturer number.

Get the manufacturer's permission first

By turning on this setting, you confirm you've received acknowledgement from the manufacturer permitting its S-PID (GTIN) to be used as the NS-PID. Zonos saves the acknowledgement text you agreed to, who turned the setting on, and when.

Checkout and Landed Cost API 

If you integrate with Zonos directly rather than through a platform plugin, you have two ways to supply the identifiers: store them once per product in Zonos Catalog, or pass them on each item in your request. Catalog fills in any identifier your request leaves blank, so most merchants store them once and send nothing extra at quote time.

Identifier on this page↕API field↕
Merchant product ID (M-PID)sku or productId
Manufacturer numbermanufacturerProductId
S-PID (GTIN, UPC, EAN, ISBN)gtin

For the M-PID, send either sku or productId. The field names are the same on itemCreateWorkflow, on the items in a cart, and on catalogItemCreate, so nothing changes between the quote path and the catalog path.

Add the identifiers to each item in itemCreateWorkflow. Use this if you don't keep a catalog with Zonos, or when an item's identifiers differ from its catalog entry.

1mutation ItemCreateWorkflow($input: [ItemCreateWorkflowInput!]!) {
2 itemCreateWorkflow(input: $input) {
3 id
4 sku
5 manufacturerProductId
6 gtin
7 }
8}
Formatting the S-PID

Send the gtin as digits only, with no dashes or spaces. UPC, EAN, JAN and 13 digit ISBN values all go in this one field, and Zonos works out which standard it is from the number itself.

  • Correct: 012345678905
  • Rejected: 0-12345-67890-5

If you hold a 10 digit ISBN, send the 13 digit version instead, because a 10 digit ISBN can end in the letter X.

If a product has no barcode, leave gtin out rather than sending an empty string, reusing your SKU, or filling it with placeholder text such as N/A. An identifier that points at the wrong product is worse than none, because customs may use it to look the goods up.

How Zonos sends them to your carrier 

Once the identifiers are on your products, Zonos puts them where each carrier expects them when it creates the label and the commercial invoice. You don't need to format anything yourself.

Zonos sends the identifiers on shipments into the EU, where they're required, for:

  • FedEx
  • UPS
  • DHL Express
  • APC
  • Asendia
  • USPS

Zonos is adding more carriers. Add the identifiers to your products whichever carrier you ship with: they're stored on your catalog and used for landed cost now, and they'll be sent as soon as that carrier is added — nothing to redo later. To check where a carrier stands, contact Zonos support.

If you create your own labels

If you generate labels through your own carrier integration rather than through Zonos, you're responsible for sending the identifiers yourself. Each carrier expects them in a different place, and they differ on what to send when a product has no S-PID: some want an explicit "none" value, others want the field left out. Contact Zonos support for the details that apply to your carriers.

Before November 1 

Book a demo

Was this page helpful?


Get support·Legal docs·© 2026 Zonos