Instead of ProduceLinc
Stop paying for ProduceLinc. Own your packhouse and pool records.
We shape the system around how your packhouse grades, stores and settles with growers, move your ProduceLinc records across, and look after it for you every day.
Equerra lists ProduceLinc on Business Central as a fixed-price project from NZ$80,000, typically NZ$120,000 to NZ$250,000 for a mid-sized packhouse, with Microsoft's licence on top at NZ$129.40 or NZ$178.00 per user per month.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
Where the money goes
A packhouse bought an ERP to get pallet tracking and pool payments
ProduceLinc is an add-on that lives inside Microsoft Dynamics 365 Business Central. To use it you buy the whole accounting system, the implementation and the licences. The packhouse part itself is a modest set of records: growers, blocks, bins received, pallets, rooms, consignments and pools.
An implementation priced like a building project
Equerra's fixed-price implementation starts at NZ$80,000 for a smaller single-site operation. A mid-sized packhouse with a grading line, several pools and export work typically lands between NZ$120,000 and NZ$250,000.
A monthly licence for every person who logs in
Business Central is licensed per user, per month: NZ$129.40 for Essentials or NZ$178.00 for Premium. The pack shed supervisor, the grower liaison and the accounts clerk each need a seat.
Three products stacked to make one system
ProduceLinc, Yaveon 365 for food compliance and shelf life, and Equerra's own EQProduce add-on for New Zealand needs, all running inside Business Central. Every layer is another thing to configure, upgrade and pay someone to understand.
A go-live you plan around the harvest
Equerra describes a phased rollout with parallel running before peak season. A test run of the free version takes a minute on a laptop.
Returns analysis through another tool
Margin by grower, market and season is pitched through Power BI dashboards. Here, asking which growers' packouts dropped this week, or which pool is still waiting on sale proceeds, is a plain question with an answer straight away.
Season records inside a licensed system
Your grower history, pallet trail and settlements sit inside Business Central. Here they are ordinary records in a database you keep, back up and read with anything.
What you run instead
The packhouse jobs, without the ERP around them
Receiving
Fruit is checked at the door, not at audit time
Each delivery arrives with its grower, block and spray record, and the checks happen before a single bin goes near the grader.
- check Bins picked before the spray withholding date has passed are put on hold, with the date they clear shown next to them
- check Grading is refused for any delivery that arrives without its spray diary
- check Held fruit is only released with a recorded reason: a residue result, a market it is cleared for, or disposal
- check Bins waiting too long to be graded show up on the morning list without anyone running a report
Pallets and coolstore
Every pallet can name the block it came from
A graded run creates the pallets, the rooms record where they sit and how cold it is, and the consignment picks them up. The recall question has its answer before anyone asks.
- check Ask about any pallet number and see the grading run, the delivery, the orchard block, the pick date and the certificate behind it
- check Rooms reading outside their temperature band are flagged with how many pallets are sitting in them
- check An export consignment will not leave without its MPI assurance reference
- check Fruit from a block whose GAP certificate has lapsed is kept off export consignments automatically
Grower pools
Pool returns every grower can follow, all season
Trays go into a pool by crop and variety, sale proceeds are recorded against it, and each grower's share, less packing charges and levies, is visible whenever you ask.
- check See each grower's gross share, charges and net per tray while the pool is still selling
- check A pool will not close while any dispatched trays still have no sale recorded, so no grower is short-paid by an early close
- check Grower return statements and packout statements are drafted in your own branding, ready for a person to check and send
Ownership
A database you keep, and no seat count
It runs on one laptop for a trial or on your own server for the whole shed. Anyone on your team can ask it questions without a licence each.
- check Open source under the MIT licence: read it, change it, keep it
- check Nine compliance rules written out with their sources, in plain words you can edit
- check Works with Claude Code and similar assistants; the records are what matter
- check Your season history stays readable by any tool you choose, now and after you stop using ours
Make it yours
Design your own ProduceLinc replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from ProduceLinc. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your ProduceLinc data across and run it for you.
Switching
How to switch from ProduceLinc
Moving off ProduceLinc is mostly a matter of getting your records out of Business Central, checking they land correctly, and running the two systems together for a while before you cancel anything.
- 1
Export your records from Business Central
ProduceLinc keeps its records inside Business Central, so that is where the export comes from. Export whatever your account allows, usually CSV or Excel, and check the exact steps with ProduceLinc or your Business Central partner. Pull out your growers, blocks, deliveries, pallets, coolstore records, consignments and pool returns, since these are the records the new system needs to hold.
- 2
Load your data in, with a test run first
Business Central's export columns are not the same as the ones Packhouse for Claude Code reads, so the columns need matching up. Ask Claude Code to map them for you, and do a test run before anything is saved. The test run shows you what would come across without touching the real database, so you can fix mismatches before they matter.
- 3
Check what the import flags
The import is the first audit of your own records, not just a data move. Once it runs for real, look at what it flags: a block with an expired GAP certificate, a delivery missing its spray diary, a pool with dispatched trays and no sale recorded. These are the same gaps the old system may have been quiet about. Deal with them before you rely on the new record.
- 4
Run both systems side by side
For a short period, keep entering the same deliveries, grading runs and pool returns in both systems. Pick a few pallets and a grower's return and check the numbers match between them. This is how you find any gap in the move before growers are paid from the new system instead of the old one.
- 5
Switch off ProduceLinc
Once a full cycle, receiving through to a grower return, checks out clean in the new system, stop entering data into ProduceLinc and cancel the Business Central licence for every seat that was only there for it. Keep your ProduceLinc exports on file in case you need to check something from an earlier season.
Where the real effort goes
The real work is not moving the data across, it is mapping your own fields and rules onto the new record and deciding how much history to bring with you rather than leave in an export file. That is fiddly the first time. Enterprise DNA does this part for you when they set it up and run it on your behalf.
Not ready for a call?
Get your ProduceLinc switch plan by email
We will send you the step-by-step plan for moving your business off ProduceLinc, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your ProduceLinc switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to switch
Set it up yourself, or have Enterprise DNA build and run it
Open source
Set it up yourself
Free
- 1 Clone the packhouse-for-claude-code repo from GitHub
- 2 Run npm run demo and open the folder in Claude Code
- 3 Type /attention to see what needs a decision on the demo season
- 4 Export your growers, blocks and deliveries from Business Central and ask Claude Code to map the columns before importing
Omni by Enterprise DNA
Have Enterprise DNA build and run it
One setup fee, then a monthly retainer
- check We bring your growers, blocks, pallet history and pool records across from ProduceLinc and check them as they land
- check We set up your pool structure, packing charges, levies and settlement rules exactly as you pay growers today
- check We add what your shed needs: your grader's file, your exporter's documents, a screen for the pack floor if you want one
- check It runs inside Omni, our managed Command Center, beside the rest of your business
Questions
Instead of ProduceLinc, answered
We already paid for the ProduceLinc implementation. Why switch now? expand_more
The implementation is spent either way. What keeps coming is the Business Central licence for every user, every month. The question is whether the next few seasons are worth that, when the packhouse records themselves can sit in a database you own.
How do our ProduceLinc records come across? expand_more
ProduceLinc keeps its records inside Business Central, so they come out as exports from there. Those exports have different columns from the ones the free version reads today, so matching them up is part of what Enterprise DNA does when we set it up for you. If you are doing it yourself, you can ask Claude Code to map the columns, and do a test run before anything is saved.
Business Central is also our accounting system. What happens to that? expand_more
This replaces the packhouse side: receiving, grading, pallets, coolstore, consignments and grower pools. It is not a general ledger. Most businesses our size keep their books in an accounting package, and Enterprise DNA connects the grower settlements to whichever one you use.
Does it cover export paperwork and phytosanitary certificates? expand_more
The free version checks the basics every programme shares: spray diaries, withholding periods, GAP certificates and an MPI assurance reference before an export consignment leaves. It does not produce phytosanitary certificates for each market today. When Enterprise DNA builds your version, your exporter's documents and market rules are added. Whether a consignment meets a market's rules remains your exporter's and MPI's decision.
Can it read our grading line? expand_more
The free version takes the end-of-run grading totals and builds the pallets and packout statement from them. It does not take a live feed from the grader. If your grader writes out a file, that can be read in, and a live connection is something Enterprise DNA can add in your version.
Find out what your packhouse records really cost you
Book 30 minutes with Sam. Bring your ProduceLinc and Business Central costs, and we will go through what your packhouse actually records and what your own version would look like. If it fits, we build it and run it. If not, the free version is yours to keep.
Packhouse for Claude Code is free and open source, published by Enterprise DNA.
Done paying for ProduceLinc?
Get your version built