New Zealand's wine industry produces around 350 million litres of wine annually — roughly 70% of it Sauvignon Blanc, mostly from Marlborough. Despite this scale and the industry's strong export focus, a significant proportion of the country's wine operations are still managed through some combination of spreadsheets, paper logs, and institutional memory.
This is changing. Export market expectations, MPI compliance requirements, and the commercial pressures of operating in a high-value, competitive sector are all accelerating the shift toward purpose-built winery management software. This guide examines where spreadsheets fall short for New Zealand wineries and what the transition to dedicated software actually involves.
The Spreadsheet Reality in New Zealand Wineries
Walk through almost any winery in Marlborough, Central Otago, or Hawke's Bay, and you will encounter the same configuration: a harvest intake spreadsheet, a separate fermentation log, perhaps a barrel tracking file, and a pre-bottling checklist. Some of these will be on a shared drive; some will be on an individual's computer. The winemaker knows where everything is. Until they leave.
This is not a criticism of the individuals involved — it is a structural observation. Spreadsheets are genuinely flexible tools, and for a small operation making one or two wines from a single vineyard, they can be entirely adequate. But as complexity grows — more growers, more varieties, more wines, more export markets — the structural limitations of disconnected spreadsheets become operational liabilities.
The specific failure modes are consistent across operations:
Version proliferation. When the harvest intake spreadsheet is emailed around or saved in multiple locations, it is only a matter of time before different people are working from different versions. In vintage, when decisions need to be made based on current data, outdated spreadsheets create real risk.
Manual reconciliation overhead. Connecting grape intake records to fermentation batches, fermentation batches to blend records, and blend records to bottling documentation requires manual data matching. At low volumes, this is manageable. At 50 or more distinct batches across a vintage, it is a significant administrative burden.
No audit trail. Spreadsheets do not record who changed what, and when. If an MPI audit questions a specific volume figure — why does the bottling record show a different volume than the production record? — a spreadsheet cannot tell you whether the discrepancy is a data entry error or a genuine production issue.
Limited concurrent access. Google Sheets has improved multi-user editing, but most wineries still use Excel files stored on shared drives. Concurrent editing generates conflicts. In vintage, when lab staff, winemakers, and cellar hands all need to update records simultaneously, this becomes a practical bottleneck.
What New Zealand Wine Compliance Actually Requires
New Zealand's Wine Act 2003 and MPI's wine regulations create documentation requirements that directly affect how winery records should be structured.
The requirements centre on being able to demonstrate:
- The origin of grapes (grower, vineyard, GI or region, variety)
- The production chain from intake to finished wine
- Accurate volume accounting at each stage
- Compliance with labelling claims (variety, vintage, origin)
For export wines — the vast majority of New Zealand's premium production — additional requirements apply through NZW's export certification system. Each wine exported needs documentation of its composition that can be cross-checked against production records.
For wines carrying GI designations (Marlborough, Central Otago, Hawke's Bay, etc.), the traceability chain from grape intake to finished wine must support the origin claim. The Wine Act's definition of GI compliance (85% of the labeled region's fruit) is not just a labelling rule — it is a documented production requirement.
Spreadsheet systems can contain all of this data, but they are not designed to enforce it. There is nothing in an Excel file that prevents a user from recording inconsistent data, misidentifying a variety, or failing to update a record when wine is racked. Purpose-built winery software builds these constraints in structurally.
SWNZ Documentation: An Additional Layer
For the majority of New Zealand wineries that are SWNZ certified (or working toward certification), there is an additional documentation layer: environmental performance metrics.
SWNZ requires that certified wineries track energy use per unit of production, water use per litre of wine, waste generation and diversion, and chemical use. Pulling this data together from winery operations for the annual self-assessment is a manual exercise when the underlying data lives in separate systems — energy invoices in the accounts system, water use in a spreadsheet, winemaking records in another spreadsheet.
Winery management platforms that integrate production data with environmental metrics make SWNZ reporting substantially less burdensome. When each winemaking activity — a tank transfer, a refrigeration run, a fining treatment — is recorded in the same system, the data needed for SWNZ self-assessment is largely already available.
Purpose-Built Winery Software: What Changes
The core difference between spreadsheet-based management and a purpose-built winery platform is integration. Rather than separate files for each function, a winery management system links data across the production chain.
The practical changes that New Zealand wineries commonly report after switching:
Single source of truth for inventory. Current tank and barrel contents are always up to date, visible to all authorised users, and historically accurate. When a question arises about what is in tank 14, anyone with access can answer it instantly.
Lot traceability without manual work. When a lot moves from a tank to barrels, the lot history moves with it. Blend records automatically calculate variety and origin percentages based on the components' histories. Export documentation is generated from this data rather than assembled from scratch.
Compliance reporting on demand. Rather than preparing MPI export certification documentation as a separate exercise each time wine is shipped, the underlying production data is already structured correctly. The report is a matter of selecting the relevant lot and exporting.
Harvest management integration. Intake data — grower, variety, GI, weight, Brix, pH — entered at the weighbridge automatically creates the production batch record that persists through fermentation, blending, and bottling. No separate data matching is needed.
Multi-user real-time access. Lab staff, cellar hands, winemakers, and administrative staff all work in the same live system. Changes are visible immediately, and there is a complete audit log of who entered what and when.
Managing the Transition
Moving from spreadsheets to a winery management platform is a genuine change management exercise. Common challenges and how to address them:
Data migration. Historical production records in spreadsheets often need cleanup before they can be imported into a new system. Inconsistent variety naming, missing grower records, and uncategorised losses all need to be resolved. This cleanup is worthwhile — it forces a documentation audit that surfaces issues that have been obscured for years.
Staff buy-in. The platform is only as good as the data going into it. Cellar staff who have been recording events on clipboards need to adopt new data entry habits. Involving them in the selection process and investing in practical training significantly improves adoption rates.
Process standardisation. Switching systems is an opportunity to define standard procedures that may have been informal. Agree on how intake events are recorded, who updates vessel volumes after transfers, and what information is required before a batch can be closed.
Vendor selection. Choose a platform that handles New Zealand-specific compliance requirements (MPI documentation, NZW export certification, SWNZ data) rather than adapting a generic production management tool. Platforms like Cepaos are designed for wine industry traceability and compliance from the ground up.
The Long-Term View
New Zealand wine commands premium prices in export markets precisely because of its reputation for quality, authenticity, and integrity. The documentation systems that support that reputation — accurate origin records, verifiable composition data, traceable production chains — need to be robust enough to withstand scrutiny.
Spreadsheets were adequate for a simpler era. As export volumes grow, market expectations for transparency increase, and compliance requirements evolve, the operational case for purpose-built winery management software becomes progressively harder to ignore.
The wineries that invest in this infrastructure now will spend less time on compliance firefighting and more time on the things that actually differentiate their wines in a competitive global market.