Your grape pack-out, your water orders, and your export bookings never agree by Thursday
A custom ERP (Enterprise Resource Planning) for a Mildura packing or processing operation runs $80k to $180k and 4 to 7 months. The reason generic ERP fails here is the export dispatch deadline: when a table-grape line changes bin sizes mid-harvest or a citrus exporter rebooks a vessel, NetSuite and SAP make you re-key it across three modules while the cold-chain clock keeps running. Custom ties grower intake, pack-out, and dispatch to one record so a changed order updates everywhere at once.
You run a Sunraysia packing shed where bins come in from a dozen growers, get graded and packed across two or three lines, and have to hit a refrigerated container booking that someone made three weeks ago. NetSuite or Microsoft Dynamics handles the invoices fine. What it does not handle is that your fruit weight at intake, your pack-out yield, and your export commitment are three different numbers that drift apart every single day of harvest, and nobody can see the gap until dispatch morning.
So you bolt on a spreadsheet for grower consignments, another for line scheduling, and a third someone keeps for which container leaves when. Odoo gets you closer than SAP because it is cheaper to bend, but you still hit the same wall: off-the-shelf ERP models a warehouse, not a perishable that loses grade every hour it waits and a crew whose numbers you only learn at 6am.
- You pack for multiple growers and export to several markets with differing compliance and spec needs
- Reconciling intake against pack-out against export commitment is eating a person's whole week
- You have repeatedly missed or scrambled a cold-chain dispatch because the data was scattered
- Your seasonal volume swing is large enough that fixed off-the-shelf workflows fight you every harvest
- You are a single-grower operation with predictable volume and one or two export channels
- Your finance and inventory needs are standard and Odoo or NetSuite covers them without heavy bending
- You do not have someone internal who can own requirements and testing through a multi-month build
- Cash is tight and an off-the-shelf plus an integration gets you 80 percent of the value now
- One record from grower bin intake to container dispatch, so a changed export order updates pack scheduling and inventory at once
- Real-time pack-out yield against export commitments, so you see the shortfall on Tuesday not at the dock on Thursday
- Grower consignment settlement that reconciles automatically against actual graded weights, paying growers on real numbers
- Cold-chain dispatch view that flags fruit losing grade before it misses its booking
- Built around your bin specs, grade bands, and the export markets you actually ship to, not a generic warehouse model
- A custom ERP is a multi-year commitment; you own the maintenance, the upgrades, and the on-call when a line stops mid-harvest
- During peak harvest you cannot pause for a slow rollout, so go-live timing is genuinely hard and constrains the build
- You lose the free flow of vendor updates, tax-table changes, and integrations that come bundled with NetSuite or Dynamics
- If your volume is modest, a well-configured Odoo plus a tight integration may carry you for less money and less risk
ERP pricing in Mildura: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| Core ERP: intake, pack-out, dispatch | $80k to $130k | 4 to 6 months |
| Plus grower settlement and export compliance | $120k to $180k | 5 to 7 months |
| Phased: replace worst spreadsheet first | $35k to $60k | 8 to 12 weeks |
The features that matter for Mildura
ERP services we deliver in Mildura
Digital Heroes builds the full ERP stack for Mildura teams. Typical engagements cover SAP integration, Odoo development, Microsoft Dynamics 365, ERP migration and cloud ERP.
Exactly what you get
A working ERP where a grower's bins are scanned at intake, follow through grading and pack-out as one traceable consignment, and land against a specific export booking with the cold-chain deadline visible the whole way. Finance, inventory, grower settlement, and dispatch read from the same record, so the Thursday-container question has a live answer. You also get the boring essentials done right: real per-consignment costing that includes water orders and seasonal labour, and reports your accountant and your exporters both trust.
How to choose a developer in Mildura
Pick a team that asks about your harvest calendar before they talk technology. The right partner will want to sit in the shed during a pack run, watch a dispatch morning, and understand that go-live timing around the season is a constraint, not a detail. Ask for examples where they integrated with grading lines or perishable supply chains. Be wary of anyone selling a generic ERP they will lightly reskin; this only pays off if it is built around your consignments, your export markets, and the Murray River seasonality that drives everything.
From kickoff to launch: the schedule
- !They have never asked what a cold-chain dispatch deadline does to your data; ask them to walk through a rebooked vessel
- !They quote a fixed price before seeing your grower settlement rules; ask how they handle consignment reconciliation
- !They push a generic manufacturing ERP template; ask what they would change for perishable horticulture
- !No plan for going live around harvest; ask exactly when in your season they would cut over
- !They cannot name how this ERP talks to your inventory, accounting, and booking systems
If erp is on the roadmap, internal tools, shopify, inventory management usually follow within the year. Budget them as one conversation.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
How is a custom ERP different from configuring NetSuite for Mildura?
NetSuite gives you solid finance and inventory but models a static warehouse. A custom ERP makes the export dispatch deadline the spine and ties grower intake, pack-out yield, and cold-chain bookings to it in real time, which is the exact thing that breaks for Sunraysia packers during harvest.
Can we phase it instead of a big-bang replacement?
Yes, and you should. Most Mildura operations start by replacing the worst spreadsheet, usually grower consignment reconciliation or the dispatch board, for $35k to $60k, prove the value over one season, then extend. This also avoids cutting over the whole business mid-harvest.
Will it handle different export markets with different paperwork?
That is a core reason to go custom. The build holds each market's spec and compliance documents against the export order, so a citrus shipment and a table-grape shipment carry the right paperwork automatically rather than someone rebuilding it per container.
What about our existing accounting software?
The ERP integrates rather than replaces it where that makes sense. Many packers keep their accounting package and feed it costed, reconciled consignment data, which is cleaner than forcing finance into a brand-new general ledger mid-season.
How do we cost water orders and seasonal labour per consignment?
The build captures water-order and crew costs at the block and shift level, then allocates them to the consignments they produced. That gives you true per-line and per-grower margins instead of a season-end estimate, which is most useful when you are deciding which blocks and which export channels are actually worth it.