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

# Which Supplier Address? Country Controls Automation

> How Polygon One uses the supplier country — and why the country of production still determines EUDR treatment

## The short answer

On a supplier record, Polygon One uses the **Country** field for automatic order routing, invitations and supplier email language. The supplier country is **not automatically the country of production** of the goods. Street, postal code and city do not replace origin information or a plot.

Record the actual business partner with an appropriate business address and its **country**. Do not enter the production country or a warehouse in a different country as the supplier country just to trigger a particular automation.

> [!WARNING]
>
> If a supplier has **no country**, the automatic EU-seat exception does not apply. Purchase orders with EUDR-relevant articles can then enter the import-DDS process. This is a platform rule, not a final legal assessment. Country is **required** when creating a supplier manually.

## What the supplier country controls

| Effect | Explanation |
| - | - |
| **Purchase orders** | With the EU-seat exception enabled, the platform excludes purchases from EU suppliers from the automatic import-DDS process. If this company configuration is disabled, these purchases are also considered based on their articles' EUDR relevance. A **low-risk non-EU country** does not exclude an order from this process. |
| **Sales orders** | The platform uses the linked business partner's country as the destination for EU/non-EU routing. Check both the business partner and the order type. |
| **Automatic supplier invitations** | With invitation automation enabled, article and order imports can trigger invitations for missing EUDR data. The EU-seat exception, article scope, existing invitations and an available email address all matter. **Low country risk alone does not prevent an invitation.** |
| **Supplier email language** | The country-based default for invitation emails is **German for Germany and Austria**, otherwise **English**, including when the country is missing. The portal language can differ; invitation links for China open the Chinese version, for example. |

Routing and actual DDS creation are separate steps. Missing data or further checks can prevent creation. See [Incoming or Outgoing?](https://help.polygon-one.com/en/eudr/dds-bestellungen/eingehend-oder-ausgehend.md) for the workflow.

## What the supplier country does not control

Origin and risk assessment use the **production countries and plots**:

* **Satellite analysis** considers the **plot's country**. Whether automatic analysis is skipped for low risk also depends on company settings and further checks.
* **Legal risk categories** are determined using the **production countries**. Origin information can appear in plots, article assignments and evidence; it must be consistent. See [Risk Assessment](https://help.polygon-one.com/en/eudr/datensammlung/risikoanalyse.md).

> [!NOTE]
>
> For a German intermediary supplying cocoa from Côte d'Ivoire, Polygon One produces **no automatic import-DDS suggestion** for the purchase order **when the EU-seat exception is enabled**. This does not turn Côte d'Ivoire into Germany: the goods' origin still requires a separate check. The supplier address alone does not establish simplified due diligence.

> [!WARNING]
>
> **Low risk is not a blanket exemption.** Simplified due diligence depends on the country of production of all relevant commodities and products, not the supplier's registered address. Check your role, origin and indications of mixing or circumvention. The [European Commission explains the conditions](https://green-forum.ec.europa.eu/nature-and-biodiversity/deforestation-regulation-implementation/understand-due-diligence_en).

## What the address is still useful for

* It appears in the supplier list's **Address** column (street, postal code and city), helping distinguish suppliers with the same name.
* During **CSV import**, it can supply a missing country: if the **Country** column is absent or unusable, Polygon One tries to derive the country from the **end of the address**.

### How country detection from an address works

**1. The country from the file always takes precedence**

If the Country column contains a recognised value, the address is not examined.

**2. Otherwise: the last two address parts**

The last two comma-separated sections are checked, working backwards.

**3. Recognised sections only**

A section counts only if the **whole section** resolves to a known country. Two-letter abbreviations are deliberately **ignored**: otherwise a US address ending in `, CA` could become Canada and `, DE` could become Germany. Use full country names in the address and ISO codes in the separate Country field.

Example: `Hauptstrasse 5, 10115 Berlin, Germany` yields **Germany**. `Hauptstrasse 5, 10115 Berlin` yields **no country**; fill the Country column in that case.

## Accepted country values

| Path | Accepted values |
| - | - |
| **Manual creation/editing** | Choose from the country list. Still check that the selected country belongs to the business partner. |
| **CSV import** | **ISO code**, such as `DE` or `DEU`, an English country name such as `Germany` or `Côte d'Ivoire`, or a supported localized country name. |

> [!WARNING]
>
> **ISO codes are the least ambiguous option.** Supported localized names such as `Deutschland` are also resolved to a canonical country. Use an ISO code when a name is ambiguous or not recognised; the same rule applies to supplier, article and order imports.

### Existing suppliers and other import paths

* In a **supplier import**, an explicitly supplied, recognised country can change an existing value. Review the listed changes and any overwrite confirmation.
* A country **derived from the address** only fills an empty country in a supplier import. It does not overwrite an existing country.
* **Article imports** can create suppliers with a country and address. Matching by name or external supplier ID can fill empty master data; matching directly by the internal supplier ID does not enrich those fields.
* **Order imports** can create missing suppliers with these details. Use supplier editing or a supplier import to deliberately correct an existing supplier country.
* A free-text imported address is initially stored as address text; street, postal code and city are not automatically split into reliable separate fields.

## Add a missing country

**1. Find the supplier**

Search for the supplier in the list. If it is missing, check active filters, especially **EUDR-relevant only**. Check the stored country in the Edit dialog.

**2. Edit**

Open the supplier's actions menu (⋯) and select **Edit**.

**3. Set the country and save**

Select the actual supplier country and save. Then check affected orders and their DDS assignments. Saving the country alone does not promise that existing DDS will automatically be recreated, changed or removed.

## Related pages

> **[Suppliers](https://help.polygon-one.com/en/eudr/datenhaltung/lieferanten.md)**
>
> Create, import and edit suppliers.

> **[Incoming or Outgoing?](https://help.polygon-one.com/en/eudr/dds-bestellungen/eingehend-oder-ausgehend.md)**
>
> Check order type, automatic routing and the DDS process.


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