> ## 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 Deforestation Regulation (EUDR)

Part of [EU Deforestation Regulation (EUDR)](https://docs.global-e.com/eu-deforestation-regulation-eudr.md).

On SAP Commerce (Hybris), the Global-e addon reads the product attributes you list in configuration and sends them to Global-e at checkout as `eudrDdsReference` and `eudrTaricCode`. This uses the same configuration properties as EU Product Identifiers (PID).

## Prerequisites

| Requirement | Value |
| - | - |
| Minimum plugin version | Global-e plugin `2211.12` |

## What you need to do

1. 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.
2. 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.
3. 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=ean,manufacturerAID,eudrDdsReference,eudrTaricCode
globale.product.metadata.attributes.map={"ean":"standardcode","manufacturerAID":"mididentifier","eudrDdsReference":"eudrDdsReference","eudrTaricCode":"eudrTaricCode"}
```

`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.

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 |
| - | - | - |
| `eudrDdsReference` | The Due Diligence Statement (DDS) reference for that variant | When the item has no DDS reference |
| `eudrTaricCode` | The TARIC document code for that variant | When the item has no TARIC document code |

## How Global-e reads the values

For each cart line and each mapped attribute, the addon uses the first non-empty value:

1. The attribute on the variant in the cart
2. The same attribute on the parent (base) product
3. 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 `eudrDdsReference` and `eudrTaricCode`.
* **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.** `standardcode` and `mididentifier` are sent unchanged alongside the EUDR keys.

## Quick check before go-live

| Check | Done |
| - | - |
| DDS reference and TARIC document code stored in **Type System** attributes | ☐ |
| Both configuration properties include the EUDR attributes, with the map using `eudrDdsReference` and `eudrTaricCode` | ☐ |
| `eudrDdsReference` and `eudrTaricCode` appear in SendCart when values exist | ☐ |
| Keys omitted when a variant and its parent have no value | ☐ |
| `standardcode` and `mididentifier` still appear when configured | ☐ |


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