Enterprise DNA

Instead of Radfords

Stop renting Radfords. Own your packhouse management system.

We build your version around how you pack, trace and pay growers, bring your Radfords data across, and run it for you.

Radfords is quoted privately after a demo call, with businesses in this lane paying five to six figures a year for software of this shape.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What you are paying for

Packhouse software is priced like an ERP. Underneath, it is a handful of records

Systems in this family are quoted privately behind a demo call and installed as a project; the anchor case in this lane is a business paying six figures a year for software that is a front end over a database. What a packhouse holds is ordinary: growers, blocks, deliveries, packouts, pallets, consignments, pools.

paid

A privately quoted enterprise licence

No public pricing: a demo call, a scoped quote, an annual invoice that grows with modules and sites. The businesses this lane rebuilds for pay five to six figures a year for systems of exactly this shape.

schedule

An implementation project before the first bin

Scoping, configuration, training and go-live before a single delivery is on the books. Here, a test run takes sixty seconds, and your growers and blocks import automatically from the old system's own exports.

extension

Grower payments as a bespoke add-on

Radfords describes grower payment handling as a bespoke add-on function designed per arrangement. Pooling proceeds and paying growers pro-rata less charges is a handful of records and a summary view, and it is in the free version on day one.

dashboard

Dashboards that answer the vendor's questions

Packout screens, stock screens, dispatch screens: what the vendor decided to chart. The question you actually have on a Tuesday (which grower's packout is sliding, which buyer is sitting on proceeds) is a sentence here, not a feature request.

lock

Compliance workflow gated by the product

Traceability, spray records and export documentation are the reasons packhouses buy these systems at all. The gates the law and the programmes actually imply are a page of rules with sources, enforced in a checklist you can read.

layers

Your history behind their login

Seasons of deliveries, packouts and grower statements live inside the vendor's system, reachable through their reports. Here it is a plain database you own: back it up, query it from anything, leave nothing behind when you change tools.

What you get instead

The same packhouse, over a database you own, with the gates kept sharp

The door

Intake that argues back before fruit becomes a problem

A truck arrives, the delivery lands with its spray history, and the gates do their job at the door instead of in an audit six months later.

  • check Fruit picked inside its spray withholding period is held, not received: the hold names the clear date and sits at the top of the attention list until someone decides
  • check A delivery cannot be graded without its spray diary on record, and the refusal explains what an MRL breach costs the whole programme
  • check Releasing held fruit requires the decision on the record: residue result, cleared market, or the dump
  • check Bins sitting ungraded past three days surface by themselves, because condition is money

The trace

One step back, one step forward, in seconds

Every pallet knows its grading run, its delivery, its block and its grower, so the recall drill is a join, not a paper chase. Grading builds the pallets, the coolstore holds them, the consignment takes them.

  • check Tracing a pallet walks from the pallet number on the docket to the block, the pick date, the spray record and the GAP certificate on one card
  • check The consignment manifest renders the same trace for everything on the truck: the recall answer printed in advance
  • check An export consignment cannot dispatch without its MPI assurance reference, and there is no force flag
  • check Fruit from a block with an expired GAP certificate cannot join an export consignment at all: the register enforces itself

The money

Grower pools and returns, the add-on the incumbent quotes, built in

Trays pack into a pool per crop and variety, sale proceeds land in the pool, and every grower's return is pro-rata less charges, visible at today's numbers all season.

  • check Checking a pool shows every grower's gross share, packing charges, levies and net, per tray, while the pool is still moving
  • check A pool cannot close while dispatched trays have no sale proceeds recorded: closing early would short-pay every grower in it
  • check Return statements render per grower per pool in your brand, with their fruit listed, drafts a person sends with the payment run
  • check Packout statements draft the moment a delivery grades, with the class 1 share the phone call is always about

Your data

A database you own, any agent, and an import that audits as it lands

Runs on a laptop with no setup needed, or on your own system for the whole operation. Works with Claude Code and similar tools. The records are the product, the assistant is just the door.

  • check Import growers, blocks and deliveries from FreshPack's own CSV exports in one command, dry run first
  • check The import is the first audit: expired GAP certificates and missing spray diaries are loud the moment it finishes
  • check The coolstore temperature record per room, with the printable register the export programme audits
  • check MIT licence, plain records, nine compliance rules with their sources in a file you can read and change

Make it yours

Design your own Radfords replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Radfords. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Radfords replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Radfords data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Packhouse for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Packhouse for Claude Code

Connected to your own database

What needs my attention right now?

Needs a decision (11)

Phi hold

Record
DEL-505
Grower
Bledisloe Avocados
Where
Bledisloe Grove
Days
2
Detail
HELD: picked 2026-09-22, spray window clear from 2026-09-28. Picked six day...

Spray diary missing

Record
DEL-504
Grower
Pongakawa Family Trust
Where
Pongakawa Road Block
Days
1
Detail
20 bins of kiwifruit received 2026-09-23 with no spray diary: grading is bl...

Assurance missing

Record
CON-302
Grower
Golden Coast Produce
Where
Singapore
Days
9
Detail
export consignment with 2 pallet(s) loaded and no assurance reference: it c...

Coolstore out of range

Record
Room 3
Where
Room 3
Detail
last reading 8.4 C against a 4 to 7 C band, with 3 pallet(s) in the room

Gap expired

Record
KPIN-10455
Grower
Kauri Point Growers
Where
Kauri Point Block 2
Days
20
Detail
NZGAP certificate expired 2026-09-04: fruit from this block cannot join an ...

Delivery ungraded

Record
DEL-503
Grower
Kauri Point Growers
Where
Kauri Point Block 2
Days
4
Detail
12 bins (3400 kg) received 2026-09-20 and still not graded: condition is mo...

Pool unsold

Record
Hayward 2026
Where
kiwifruit
Detail
300 dispatched tray(s) with no sale recorded: proceeds are missing and the ...

Pallet aged

Record
PLT-4024
Grower
Te Puna Orchards Ltd
Where
Room 1
Days
49
Detail
220 trays of Hayward class2 packed 2026-08-06: 49 days in store

Consignment stale

Record
CON-302
Grower
Golden Coast Produce
Where
Singapore
Days
9
Detail
open 9 days with 480 tray(s) allocated: dispatch it or free the fruit

Coolstore quiet

Record
Room 2
Where
Room 2
Days
30
Detail
no temperature check for 30 hours (7 pallet(s) in the room)

Gap expiring

Record
KPIN-10502
Grower
Pongakawa Family Trust
Where
Pongakawa Road Block
Days
18
Detail
NZGAP certificate expires 2026-10-12: book the audit now

Ask it anything

Questions Radfords cannot answer

Every one of these is a real question the demo answers today. Yours will be different, and that is the point.

chat_bubble Is there fruit on our floor right now that was picked inside its spray withholding period, and what is the plan for it?
chat_bubble Which deliveries cannot be graded because the spray diary never arrived, and which grower owes us paperwork most often?
chat_bubble Which export consignments are loaded but legally unable to leave, and how long have they sat?
chat_bubble Which blocks' GAP certificates lapse inside 30 days, and how many export trays came off each last season?
chat_bubble Which grower's packout is trending down run over run, and did the weather note on the grading run explain it?
chat_bubble What is every grower's return at today's numbers, charges shown, before the pool closes?
chat_bubble How many dispatched trays have no sale proceeds recorded, and which buyer is sitting on the money?
chat_bubble Which coolroom readings went out of range this month, with which fruit inside, and what did we do each time?
chat_bubble What is the oldest pallet in the store, whose fruit is it, and what has it cost in condition so far?
chat_bubble If this pallet number came back in a recall, how fast can we name the block, the pick date, the spray record and everything that travelled with it?

Switching

How to switch from Radfords

Moving off Radfords is mostly an export and an import, but expect to spend real time checking what the import turns up before you trust it and cutting over.

  1. 1

    Export your growers, blocks and deliveries

    Export what your Radfords FreshPack account allows, usually CSV or Excel. You want growers, blocks (orchards) and deliveries at minimum, since those are the files the import command reads. Check with Radfords on the exact export path if you're not sure where it lives in your account, since this varies by setup.

  2. 2

    Run the import as a dry run first

    Point the import tool at your growers, orchards and deliveries spreadsheet files and do a test run first. This loads nothing but shows you what the import would do, so you can catch mapping problems before anything lands in your records.

  3. 3

    Run the import for real, then read what it flags

    Run the same import for real this time. The import is the first audit: it will surface things loudly, like a block carried in with an expired GAP certificate, or a delivery with no spray diary flag. Go through every flag before you treat the data as trustworthy.

  4. 4

    Run both systems side by side briefly

    Keep Radfords running while you use Packhouse for real intake, grading and dispatch decisions. This is where you find out if anything didn't map the way you expected, before Radfords stops being your safety net. Keep it short, just long enough to be confident.

  5. 5

    Switch off Radfords

    Once the side-by-side period has shown the record holds up, and everyone is working from Packhouse day to day, cancel Radfords. Your season's data now lives in plain records you own, readable by any tool, with no export request needed if you ever want to move again.

construction

Where the real effort goes

The real work is not the import command, it's deciding what actually maps: your KPINs, block boundaries, pallet sizes, pool rules and which history is worth carrying forward versus leaving behind. That judgment call takes longer than the export itself. If Enterprise DNA installs and runs it for you, this is the part they do with you, not just the migration script.

Not ready for a call?

Get your Radfords switch plan by email

We will send you the step-by-step plan for moving your business off Radfords, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Two ways to run it

Run it yourself, or have it run for you

Open source

Run it yourself

Free

  1. 1 Clone the repo
  2. 2 npm run demo, then open the folder in Claude Code
  3. 3 Type /attention
  4. 4 Import your FreshPack exports and point it at your own database
Get it on GitHub

Omni by Enterprise DNA

Have Enterprise DNA install it

One setup fee, then a monthly retainer

  • check We migrate your growers, blocks, delivery history and certification records from FreshPack
  • check We write your crop's rituals in as commands: your maturity clearances, your bin tracking, your exporter's paperwork
  • check We tune the gates and charges to your operation: your withholding rules, your pool structure, your tray counts
  • check It runs inside Omni, our managed Command Center, with the rest of your business
Book a discovery call

Questions

Instead of Radfords, answered

Is it really free? expand_more

Yes. MIT licence. Run it anywhere, change anything, no account with us.

How does grading data get in without a grader integration? expand_more

The grader's end-of-run tally is entered once, and the pallets, the pool assignment and the packout statement follow from it. The free version does not read a live feed from your grader today. If your grader exports a file, the import reads it. A live feed is something Enterprise DNA can add when it builds your installed version.

Can it really handle grower payments? expand_more

The pool model is built in: trays pack into a pool per crop and variety, proceeds land as sales, and every grower's return is pro-rata less your packing charge and levies, visible at today's numbers all season. A pool refuses to close while dispatched trays have no proceeds recorded. Different arrangements (paid on pack, fixed price per tray) are a rule change in a file you can read, not a bespoke quote.

What about our exporter's specific requirements? expand_more

The gates ship with the floor every programme shares: spray diaries before grading, withholding periods at the door, assurance references before an export moves, GAP certification on the block. The free version does not include your exporter's specific documents and thresholds today. That's exactly what customising it and the rule book are for, and when Enterprise DNA builds your installed version those specifics can be added. Whether a specific consignment meets a specific market's rules is your exporter's and MPI's call, not the software's.

What does the installed version add? expand_more

Migration from FreshPack, your crop's rituals written in as commands, the rule book tuned to your programmes, your team shown the five commands that matter, and someone to call in week one of harvest. It runs alongside everything else Enterprise DNA runs for you.

Stop renting screens over your own season

30 minutes with Sam. We look at what your packhouse system costs a year, what your registers actually hold, and what the installed version would look like for your operation. If it is a fit, we install it. If it is not, take the free version and run it yourself.

Book a discovery call Get the free version

Packhouse for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Radfords?

Get your version built