2026 buyer guide for NZ wineries
A neutral 8-category framework with the questions every New Zealand winemaker should ask a vendor before signing — covering SWNZ, MPI export documentation, and the realities of running a winery from Marlborough to Central Otago.
Most New Zealand wineries start evaluating software under pressure: an SWNZ scorecard chase that took two weekends, an MPI export submission rejected for missing batch data, a spreadsheet that fell over in the middle of a tight vintage. In that mode it is tempting to sign the first contract that addresses the immediate pain and discover six months later that the platform does not actually model the way an SWNZ-certified, GI-aware NZ winery operates.
The market offers very different products. Legacy platforms still sell perpetual licenses with 20% annual maintenance. Newer tools designed for Northern Hemisphere boutique wineries do not always fit a Marlborough Sauvignon Blanc producer with three vintages worth of contract crush data to migrate. And generic ERPs offer a ‘wine module’ that is really an SKU template with no concept of a lot, a tank or a blend. None of these is universally right.
This guide does not compare vendors by name. It compares the questions you should bring to every vendor — Cepaos included. The eight categories below are the framework. The closing section explains where Cepaos sits inside the same framework, without disguising it as a competitor matrix.
Evaluation framework
Apply the framework to every shortlisted vendor, including us. If a category stays vague during the demo, that is enough information to make a decision.
Does the system hold the lot-level evidence MPI expects for Export Certificates and the Wine Standards Management Plan? Does it record the inputs SWNZ scorecards require — water, energy, additions, waste, biodiversity — at the moment they happen instead of in an annual scramble? If the answer involves rebuilding from spreadsheets, you do not have compliance — you have an annual reconstruction project.
Ask the vendor to walk through a real NZ case: Sauvignon Blanc picked from three Marlborough sub-regions on different dates, fermented in two tanks, blended into one cuvee, then bottled in 750 ml screwcap and 187 ml singles. If the demo stalls or relies on direct database queries, that platform does not have traceability — it has tables.
Pick, crush, sort, ferment, racking, ageing, blending, fining, filtration, bottling. Real winery software treats each step as a stock event with loss accounting, not a comment in a free-text field. Ask how filtration loss is recorded, how free and total SO2 attach to a lot, and how vintage is closed at the last operation of the year.
If you ship to the US, the UK, China or Australia, you need real multi-currency, market-specific pricelists, digital export certificates, and the ability to generate proformas and packing lists in the importer's language. Some legacy systems still rely on a parallel Excel in USD or GBP — that is not acceptable in 2026.
Integrations are where the difference between a winery platform and a glorified template shows up. Ask for live demos: Xero or MYOB accounting sync, lab equipment APIs for analytical instruments, and lot-level handoff to MPI Export Certificates. If the answer is 'export a CSV and upload manually', that is not an integration — it is a workaround dressed up as one.
Monthly or annual subscription vs perpetual license. Per tonne crushed, per user, per site, or flat. Each model has a trap: perpetuals hide maintenance, per-user pricing punishes large teams, per-tonne penalises growth. Ask for a five-year total cost projection under two scenarios — stable and 30% annual growth.
A boutique NZ winery can be live in one to two weeks. A mid-size operation, in four to six. If a vendor promises 'go-live in 48 hours' with vintage history migrated, push back: real migration requires mapping block codes, chart of accounts and SWNZ input categories. Confirm support hours in NZ business time, language, real SLA and whether the first month includes scheduled onboarding.
Where is the data hosted? Who is the subprocessor for backups? Is a DPA available? How do you export the full database the day you decide to leave? You own the data — but ownership is only meaningful if the vendor honours it in practice. Ask for an up-to-date subprocessor list and the data retention policy.
We are not asking you to trust a comparison chart. We are asking you to apply the 8-category framework above and verify each answer in a live demo with your real vintage data.
Water, energy, additions, waste and biodiversity inputs logged as events on the lot they affect. No annual scorecard rebuild from notebooks and emails.
Accounting sync and analytical instrument APIs demoed against your own data during the trial. Lot-level evidence ready for MPI Export Certificates. No CSV-and-pray exports.
Transparent monthly pricing published on the website in NZD. No annual maintenance percentage, no per-user surcharge, no penalty for tonnage growth. What you see is what you pay.
Assisted migration from Excel or your previous system in the first 30 days at no extra cost. Scheduled onboarding sessions in NZ business hours, not a generic email inbox.
Avoid contracts with long lock-in periods that have no exit clause, perpetual licenses that quietly add 18-22% annual maintenance, and vendors that will not commit in writing to full data export in an open format. Ask explicitly who owns the data and how it is exported the day you decide to cancel.
A small Central Otago or Marlborough boutique winery can be operational in one to two weeks. Mid-size operations spanning Hawke's Bay and Marlborough vineyards typically go live in three to five weeks. Multi-site producers with contract crush deals can take six to twelve weeks. Be cautious of vendors promising 'go-live in 48 hours' with real vintage history to migrate.
If you export wine, you deal with MPI Export Certificates and the Wine Standards Management Plan. If you are part of Sustainable Winegrowing New Zealand (SWNZ), your scorecard requires lot-level records on water, energy, additions and waste. A serious winery platform should hold the evidence in a structured form, not in narrative paragraphs that get rewritten each year for the audit.
Perpetual licenses are paid once but usually carry 18-22% annual maintenance for updates and support. Subscriptions bundle updates, support and backups in the monthly fee. For wineries crushing under 1,000 tonnes, subscription tends to be cheaper over five years and avoids the technical debt of running legacy on-prem versions.
Insist in the contract on the right to export every record in CSV or JSON: movements, lots, vessels, lab analyses, SWNZ inputs and invoicing. Portability is increasingly expected but the practical quality of the export depends on the vendor. Run a test export during the trial and confirm the file can be re-imported elsewhere without losing relationships between blocks, lots and blends.
Not strictly, but the cost of running disconnected systems is real. If cellar door and wine club volume matters, an integrated platform means the bottle you ship to a club member is the same lot tracked against your tank in the cellar. Disconnected systems mean double entry, stocktake disagreements and one more reconciliation at month-end.
TRANSPARENT PRICING
From $29/month
Boutique plan $249/month
14 days free, no credit card. Excel migration included. We apply the same framework you just read and answer each of the 8 categories against your real vintage data during onboarding.
Start free trial