Instead of iDSnet Packhouse Software
Move on from iDSnet Packhouse Software. Own your packhouse tracking system.
We shape your version around your lines, grades, labels, trace rules and grower settlements, bring the records Matthews can supply across, and run it for you.
Matthews publishes no packhouse price. Buyers request a private quote, and its terms allow either a perpetual licence or a subscription renewed monthly or annually.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the quote covers
Packing-floor visibility sold as configured software and integration
iDSnet Packhouse Software focuses on the packing floor: who packed each carton, its grade, the line it came from and where it went. Matthews does not list the price. The buyer requests a quote for the software, configuration and connections their facility needs.
A quote before you can compare the bill
The product page shows a quick-quote form rather than a price list. Your actual licence and project cost arrive only after Matthews has your company and facility details.
A licence chosen inside the proposal
Matthews' terms allow software to be licensed perpetually or by subscription, with subscription periods renewed monthly or annually. The available option is set by Matthews rather than published on the packhouse page.
Connections to the equipment on your floor
The value is tied to packer identification, carton labels, scanners and packing-line data. Those connections need to match the devices and processes already operating in your shed.
An integration beside your management system
Matthews says iDSnet integrates into standard packhouse management software. It is designed to connect packing-floor records with another management system.
Reports shaped around line performance
The advertised insight is carton quantity and quality by grade and packer, including who packed each carton and on which line. Questions outside that model depend on the other systems holding the rest of the season.
Backups remain your responsibility
Matthews' licence terms say it makes no commitment to back up item data and places responsibility for backup and replication on the customer. Ownership needs a copy you can inspect and keep yourself.
What you own instead
One connected season record, not a floor layer beside it
From the orchard
Every delivery arrives with the context behind it
The record begins with the grower and block, then follows the fruit through receiving and grading rather than starting when a carton reaches the line.
- check Growers, orchard blocks, deliveries and grading runs remain connected through the season
- check Spray diaries and withholding dates are checked before fruit moves into grading
- check A held delivery records why it was stopped and what decision released or disposed of it
- check Ungraded bins surface on the attention list before condition becomes a quiet loss
Across the floor
Pallet accountability with the rest of the trace attached
The packout detail still matters, but it sits inside the full story of the fruit instead of ending at a performance report.
- check Record the grade and packed date against each pallet
- check Compare packout and quality results by grower, block or grading run
- check Start with a pallet and follow it back to the delivery, block and spray history
- check Follow the same record forward into coolstore, consignment and customer destination
Through dispatch
Exceptions appear before the truck leaves
Temperature, certification and export checks sit beside the stock they affect, so the morning question is what needs a decision rather than which report to open.
- check Coolstore readings outside the room's range show which pallets are exposed
- check Fruit tied to an expired GAP certificate stays off export consignments
- check An export load cannot move without its assurance reference recorded
- check A recall view identifies the affected fruit, its source and every destination in the same record
Back to the grower
The trace ends with the grower's return, not the carton label
Packed trays, sale proceeds, charges and levies meet in the same season record, giving owners the operational and financial answer together.
- check See each grower's gross share, deductions, net return and return per tray while a pool remains open
- check A pool stays open while dispatched fruit is missing a recorded sale
- check Draft packout and grower return statements in the packhouse's own branding
- check Keep the complete history in a database the business can back up, inspect and move
Make it yours
Design your own iDSnet Packhouse Software replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from iDSnet Packhouse Software. 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 iDSnet Packhouse Software data across and run it for you.
Switching
How to switch from iDSnet Packhouse Software
A move like this involves confirming what iDSnet can supply, mapping those records, testing the import and comparing both systems before you cut over.
- 1
Get your records out
Ask iDSnet Packhouse Software or Matthews what your account can export, including carton, packer, grade, line and destination records. Also ask about the grower, block and delivery records you want to bring across. Ask Matthews which format your account can export, then check what is included. Decide how much history you need before requesting it.
- 2
Map and load the records
Packhouse for Claude Code's ready-made import expects a different packhouse format, so map your export columns to its fields before loading anything. The import offers a test run. Use it first to see how your records fit without making them the working record. If Enterprise DNA is installing and running your version, it confirms the available data, maps the fields and tests the move with you.
- 3
Review what the import flags
Check the import results before you rely on the new records. For example, the import flags blocks with expired GAP certificates and deliveries with no spray diary. Review those findings against your source records and investigate anything you cannot reconcile. Also compare a sample of pallets end to end, including the trace back to the block and forward to the consignment.
- 4
Run both systems briefly
Keep iDSnet as your live record while you run both systems side by side for a short period. Compare the same sample of pallets in each system, then check that the recall trail, stock position and grower totals agree. Resolve differences before cutover. Do not stop using iDSnet as the working record until these checks are complete.
- 5
Switch off iDSnet
Once the checks agree and your team is ready, make Packhouse for Claude Code the live packhouse record and stop entering new activity in iDSnet Packhouse Software. Confirm with Matthews what happens to your existing access and records under your agreement. Matthews' public materials do not document a standard export or shutdown process, so check those details before ending your current arrangement.
Where the real effort goes
Most of the work is mapping your own fields and rules to Packhouse's import format, then checking exceptions and deciding how much history to bring across. The ready-made import expects a different packhouse format, so exported columns may need mapping first. If you have Enterprise DNA install and run your version, it confirms the available data, maps it and checks the test move.
Not ready for a call?
Get your iDSnet Packhouse Software switch plan by email
We will send you the step-by-step plan for moving your business off iDSnet Packhouse Software, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your iDSnet Packhouse Software switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to move
Run the free base yourself, or have Enterprise DNA build and operate your version
Open source
Do it yourself
Free
- 1 Open the packhouse-for-claude-code repo on GitHub
- 2 Run npm run demo, then open the folder in Claude Code
- 3 Type /attention to review the sample season's held fruit, missing records and stalled sales
- 4 Export the records Matthews can provide and ask Claude Code to map the iDSnet columns before importing
Omni by Enterprise DNA
Have Enterprise DNA customise and run it
One setup fee, then a monthly retainer
- check We confirm what iDSnet data Matthews can supply, map it to the new record and check a test move with you
- check We match your lines, grades, carton labels, packer rules, coolrooms, export checks and grower pools
- check We add a floor screen or connect the files from your graders, scanners and label equipment where your operation needs them
- check We install it inside Omni by Enterprise DNA and operate it alongside the rest of your business
Questions
Instead of iDSnet Packhouse Software, answered
What does iDSnet Packhouse Software cost? expand_more
Matthews does not publish a packhouse price. Its product page asks for a quick quote, and its terms allow either a perpetual licence or a subscription renewed monthly or annually. Your current proposal and renewal documents are the reliable source for your own total.
Can we bring our iDSnet history across? expand_more
Matthews' public packhouse and support pages do not document a standard export process. We first confirm which carton, packer, grade, line and destination records Matthews can supply, then map those fields into your version and do a test move before anything becomes the working record. The free version's ready-made import expects a different packhouse format, so a do-it-yourself move needs its columns mapped first.
Will the free version connect to our scanners, printers and grading equipment? expand_more
Not live by default. The free version can take the results your equipment exports and keep the operational record around them. If a live connection matters, Enterprise DNA scopes it into your version after checking the equipment and the data it makes available.
Does this replace every system iDSnet connects to? expand_more
It replaces the packhouse record for growers, deliveries, grading, pallets, coolstore, consignments and grower pools. It is not an accounting ledger, and it does not pretend to replace specialist hardware controls. We connect those parts where the business needs one joined process.
How do we switch without losing traceability during the season? expand_more
Start with a test move, compare a sample of pallets end to end, and run both records together briefly. Cut over only after the same recall trail, stock position and grower totals agree. Enterprise DNA handles that checking when we build and run your version.
See what sits behind your iDSnet quote
Spend 30 minutes with Sam. Bring the iDSnet proposal or renewal, the other packhouse systems it connects to and one real recall or grower-settlement workflow. We will map what belongs in a database you own and show what your version would need. If it fits, we build and run it. If it does not, keep the free version.
Packhouse for Claude Code is free and open source, published by Enterprise DNA.
Done paying for iDSnet Packhouse Software?
Get your version built