---
id: KB-NO-018
url: https://app.codecontract.io/help/regulation/the-same-product-in-several-countries
idioma: en
categoria: normativa
subcategoria: producto
audiencia: usuario
nivel: avanzado
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-NO-015, KB-NO-007]
citadoPor: [KB-NO-025]
---

# The same product in several countries

_The product is identical and the documentation is not. What decides is the destination market, not yours._

**Responde a:** selling the same product in another country · documentation to export a product · what changes when selling abroad · the importer asks for different papers

The first export is prepared like a sale that happens to be further away. Commercially, it is. Documentation-wise it is not: the same product, from the same factory and the same batch, may need different papers depending on where it goes — and it is not you or your client who decides, it is the destination market.

## What repeats and what changes

| Element | Does it change by country? | What it means |
| --- | --- | --- |
| The product itself | No | Same batch, same factory, same controls |
| What must be declared about it | Yes | Each market requires its own statements |
| The label's language and content | Yes | And it is usually the first thing rejected on arrival |
| Who answers to the local authority | Yes | Often a local importer or representative, not you |
| What you will be asked for later | Yes | And that representative will ask, on their deadlines |

> [!IMPORTANT]
> The fourth row is the surprising one and the one that strains relationships most: **in many markets it is the importer who answers to the local authority**, so requests reach you not from a regulator but from your own client — and they arrive urgently, because deadlines are running for them that you cannot see. They are not becoming demanding: they are passing on an obligation of their own. Understanding that changes the tone of the conversation entirely.

## How to organise it without duplicating everything

1. **One shared product file** — Tests, composition, controls: none of that changes by destination.
2. **And a folder per market with the specifics** — Label, declarations and who the representative there is.
3. **With the label version used on each shipment** — If anything is reviewed, it is reviewed against that one.
4. **And the importer's requests in the same place** — They tend to repeat yearly and different people answer them.

> [!WARNING]
> A practical detail that saves complaints: **the same product may be sold under different names in each market**, and if your system treats those as separate products you end up with fragmented documentation for one identical thing. Keep one internal reference with the trade names hanging off it. When a query comes in under the local name, it is settled in a minute rather than a morning.

## What to ask before the first shipment

**En corto**

- Who is registered as responsible at destination and what they need from you.
- What the label must say and in which language.
- And what they can be asked for, because they will end up asking you.

> [!NOTE]
> Which requirements apply in each market, who must be registered as responsible and what documentation travels with each shipment are governed by destination rules and trade agreements. **Your adviser or customs broker settles that**; the point here is organising your side so that answering does not depend on who happens to be in that day.

**Is one declaration valid for every country?**

Rarely: what must be declared, and to whom, changes.

**Can I just use a translated label?**

Translating is not adapting. The required content changes too.

**What if the importer changes?**

That market's part is redone; the shared file stays as it is.

## Ejemplos

**A manufacturer starts selling in two countries and creates a separate code per trade name.**

- Unifies into one internal reference with trade names attached and a folder per market

→ A query under the local name reaches the shared documentation without duplicating anything.

**The home market's documentation is sent to another country.**

- Asks for the destination market's list

→ You prepare what they ask for there.

**A document from here does not exist there under that name.**

- Explains the equivalence in writing

→ The gap reads as a footnote rather than a failure.

**Forty pages are translated that nobody asked to be translated.**

- Asks what needs translating before translating

→ Only what is needed is translated.

**Each market is prepared from scratch every year.**

- Keeps the explained equivalence as a document of its own

→ The following year reuses it.

**The same product carries different labels by country.**

- Stores each version against its market

→ You know what was sold with which label.