Instead of Producepak
Stop renting Producepak. Own the system your shed runs on.
We shape it around how your shed receives, packs and pays growers, move your Producepak records over, and keep it running for you through the season.
Producepak lists US$6,200 a year, paid in advance, for 8 users, then US$550 a year for every extra user, in US dollars before tax.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
How the Producepak bill works
One price in US dollars, then extras for people and for changes
Producepak's pricing is published, which is more than most packhouse vendors manage. Read the terms under the headline, though, and the fee is the start of the bill, not the whole of it. What it holds for a packer is familiar: suppliers, receivals, stock, packing runs, pallets, orders and shipments.
A year paid before the first carton
The fee is US$6,200 per annum, payable in advance, in US dollars and before tax. There is no monthly option and no trial, so you commit to the full year before you know whether it suits your shed.
Eight people, then a fee for each one after
Eight user licences are included. The ninth person, and every one after, is another US$550 a year. Harvest brings casual supervisors, a second shift and a quality officer, and each of them is a line on next year's invoice.
Your changes become their recurring revenue
Producepak says it will not negotiate on price, and a feature added just for you puts 35% of its cost onto your annual fee. You pay once to have it built, then keep paying for it every year after.
Billed from overseas, in another currency
Prices are set in US dollars by a vendor based in New York. You can pay in your local currency, but the number you budget for still moves with the exchange rate at every renewal.
Built for packers, wholesalers and food service
Producepak is built for packers, wholesalers and food service: inventory, invoices, orders, labels and quality inspections.
Your seasons inside a hosted app
Receivals, packouts, recalls and inspections live in the vendor's system and are read through its screens and reports. Stop paying and you are asking for an export of your own history.
What your shed runs on instead
Every packhouse job, priced the same whether five people use it or fifty
At the dock
A receival that checks the paperwork before the fruit moves
Each load is booked in against its grower and block with its spray record, and the problems show up while the truck is still being unloaded.
- check A load picked before its spray withholding period has ended goes on hold, with the day it becomes clear shown beside it
- check No load is graded until its spray diary has been recorded, so a missing diary is chased on the day, not at audit
- check Held fruit comes off hold only with a decision written down: a residue result, a market it is cleared for, or disposal
- check Bins still waiting to be graded after three days appear on the morning list by themselves
Pallet to paddock
The recall answer is ready before anyone rings
The grading run makes the pallets, the cool room record holds them, and every consignment knows exactly what went on the truck.
- check Ask about a pallet number and get its grading run, its receival, the block, the pick date and the certification behind it
- check Each consignment's manifest lists where everything on the truck came from, printed before it leaves
- check Cool room temperature readings are logged per room, and a reading out of range shows which pallets were inside
- check Fruit from a block whose GAP certificate has lapsed is kept off export consignments without anyone having to remember
Paying growers
Grower returns worked out from the season's own numbers
Trays go into a pool by crop and variety, sales land in the pool, and each grower's share is calculated after packing charges and levies, at today's figures, whenever you ask.
- check See every grower's gross share, charges and net return per tray while the pool is still open
- check A pool cannot be closed while dispatched trays have no sale recorded, so no grower is paid short by accident
- check A return statement in your own branding is drafted for each grower in each pool, ready for a person to check and send
- check A packout statement is drafted as soon as a load is graded, showing the class one share every grower asks about
Growing the team
Add people and changes without adding to a yearly fee
The free version has no licences to count. Your harvest crew, your quality officer and your accountant can all use it at no extra charge.
- check No charge per person, so the busy season does not change the cost
- check Ask for a new field, a new rule or a renamed stage in plain words, and it is added to your own records
- check Works on a laptop in minutes, or on your own system for the whole operation, with Claude Code and similar tools
- check Open source under the MIT licence, with your records in a database you can back up and read with anything
Make it yours
Design your own Producepak replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Producepak. 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 Producepak data across and run it for you.
Switching
How to switch from Producepak
Moving off Producepak means exporting what you already hold, matching it to the new system's fields, checking what the import flags before you trust it, and running both together for a while before you cancel the old one.
- 1
Export your records from Producepak
Ask Producepak for spreadsheet exports of your suppliers, receivals, stock and shipments, in whatever format your account allows. Check with Producepak on the exact export options open to your plan. This is the raw material the new system needs, and it is the same data you already pay Producepak to hold, just leaving in a file instead of staying locked inside its screens.
- 2
Match your columns, then test load
Producepak's columns will not line up automatically, since the free version expects a different packhouse system's layout by default. Someone needs to match your columns to the right fields before anything goes in. Once mapped, run a test load first so nothing is saved yet. That way you can see what would happen before you commit any real records to it.
- 3
Check what the import flags
The import is the first audit. A block with an expired GAP certificate, or a delivery missing its spray diary, will show up loudly the moment the load finishes. Go through everything it raises before you trust it with real work, since these are the same gaps that stop fruit from grading or an export consignment from dispatching once you rely on the system day to day.
- 4
Run both systems side by side
Keep Producepak running and let the new system carry the same receivals, grading and dispatch for a while. Compare what each one shows for growers, pallets and returns. This is how you catch anything the export missed or the mapping got wrong, before your team stops checking the old system and starts trusting the new one on its own.
- 5
Switch off Producepak
Once the numbers agree and your team is working from the new system without needing to double check the old one, cancel Producepak. Your records already sit in a database you own, so there is nothing left to move out later, no per person fee building up, and no annual invoice still coming from Producepak.
Where the real effort goes
The real work is not moving files, it is mapping your fields and your own rules onto the new system, and deciding how much history is worth bringing across rather than starting the season fresh. That mapping doubles as the first audit, since gaps like expired certificates or missing spray diaries surface as soon as the load runs. Enterprise DNA carries out this mapping and checking when you have them build and run your version.
Not ready for a call?
Get your Producepak switch plan by email
We will send you the step-by-step plan for moving your business off Producepak, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Producepak switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to switch
Run the free version yourself, or have Enterprise DNA build and run yours
Open source
Run it yourself
Free
- 1 Clone the packhouse-for-claude-code repo from GitHub
- 2 Run npm run demo, then open the folder in Claude Code
- 3 Type /attention to see what needs a decision in the demo season
- 4 Ask Producepak for spreadsheet exports of your suppliers, receivals and stock, then ask Claude Code to map the columns before you import
Omni by Enterprise DNA
Have Enterprise DNA build and run it
One setup fee, then a monthly retainer
- check We move your growers, receivals, pallets and inspection history out of Producepak and check every record as it lands
- check We set up your pools, packing charges, levies and grower statements to match how you pay growers now
- check We add what your shed relies on: retailer labels, quality photos, a simple screen for the packing floor if you want one
- check It runs inside Omni, our managed Command Center, alongside the rest of your business
Questions
Instead of Producepak, answered
Producepak is not that expensive. Why would we move? expand_more
The headline fee is modest for software of this kind. The question is what it becomes: every person past the first eight is US$550 a year, any feature built for you adds 35% of its cost to every future annual fee, and the price is set in US dollars. Here there is no per-person charge, changes to your own version are not billed yearly, and the records are yours whether or not you keep working with us.
How do we get our records out of Producepak? expand_more
Ask Producepak for spreadsheet exports of your suppliers, receivals, stock and shipments. The free version reads a different packhouse system's export layout by default, so Producepak's columns need matching up first. When Enterprise DNA builds your version, that mapping and the checking of every record is part of the job. If you run it yourself, you can ask Claude Code to do the mapping and run a test import before anything is saved.
Producepak prints our Coles and Woolworths labels. Does this? expand_more
Not in the free version today. It produces packout statements, grower returns and consignment manifests in your own branding, but not retailer carton labels. Retailer labels built to each customer's specification are something Enterprise DNA adds when it builds your version.
What about quality inspections and photos? expand_more
The free version records grading results and the class one share for every load, but it does not store inspection photos. If your buyers expect photographs at loading, Enterprise DNA builds that into your version, along with the checks your quality officer already runs.
Does it still link to Xero or MYOB? expand_more
The free version does not send invoices to your accounting software on its own. Grower returns and sales sit in plain records, so a connection to Xero or MYOB is a small, common addition that Enterprise DNA sets up when it builds and runs your version.
See what your shed would cost to run on records you own
Book 30 minutes with Sam. Bring your last Producepak invoice and a list of who logs in, and we will walk through what your packhouse actually records and what your own version would look like. If it is a fit, 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 Producepak?
Get your version built