Skip to content
Use cases
Permanent crops

Orchards

Count the fruit, protect the blossom

Fruit counting for the pack house booking, blossom frost protection, tree by tree health, and birds at ripening.

Blocks of 1 to 40 hectares.

Book a field visit
Aerial view of vineyard rows following a slope

What actually goes wrong

An orchard's year turns on two short windows. A frost during blossom can remove the crop in a single night, and protection is expensive enough that it needs to go exactly where the cold actually collects. Then at harvest, the pack house, the labour and the storage all need a number weeks ahead, and that number traditionally comes from counting a few trees and multiplying. Between those, individual trees decline, and a declining tree in row 14 looks like every other tree from the end of the row.

How we set it up

Frost profiling through blossom, with a nightly brief when the forecast is near the threshold. Fruit counting flights at set points after fruit set, aggregated per row and per block. Tree by tree health tracking that carries an identity across seasons, so decline is a trend rather than a discovery.

The flight calendar across a season

  1. Frost pocket mapping and nightly risk briefs.

  2. Set counts against reference rows and the first crop estimate.

  3. Tree by tree health tracking, irrigation uniformity, canopy vigour.

  4. Fruit counts per row, sizing estimate and picking sequence.

  5. Bird pressure monitoring and on-demand deterrence.

What you end up with

Recorded on your fields, flight by flight. Not a projection.

  • Frost protection deployed to mapped cold pockets
  • Pack house and labour booked against counted fruit
  • Individual trees tracked across seasons rather than sampled
  • Picking sequenced from measured ripeness by row

More in Permanent crops