Instead of inecta Produce
Stop renting inecta Produce. Own the records your season runs on.
We build your version around how you grow, pack and settle with growers, bring your inecta records across, and run it for you through the season.
inecta Produce publishes no price: it is quoted privately on users, modules and complexity, with implementation, data migration and training quoted on top.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
How the inecta bill is built
A food ERP priced in pieces: seats, modules, then the people who set it up
inecta sells one food ERP across dairy, seafood, meat, bakery, beverages and produce, and quotes each business on its own. What a grower-packer actually keeps in it is short: growers, blocks, deliveries, lots, inspections, pallets, shipments and what each grower is owed.
A quote instead of a price
inecta's own FAQ says the price depends on how many users you have, which modules you take and how complex your operation is. You find out by asking for a tailored quote.
Implementation, migration and training on a separate quote
The subscription covers the software, hosting and updates. Getting it running is quoted separately up front: implementation, moving your data in, and training. Extra training and dedicated consulting are add-ons after that.
Three to six months before it carries a season
inecta puts a typical implementation at 3 to 6 months. For a grower that can mean planning the switch a whole harvest ahead. The free version here runs on demo data in a minute, and your real records go in after a test run.
Microsoft's ERP underneath
inecta Produce is built on Microsoft Dynamics 365 Business Central. You are buying general ledger, inventory, sales and finance screens along with the produce features, and living with Microsoft's platform and update cycle to get them.
Grower accounting as one line in a long list
On inecta's produce grower page, grower accounting gets a mention beside crop tracking and compliance. How proceeds pool, what gets deducted and how each grower's return is worked out is the part a packhouse argues about every season.
Your seasons inside a hosted ERP
inecta's FAQ explains how your data gets moved in. It says nothing about getting it back out. Seasons of lots, inspections and grower history sit in a system you reach through its screens and reports.
What you run instead
The produce work, without the rest of an ERP wrapped round it
Booking fruit in
Each delivery checked against its block before it is accepted
A load arrives with its grower, block and pick date, and the spray record comes with it. Problems show up at the door, not at audit time.
- check Fruit picked inside a spray withholding period is put on hold with the date it clears, and stays at the top of the list until someone decides
- check A delivery with no spray diary cannot be graded, and the hold says why
- check Releasing held fruit needs the decision written down: a residue result, a cleared market, or the dump
- check Bins waiting too long to be graded show up by themselves, before condition becomes a claim
Lots and trace
Any lot back to the orchard row, or forward to the truck
Grading builds the pallets, the coolstore holds them, the consignment takes them, and every step remembers where the fruit came from. A recall question takes seconds to answer.
- check Ask about one pallet and get the grading run, the delivery, the block, the pick date, the spray record and the GAP certificate together
- check Each consignment's manifest carries the full trace for everything on the truck, printed before it leaves
- check An export consignment will not go without its MPI assurance reference, and nobody can override that
- check Fruit from a block whose GAP certificate has lapsed is kept off export consignments automatically
Paying growers
Pools and grower returns worked out all season, not at the end
Trays go into a pool by crop and variety, sale proceeds land against the pool, and each grower's share is worked out less your charges, at today's numbers, any day you ask.
- check See every grower's gross share, packing charge, levies and net per tray while the pool is still selling
- check A pool will not close while any dispatched fruit is still missing its sale proceeds, so nobody is paid short
- check Each grower gets a return statement in your branding listing their own fruit, ready for a person to send with the payment run
- check Packout statements are drafted as soon as a delivery is graded, with the class 1 share growers ring about
Yours to keep
A database you own, open to whatever you use next
It runs on a laptop with nothing to install beyond the free version, or on your own system for the whole operation. The records are the product; the assistant is just how you ask.
- check No user count anywhere: the harvest supervisor, the quality officer and the office all use it without a new licence
- check Back it up, report on it from anything, and keep every season when you change tools
- check The rules it enforces sit in plain words with their sources, and you can change them
- check Your inecta records come across checked: a lapsed certificate or a missing spray diary shows up the moment they land
Make it yours
Design your own inecta Produce replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from inecta Produce. 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 inecta Produce data across and run it for you.
Switching
How to switch from inecta Produce
A move is mainly an export, field mapping, record checks and a short period running both systems before you stop using inecta Produce.
- 1
Request your records
Ask inecta, or whoever runs your system, how to export your growers, blocks and receipts. Export what your account allows, usually CSV or Excel, and check with inecta if you are unsure which records or export options are available. Decide which seasons of history you need before preparing the files.
- 2
Map the exported fields
The import can read a different packhouse system's export layout, but inecta's columns need mapping first. Match your exported fields to the records Packhouse uses, including growers, blocks and deliveries. If you run the free version, ask Claude Code to do the mapping. If Enterprise DNA runs it for you, they handle the mapping and check every record.
- 3
Test and review the import
Use the import's test run first if it is available for your mapped files. Review what the import flags, such as records with missing information or fields that did not map cleanly. Resolve those issues and check the imported growers, blocks and receipts against inecta before relying on the new records.
- 4
Run both systems briefly
Keep inecta Produce running while you use Packhouse for live work for a short period. Compare the records and results you rely on, including deliveries, lots, pallets, consignments and grower returns. Note any missing fields or rules you still need. Keep your existing accounting package in place, since Packhouse replaces the produce side, not your accounts.
- 5
Switch off inecta Produce
When you have checked the records and are comfortable running the produce work in Packhouse, stop using inecta Produce. Keep any exported records you need for reference. Your accounts remain in the accounting package you already use or choose, so confirm that the produce information needed for your books is handled there before ending inecta access.
Where the real effort goes
The real work is usually mapping your own fields and rules, then deciding how much history to bring across. The free version's import layout differs from inecta's, so the columns need mapping and the imported records need checking. If you have Enterprise DNA run your version, they do the mapping and check every record as part of the job.
Not ready for a call?
Get your inecta Produce switch plan by email
We will send you the step-by-step plan for moving your business off inecta Produce, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your inecta Produce switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to switch
Try the free version yourself, or have Enterprise DNA build and run yours
Open source
Run it yourself
Free
- 1 Clone packhouse-for-claude-code from GitHub
- 2 Run npm run demo and open the folder in Claude Code
- 3 Type /attention to see what needs a decision in the demo season
- 4 Ask inecta for your growers, blocks and receipts as spreadsheets, and 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 bring your growers, blocks, lots and inspection history across from inecta and check every record on the way in
- check We set up your pools, charges, levies and grower statements to match how you settle with growers today
- check We add what your operation depends on: your exporter's paperwork, your crop's checks, a simple screen for the packing floor if you want one
- check It runs inside Omni, our managed Command Center, with the rest of your business
Questions
Instead of inecta Produce, answered
inecta is a full ERP with finance built in. Do we lose our accounts? expand_more
This replaces the produce side: growers, deliveries, lots, pallets, consignments and grower returns. Your accounts stay in the accounting package you already use or choose.
How do we get our records out of inecta? expand_more
Ask inecta, or whoever runs your system, for your growers, blocks and receipts as spreadsheets. The free version reads a different packhouse system's export layout, so inecta's columns need mapping first. If you run it yourself, you ask Claude Code to do the mapping. If we build it, the mapping and the check of every record is part of the job.
We grow as well as pack. Does it cover the farm side? expand_more
The free version starts at the block: who owns it, its spray diary, its GAP certificate and what was picked from it. Field plans, fertiliser schedules and crop costing per block are not in it today. If you rely on those, Enterprise DNA adds them to your version, built around how you actually run your blocks.
Our auditors want lot traceability. Is this enough? expand_more
Every pallet traces back to its grading run, delivery, block, pick date and spray record, and forward to its consignment, and the manifest prints that trace for every truck. Whether a given audit scheme is satisfied is your auditor's call. Your version can be shaped to the exact records your scheme asks for.
What would we actually be paying? expand_more
The free version costs nothing to run. If Enterprise DNA builds and runs your version, it is one setup fee and then a monthly retainer, agreed before we start, with no charge per user. Bring your inecta quote to the call and we will show you where the money goes.
Own your season's records, not a seat on someone's ERP
30 minutes with Sam. We look at what inecta costs you all in, licences and consultants included, what you actually use it for, and what your own version would look like. If it is a fit, we build it and run it. If not, take the free version and run it yourself.
Packhouse for Claude Code is free and open source, published by Enterprise DNA.
Done paying for inecta Produce?
Get your version built