Enterprise DNA

Instead of Hectre

Stop renting Hectre. Own the record of every bin you pack.

We shape it around how your orchards and packhouse actually work, bring your Hectre bin and fruit quality results across, and keep it running for you through harvest.

Hectre publishes no prices: every page ends in a request for a demo.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the Hectre quote covers

A demo call, a quote, and a set of separate apps for one harvest

Hectre does not put a price on its website. What it sells is split in two: apps for the orchard crew and scanning tools for fruit quality. Strip away the screens and both halves write the same kind of record: a bin, from a block, picked on a day, with a size and a grade.

call

No price until you have sat through a demo

Every page ends in a request for a demo. You cannot budget for next season, or compare it with anything else, until a salesperson has scoped your operation and sent a quote.

view_module

One product family for the orchard, another for the shed

Harvest, timesheets, payroll, analytics and quality control sit on one side; fruit sizing and colour grading sit on the other.

photo_camera

Cameras in the packhouse as an option

Colour grading can run on a commercial camera installed at your door to read fruit as it arrives. That is equipment on site, alongside the software itself.

query_stats

Size and grade answers on their dashboard

Results land in the vendor's dashboard, searchable by room and lot. To join them to the grower who owns the fruit, the pallets it went into and what the buyer paid, you download the results as a file and load them somewhere else.

receipt_long

Bin tickets without the money that follows them

Bin ticketing and crediting track fruit from the row to the bin. The step a packhouse is judged on, turning sale proceeds into each grower's return less charges, is not among the products on its site.

lock

Seasons of measurements held in someone else's app

Every scanned lot and every bin record lives inside the vendor's system. The longer you use it, the more of your own history sits in their app.

What your packhouse runs on instead

From the bin ticket to the grower's cheque, in one set of records

The bin

Every bin arrives knowing where it came from

A delivery is logged against its grower, block and pick date, with the spray diary and the orchard's certification checked before anyone grades it.

  • check Fruit picked inside a spray withholding period is put on hold at the door, with the date it clears
  • check A delivery with no spray diary cannot be graded until the diary is on file
  • check Bins left ungraded for more than three days come up on their own, before condition slips
  • check A block whose GAP certificate has lapsed is flagged the moment its bins arrive

The lot

Size and grade results tied to the fruit they describe

Keep measuring with the phone or camera you already trust. The results stop being a dashboard and become part of the lot, the pallet and the grower's statement.

  • check Bring in sizing results from the file your scanning tool downloads, matched to each lot
  • check Ask which grower's class 1 share is falling this week, and get a straight answer from your own numbers
  • check Each grading run builds its pallets, so a size or grade problem traces back to the block in one question
  • check Compare this season's packouts by block with last season's

The room

The cool room and the truck, on the same record

Pallets move from grading into rooms and out on consignments, and every step keeps its trace.

  • check Temperature readings per room, with a printable register for the export programme's audit
  • check A room running out of its band shows up with how many pallets are sitting in it
  • check An export consignment cannot leave without its MPI assurance reference
  • check The manifest for each truck lists every pallet back to its orchard block

The return

Grower pools and returns, worked out while the fruit is still selling

Packed trays go into a pool for each crop and variety, sales land in the pool, and each grower's share is shown after packing charges and levies.

  • check A running view of every grower's gross, charges and net per tray, all season
  • check A pool will not close while any dispatched fruit still has no sale recorded
  • check Branded return statements per grower per pool, drafted for a person to send with the payment run
  • check All of it in plain records you own, under an MIT licence, with nothing to hand back if you move on

Make it yours

Design your own Hectre replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Hectre 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 Hectre data across and run it for you.

Switching

How to switch from Hectre

A move usually involves exporting the records Hectre makes available, mapping them to your packhouse fields, checking a test import, then running both systems before you stop using Hectre.

  1. 1

    Export your Hectre records

    Start with the records you want in Packhouse for Claude Code, such as growers, blocks, deliveries and grading results. Hectre’s help centre shows how to download sizing results as a CSV from its dashboard. For other records, export what your account allows, usually CSV or Excel, and check with Hectre if you are unsure what is available. Choose how much history to bring across.

  2. 2

    Load a test import

    Have the records mapped to the fields in your new packhouse, then check a test run before anything is saved. The import can work with plain CSV, but Hectre’s columns may not match the new records directly. If Enterprise DNA is setting up your system, they handle this mapping. If you are doing it yourself, you can ask Claude Code to map the files.

  3. 3

    Review the import flags

    Check what the import identifies before you rely on the new records. For example, an imported block with an expired GAP certificate or a delivery with no spray diary is flagged. Confirm the details against Hectre and your own records, then correct missing or mismatched information. Treat this review as part of the move, not just a check that the files loaded.

  4. 4

    Run both systems together

    Keep Hectre running while you use the new records for a short period. Compare the growers, blocks, deliveries and results you use in day-to-day packhouse work, and check that the new system gives you the records you need. Your current tools can keep running until you are happy with the new records. Do this before harvest rather than in the middle of it.

  5. 5

    Switch off Hectre records

    Once you have checked the imported records and are comfortable using the new packhouse, stop using Hectre for the records you have moved. Keep a copy of the exports you used for the import. Packhouse for Claude Code does not replace Hectre’s fruit sizing from photos, so keep your sizing tool if you still need it and bring its results into your own records.

construction

Where the real effort goes

The real work is usually matching Hectre’s columns to your own fields and rules, then deciding how much history to bring across. The more records and seasons you want to include, the more there is to check. Enterprise DNA handles the mapping and test run when you have them install and run the system. If you do it yourself, you can ask Claude Code to map the files.

Not ready for a call?

Get your Hectre switch plan by email

We will send you the step-by-step plan for moving your business off Hectre, 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

Do it yourself, or have us do it

Open source

Do it yourself

Free

  1. 1 Clone the repo from GitHub
  2. 2 Run npm run demo and open the folder in Claude Code or a similar tool
  3. 3 Type /attention to see what needs a decision
  4. 4 Download your Hectre results as CSV and ask Claude Code to map the columns on import
Get it on GitHub

Omni by Enterprise DNA

Have Enterprise DNA build and run it

One setup fee, then a monthly retainer

  • check We bring across your bin, block and fruit quality history from Hectre and check it as it lands
  • check We set it up for your crops, your size bands, your grade rules and how you pay growers
  • check We connect it to the scanning tools and payroll you keep, and add a phone screen for the crew if you want one
  • check It runs inside Omni, our managed Command Centre, with the rest of your business
Book a discovery call

Questions

Instead of Hectre, answered

Does this replace Hectre's fruit sizing from photos? expand_more

No, and it does not pretend to. Measuring fruit from a photo is a job for a scanning tool, and you can keep the one you have. What changes is where the answers live: size and grade results come into your own database, attached to the lot, the grower and the pallet, instead of staying in a separate dashboard.

Can we get our history out of Hectre? expand_more

Hectre's help centre shows sizing results downloading as a CSV file from its dashboard. Those files have their own columns, so matching them to your records is part of what Enterprise DNA does when we set it up, or you can ask Claude Code to map them in the free version. We check every file with a test run before anything is saved.

What about our pickers, timesheets and payroll? expand_more

The free version is a packhouse system: bins, lots, rooms, consignments and grower returns. It does not run payroll. If your crew's hours and piece rates already flow into a payroll system you trust, keep that, and Enterprise DNA can connect it to your records when we build your version.

Our team works in the orchard on phones. Does this work there? expand_more

The free version is run by asking questions on a laptop, not by tapping through an app in the rows. If your crew needs a phone screen for bin tickets, Enterprise DNA builds one into your version, writing straight into the same database you own.

How long does switching take? expand_more

A test run on sample data takes about a minute. Bringing your growers, blocks and past results across depends on how much history you have, and we do it before harvest rather than in the middle of it. Your current tools keep running until you are happy with the new records.

Measure your fruit with anything. Keep the record yourself

30 minutes with Sam. Bring what Hectre has quoted you and what you actually use it for. We will show you what your own version would hold, what it would connect to, and how your history comes across. 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 Hectre?

Get your version built