Your ERP has to survive a Napier February: vintage, Art Deco crowds and a cruise ship at the wharf in the same week
A custom ERP (Enterprise Resource Planning) for a Napier winery or orchard operation lands at NZ$85,000 to NZ$240,000 over 14 to 30 weeks, based on Digital Heroes delivery patterns across 2,000+ projects. The band is wide because a Hawke's Bay ERP is three systems wearing one badge: block and vineyard operations, cellar or packhouse production, and an export paper trail that has to satisfy MPI and NZ Customs. If you only need the third one, buy NetSuite and stop reading.
It is the third week of February in Napier. Brix readings say two Gimblett Gravels blocks need picking inside 48 hours, the Art Deco Festival has taken every bed from Ahuriri to Marine Parade, and a cruise ship berths Thursday with a thousand people who will want to taste something. Your NetSuite instance knows about none of that. It knows about invoices.
That is the real limit of off-the-shelf ERP here. SAP and Microsoft Dynamics were designed for plants with stable throughput and a bill of materials that does not change because it rained. Odoo will model a manufacturing order beautifully, then buckle when the order is a ferment that splits across four tanks, gets pressed three days early, and comes back as two wines and a rosé you did not plan. Meanwhile the orchard side counts bins on paper and the cellar door runs its own till. The office becomes the integration layer, which is a polite way of saying two people spend February retyping.
Why the usual tools struggle in Napier
- Vintage yield changes daily with heat and brix, but NetSuite production orders assume a fixed recipe and a fixed output
- Cellar door, wine club and export sales sit in three ledgers, so nobody can say what a single vintage actually earned
- MPI wine export eligibility packs and NZ Customs excise returns get assembled by hand in the busiest fortnight of the year
- Orchard bin counts, packhouse throughput and coolstore stock reconcile weekly at best, so a short shipment shows up after the container is booked
What a custom ERP build changes
Custom earns its keep when your operating calendar, not your accounting calendar, is the thing that breaks. A Napier ERP built properly treats a vintage as a first-class object: blocks, pick dates, weighbridge dockets, tank movements, additions, and the excise status of every litre from press to pallet. It lets a cellar door sale, a wine club dispatch and a container bound for Southampton settle into the same ledger without a monthly spreadsheet marriage. For orchard operators it means bin-level traceability from row to controlled-atmosphere coolstore to phytosanitary certificate, which is the difference between answering a market query in an hour and answering it in a fortnight.
The features that matter for Napier
ERP services we deliver in Napier
Digital Heroes builds the full ERP stack for Napier teams. Typical engagements cover ERP migration, cloud ERP, manufacturing ERP, distribution ERP and custom ERP modules.
- Your production reality is fermentation or fruit flow, not discrete assembly, and every demo needs a workaround before the second screen
- Export documentation for MPI or NZ Customs is produced by one person who is a single point of failure
- You run a wine business and a hospitality business on the same site and the two never share a number
- Seasonal headcount swings by more than triple and rostering, piece rates and cost accounting do not talk to each other
- You are under about 40,000 cases and your main pain is accounting hygiene rather than production complexity
- A specialist winery package already covers your cellar workflow and you only need it plumbed into finance
- You have no in-house owner for the system after go-live and nobody is willing to become one
- Your export volume is small enough that manual MPI documentation costs a few hours a month, not a few days
ERP pricing in Napier: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| Core ERP for a single-site winery or packhouse | NZ$85,000 to NZ$130,000 | 14 to 18 weeks |
| Multi-entity build spanning vineyard, cellar door and export | NZ$130,000 to NZ$190,000 | 20 to 26 weeks |
| Full operation including orchard, coolstore and port documentation | NZ$190,000 to NZ$240,000 | 26 to 30 weeks |
From kickoff to launch: the schedule
Exactly what you get
A working system, a data model you can explain to your bank, and a documented handover. In practice that means a vintage module following fruit from block to bottle, a stock ledger that knows the difference between excise-liable and export-bound litres, and a sales layer where the cellar door, the wine club and the container all draw down the same allocation. Orchard operators get bin-level intake, coolstore location and a traceability export that survives a market query.
You also get the unglamorous parts that decide whether this lasts: role-based access so a casual cellar hand cannot edit a bond record, an audit trail on every stock movement, and clean integration into your existing NZ accounting stack rather than a replacement for it. Most Napier builds pair this with a business intelligence (BI) layer, a customer system for the wine club, and eventually a warehouse system once coolstore volume justifies it.
How to choose a developer in Napier
Ask for the ugly parts. Any agency can show you a clean dashboard. Ask them to explain how they would handle a tank topped from two different lots, or a bin of Royal Gala downgraded after grading. If they cannot describe the edge case without asking you to define it first, they will discover it during build at your expense.
Local presence matters less than harvest literacy, though it is not nothing. Someone who can drive to Havelock North during a cutover week is worth more than someone brilliant in a distant timezone. Check that they will work in winter and go live in winter. Check that they will write down how the system works in language your operations manager can read. And settle code ownership before the first invoice, because retrofitting that conversation after a build is expensive and awkward.
- One vintage ledger covering fruit intake, tank movements, blending and bottling, so cost per litre is real rather than reconstructed in June
- Excise-liable stock is tracked separately from export-bound stock from the moment it enters bond, which makes the NZ Customs return a report instead of a project
- Cellar door, wine club and distributor demand share one stock position, so you stop selling allocation you already shipped
- Seasonal crew hours, piece-rate picks and packhouse output feed payroll and cost accounting without a second data entry pass
- Cruise arrival dates and Art Deco Festival weekends load as demand events, so purchasing and rostering see the spike weeks out
- You own the roadmap. No vendor ships a compliance update when MPI changes an export form, so budget maintenance from day one
- A 20 to 30 week build means at least one vintage runs on the old system. Sequencing the cutover into a post-harvest window is not optional
- Your team has to be available during discovery in the season they are least available, which is why we push discovery into winter
- Custom removes the fallback of hiring someone who already knows the software. Documentation and handover quality become a risk you have to manage
- !They demo a generic manufacturing module and call fermentation a batch process. Ask them to walk through a tank split and a rosé bleed on screen
- !No question about excise or MPI export eligibility in the first meeting. Ask what they have shipped that touched NZ Customs
- !A fixed price quoted before anyone has seen your intake dockets. Ask for a paid discovery instead
- !They propose go-live in February. Ask them to justify that cutover date against your harvest calendar
- !No named maintenance owner or handover plan. Ask who supports this in year three and what it costs
Teams investing in ERP in Napier usually scope it next to internal tools, shopify, inventory management, since these systems share data and budgets. Weighing options across the region? We publish the same ERP guide for Hastings. Want it built, not just budgeted? That is our ERP development practice.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- The federal government spends about 80% of its IT budget on operations and maintenance of existing systems rather than on development or modernization, with many critical systems being decades old. Source: U.S. Government Accountability Office (GAO) (2025) →
- In a February 2026 survey of 517 small-business employers, 82% had adopted at least one AI tool (typical firm uses five), 66% reported revenue increases linked to AI (22% reported gains exceeding 10%), and 74% said digital platforms make it easier to compete with larger firms; owners saved a median of 5 hours per week and businesses saved a median 11.5 employee-hours weekly. Source: Small Business & Entrepreneurship Council (SBE Council) (2026) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
Lachlan heads mobile design at Digital Heroes, covering iOS and Android work from first flows through to handoff specs the engineering leads can build against. He spends a lot of time on the unglamorous parts: navigation, empty states, permissions. Readers get the design side of what makes an app feel finished.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
What does a custom ERP cost for a Hawke's Bay winery?
Expect NZ$85,000 to NZ$240,000 depending on how much of the operation you fold in. A single-site winery with a cellar door and a modest export book sits near the bottom of that band. Add an orchard, a coolstore and full MPI export documentation and you move to the top. Digital Heroes prices these in stages so you can stop after the vintage module proves itself.
How long does an ERP build take if I want it running before the next Napier vintage?
Fourteen to thirty weeks of build, plus a cutover window. If vintage starts in late February, work backwards: discovery in June or July, build through spring, parallel running across December and January. Starting a build in November and hoping to be live for harvest is how projects end up half-migrated during the worst month of the year.
Can custom ERP handle NZ Customs excise returns for cellar door sales?
Yes, and this is one of the strongest arguments for building. Excise applies to alcohol removed for home consumption while export volumes are excise-free, so the system needs to know the destination of every litre the moment it leaves bond. A custom ledger tags that automatically. Off-the-shelf ERP almost always leaves it to a spreadsheet someone maintains by hand.
Should I migrate off NetSuite or run it alongside a custom system?
Run it alongside for one cycle if NetSuite genuinely does your finance well. Most Napier builds keep accounting where it is, often Xero or MYOB, and put the custom system in front of it for operations. Ripping out a working general ledger during the same project that introduces a new production model doubles your risk for no operational gain.
Who owns the source code when a Napier agency builds our ERP?
You should, in full, with the repository handed over and licences in your company name. Get it written into the contract before work starts. If an agency wants to retain ownership and licence it back to you, that is a commercial choice you can make knowingly, but it changes what the asset is worth and what happens if the relationship ends.
Can the ERP account for the Art Deco Festival and cruise ship arrivals?
It can, and it should. Load the festival dates and the Napier Port cruise schedule as demand events and the system flags rostering gaps and stock shortfalls weeks ahead. That is a small feature with an outsized payoff, because both peaks land on top of vintage and the cellar door is usually the thing forgotten until the Monday before.
What ongoing maintenance should we budget after go-live?
Plan for roughly 15 to 20 percent of the build cost annually, covering hosting, security patching, small enhancements and the compliance changes that arrive without warning. Napier operators often underspend here for two years and then face a large remediation. Treat it as an operating budget line, not a contingency.
Do we need to hire an internal system owner in Napier to make this work?
You need someone accountable, not necessarily a new hire. In most Hawke's Bay operations of this size the winemaker or the operations manager becomes the product owner with about two hours a week in steady state. What fails is when nobody owns it and every change request routes through whoever answered the phone.
How does a custom ERP handle GST and IRD filing requirements?
It handles the transactional side and hands the rest to your accounting system. The ERP records GST treatment per line, separates zero-rated export sales from domestic sales at 15 percent, and posts a clean journal into Xero or MYOB, which stays the system of record for your GST return in myIR. Building your own tax filing engine is a cost with no upside.
What happens to my ERP if the agency shuts down or we part ways?
What tech stack should a custom ERP be built on?
How long does it take to build a custom web or mobile app from scratch?
Should I hire a freelancer or an agency for my software project?
How many developers does it take to build an ERP?
What should I prepare before contacting a software development agency?
How many SaaS seats do we need before building custom becomes cheaper?
What are the biggest mistakes first-time software buyers make?
Who can build custom ERP software for a business in Napier?
Digital Heroes builds custom ERP software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, so an operator in Napier gets an assigned senior team rather than a local account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other ERP software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
