---
id: KB-AL-002
url: https://app.codecontract.io/help/food-and-beverage/wineries-and-beverages
idioma: en
categoria: sector-alimentacion
subcategoria: bebidas
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-AL-001, KB-NO-002]
citadoPor: [KB-AL-001]
---

# Wineries and beverages

_Designations, export and labelling: documentation that travels with the product._

**Responde a:** documentation to export wine · designation of origin documentation · beverage labelling requirements · food export certificates

A winery has a documentary problem the wider food industry does not: much of its paperwork travels with the product to another country, where it is reviewed by someone with their own criteria and in their own language.

## The three modules

| What | Module | Why |
| --- | --- | --- |
| Grape, packaging and ancillary suppliers | Trackline | Composition and packaging conformity |
| Agreements with distributors and importers | Consigne | Signed before the first shipment |
| Documentation for each shipment | SmartCheck | Certify what was sent, with its date |

> [!IMPORTANT]
> Export documentation is prepared per shipment and reviewed abroad. A document rejected at destination can leave goods stranded in customs at a daily cost, so the draft is checked before sending, not after.

## Frameworks cited

Designation of origin and geographical indication rules, labelling and consumer information, oenological practices where applicable, and the destination country's requirements, which can differ considerably from European ones. What each market requires is confirmed by your adviser or regulatory council.

> [!WARNING]
> If you work under a designation of origin, the regulatory council's documentation has its own deadlines and renewals. It does not fit the rest of the calendar, which is why it gets forgotten.

> [!NOTE]
> When you always export to the same markets, the shipment is nearly identical. Built as a process, the twentieth costs a fraction of the first.

**Can I have one process per destination country?**

Yes, and you usually need to: markets do not ask the same things.

**What about labels in other languages?**

They go in as shipment documentation, with their version and date.

**Does it serve for a regulatory council inspection?**

It is what gets shown, with dates you did not set.

## Ejemplos

**A winery has a shipment stuck in customs over a badly prepared document.**

- Builds a process per destination market
- Reviews the draft before sending

→ Later shipments clear first time and the cost of stranded days disappears.

**Export documentation is prepared shipment by shipment.**

- Gathers what repeats into a file

→ The second shipment to the same destination costs half.

**Each market asks for different labels.**

- Stores each version against its market

→ You know what was sold with which label.

**A client asks you to evidence a specific vintage.**

- Checks that vintage's file

→ You answer per vintage rather than per winery.

**Designation documentation expires without warning.**

- Records validity when filing it

→ Renewal happens with time to spare.

**The packaging supplier changes and labels stay the same.**

- Reviews what is affected when suppliers change

→ The label stays true.