EU Product Identifiers - Global-e Docs

Part of the EU Customs Reform - Product Identifiers (PID). On BigCommerce, you store the values in your catalog using the native variant GTIN field and/or product metafields. The Global-e integration reads them at checkout and sends them to Global-e. Your SKU is already sent separately, so there is no new SKU field to add. Do not use the US MID fields (MIDCode, ManufName and similar) for EU PID. For what each identifier is, see The three identifiers on the overview page.

What you need to do

standardcode: for each variant that can appear in the cart, populate the GTIN field in BigCommerce (variant Barcodes & Identifiers).
If you do not use GTIN, create a metafield named exactly standardcode on the variant. A product-level metafield is used only as a fallback when the variant has no GTIN or variant metafield. Product Metafield
Variant Metafield
mididentifier: when available, create a metafield named exactly mididentifier on the variant. A product-level metafield is used as a fallback only.
Confirm with your Global-e CSM that EU PID is enabled for your account and that you are on a BigCommerce integration release that supports EU PID.
Place a test order and confirm both keys appear when values exist and are omitted when blank.

Sent as	What it holds	When to leave it out
`standardcode`	The barcode for that variant (GTIN, EAN or UPC)	When the item has no barcode. Global-e declares the “no barcode” code automatically.
`mididentifier`	The manufacturer’s product code for that variant	Never. This is required on every line.

How Global-e reads the values

For each cart line, the integration uses the first non-empty value in this order:

standardcode (first non-empty wins): variant GTIN, then variant metafield standardcode, then product metafield standardcode, otherwise omit.
mididentifier (first non-empty wins): variant metafield mididentifier, then product metafield mididentifier, otherwise omit.

No per-merchant field mapping is required on the Global-e side. Use the variant GTIN and/or metafields with these exact key names.

Key points

Exact lowercase. The SendCart keys, and any metafields you use, must be exactly standardcode and mididentifier. GTIN is the default source for standardcode when populated on the variant. You do not need a standardcode metafield when GTIN is set. One pair of values per variant. A value on the parent product alone is not used when the variant has its own GTIN or variant metafield. Omit, don’t fake. Leave the key out when you have no value. Never send an empty string, NA, 0 or -. When values are read: at checkout, when the customer proceeds to Global-e. Updated catalog values apply on that variant’s next checkout. Keep separate from US MID and from other product fields such as MerchantHSCode.

Quick check before go-live

Check	Done
`standardcode` appears when the variant has GTIN or a `standardcode` metafield value	☐
`mididentifier` appears when the variant (or product fallback) has a `mididentifier` metafield value	☐
Keys are omitted (not empty) when a variant has no value	☐
Each variant in the cart sends its own pair	☐
EU PID keys are separate from US MID keys and `MerchantHSCode`	☐

​What you need to do

​How Global-e reads the values

​Key points

​Quick check before go-live

What you need to do

How Global-e reads the values

Key points

Quick check before go-live