ERP · Dunedin

Your Dunedin plant passes its MPI verification on paper while NetSuite guesses at the batch

ERP Development architecture and database illustration for Dunedin, OTA, New Zealand.
The short answer

A custom ERP (Enterprise Resource Planning) for a Dunedin food processor, beverage producer, or export manufacturer runs NZ$95,000 to NZ$210,000 over 6 to 10 months. What prices you out of NetSuite, SAP, or Odoo is not the general ledger. It is that they assume a bill of materials that holds still, and yours moves with the input: carcass yield, brew gravity, casting scrap. Add a Risk Management Programme the MPI verifier expects to see evidenced, and a container that closes at Port Chalmers on a fixed cutoff, and the gap becomes structural rather than a configuration problem.

The batch sheet is a clipboard hanging by the chiller. The export pack for the next sailing gets rebuilt in Word the night before the container closes. Your MPI records live in a ring binder because that is the format the verifier actually opens, and finance closes the month by ringing the plant to ask what really came off the line. Somewhere in the middle sits a NetSuite or Odoo licence you are paying for.

The off-the-shelf platforms are not badly built, they are built for a different factory. SAP and Microsoft Dynamics model production as a scheduled run of known inputs producing known outputs. Otago production is variable yield plus flexible labour, and the cost of a run is not knowable until the run is over. Odoo gets closer and costs far less, but the moment you need batch genealogy that survives a trace, GST reconciling cleanly back to Xero, and export documentation keyed to a specific vessel, you are writing Python against Odoo. You end up paying platform fees and building custom anyway.

The fix: ERP built for Dunedin, not rented

You build custom when the product itself refuses to sit still in a fixed BOM. A Dunedin build encodes variable yield at the run level, blended casual and salaried labour costed onto the batch, genealogy that carries intake through pack to container number, and export documentation generated against a real sailing schedule. The test is simple: can a supervisor with wet hands and a cold tablet record what actually happened, in the same minute it happens, without a second data entry step at 6pm. Off-the-shelf ERP fails that test because it was never designed to be used on a plant floor in July.

The capability list that earns its budget

What to build in
+Batch and lot genealogy chaining intake, run, pack, and container in one record
+Plant-floor capture on rugged tablets or scanners that works cold, wet, and offline
+Labour costing that blends salaried, casual, and shift-loaded rates onto the individual batch
+Export document generation tied to vessel schedules and cutoff times from Port Chalmers
+Two-way Xero sync for GST, accounts payable, and payroll journals instead of a second set of books
+Risk Management Programme record keeping with verifier-ready exports on demand

ERP services we deliver in Dunedin

Digital Heroes builds the full ERP stack for Dunedin teams. Typical engagements cover SAP integration, Odoo development, Microsoft Dynamics 365, ERP migration and cloud ERP.

What ERP costs in Dunedin

Project scopeTypical costTimeline
Single-site production ERP with batch traceabilityNZ$95,000 to NZ$140,0006 to 8 months
Multi-entity ERP with export documentation and Xero syncNZ$150,000 to NZ$210,0008 to 10 months
Traceability and yield layer over existing Odoo or NetSuiteNZ$48,000 to NZ$85,0003 to 5 months
Cost by project scopeCost by project scopeSingle-site production ERP with batch traceability$95k to $140kMulti-entity ERP with export documentation and Xero sync$150k to $210kTraceability and yield layer over existing Odoo or NetSuite$48k to $85k
Typical project cost bands. Source: Digital Heroes 2026 delivery benchmarks.

How long it takes, phase by phase

Delivery timeline by phaseDelivery timeline by phaseDiscovery3 wkDesign3 wkBuild10 wkTest3 wkLaunch2 wk
Indicative delivery timeline by phase.
Want these numbers scoped for your Dunedin operation?
Bring the messy version. You leave with a plan and a real number in 48 hours.
Talk to Digital Heroes

Exactly what you get

A working ERP that understands Dunedin production starts with a variable input, not a schedule. Concretely: batch genealogy from intake to container, floor capture that survives a cold shift, blended labour costed onto the run, export packs generated against real sailings, and a clean two-way Xero sync so your accountant does not inherit a second ledger. You also receive the source code, the deployment runbook, and the data model documented well enough that another team could pick it up. The stock, movement, and freight sides sit naturally alongside custom inventory management software, a warehouse management system, and supply chain software, while your accounting software stays exactly where it is.

How to choose a developer in Dunedin

Pick the team that asks to stand on your floor before they talk modules. If the first meeting is a feature list rather than questions about yield variance, verification evidence, and who fills in the shift sheet, you are being sold a template. Ask for a reference in food, beverage, or export manufacturing and ring it. A good partner will sometimes tell you a traceability layer over your existing Odoo beats a full rebuild, and will show you the arithmetic behind that advice. Dunedin is small enough that reputations are checkable, so check them: ask who supports the build in year three and what that costs.

The benefits
  • Batch genealogy from raw intake to container number, so a trace is a search rather than a shutdown
  • Yield and landed labour cost on every run inside the shift, not four weeks later
  • Export packs generated against the actual Port Chalmers sailing and cutoff, with weights pulled from the scale rather than retyped
  • GST at 15 percent and payday filing handled in the shape IRD and your existing Xero file already expect
  • A system your Dunedin supervisors will use, because it is shaped around the shift sheet they already fill in
The trade-offs
  • You own the roadmap. When IRD changes a form, nobody ships you a module; your team builds it, and that is a real annual line
  • A 6 to 10 month build means running the ring binder and the old system in parallel through at least one full season
  • Custom ERP is only as good as floor discipline. If the supervisor will not scan, no amount of code repairs the data
  • Senior ERP talent in Dunedin is thin. Expect to keep an external team or pay above local market for an in-house lead
Red flags when hiring (and what to ask instead)
  • !They quote a fixed price before seeing a batch sheet; ask them to walk the plant floor before pricing anything
  • !They have never worked under a food safety or export regime; ask for a regulated manufacturing reference, not a generic ERP one
  • !They propose replacing Xero; ask why, because in New Zealand that is usually scope padding rather than a real requirement
  • !There is no plant-floor capture step in the plan; ask how yield reaches the system without someone retyping it after hours
  • !Build is estimated at under eight weeks; ask what they believe batch genealogy actually involves

Most Dunedin teams pricing ERP end up comparing notes on internal tools, shopify, inventory management too; the systems share one data spine. Weighing options across the region? We publish the same ERP guide for Queenstown. Prefer to talk to the team that builds these? Digital Heroes handles ERP development end to end.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. McKinsey estimates that digitizing the supply chain (Supply Chain 4.0) can cut lost sales by up to 75%, reduce inventories by up to 75%, and lower supply chain operational costs by up to 30%, with up to 30% lower transport and warehousing costs. Source: McKinsey & Company (2016) →
  2. In a survey of 113 supply chain leaders (conducted late March to mid-April 2022), 67% had implemented digital dashboards for end-to-end visibility, and those companies were about twice as likely as others to avoid supply chain problems during the disruptions of early 2022; 71% expected to revise inventory policies going forward. Source: McKinsey & Company (2022) →
  3. The performance gap between digital and AI leaders and laggards is widening: McKinsey reports leaders pull ahead on shareholder returns, and the average maturity spread between top and bottom performers jumped ~60% (from 10 points in 2016-19 to 16 points in 2020-22), reinforcing that the returns to transformation concentrate among top performers. Source: McKinsey & Company (2023) →
  4. Only 16% of respondents said their organizations' digital transformations had successfully improved performance and equipped them to sustain gains over the long term; even in digitally savvy industries such as high tech, media, and telecom, self-reported success rates did not exceed 26%. Source: McKinsey & Company (2018) →
Charlie B. · Senior Copywriter · UK · London

Charlie writes the words inside and around the products the team builds: interface copy, onboarding, product pages and the explanations that stop support tickets. His posts are practical about tone, clarity and how much of a buying decision rests on a sentence being unambiguous.

View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.

FAQ

Frequently asked questions

What does a custom ERP cost for a Dunedin food or beverage producer?

Budget NZ$95,000 to NZ$140,000 for a single-site build with real batch traceability, and NZ$150,000 to NZ$210,000 once you add multiple entities and export documentation. Timelines run 6 to 10 months to production. If your trace requirement is light and your BOM is stable, a traceability layer over your existing system at NZ$48,000 to NZ$85,000 is often the honest answer.

Can a custom ERP hold the records my MPI verifier asks for?

Yes, and that is usually the single strongest reason a Dunedin plant builds rather than buys. The build stores the evidence your Risk Management Programme requires as structured records rather than scanned paper, so a verification visit becomes an export rather than a hunt through a binder. Specify the exact evidence set with your verifier during discovery so the data model matches what gets asked for.

Do I have to replace Xero if I build a custom ERP in New Zealand?

No, and you generally should not. Xero handles GST, payday filing, and bank reconciliation to a standard that is not worth rebuilding, and every Dunedin accountant already knows it. The right pattern is a custom operational core that pushes invoices, journals, and payroll costs into Xero through the API, leaving one set of books.

How long does moving off NetSuite or Odoo actually take?

Plan 6 to 10 months end to end, with the last three months overlapping your existing system. The migration itself is rarely the long pole; agreeing what a batch is, and getting the plant to record it consistently, is. Most Dunedin operators run one full season in parallel before switching the old system off.

Who owns the source code when an agency builds our ERP?

You should, in full, with the repository in your organisation's account from the first commit. Get it written into the contract as assignment of all intellectual property on payment, alongside deployment documentation and infrastructure access. If a developer wants to hold the code and licence it back to you, that is a commercial trap rather than a technical arrangement.

Can we hire ERP developers in Dunedin to maintain this in-house?

You can hire good generalist developers here, helped by the graduate pipeline coming out of the university and the polytechnic, but senior people who have shipped manufacturing ERP are scarce in the lower South Island. Most Dunedin manufacturers keep a retained external team for the deep work and hire one internal developer as the owner. Budget accordingly rather than assuming you will staff it locally on day one.

How does a custom ERP handle GST and payday filing for an Otago exporter?

Zero-rated export sales and 15 percent domestic GST get tagged at the transaction level and posted into Xero, which files. Payday filing to IRD stays with your payroll system; the ERP contributes the labour cost allocation, not the filing. The design work is making sure an export order carries the right evidence to justify zero-rating when it is reviewed.

What does ongoing maintenance cost after launch?

Plan 15 to 20 percent of the build cost per year for hosting, security patching, small enhancements, and a support agreement. For a NZ$140,000 build that is roughly NZ$21,000 to NZ$28,000 annually, which is often less than the seat licences you were paying before. Get the number in writing before you sign the build, not afterwards.

Should a Dunedin engineering job shop build or buy?

If every job is genuinely one-off and quoting accuracy is your margin problem, build, because packaged ERP will fight you on job costing forever. If you make a stable range of products to order, buy Odoo or Unleashed and spend the saved money on getting the shop floor data clean. The deciding question is whether two jobs in a row ever look the same.

What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
What should I prepare before contacting an ERP development agency?
Bring a list of your current tools and spreadsheets, a rough map of how an order or job moves through the company today, your user count by role, and the three problems costing you the most hours. You do not need a formal specification; a good agency writes that with you during discovery. Companies that arrive with those four things typically cut two to three weeks off scoping in our experience.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
How much does a custom ERP cost for a small business?
A small-business ERP covering two or three core modules typically runs $40,000 to $120,000, with inventory, ordering, and accounting sync being the usual starting set. Across 2,000+ Digital Heroes projects, integration count and user roles drive cost far more than screen count. A full mid-market ERP with six or more modules usually lands between $150,000 and $400,000.
Who owns the source code if an agency builds my ERP?
You should, in full, and it must be written into the contract as work for hire with IP assignment on payment. At Digital Heroes every client receives the complete repository, database schemas, and deployment documentation, so they could hand the system to another team tomorrow. Walk away from any ERP proposal built on the agency's proprietary platform with ongoing license fees, because that recreates the vendor lock-in you were escaping.
What does it cost to maintain a custom ERP each year?
Budget 15 to 20 percent of the original build cost per year, so a $150,000 ERP needs roughly $22,000 to $30,000 annually for hosting, security patches, integration upkeep, and small improvements. Across Digital Heroes maintenance contracts, third-party APIs changing is the biggest recurring work item. That total still usually sits well under the license bill for a comparable NetSuite or Dynamics seat count.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
How do I vet an agency for an ERP project?
Ask to speak with two clients who have been running an ERP the agency built for at least two years, because ERP quality shows up in year two, not at launch. Then ask for their data migration plan, their module rollout sequence, and the named senior engineers who will be on your project. An agency that leads with screen designs instead of process mapping is a red flag for ERP work.
Who can build custom ERP software for a business in Dunedin?

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 Dunedin 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.

Keep reading
let's build

Build something worth launching.

A plan, a team, a timeline, within 24 hours. No decks, no discovery calls. Tell us what you're building and we'll come back with a real scope and a real number.

message us directly · we reply within one business day

mission briefing

Monthly dispatch

Playbooks, real build costs, and what we're shipping. One email a month. No fluff.

visit us

New York HQ

1140 Broadway, Suite 704 · New York, NY 10001

Get directions
Online now

Hey there 👋 How can we help you today?