Enterprise DNA

Instead of Croptracker

Stop renting Croptracker. Own your orchard records.

We build around your blocks, varieties and picking routines, map your Croptracker exports and run your version through Omni by Enterprise DNA.

Croptracker plans start at US$3,300 a year including the first ten users. Enterprise pricing depends on your requirements.

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

The Croptracker comparison

Price the records you need, then the work around them

Croptracker publishes a US$3,300 yearly starting price. Its modules cover much more than orchard records. Match your actual subscriptions to the work your team uses before deciding to switch.

paid

An annual starting plan

The advertised starting plan includes ten users. Confirm the scope and your actual renewal bill with Croptracker.

layers

Module subscriptions

Croptracker says most users subscribe to individual modules annually. Monthly subscriptions are available at a premium.

eco

Spray recording

The Spray module records applications. Compare that with your own diary, evidence checks and recorded harvest holds.

agriculture

Harvest records

The Harvest module tracks yields and traceability. Your block and lot history is the starting point for migration.

schedule

Time recording

Punch Clock handles employee time. The free version here holds labour allocations for block review; payroll stays with your existing provider.

settings

Custom requirements

Enterprise pricing varies with requirements. Compare the quoted reporting and connection work with a version built for your orchard.

What you own

An orchard record you can change with the season

Before picking

Put unresolved spray evidence in view

Review entered intervals and diary evidence together before scheduling a pick.

  • check See each block’s recorded pick and reentry times
  • check Spot unknown label rules without treating them as zero
  • check Flag a pick planned before its recorded hold ends
  • check Keep the final label and market review with your responsible person

Harvest history

Trace a lot back to its block

Follow a harvest record through its pick date, prior sprays, destination and docket.

  • check Bring bin records across from the supported harvest report
  • check Convert documented weight units to kilograms
  • check Keep imported history held for reconciliation
  • check Find lots missing a destination or docket

Block review

Read labour, water and yield together

Use recorded allocations to investigate the blocks that need a closer look.

  • check Compare kilograms per hectare by block
  • check See labour cost per recorded kilogram
  • check Find labour allocated to blocks with no harvest
  • check Compare irrigation litres with recorded harvest weight

Weekly work

Make the next action visible

Your review uses the records you hold and the operating rules you choose.

  • check List overdue block tasks with their owners
  • check Review missing or expired certificate dates
  • check Print spray diaries, harvest dockets and labour summaries
  • check Add a new review question without buying another reporting tier

Make it yours

Design your own Croptracker replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Croptracker 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 Croptracker 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 Orchard for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Orchard for Claude Code

Connected to your own database

Which blocks need review before the next pick?

B02

Ock pl
Hill Gala
Anned pick pi
2026-10-05
Ck after en
2026-10-06T00:00:00.000Z
Ter after un
2026-10-04T00:00:00.000Z
Known rules de
0
Cision
WITHHOLD

B01

Ock pl
River Gala
Anned pick pi
2026-10-07
Ck after en
2026-10-09T00:00:00.000Z
Ter after un
2026-10-03T00:00:00.000Z
Known rules de
0
Cision
WITHHOLD

B04

Ock pl
East Pear
Anned pick pi
2026-10-09
Ck after en
2026-09-21T00:00:00.000Z
Ter after un
2026-09-20T00:00:00.000Z
Known rules de
0
Cision
REVIEW BEFORE PICK

B03

Ock pl
South Sauvignon
Anned pick pi
2026-10-16
Ter after un
2026-09-15T00:00:00.000Z
Known rules de
1
Cision
REVIEW DIARY

Ask it anything

Ten questions to ask across your orchard records

These questions run against the demonstration records below. Croptracker also offers configurable reports; the difference here is owning and changing the underlying record.

chat_bubble Which blocks have pick dates before their recorded spray interval ends?
chat_bubble Which blocks have no recent diary review?
chat_bubble Which spray entries still lack a label rule?
chat_bubble Which recorded picks overlap a prior spray interval?
chat_bubble Which harvest lots have no destination or docket?
chat_bubble Which blocks have the highest recorded labour cost per kilogram?
chat_bubble Where have we logged labour but no harvest yet?
chat_bubble How much recorded irrigation water is allocated per harvested kilogram?
chat_bubble Which block tasks are overdue and who owns them?
chat_bubble Which spray records used an operator whose training date had passed?

Switching

How to switch from Croptracker

A move like this usually involves exporting the records you need, mapping your fields and rules, testing the import, then checking the new records alongside Croptracker before you switch.

  1. 1

    Export the records you need

    Start with Croptracker’s standard Harvest Inventory Report for bin records. For other history, export what your account allows, usually CSV or Excel, and check with Croptracker if you are unsure how to get it. Configured exports need their headings checked. Spray history, attachments and other modules need separate mapping, so decide which records you want to bring across before you begin.

  2. 2

    Load a test import

    Use the supported Harvest Inventory Report for bin records, or a mapped harvest CSV for other harvest records. Run the test import first, before loading records into your working database. Check that the headings and units match the data you exported, including any weight conversions. Do not assume the base import covers every Croptracker module.

  3. 3

    Review and reconcile the results

    Check the test results for records that were held, rejected or need mapping changes. Imported harvest records remain held for review, and conflicting history stops the import. Compare the imported bin or harvest records with the Croptracker report, including totals and original units. Resolve differences and agree which history is in scope before loading the final set.

  4. 4

    Run both systems briefly

    Keep using Croptracker while you use Orchard for Claude Code with a small, agreed set of current records. Compare new entries and the records your team relies on in both systems. Use this period to check your field rules and capture workflow, including any agreed screens or connections, before your team depends on the new setup.

  5. 5

    Switch off Croptracker

    Once you have checked the imported history and your team can record its agreed work in Orchard, choose a cutover point. Confirm that the records you need are present and that any differences have been resolved. Keep a copy of your Croptracker exports according to your business recordkeeping needs, then stop entering new work in Croptracker.

construction

Where the real effort goes

The real work is usually mapping your own fields and rules, checking configured export headings and units, and deciding how much history to bring. Bin inventory has a supported import, but spray history, attachments and other modules need separate mapping. Plan time to review and reconcile the results. If you have Enterprise DNA run it, they handle this migration work as part of the agreed scope.

Not ready for a call?

Get your Croptracker switch plan by email

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

Three ways to run it

Do it yourself, customise it, or have us run it

Open source

Do it yourself

Free code under MIT

  1. 1 Clone Orchard for Claude Code and run npm install, then npm run demo
  2. 2 Open the folder in Claude Code, Codex, OpenCode or Cursor
  3. 3 Check the import guide, map your export and run a dry run
  4. 4 Set your real rules and arrange hosting, access and backups before use
Get it on GitHub

Built around your business

We customise it

Scoped setup, with ongoing work agreed

  • check Your block names, fields, crop programmes and review rules
  • check Your Croptracker exports mapped and reconciled
  • check Mobile capture or a web front end built to the agreed brief
  • check A different database platform if your team needs one
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Agreed connections to your other business records
  • check Managed access, backups and regular record checks
  • check A person to call when your picking process changes
Book a call

Questions

Instead of Croptracker, answered

What does Croptracker cost compared with this? expand_more

Croptracker advertises plans starting at US$3,300 a year for the first ten users. Your modules and enterprise requirements determine the actual quote. The free version here has no software licence fee. Running costs remain yours. Enterprise DNA quotes a setup fee, then a retainer for the managed version.

Will our Croptracker history come across? expand_more

The free version imports bin inventory from the supported Harvest Inventory Report, with known weight conversions and a test run first. Configured exports need their headings checked. Spray history, attachments and other modules need separate mapping. We agree that scope and reconcile the results before cutover.

Does this tell us fruit is safe to pick? expand_more

It checks your entered spray intervals and record evidence. It does not certify residues, market access or GAP compliance. Your responsible person checks the actual label and buyer programme. Imported harvest records remain held for review.

What about mobile capture, scanning and our field team? expand_more

We scope those capture screens and connections as part of your custom version. Show us how your team works at the block and which records must still be captured without reception. We agree and test that workflow before switching.

Can we leave or change who runs it later? expand_more

Yes. You retain the code and database, and can export the records. The free version is open source under MIT. Your managed arrangement covers the agreed operating work, with the migration and handover responsibilities written into the scope.

Bring your Croptracker bill and one harvest report

Spend 30 minutes with Sam. Show him the modules you use, the records you need and the field workflow that must keep working. He will scope your version, the migration and who runs it.

Book a call Get the free version

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

Done paying for Croptracker?

Get your version built