> ## Documentation Index
> Fetch the complete documentation index at: https://docs.global-e.com/llms.txt
> Use this file to discover all available pages before exploring further.

# EU Product Identifiers

Part of the [EU Customs Reform - Product Identifiers (PID)](/eu-product-identifiers-pid).

On BigCommerce, you store the values in your catalog using native product/variant fields (**UPC/EAN**, **MPN**, and product-level **GTIN**) and/or 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. Those remain for US customs and coexist with EU PID keys.

For what each identifier is, see [The three identifiers](/eu-product-identifiers-pid#the-three-identifiers) on the overview page.

## What you need to do

1. **`standardcode`:** for each variant that can appear in the cart, populate the native **UPC/EAN** field in BigCommerce (variant **Barcodes & Identifiers**).

   <Frame>
     <img src="https://mintcdn.com/globale-enterprise/LezcnfC2KKGsi0cK/images/eu-product-identifiers/bigcommerce-gtin.png?fit=max&auto=format&n=LezcnfC2KKGsi0cK&q=85&s=c4712b52acdc73db40e5630afc9a05dc" width="2592" height="1074" data-path="images/eu-product-identifiers/bigcommerce-gtin.png" />
   </Frame>

   If a variant has no UPC/EAN, create a metafield named exactly `standardcode` (or `StandardCode`) on the variant. Product-level sources are used only as a fallback when the variant has no UPC/EAN and no variant metafield: product **GTIN**, then product **UPC/EAN**, then a product metafield `standardcode`.

   **Product Metafield**

   <Frame>
     <img src="https://mintcdn.com/globale-enterprise/LezcnfC2KKGsi0cK/images/eu-product-identifiers/bigcommerce-product-metafield.png?fit=max&auto=format&n=LezcnfC2KKGsi0cK&q=85&s=5ae199fcc8cf0e2454bb7a14a338cc52" width="2660" height="992" data-path="images/eu-product-identifiers/bigcommerce-product-metafield.png" />
   </Frame>

   **Variant Metafield**

   <Frame>
     <img src="https://mintcdn.com/globale-enterprise/LezcnfC2KKGsi0cK/images/eu-product-identifiers/bigcommerce-variant-metafield.png?fit=max&auto=format&n=LezcnfC2KKGsi0cK&q=85&s=d2ded95d91603d3e32480d10e3dc222d" width="2646" height="1076" data-path="images/eu-product-identifiers/bigcommerce-variant-metafield.png" />
   </Frame>

2. **`mididentifier`:** when available, populate the native **MPN** (Manufacturer Part Number) on the variant. If a variant has no MPN, create a metafield named exactly `mididentifier` (or `MidIdentifier`) on the variant. Product-level **MPN** or a product metafield `mididentifier` is used only as a fallback.

3. **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.

4. **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 (UPC, EAN, or GTIN) | When the item has no barcode. Global-e declares the "no barcode" code automatically. |
| **`mididentifier`** | The manufacturer's product code for that variant | When you have no manufacturer code to send. |

## How Global-e reads the values

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

**`standardcode`**

1. Variant native **UPC/EAN**
2. Variant metafield `standardcode` / `StandardCode` (case-insensitive)
3. Product native **GTIN**
4. Product native **UPC/EAN**
5. Product metafield `standardcode` / `StandardCode` (case-insensitive)
6. Otherwise omit

**`mididentifier`**

1. Variant native **MPN**
2. Variant metafield `mididentifier` / `MidIdentifier` (case-insensitive)
3. Product native **MPN**
4. Product metafield `mididentifier` / `MidIdentifier` (case-insensitive)
5. Otherwise omit

<Note>
  Variant-level GTIN is **not** used for `standardcode` (BigCommerce Admin exposes GTIN at product level; use variant UPC/EAN instead).
</Note>

## Key points

**Exact lowercase on SendCart.** Outbound MetaData keys are exactly `standardcode` and `mididentifier`. Metafield keys may vary in casing (`StandardCode` / `MidIdentifier`).

**UPC/EAN is the preferred source for `standardcode`** when populated on the variant. You do not need a `standardcode` metafield when UPC/EAN is set.

**MPN is the preferred source for `mididentifier`** when populated on the variant. You do not need a `mididentifier` metafield when MPN is set.

**One pair of values per variant.** A value on the parent product alone is not used when the variant has its own UPC/EAN, MPN, 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** (`MIDCode`, `ManufName`, namespace `GE_MID`, and similar) and from other product fields such as `MerchantHSCode`. EU PID and US MID MetaData keys coexist; they are not interchangeable.

<h2 id="quick-check-before-go-live">
  Quick check before go-live
</h2>

| Check | Done |
| - | - |
| `standardcode` appears when the variant has UPC/EAN (or a `standardcode` metafield / product fallback) | ☐ |
| `mididentifier` appears when the variant has MPN (or a `mididentifier` metafield / product MPN fallback) | ☐ |
| 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` | ☐ |

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can we use the BigCommerce UPC/EAN field for standardcode?">
    Yes. Variant UPC/EAN is the primary source. Product GTIN / product UPC/EAN are fallbacks when the variant has no UPC/EAN and no variant metafield.
  </Accordion>

  <Accordion title="Can we reuse US MID metafields (GE_MID / MIDCode) for mididentifier?">
    No. Those fields continue to feed US MID MetaData. For EU `mididentifier`, use native **MPN** (preferred) or a metafield keyed `MidIdentifier`.
  </Accordion>

  <Accordion title="Only a manufacturer code, no barcode?">
    Send `mididentifier` only; omit `standardcode`.
  </Accordion>

  <Accordion title="Who configures Global-e field mapping?">
    No per-merchant field mapping is required. Your CSM enables EU PID on the Global-e side.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.