standardcode and mididentifier. Your SKU is already sent separately, so there is no new SKU field to add. Do not use the US MID fields for EU PID.
For what each identifier is, see The three identifiers on the overview page.
Prerequisites
What you need to do
-
Confirm with your Global-e CSM that EU PID is enabled for your account and that you are on a Global-e addon release that supports it (
2211.12). -
Store the values in product attributes defined in the Type System (
items.xml). The native SAP Commerce attributeseanandmanufacturerAIDwork out of the box. Classification attributes and Dynamic Attributes are not supported. - Populate the values on each variant that can appear in the cart. If a variant has no value, the addon uses the value on the parent (base) product.
-
Set the two Global-e configuration properties, in the Administration Console (HAC) or in
local.properties:globale.product.metadata.attributesis a comma-separated list of the attribute qualifiers to send.globale.product.metadata.attributes.mapmaps each qualifier to the key Global-e receives. The values must be exactlystandardcodeandmididentifier(lowercase).- If your barcode or manufacturer code is stored in a different attribute, replace
eanormanufacturerAIDwith that attribute’s qualifier in both properties.
- Place a test order and confirm both keys appear when values exist and are omitted when blank.
How Global-e reads the values
For each cart line and each mapped attribute, the addon uses the first non-empty value:- The attribute on the variant in the cart
- The same attribute on the parent (base) product
- Otherwise omit
Key points
- Type System attributes only. Values held in Classification attributes or Dynamic Attributes are not read.
- Exact lowercase keys. The keys Global-e receives are whatever you put in the map, so use exactly
standardcodeandmididentifier. - The original attribute is also sent. Each listed qualifier is sent under its own name as well as under the mapped key, for example both
eanandstandardcodewith the same value. Global-e uses onlystandardcodeandmididentifierfor EU PID; the extra keys are expected. - Omit, don’t fake. When an attribute is blank, the addon leaves it out. Never enter a placeholder such as NA, 0 or -.
- Keep separate from US MID fields and from other product fields such as
MerchantHSCode.
Quick check before go-live
Frequently asked questions
Do I need new attributes named standardcode or mididentifier?
Do I need new attributes named standardcode or mididentifier?
No. Those are the keys Global-e receives. Keep your values in your existing attributes and map them in
globale.product.metadata.attributes.map.Our barcodes are in Classification attributes. Can Global-e read them?
Our barcodes are in Classification attributes. Can Global-e read them?
No. Only Type System attributes are supported. Store the values in a Type System attribute such as
ean, or contact your CSM.Only a manufacturer code, no barcode?
Only a manufacturer code, no barcode?
Map only the manufacturer code attribute.
standardcode is omitted and Global-e declares the “no barcode” code.
