Platform module

Crop recipes & lifecycle

Define the target environment once per crop and stage, then track every batch against it.

Overview

What this module does

A crop recipe is the plan you intend; the batch record is what actually happened. BeeGrow AI versions the recipes, applies them to batches and keeps the two side by side, so a disappointing cycle comes with evidence rather than a theory.

Recipes are versioned, so you know which version a batch actually ran
Re-activation and multi-cycle histories kept on the same batch record
Stage-specific targets for the environment and the nutrient feed
Comparison of planned against delivered conditions across cycles

Capabilities

In detail

Lifecycle and BBCH stages

Batches move through defined growth stages, each with its own targets. Stage transitions are recorded, not inferred, so day 24 means the same thing on every site.

Cultivar catalogue

Cultivars carry their baseline recipes, expected cycle lengths and quality parameters, so a new batch starts from what you already know rather than from blank fields.

Stage targets

Each growth stage carries its own environmental and nutrient targets, so the setpoints move as the crop develops, and the conditions actually delivered sit beside them.