Your ERP Assumes a Production Plan. Port Nelson Delivers 30 Tonnes on a Sunday Instead.
A custom ERP (Enterprise Resource Planning) for a Nelson seafood, aquaculture, hop or pipfruit business usually lands at NZ$90,000 to NZ$180,000 over five to eight months, and almost none of that money goes on accounting. It goes on the parts NetSuite, SAP and Odoo were never shaped for: an unscheduled landing at Port Nelson, a processing slot that has to be re-cut when the swell in Tasman Bay kills tomorrow's steaming, and product whose value drops every hour it sits. Across 2,000+ Digital Heroes builds, the ERP work that pays back fastest in Nelson treats a landing, a bin or a hop lot as the primary record, and lets the purchase order follow it.
You did not buy an ERP because you love software. You bought it because the whiteboard in the processing office stopped matching the freezer, because the wholesale team was quoting product that had already been allocated, and because nobody could tell you the true cost per kilogram of anything. Then you discovered that your ERP wants a demand forecast, a bill of materials and a stable production calendar, and your operation has none of those. What it has is a skipper on the radio saying he is coming in twelve hours early with more than expected.
The off-the-shelf tools handle the tidy half of your business well. NetSuite will do your general ledger and your consolidated reporting properly. Odoo will hold a customer list. Where they fall over is the specific thing Nelson runs on: yield. A landing becomes fillets, frames, roe and waste at ratios that change by species, size grade and season. A hop lot from Motueka has an alpha acid figure that decides which brewery contract it can satisfy. An apple bin out of a Riwaka orchard splits into export grade, local market and juice at a percentage nobody knows until it is over the grader. Standard ERP conversion logic assumes you know the output before you start.
Where the off-the-shelf tools fall short
- Processing schedules built in Excel the night before, then rebuilt by 6am when the landing volume or the Tasman Bay forecast changes
- No live yield picture, so cost per kilogram of finished product is calculated weeks later by the accountant instead of during the run
- Traceability for MPI Risk Management Programme verification stitched together from paper run sheets, label rolls and a shared drive
- Wholesale and export orders promised against stock that processing has already committed elsewhere, discovered at the loadout door
Custom ERP: what Nelson teams actually get
The custom case here is narrow and strong: model the event, not the order. A build that starts from a landing, a harvest or a bin, and carries that identity all the way through processing, chilled storage, dispatch and invoice, gives you three things off-the-shelf cannot. Live yield by species and grade. A traceability chain that answers a market access query in minutes rather than a day of folder archaeology. And a scheduling view that lets the processing manager re-cut tomorrow in ten minutes when the weather turns. You still keep Xero for the ledger, and you can wire the same core into inventory management software, a warehouse management system (WMS) for the chilled store, and business intelligence (BI) dashboards for the weekly numbers.
- Your margin lives or dies on yield percentages that no current system records at the point they happen
- You run more than one site, for example a Nelson processing floor and a Motueka packhouse, on different spreadsheets
- An export customer or verifier has asked a traceability question and it took you more than a day to answer
- Scheduling is a person, and that person going on leave is a genuine operational risk
- You are under about NZ$4 million turnover and your process would fit a configured Odoo instance with minor tweaks
- Your product is shelf stable and your production plan is set weeks ahead, not the morning of
- You need a general ledger and consolidated reporting more than you need operational scheduling
- You have no internal owner who can make process decisions quickly during a build
- Yield and cost per kilogram visible during the run, not reconstructed at month end
- One traceability chain from landing or bin through to the export consignment, ready for MPI verification without a paper hunt
- Processing slots that can be redrawn in minutes when a vessel comes in early or a hop kiln goes down mid harvest
- Wholesale allocation locked against real available stock, so the sales team stops selling the same pallet twice
- Reporting that speaks your units: tonnes landed, bins tipped, kilograms of alpha acid, cases of finished product
- You take on the roadmap. Nobody ships you a compliance update when reporting requirements shift, so you budget for it
- Six months is a long time in a business with a February harvest window, and a bad launch date can cost you a season
- Finance teams and auditors know NetSuite. A custom core means documenting your own controls and reconciliations properly
- If your process is genuinely standard, custom is the expensive answer to a problem a configured platform would have solved
Feature priorities for Nelson teams
ERP services we deliver in Nelson
Everything an ERP build here can cover: Odoo development, Microsoft Dynamics 365, ERP migration, cloud ERP and manufacturing ERP.
The honest cost picture for Nelson
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single module, harvest to dispatch scheduling only | NZ$45,000 to NZ$75,000 | 10 to 14 weeks |
| Core ERP with inventory, processing, orders and traceability | NZ$90,000 to NZ$180,000 | 5 to 8 months |
| Multi site rollout across Nelson, Richmond and Motueka | NZ$200,000 to NZ$340,000 | 9 to 14 months |
Timeline: what happens, and when
Exactly what you get
A working system, the source code assigned to your company, and a deployment your own IT contractor can take over. In practice that means an operations core covering capture, processing, stock and dispatch, an admin layer for grades, species, blocks, growers and customers, integrations to Xero and to whatever label printers and scales you already run, and a set of reports the operations manager actually opens on a Monday.
You also get the unglamorous parts that decide whether people use it: a wharf or weighbridge screen that works with wet hands and gloves, a packhouse view that a seasonal worker can learn in ten minutes, and a data migration that brings across your customer list, product codes and open orders rather than leaving you double entering for a month.
How to choose a developer in Nelson
Nelson and Tasman have a small but real technical community, and you will find good contractors here alongside teams in Christchurch and Wellington. The question is not location, it is whether they have shipped operational software for perishable product. Ask directly: have you built anything where a batch had an expiry, a hold status and a traceability obligation at the same time? The answer separates the field fast.
Insist on a paid discovery of two to four weeks before any build number is quoted. Insist on seeing a reference system running, not a slide deck. And be blunt about support: who answers at 5am in March when the packhouse cannot print labels, and what does that cost per year. A build partner who cannot answer that in writing is selling you a project, not a system.
- !They demo a generic manufacturing module and call your yield problem a configuration option. Ask them to whiteboard how a single landing splits into four grades and two waste streams
- !No question about MPI verification or export certification in the first meeting. Ask what traceability evidence they have built before
- !A fixed price quoted before anyone has stood on your processing floor. Ask for a paid discovery with a written scope instead
- !They plan a go live in February. Ask them to name the harvest and landing peaks in your year and schedule around them
- !Source code ownership is vague or sits behind a licence. Ask for a written assignment of the code to your company at final payment
Most Nelson teams pricing ERP end up comparing notes on internal tools, shopify, inventory management too; the systems share one data spine. Prefer to talk to the team that builds these? Digital Heroes handles ERP development end to end.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
- In PMI's 2014 Pulse of the Profession report on requirements management, inaccurate requirements management is cited as a leading cause of project failure, with 47% of unsuccessful projects failing to meet goals due to poor requirements management. Source: Project Management Institute (PMI) (2014) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- 73% of surveyed businesses now use a headless architecture (up nearly 40% since 2019), and 98% of those not yet using it are evaluating or planning to evaluate headless within 12 months, with 82% saying it makes delivering consistent content easier. Source: WP Engine (2024) →
Connor manages client accounts at Digital Heroes from Sydney, handling the running relationship once a project is underway: updates, approvals, change requests and the questions clients feel awkward asking twice. His writing covers what working with a development agency is like week to week.
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 Nelson seafood processor?
Expect NZ$90,000 to NZ$180,000 for a core build covering landings, processing, yield, stock and dispatch, delivered over five to eight months. A narrower first phase covering only scheduling and yield capture can be done for NZ$45,000 to NZ$75,000. Digital Heroes usually recommends the narrow phase first so the processing floor gets value before the next peak season.
Can I keep Xero and still build a custom ERP?
Yes, and you should. Xero handles the general ledger, GST at 15 percent and your myIR filing perfectly well, and your Nelson accountant already knows it. The custom ERP owns operations and pushes invoices, bills and credit notes into Xero through the API, so nobody rekeys anything and your annual accounts do not change shape.
How does a custom ERP handle MPI traceability and export certification?
It holds one unbroken chain from the landing or harvest event through every split, merge and pack, so a recall query resolves from a batch number rather than a folder of run sheets. For export consignments the system produces the consignment level data your certifier needs, which shortens the gap between packing and paperwork. It does not replace your Risk Management Programme, it makes evidencing it fast.
We run NetSuite and it is not working for our hop business. Is migration realistic?
Realistic, and common. The usual pattern is to leave NetSuite or Odoo doing finance while a custom operational layer takes over harvest, lots, alpha acid results and contract allocation, then retire the ERP modules that were never used. Full replacement of a live NetSuite instance takes six to nine months and needs a parallel run through one harvest before you switch off.
Will the system work in a packhouse in Motueka with poor connectivity?
It has to, so we build capture screens offline first with a local queue that syncs when the connection returns. Bins get scanned and grades get recorded whether or not the link to Nelson is up. Anything that requires live connectivity, such as customer pricing lookups, is designed to degrade to a cached copy rather than block the line.
Who owns the source code when the project ends?
You do, in writing, assigned at final payment. That is the standard Digital Heroes term and you should demand it from any supplier. Ask for the repository, the deployment scripts and the environment documentation as part of handover, because owning code you cannot deploy is not ownership.
How long before the operations team actually uses it during a season?
Plan on five to eight months from discovery to a live core, then one full season of running alongside your existing process before you trust it entirely. For a Nelson operation that means starting a build in April or May so that testing lands well before the February harvest and landing peaks rather than during them.
What does ongoing maintenance cost after launch?
Budget 15 to 20 percent of the build cost per year for hosting, monitoring, security patching, small changes and a support agreement with defined response times. For a NZ$120,000 build that is roughly NZ$18,000 to NZ$24,000 a year. Anyone quoting materially less is either not including support hours or expects you to call a developer directly when something breaks at 5am.
Should we build one ERP or separate systems for processing and sales?
Build one core that owns stock and batches, then add interfaces around it. Splitting processing and sales into separate systems recreates the exact problem you are trying to solve, which is two people believing they can sell the same chilled pallet. A CRM can sit alongside for relationship management, but available stock must have a single source of truth.
Can we keep our current ERP and just build custom modules around it?
Is SAP overkill for a mid-sized company?
Does it matter which tech stack the agency wants to use?
How do I vet an agency for an ERP project?
Can a freelancer build an ERP, or do I need an agency?
How long does it take to build a custom web or mobile app from scratch?
Who can build custom ERP software for a business in Nelson?
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 Nelson 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.
