Adding product identifiers for the EU

From November 1st, every item you ship into the EU must carry three additional product identifiers on its customs declaration. You most likely already have two of them. Here is how to add the one you probably don't.

What’s changing?

The European Union is introducing a new customs requirement under Commission Delegated Regulation (EU) 2026/1022. Every item sold into the EU must be declared with three separate product identifiers that enable EU customs authorities to trace an item back to both the seller and the manufacturer.

• This new requirement applies to all 27 EU countries, and to every shipment regardless of value. There is no low-value exemption.
• It applies per product, not per order. A five-item order will require five sets of identifiers.
• You provide the product identifiers in Shopify or in the FlavorCloud product template. FlavorCloud sends them to the carrier and puts them on the customs paperwork.

What we need from you

Your product SKU: Already have it

Merchant Product Identifier (M‑PID)

In Shopify, we use the SKU already associated with each variant, so no action is needed. If you use the product template, enter each variant's SKU in the SKU column.

Manufacturer product reference: Needs to be done

Non-Standardised Manufacturer Product Identifier (NS‑PID)

This is a code defined by the product manufacturer, not the merchant. This is the key field that needs new data, and it’s required for every product variant with no exceptions.

Standardised product code: Confirm either way

Standardised Manufacturer Product Identifier (S‑PID)

An EAN, UPC, GTIN or ISBN, where the product has one. If it doesn't have one, set the code type to NONE. You cannot leave this field blank.

How to get started

There are two ways to provide your identifiers: directly in Shopify, or in the FlavorCloud product template. Start with step 1, then follow the option that fits how you manage your catalogue.

1. Find your manufacturer references

This value comes from your supplier rather than from your own systems. It is usually on:

• The purchase order or commercial invoice from your supplier
• The product spec sheet or tech pack
• The carton or case label on inbound stock

If you manufacture your own products, your own internal product code will suffice. It's fine for it to be the same as your SKU in that case, as long as you're confirming that deliberately rather than copying it in to fill the box.

Option A: Add them in Shopify

Shopify now has built-in fields for EU product identifiers, so you don’t need to create custom fields. FlavorCloud syncs them automatically.

A1. Add the manufacturer product reference

1. From your Shopify admin, go to Products.
2. Click the product. If it has variants, click the variant.
3. In the Barcodes section, add the manufacturer’s model number, part number or style code.
4. Set the barcode type to NS-PID.
5. Click Save.

A2. Add standardised codes, or confirm there aren’t any

If the product has an EAN, UPC, GTIN or ISBN:

1. In the Barcodes section, add the code exactly as printed, including any leading zeros.
2. Select the matching barcode type.
3. Click Save.

If the product has no standardised code:

1. In the Shipping section, make sure Physical product is on, then click More details.
2. Under EU customs declaration, turn on Has no standardized identifier.
3. Click Save.

Only turn this on when the product truly has no standardised code. Do not invent a code or copy in the SKU. A wrong code is a false customs declaration.

A3. Update in bulk

For large catalogues, use Shopify’s bulk editor, or export your products to CSV, fill in the barcodes, and re-import.

Already set up custom fields? You don’t need to redo anything. FlavorCloud still reads the custom fields you created. If a variant has both, FlavorCloud uses the Shopify barcode.

Option B - Non-Shopify: Use the FlavorCloud product template

B1. Download the product template

Download the FlavorCloud product template. It includes every field we need, including all three product identifiers, plus example rows that show the correct format. Start preparing your file now.

B2. Fill in one row per variant

Each row in the template is one product variant. A style in 8 sizes gets 8 rows, each with the same Title and its own Variant Title and SKU. Delete the example rows before you add your own.

B3. Add standardised codes, or confirm there aren't any

Before you enter any codes, format the SKU, Manufacturer Product Reference and Standardised Product Code columns as Text. Spreadsheet apps like Excel treat long numbers as numbers and drop the leading zeros.

If a product carries an EAN, UPC, GTIN or ISBN, enter it in the Standardised Product Code column and enter the matching type in the Type Of Standardised Code column: GTIN, EAN13, EAN8, UPC, ISBN, OTHER or NONE. Enter the code exactly as printed, including any leading zeros.

If a product has no such code, leave the code column empty and set the type to NONE. EU rules require the absence of a code to be explicitly declared, so we need you to confirm it rather than infer it from a blank field. Once you have, we’ll make that declaration for you.

What happens if you leave a field blank

Never type "N/A", "none" or "TBC" into the manufacturer product reference. 

Quick rules

• One value per field. No lists, no separators, no notes like "see supplier sheet". Each field must contain exactly one identifier.
• Ensure the Product ID lengths fit within the max character limits in the table below. Values that exceed these limits can be rejected, so ensure none of your IDs exceed them.
• Type it exactly. Capitals, hyphens and leading zeros all matter. We pass the value through unchanged. Copy and paste directly wherever possible to avoid typos.
• Plain characters only. Letters, digits, hyphens, full stops, slashes and underscores.

Field reference

Here are the exact field names and accepted formats for Shopify, API and template setups. All Shopify and API keys are from the flavorcloud namespace.

Use a text type for every one of these fields, whether that's a Shopify definition or a spreadsheet column. A number type drops leading zeros and turns a valid code into an invalid one.

FAQs

Q: Our UPCs are already in Shopify’s barcode field. Do we need to enter them again in the standardized product code field?

No. FlavorCloud ingests codes from Shopify’s native barcode field, so you can leave them where they are.

Q: Do we need to fill in the Merchant PID override field?

Only if your merchant identifier differs from your SKU. If the field is blank, FlavorCloud uses the variant SKU as the M-PID. Do not copy your SKU into this field.

Q: We created our PID fields under the flavorcloud namespace. How do we fix them?

Shopify does not allow a namespace or key to be edited after a field is created, so the fields need to be recreated.

1. In Shopify, go to Settings › Custom data › Variants.
2. Delete the four definitions that use the flavorcloud namespace. When prompted, keep any values you have already entered.
3. Create four new definitions. Open Advanced options on each and set the namespace and key exactly: custom.ns_manufacturer_pid, custom.std_manufacturer_pid, custom.std_manufacturer_pid_type, custom.merchant_pid.
4. Re-enter or re-import any values linked to the old fields.

See above for field types and names.

Q: Where in Shopify do we enter the PID values?

Open a product, click into a variant, and scroll down to the metafields section. Enter the values and save. For large catalogs, use Shopify’s bulk editor, or export your products to CSV, fill in the columns, and re-import. Once you finish, FlavorCloud can confirm the data has synced.

Before November 1st

The October 15th preparation target has passed. If you haven’t completed these steps, finish them now. From November 1st, EU shipments for any product without a manufacturer product reference will be blocked.

• Shopify: the four fields are created, with the exact namespace and keys. Template: you've downloaded it and added every product you ship to the EU.
• Every variant you ship to the EU has a SKU
• Every one of those has a manufacturer product reference
• Standardised codes added where the product has one, and the type set to NONE where it doesn't
• No placeholders like "N/A" anywhere in the manufacturer reference field

Questions about a specific product or a bulk upload? Contact your FlavorCloud account manager.