Cepaos · Product news · June 10, 2026
Cepaos becomes the wine industry standard SaaS, 20 markets, native compliance, June 2026
From Mendoza voseo to Mosel Sie-Form, Cepaos ships the only winery platform with native compliance plus native voice across 20 wine markets. The June 2026 milestone closes a 24-month build covering 9 compliance authorities, 22 locale message files, and 63 honest side-by-side competitor comparisons.
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. Until June 2026, no SaaS shipped all three natively in one product. Cepaos now does, and adds 17 more.
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, by people who read the Amtsblatt. This is the work most software vendors avoid. Cepaos finished it.
Why this matters
Wine SaaS has been fragmented for 20 years. That ends now.
The wine industry is structurally fragmented: 17 producing countries, 30+ regulators, 11 wine languages, and a long tail of sub-national appellations with their own rules. Most ERP and winery-management vendors picked a single geography, California, Bordeaux, Tuscany, and stayed there. Anything beyond required consultants, spreadsheets, or rip-and-replace migrations.
That model worked when wineries operated in one country. It stops working the moment a producer exports to the EU, opens a Hong Kong subsidiary, or buys a vineyard in Mendoza. Compliance becomes a patchwork. Costs balloon. Audits become guesswork.
Cepaos was built on the inverse premise: one platform, every market, every regulator, in the local language and the local register of formality. The economics only work because the platform is multi-tenant and the compliance libraries are shared across customers in each jurisdiction. As of June 10, 2026, the coverage is complete enough to call it the industry standard.
By the numbers
What 20-market coverage actually looks like
Counts reflect shipped artifacts as of commit ba56224fc (Wave 3 EU re-dispatch) and b32fb22d4 (OG image pipeline scaffold). Coverage is verified againstlib/compliance/<country>/ libraries and messages/<locale>.json source files.
What changed in 2026
Three quarters, three completions
DACH parity
Germany, Austria and Switzerland closed at 100 percent native. ZUGFeRD 2.x Factur-X hybrid invoicing, 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 and Portugal reached parity (ICQRF, IVV SIVV, ATCUD on Portuguese invoices). Spain closed the REGEPA gap. France completed CVI and INAO declarations end-to-end. 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 (HCPA), Georgia (NWA) closed via the same template. Twenty markets, one codebase.
Native compliance per market
Twenty wine markets, twenty regulators, twenty 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) | HCPA, vinogradarstvo i vinarstvo | Vi formal |
| Tail | Georgia (ka-GE) | NWA, 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. Native review by mother-tongue operators per market is in progress; libraries and routes are shipped.
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
Hardware is part of the platform, not a roadmap promise
Most winery SaaS stops at the database. Cepaos ships a native IoT layer that talks to the cellar, the vineyard, the truck and the drone. Sixteen equipment types are modelled in the schema today: barrel sensors, warehouse zones, bench scales, truck shipments, drone flights, plant-health observations, plus the usual tanks, presses, bottling lines and weather stations.
Eleven vendor clouds are wired through OAuth credentials and AES-256 sync: Davis Instruments (weather), Sencrop (vineyard weather), Pix4D Fields (drone imagery), Plant.id (agronomy vision), Wialon (LATAM GPS), Geotab (EU fleet), OnVi (barrel telemetry), Krones (bottling), Pellenc (viticulture), Anton Paar (lab instruments) and Endress+Hauser (process). Seven partnership emails are drafted and queued; the beta-customer pipeline targets fourteen wineries in seven regions before the 2026 vintage.
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, multi-tenant by API key, with token refresh and Sentry instrumentation. Sixty-plus bidirectional commands are modelled with a three-tier approval workflow: LOW commands auto-execute, MEDIUM commands need a single operator signature, and HIGH commands (purge, valve-open, CIP-start) require a dual-operator approval ledger.
The dashboard surfaces a per-organisation IoT widget with analytics hashed via SHA-256, a CSV export, a weekly cron (Monday 14:00) for usage rollups, and Sentry alerts for stale syncs. Nineteen locale landings live at /{locale}/iot with i18n parity in DACH, France, Italy, Iberia, LATAM, North America, ANZ, South Africa, Croatia and Georgia. The master plan lives in docs/strategy/PATH-TO-100-PCT-IOT.md; nothing in it is theoretical anymore.
What is next
From coverage to depth
Coverage is the floor. With twenty markets and an IoT layer already in production, the next twelve months go vertical: regulatory cron jobs that file forms without human intervention where law allows, deeper per-vendor IoT sync coverage, and customer-beta programs in every market that produced a second-generation winery. The compliance libraries that closed this milestone become the substrate.
The roadmap is not secret: the IoT vendor catalogue already covers eleven clouds (Davis, Sencrop, Pix4D, Plant.id, Wialon, Geotab, OnVi, Krones, Pellenc, Anton Paar, Endress+Hauser); the beta-customer pipeline targets fourteen wineries in seven regions before the 2026 vintage. The ambassador program now spans nine countries.
For wineries that have lived on spreadsheets, consultants, or one-country ERPs because nothing else fit: that gap is now closed. Cepaos is the industry standard you can compare honestly against anything else.
Try it for fourteen days
See the platform in your own market
Pick your country, sign up in the local language, and ship your first compliance form in fourteen days. No card on file. No call required.
- 20 markets covered as of June 10, 2026
- 63 honest side-by-side comparisons published
- 9 compliance authorities natively supported
- 11 voice registers (Sie-Form, voseo, vouvoiement, and Anglo English), mother-tongue copy per locale