Enowise
End-to-end operating platform for wineries — vineyard mapping, batch tracking, EU compliance labelling, and wine-tourism modules running on one schema.
- Client
- Enowise
- Industry
- AgriTech / Wine
- Timeline
- Multi-phase
- Team
- 3 engineers
The brief
Wineries were juggling four or five tools to run a single vintage — a spreadsheet for blocks, a separate app for vessels, a printer for labels, a third party for QR-based e-labels, and yet another platform for tasting-room bookings. Enowise needed one operating system with a shared data model so every action — from phenology entry to harvest report — feeds the same source of truth.
The approach
- 01
Designed a domain model spanning vineyard (blocks, varieties, phenology), winery (batches, vessels, movements) and brand (labels, e-labels, tasting bookings) — all under one tenant boundary.
- 02
Built a Next.js + tRPC application with Mapbox-driven block editing and a typed event log per vessel, so any operation is auditable from grape to bottle.
- 03
Implemented the EU e-label flow end to end: QR generation, allergen and nutrition declarations, multilingual content, and harvest-report exports that satisfy regulatory submissions.
- 04
Integrated WineKite tourism and ScanForFacts compliance as first-class modules instead of bolt-ons — they share users, brands and analytics with the core platform.
The outcome
Wineries onboard once and run vineyard, cellar, compliance and visits from one schema. The platform ships EU-compliant e-labels out of the box, and the tourism layer drives direct bookings without leaving the brand surface.