Product Release Update - October 25, 2026: Daisy area table, Metos climate stations, custom soil line names and Phytech Program (Beta)

Four updates across the platform:

1. Daisy Area Recommendations Table

2. Metos Climate Station Integration

3. Custom Names for Soil Graph Threshold Lines

4. Phytech Program (Beta)

Feature 1 · Daisy area recommendations

Daisy Area Recommendations Table

Daisy now shows the irrigation recommendations for all plots in an area together, in one table. Growers no longer need to open each plot one by one to see what Daisy recommends.

What it does.

• See every plot at a glance: plot name, recommendation direction (increase / decrease / maintain), recommended weekly amount and the matching irrigation duration (run time)

• Switch between views: the existing grouped list or the new table. The choice is saved per user

• Available on web and mobile

Why it matters. "How much water this week?" is the question growers ask Daisy most often. They can now answer it for the whole area in seconds.

Feature 2 · Climate stations

Metos Climate Station Integration

Phytech now connects to Metos climate stations. Growers who already use Metos stations can see that climate data directly in Phytech, without installing a separate station.

Why it matters. Metos is widely used, especially in South America. Growers keep the station they already trust and get its data alongside their plant and soil data in one place.

Feature 3 · Soil graph threshold lines

Custom Names for Soil Graph Threshold Lines

Growers can now choose what the soil graph threshold lines are called, so they see the terms they already use.

What it does.

• Choose the names in Settings: for example "SAT" or "Field Capacity" for the upper line, and "Stress" or "MAD" for the lower line

• Available on web and mobile

Why it matters. Growers asked for it directly. The graph now speaks the same language as their irrigation team.

Feature 4 · Phytech Program (Beta)

Phytech Program (Beta): Plan once. Every irrigation follows.

A live irrigation plan that owns its schedule, its shifts and every event it creates.

The problem today. A template creates events and lets go. Change one duration and the week is re-created by hand. An irrigation on the planner can't tell you which plan it came from, and moving one event by hand can break the order of pumps and valves. On farms with 50 to 100+ valves and several pump houses, this does not scale.

The solution: one live plan. Edit the Program once and every future irrigation updates. What already ran, or is running now, stays as it was.

Set it up the way the farm runs.

• Shifts: group valves and valve groups into shifts that run in order

• Timing: parallel, delay or overlap between shifts and between valves, to protect pressure and pipes

• Many pumps: assign every pump a shift needs, right inside the shift

• Cycles: repeat the full sequence several times a day, with a rest time between cycles

• By weekday: set a different duration per day. Run longer on a forecast heat day, no new program needed

• Any schedule: selected days, every few days, or no schedule and start it by hand

Every action in one place. Freeze & Release for the off-season, Stop & Resume without deleting anything, Start now without changing the schedule, and Duplicate to use a program as a starting point. Each program shows its status at a glance: Ready, Running, Running with failures, Stopped, Frozen or Incomplete.

Safe by design. Program irrigations are locked in the planner, so changes are made in the Program. Two Programs on the same valve stay fully independent, and existing templates and manual irrigations are not touched.

Coming next. Cooling programs, fertigation by shift, and Smart Planning recommendations applied straight to the Program.

Available now as Beta.