Cepaos · Product news · June 10, 2026
Cepaos in June 2026: local compliance modules and native-language copy across wine markets
From Mendoza voseo to Mosel Sie-Form: what Cepaos covers per market, which regulator each compliance module targets, and how the product copy is written for each locale.
Winery operations live or die on jurisdiction. A Mendoza bodega owes INV a Libro de Movimientos. A Mosel Weingut owes the BLE a Weinbuchführung. A Stellenbosch estate owes SAWIS a monthly declaration. Cepaos ships a compliance module for each of the three in one product, and for the other markets listed below.
The wine industry runs on regulator forms, harvest deadlines, and export certificates that do not translate. They have to be built per-country, in the local language, against the text of each regulation. That is the work this article describes.
Why this matters
One platform across jurisdictions
Wine regulation is national, and often regional: each producing country has its own regulator, forms and deadlines, plus appellations with their own rules. A winery that operates in more than one country usually ends up combining tools, consultants and spreadsheets.
That gets harder when a producer exports, opens a subsidiary abroad or buys a vineyard in another country: compliance becomes a patchwork of separate systems.
Cepaos was built on the inverse premise: one platform, every market, every regulator, in the local language and the local register of formality. The platform is multi-tenant, so each jurisdiction's compliance library is shared by every customer in that jurisdiction.
By the numbers
Coverage, counted from the code
The first two figures are computed from the pricing registry and the locale list at build time, so they stay current. Each market in the table maps tolib/compliance/<country>/ libraries and messages/<locale>.json source files.
What changed in 2026
What shipped, by region
DACH
Germany, Austria and Switzerland: ZUGFeRD 2.x / Factur-X hybrid invoice files, DATEV CSV export, Lieferantenerklärung, ÖWK Erntemeldung, DAC Codex selector, FADP-aligned cantonal rules. Steuerberater and Weinbauberater review pending; libraries shipped.
Romance markets and Iberia
Italy (ICQRF registers), Portugal (IVV / SIVV declarations, ATCUD on invoices issued through the customer's certified software), Spain (REGEPA) and France (CVI and INAO declarations). The shared lib/compliance tree replaced per-country forks of ad-hoc reporting code.
LATAM, Anglo and tail markets
Argentina INV, Chile SAG, Brazil MAPA, Mexico COFEPRIS, Uruguay INAVI shipped with the Spanish and Portuguese voice registers their markets actually use (voseo in Mendoza, Portuguese Acordo 90). Australia (Wine Australia), New Zealand (NZW), South Africa (SAWIS), Canada (CFIA), Croatia (HAPIH), Georgia (National Wine Agency) followed the same template. One codebase for all of them.
Native compliance per market
Markets, regulators and voice registers
| Region | Market | Authority | Voice register |
|---|---|---|---|
| LATAM | Argentina (es-AR) | INV, Instituto Nacional de Vitivinicultura | Voseo (vos tenés) |
| LATAM | Chile (es-CL) | SAG, Servicio Agrícola y Ganadero | Usted formal, Chilean inflection |
| LATAM | Brazil (pt-BR) | MAPA, Ministério da Agricultura | Você institucional, Brazilian spelling |
| LATAM | Mexico (es-MX) | COFEPRIS, Comisión Federal | Usted, Mexican lexicon |
| LATAM | Uruguay (es-UY) | INAVI, Instituto Nacional de Vitivinicultura | Voseo uruguayo |
| Iberia | Spain (es-ES) | REGEPA + autonomous regions | Usted peninsular |
| Iberia | Portugal (pt-PT) | IVV, Instituto da Vinha e do Vinho | V.Exa., Acordo Ortográfico 90 |
| DACH | Germany (de-DE) | BLE + Weinbaukartei + VDP | Sie-Form, Hochdeutsch |
| DACH | Austria (de-AT) | ÖWK + DAC Codex + Bundesamt | Sie-Form, Austrian lexicon |
| DACH | Switzerland (de-CH) | BLW + cantonal rules | Sie-Form, Helvetisms, ss for ß |
| France | France (fr) | CVI + INAO + Douanes | Vouvoiement standard |
| France | Romandy (fr-CH) | Swiss federal + Romand cantons | Vouvoiement, Romand vocabulary |
| Italy | Italy (it-IT) | ICQRF + Registro Telematico | Lei formale |
| Anglo | United States (en-US) | TTB + state DTC matrix | US English institutional |
| Anglo | Australia (en-AU) | Wine Australia + ATO BAS | Australian English |
| Anglo | New Zealand (en-NZ) | NZW, New Zealand Winegrowers | NZ English, te reo terms |
| Anglo | South Africa (en-ZA) | SAWIS + WoSA | SA English |
| Anglo | Canada (en-CA) | CFIA + provincial liquor boards | Canadian English |
| Tail | Croatia (hr-HR) | HAPIH, vinogradarstvo i vinarstvo | Vi formal |
| Tail | Georgia (ka-GE) | National Wine Agency | თქვენ formal, Mkhedruli script |
Each row maps to a lib/compliance/<country>/ library, a localized canonical compliance page, and a messages/<locale>.json source file.
Why native voice matters
Translated software loses customers
Argentina vs Spain
In Mendoza, a button labeled “tú puedes cargar la cosecha” reads as foreign software. The same button in voseo - “vos podés cargar la cosecha”, reads as built-for-here. Cepaos ships the voseo register throughout the Argentine product. Spain gets peninsular tú; the two never mix.
Portugal vs Brazil
Portuguese splits on the Acordo Ortográfico 90 and on register. The Portuguese product uses V.Exa. for fiscal correspondence and respeitar the Acordo. The Brazilian product uses você and the Brazilian spelling family. Mixing them is the classic tell of an export, not a product.
Germany, Austria and Switzerland
All three share Sie-Form, but the lexicon does not transfer. Austrian Erdäpfel is not German Kartoffeln. Swiss German drops ß. Austrian wine law refers to ÖWK and Bundesamt; German law refers to BLE and Weinbaukartei. Cepaos ships three separate message files, de-DE, de-AT, de-CH, that read as native in each market.
The IoT layer
Equipment data in the same record as the cellar book
Cepaos includes an IoT layer for the cellar, the vineyard and logistics: equipment types are modelled in the schema (tanks, barrels, presses, bottling lines, scales, weather stations and more), and vendor-cloud connectors read data using credentials the winery stores encrypted in its own account.
For the industrial gear that does not speak HTTP, Cepaos ships a Node.js Gateway agent (v0.3) that speaks Siemens S7 natively via nodes7. The agent runs in the cellar. Commands sent to equipment carry a risk tier (LOW, MEDIUM, HIGH); HIGH-risk commands need a second administrator to approve them before they run.
Sensor readings land in the same organisation as the cellar book, and localized IoT landings live at /{locale}/iot.
What is next
From coverage to depth
Coverage is the starting point. Next we are working on depth: more regulatory filings generated automatically where the law allows it, broader per-vendor IoT sync, and feedback from wineries using Cepaos in each market.
Every market page and competitor comparison on this site is public, so you can check what Cepaos covers in your country before talking to us.
Book your demo
See the platform in your own market
Pick your country and we walk you through your first compliance form in the local language. 30 minutes, no commitment.
- 33 markets with published pricing
- 20 markets with a dedicated compliance module listed above
- Product copy written per locale (voseo, Sie-Form, vouvoiement, V.Exa.)