eudrDdsReference and eudrTaricCode. This uses the same configuration properties as EU Product Identifiers (PID).
Prerequisites
What you need to do
- Store the DDS reference and TARIC document code in product attributes defined in the Type System (
items.xml). 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.
- Add the attributes to the two Global-e configuration properties, in the Administration Console (HAC) or in
local.properties. If you already send EU Product Identifiers, append the EUDR attributes to the same properties:
globale.product.metadata.attributes is a comma-separated list of the attribute qualifiers to send. globale.product.metadata.attributes.map maps each qualifier to the key Global-e receives. The mapped values must be exactly eudrDdsReference and eudrTaricCode. If your values are stored in attributes with different qualifiers, use those qualifiers 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 camelCase keys. The keys Global-e receives are whatever you put in the map, so use exactly
eudrDdsReferenceandeudrTaricCode. - Omit, don’t fake. When an attribute is blank, the addon leaves it out. Never enter a placeholder such as NA, 0 or -.
- EU PID keeps working.
standardcodeandmididentifierare sent unchanged alongside the EUDR keys.

