| IT for wineries is the technology that runs a vineyard, a winery and a cellar door as one business. It has to survive a wash-down environment, carry a network across blocks with no cable, and produce the batch records that make wine sellable at home and overseas. |
Fruit started arriving on the Tuesday. By Thursday the link between the winery and the office had dropped, and it stayed down for most of a day.
Nobody could enter a weighbridge docket or update the vessel board. The lab wrote its numbers on paper and the office guessed at the rest.
A day like that in November barely registers. This one landed in the second week of vintage, with twenty-two people on site and fruit still coming through the gate.
Call it an illustrative 35,000-case North Canterbury producer: fourteen permanent staff, about thirty through vintage, cellar door open six days a week. The figures below are illustrative too.
Two half-day outages like that one cost it roughly $6,000 in idle wages, at a loaded $34 an hour.
Three days across the summer when the cellar door could not take payment cost it about $2,100 in trade.
The third line is the largest. A winemaker and an administrator spend around six hours a week copying vessel movements off a whiteboard into a spreadsheet, which over a 40-week season at $45 an hour comes to about $10,800.
Those three lines come to about $18,900 a year.
Wineries run three operations on one site. Vineyard blocks spread across hectares with no cable, a working winery with hoses and wash-down, and a cellar door selling to the public.
Each has different requirements, and all three peak in the same eight weeks.
What Is IT for Wineries?
IT for wineries is the technology that runs the vineyard, the winery and the cellar door as a single business. It covers the network across the blocks, hardware that survives a wet production floor, the winemaking records that make wine sellable, and the payment and stock systems at the counter.
Most of it looks like ordinary business IT until you look at the calendar. Everything has to work between February and April.
The industry calls that window vintage, or harvest. It runs from the first fruit over the weighbridge to the last ferment going dry.
Which systems does a winery run?
A winery runs five. A winemaking or cellar system holding batches and vessels, a vineyard record system for blocks and spray applications, an accounting ledger, a point-of-sale and stock system at the cellar door, and a wine club database for direct sales.
Larger producers add a laboratory system for analysis results and a dispatch system for export documentation.
Smaller wineries often run three of those five on spreadsheets. The spreadsheets hold up until somebody asks for a batch history going back three vintages.
How is a winery different from a farm?
A winery adds a processing step and a shop to what a farm does. Growing fruit is agriculture, and the moment that fruit goes into a press it becomes a manufactured food product with a record trail attached to it.
The vineyard side shares most of its problems with other rural operations, and our guide to rural connectivity for farms covers the paddock end of it.
The winery side behaves like a small food plant. Tanks, pumps and temperature control sit on a floor that gets hosed down twice a day.
Where that floor carries machine controllers and plant networks, IT for manufacturing is the closer guide.
What Happens When Winery Systems Go Down During Vintage?
Work stops at the point of failure, and during vintage none of it can be deferred to next month. For six to eight weeks the winery runs long shifts, fruit arrives on somebody else’s schedule, and people are paid to wait while a system is unavailable.
The cost of an hour changes with the calendar. An outage that costs the office an afternoon in July stops a press in March and leaves eleven people standing.
What breaks first when the crop arrives?
The connection between the blocks and the winery breaks first, usually because it was marginal all along and nobody tested it under load. Vintage puts several times the traffic on the same link: weighbridge dockets, harvest lot entries, photographs and calls.
Second is the printer nobody owns. Grower statements and weighbridge dockets get printed at the crush pad, and the device sitting there is often the oldest one on site.
Third is access. Vintage casuals need logins on day one and lose them on the last day, and a winery hiring sixteen people in a fortnight rarely has that as a routine.
When should a winery do its IT work?
Between May and December. Anything that changes a system, moves data or replaces hardware belongs outside the vintage window and finished by the end of January.
Decide in winter what has to be different by the next harvest, and buy it with enough lead time to test it properly.
Wineries that skip that step end up paying rush rates for the same work in March.
How Do You Get Internet to a Vineyard and Winery?
Usually with a business-grade fibre or fixed wireless connection at the main building, then a point-to-point wireless link out to whatever the cable does not reach. Rural internet on a winery site is a design job, because the buildings sit at different distances from the road and the blocks have nothing at all.
Sites also need hardened wireless coverage across the crush pad and tank hall, designed as one winery network in place of three that grew separately.
What links a building the cable does not reach?
A point-to-point wireless link, which is a pair of directional radios mounted with clear line of sight between two buildings. It carries a usable connection over several kilometres for a fraction of the price of trenching fibre.
Trenching through planted rows is expensive and disruptive.
Where a block has nothing at all, cellular with an external antenna will cover a scale house or an irrigation controller. Vineyard connectivity rarely needs more bandwidth than that.
A single internet connection with no fallback is the common weak point on a rural site, and business internet and failover covers how to size and back it up.
What hardware survives a working winery?
Hardware rated for dust and water survives a winery floor. Office-grade access points and tablets fail inside two vintages in a room that gets hosed down and swings between four and thirty-five degrees.
Ask for an ingress protection rating, written as IP followed by two digits. IP65 means dust-tight and protected against water jets, which is the practical minimum inside a tank hall.
Mount access points high and clear of the wash-down path. Put the switch and the recorder in a sealed cabinet with ventilation.
Tablets used at the crush pad want a rugged case and a screen that responds to wet hands.
What Records Does a Winery Have to Keep?
Enough to trace any bottle back to the block it was picked from. New Zealand grape wine made for export must be produced and packaged under a Wine Standards Management Plan, shortened to WSMP, registered with the Ministry for Primary Industries.
MPI is the regulator, and the plan sets out how the winery meets the standards in the Wine Act 2003.
The record duty is specific. For each lot or batch, an exporter has to record the WSMP number the wine was made under, the quantity, the storage location and the package type, and the person or business the wine was bought from and sold to.
Documents also have to support any label claim about grape variety, vintage or region, alongside export eligibility requirements and any overseas market access requirements.
None of it is optional if you export. A winery that cannot produce the record ends up holding wine it cannot ship.
What is batch and vessel traceability?
Batch traceability is an unbroken record linking a bottled batch back through every blend, ferment vessel and harvest lot to the vineyard block it came from. Every transfer and addition has to be recorded against the vessel that received it.
- Block and row, with the pick date and the weight recorded over the weighbridge.
- Harvest lot, carrying the grower, the variety and the condition of the fruit on arrival.
- Ferment vessel, with every addition, analysis result and temperature reading against it.
- Blend components, each named with the proportion it contributed.
- Bottled batch, with the fill date, the bottle count and the label version used.
- Dispatch, naming the customer, the market and the documentation issued.
A whiteboard holds that chain for one vintage. By the fourth year, when a buyer asks about a wine bottled in 2023, the whiteboard has been wiped a dozen times.
What does an export buyer ask a winery to produce?
Usually the batch history and the analysis behind a label claim, wanted in days. Export records spread across three spreadsheets and a shed folder take a week to assemble, and they still come back with gaps.
MPI Trade Certification keeps a record of export transactions, which helps a winery track eligible litres by market. The winery still has to keep its own records behind that.
A wine stopped at a border is a harder deadline. Where an export no longer meets the requirements, MPI has to be told within 24 hours.
A winery running its records on one server in a shed should get them off site, and our cloud solutions cover where that data should sit and how it gets backed up.
Where do spray and chemical records sit?
In the vineyard record system, and they have to come out quickly when you are asked for them. Spray applications, product, rate, date, block and operator all belong in one place with the harvest data they affect.
Some substances on a winery site carry a stricter duty. Where a substance is one of the tracked substances under the hazardous substances rules, WorkSafe requires the record to let an inspector find its location within two minutes and the substance itself within an hour.
A folder in a shed will not meet a two-minute test.
Certification gives a second reason to keep them tidy. Sustainable Winegrowing New Zealand, the programme led by New Zealand Winegrowers, requires vineyard members to submit a full spray diary each year covering every agrichemical application made that season, and it certifies 98 per cent of New Zealand’s producing vineyard area.
How Should a Cellar Door Be Set Up?
As a retail and hospitality operation on an industrial site, with its own network and its own payment path. Cellar door technology means point of sale, stock that reconciles to bottled inventory, a wine club database and guest wifi that touches none of them.
Payment has to keep working through all of it. A terminal that fails on a Saturday in February costs a full trading day at the busiest time of the year, with a queue at the counter and no way to take money.
The counter itself is a shop, and the same rules apply there as anywhere else in retail. Our guide to point-of-sale and stock control goes into how to size it. Where the cellar door runs a restaurant or functions, the booking and kitchen side belongs with hospitality IT.
Where the cellar door serves food, a plan under the Food Act 2014 applies. New Zealand Food Safety publishes a Food Safety Template for Winemakers covering winemakers who serve food made by others in a cellar-door tasting room or cafe.
Older guidance called this a food safety programme, and plenty of operators still search for it under that name.
What happens when the cellar door loses its connection?
Trading stops unless the terminal has an offline path. Ask the payment provider what the terminal does with no connection and how long it can hold transactions before it starts refusing them.
A second connection dedicated to the cellar door is cheap insurance over summer.
Who owns the wine club list?
The winery owns it and the platform holds it under the subscription agreement. Confirm the export format before signing, and run an export during the trial to see whether purchase history and consent records come out alongside the names.
Direct sales through a wine club come in at full margin, so that database is worth protecting properly.
What Does Winery IT Cost?
IT for wineries costs a mid-sized producer roughly $4,000 to $6,000 a year in software and support, plus a one-off site spend of $5,000 to $12,000 to fix connectivity and hardware. Distance between buildings drives most of the variation.
| What you are paying for | What it covers | Indicative range |
|---|---|---|
| Winemaking and traceability software | Batches, vessels, additions and analysis results | $300 to $600 a month |
| Vineyard records | Blocks, spray diary and harvest lots, often bundled with the winery module | $0 to $1,800 a year |
| Site network | Point-to-point link, rated access points, sealed cabinets and cabling | $5,000 to $12,000 once |
| Cellar door systems | Point of sale, stock sync and a second connection | $150 to $400 a month |
| Managed support and backup | Monitoring, patching, offsite backup and a vintage response time | $90 to $150 per user a month |
| Doing nothing | Reconciliation hours, vintage downtime and cellar door outages | Recurs every year |
What does that net out at for the illustrative winery?
About $7,900 in the first year and about $14,100 a year after that. Return to the illustrative 35,000-case North Canterbury winery, whose reconciliation hours, vintage outages and cellar door downtime came to about $18,900 a year.
Fitting winery software and rebuilding the site network costs it about $4,800 a year in subscription and about $6,200 once for the link and the rated hardware, so year one runs to about $11,000. Year two onwards carries the $4,800 alone.
Subtract one from the other: about $7,900 avoided in year one, then about $14,100 a year.
The reconciliation saving only lands if the cellar crew records movements as they happen. The rated tablets in the table above are there for that reason.
What Should a Winery Do Before the Next Vintage?
Work through six things between May and December. Each one removes a failure that otherwise turns up in the worst eight weeks of the year.
- Test the link between the blocks and the winery under load. Push several times normal traffic through it in winter and watch what drops.
- Write the vintage roster and create the logins before the fruit arrives. Name the person who disables them on the last day.
- Replace any device inside the tank hall without a dust and water rating. Check the cabinet seals while you are in there.
- Get one vintage of records into the system before you need three. Start with the current season and back-load one earlier year.
- Confirm the cellar door can take payment with the main connection down. Test it on the terminal itself.
- Check the backup by restoring something. A backup nobody has restored from has never been tested, so do the restore in September.
Book a Winery IT Review Before Vintage
Exodesk has supported South Island businesses since 1989 and works with clients across Canterbury, Otago and Southland from offices in Christchurch and Dunedin. Reviewing IT for wineries means walking the site from the vine rows through to the tasting room, then costing the gaps against what the next vintage will ask of them.
Contact us today to discuss how we can help your business or connect with us on LinkedIn to stay updated with more insights.
Frequently Asked Questions
What does an IT provider do for a winery?
An IT provider looks after the site network, the hardware in the production areas, the systems holding winemaking and vineyard records, and the point-of-sale gear at the cellar door. Most wineries also buy monitoring and offsite backup as a managed service. During vintage the part that matters is a guaranteed response time.
What is a Wine Standards Management Plan?
A Wine Standards Management Plan, or WSMP, is a registered plan setting out how a winery meets the winemaking standards under the Wine Act 2003. New Zealand grape wine intended for export must be made and packaged under a WSMP registered with the Ministry for Primary Industries. The plan is verified by an approved verifier, and the winery keeps records against it for every lot or batch.
Is winery software worth it for a producer making 3,000 cases?
Yes, once the producer exports or sells through more than one channel. A 3,000-case winery can hold a vintage on spreadsheets, but the cost lands later, when a buyer asks for a batch history and somebody spends two days rebuilding it. Subscription pricing at the small end starts around $150 a month. Below that volume, and selling only at the gate, a disciplined spreadsheet with one owner will still hold the line.
How much should a boutique winery budget for IT in its first year?
A boutique winery should budget $8,000 to $15,000 across the first year, covering software subscriptions plus a site network fix and the support around it. The one-off network and hardware spend takes up most of that first-year figure. IT for wineries then settles to roughly $4,000 to $6,000 a year once the site is right.
How far can a point-to-point wireless link reach?
A point-to-point wireless link carries a usable business connection several kilometres where the two radios have clear line of sight. Trees, a ridge or a shed roof in the path will cut that range sharply, so survey the path before choosing the radios.
Can one system handle both the vineyard and the winery?
Yes. Several platforms sold into New Zealand wine cover vineyard records and cellar operations in one product, which keeps the block data and the batch data joined. Wineries that buy them separately need the harvest lot number to carry across, because the harvest lot number carries the block data into the winery records.
Do vintage casuals need their own logins?
Yes. Shared logins on a vintage crew hide who entered a weighbridge docket or an addition, and a traceability record depends on knowing that.
What should a winery back up, and how often?
Back up the winemaking and vineyard records, the accounting file, the cellar door sales and customer data, and any laboratory results, daily during vintage and at least weekly outside it. Keep one copy off site. Test a restore before the season starts, not after something fails. Cloud-hosted platforms still need an export you hold yourself, because a subscription lapse can put the data out of reach.
How long do wineries need to keep batch records?
Long enough to answer questions about wine still in the market, which for a cellared red can run to a decade. MPI sets record requirements for exporters under the Wine Act 2003, and the winery’s own Wine Standards Management Plan states what it keeps and for how long. Treat the plan as the answer, then check the system can still produce the record at the end of that period.
Does a cellar door serving food need a food control plan?
Yes. A cellar door serving food comes under the Food Act 2014, and New Zealand Food Safety publishes a Food Safety Template for Winemakers that covers winemakers serving food made by others in a tasting room or cafe. Check the requirement through the My Food Rules tool before opening a kitchen.
Does SWNZ certification change what records a vineyard has to keep?
Yes. Sustainable Winegrowing New Zealand requires vineyard members to submit a full spray diary every year, documenting each agrichemical application made that season. SWNZ certifies 98 per cent of New Zealand’s producing vineyard area, so for most growers the spray record is already an annual obligation. Keeping it in the vineyard system means the submission is an export, and no one spends a week rebuilding it from paper.
Who provides IT for wineries in Canterbury and Central Otago?
Exodesk provides IT for wineries across Canterbury, Otago and Southland, working from offices in Christchurch and Dunedin. The work covers site networks between vineyard blocks and the winery, rated hardware for production areas, winemaking and traceability systems, cellar door point of sale, and backup that survives a vintage. Exodesk has operated since 1989 and builds its own business software alongside the products it supports. A site review before vintage is the usual starting point.
