OYO AIOYO AI
Book a demo
USE CASES / GREENHOUSE MANAGEMENT
USE CASE · GREENHOUSE MANAGEMENT

From crop plan to invoice, on one governed model.

How a commercial greenhouse runs planning, tasks, climate monitoring, harvest, sales, finance and compliance on OYO AI: every plan activated atomically, every lot traceable in seconds, every promise checked against what can really be delivered.

Book a demoDownload the PDF
20 use cases across ten modules7 personas, from owner to field worker10 s to trace a lot one-up and one-back6 gates the system enforces on its own
Cover of the OYO AI use case: From crop plan to invoice
THE PAYOFF

What a grower like you stands to gain.

Each figure is an industry benchmark with its source, paired with the platform rule that turns it into your number. No custom code: configured on OYO AI, so it holds on day one and on day one thousand.

10 s
to trace any lot one-up and one-back. The law gives you 24 hours.

From seed supplier to customer invoice and back, with the notification list exported and the elapsed time recorded. Before digital lots, a manual trace at one major retailer took almost seven days.

Source: FDA FSMA 204 Food Traceability Rule, records within 24 hours. Walmart and IBM mango trace: 6 days 18 hours before, 2.2 seconds after.
$10M
average direct cost of a food recall

A failed water test flags every lot harvested since the last passing test and names the customers who received them. The recall starts before it spreads.

Source: Grocery Manufacturers Association and FMI recall study, as reported by Food Safety Magazine. Direct costs only.
49%
of a controlled-environment farm’s operating cost is labor

Tasks are generated from the plan, assigned in bulk to certified hands, and started in three taps on a phone, online or offline. The largest cost pool gets the most attention.

Source: Agrilyst State of Indoor Farming report, 150+ growers. Labor 49% of operating cost for hydroponic farms, 56% for vertical farms.
12.6%
of fresh fruit is lost to shrink at retail alone

First-expired-first-out is enforced at the scanner, and a disposal cuts what Sales can promise within one cycle, so nothing is sold that will not arrive fresh.

Source: USDA Economic Research Service, retail shrink 12.6% for fresh fruit and 11.6% for fresh vegetables.
And the rules that make the numbers stick
  • 6 gates enforced automatically: PHI, REI, certification, credit, capacity, water
  • ATP recomputed within one cycle of a disposal
  • 0 ghost inventory
  • 100% of licensed work on certified hands
  • 3 taps to start a task, offline included
  • 1 open alert per zone, parameter and rule
  • 12-month cash projection, negative months flagged
  • 4 h for a full mock recall, customer notification included
  • 0 edits to a lot code, ever
BEYOND THE USUAL

Where typical software stops, and where OYO AI keeps going.

Climate systems publish yield and energy percentages. Produce ERPs promise faster recalls. Almost none say how holds, promises and lot records actually behave. This is the difference, area by area.

AreaTypical solutionsOYO AI
TraceabilityTypical“Faster recalls”, stated as a percentage. Records inside the 24 hours the rule allows.OYO AIOne-up and one-back in 10 seconds, customer list exported, elapsed time recorded on every query.
Food-safety holdsTypicalSpray applications are recorded.OYO AIA treatment places PHI and REI holds that block harvest and re-entry, with the release date on screen. Overrides are flagged on the compliance dashboard.
What Sales can promiseTypicalStock on hand, sometimes a yield forecast.OYO AIAvailable to promise: stock within shelf life plus forecast, minus reservations and contracts, recomputed within one cycle of a disposal.
PickingTypicalLot histories you can look up.OYO AIFirst-expired-first-out enforced at the scanner. Another lot needs a reason and leaves an audit record.
Mobile workTypicalHours saved, online.OYO AIThree taps to start, an offline queue with idempotency keys, and published conflict rules: earliest start wins, latest progress wins, completion never reverts.
Lot recordsTypicalEditable master data.OYO AIAn immutable lot code written once at harvest, carrying seed batch, treatments, water tests, workers and equipment for its whole life.

The typical column summarises what greenhouse climate, farm management and fresh-produce ERP software publicly state for each area as of September 2026. It describes the category, not any single vendor.

THE OPERATION

Two objects carry everything: the crop plan and the lot.

A greenhouse plans crops per zone, turns each plan into tasks, watches the climate through sensors, treats and harvests under food-safety holds, sells against what it can honestly promise, and closes every plan with its economics.

A plan is one variety, in one zone, over one date range, activated all or nothing. A lot is born at harvest with an immutable code and carries its whole history forward and back: seed batch, treatments, water tests, workers, orders, customers, invoices.

THE SPINE

What the system can promise, and what it will not let through.

ATP = unreserved stock within shelf life + forecast harvest − reservations − contract commitments

Available to promise, recomputed within one aggregation cycle of any disposal. Sales never sees a crop that no longer exists.

PHI and REI holds

A treatment computes its own pre-harvest and re-entry intervals. Harvest and task assignment are blocked until they expire, and any override is flagged on the compliance dashboard.

Certification and credit

A licensed task cannot go to an expired licence; an order cannot confirm beyond the customer’s credit limit without Finance.

Capacity and water

Plans cannot overlap beyond a zone’s productive area. A failed water test flags every lot harvested since the last passing test on that source.

END TO END

The chain a crop follows.

  1. 01Crop plan
  2. 02Tasks
  3. 03Sensor readings and alerts
  4. 04Treatments with PHI / REI
  5. 05Harvest, creates the lot
  6. 06FEFO picking
  7. 07Sales order with ATP and credit
  8. 08Delivery
  9. 09Invoice and payment
  10. 10Plan economics
WHAT IS COVERED

Ten modules, in the order of the release plan.

The core loop and harvest first, then sales and finance, then compliance and analytics, with water, energy and workforce alongside. Twenty use cases, each with its main flow, alternative flows, postconditions and the rules it enforces.

Module 1 · Crop planning and activation

  • UC-01Create and activate a crop plan
  • UC-02Apply a rotation template to a zone

Module 2 · Task management and mobile execution

  • UC-03Bulk assign generated tasks
  • UC-04Execute a task offline, on mobile

Module 3 · Environmental monitoring and IPM

  • UC-05IoT anomaly detection and alert generation
  • UC-06Record a treatment application with PHI / REI holds

Module 4 · Harvest, QC and lot management

  • UC-07Harvest produce with the PHI gate
  • UC-08FEFO picking with override

Module 5 · Sales and order fulfilment

  • UC-09Place a sales order with ATP and credit check
  • UC-10Handle a delivery rejection

Module 6 · Finance and invoicing

  • UC-11Auto-generate an invoice and record payment
  • UC-12View the 12-month cash flow projection

Module 7 · Compliance and traceability

  • UC-13Run a traceability query (mock recall)
  • UC-14Handle a failed water test

Module 8 · Analytics and strategic re-planning

  • UC-15Review plan economics at completion
  • UC-16Record a disposal and update ATP

Module 9 · Water and energy management

  • UC-17Record an irrigation event with drain metrics
  • UC-18Record the monthly energy meter reading

Module 10 · Workforce and payroll

  • UC-19Process payroll with mixed pay types
  • UC-20Assign a pesticide task to a certified worker only
WHO DOES WHAT

Seven personas and a system that acts on its own.

Owner

Reads the cash runway and the plan economics, and holds the final override.

Manager

Assigns tasks in bulk, authorises IPM actions, confirms dispositions on rejections and disposals.

Agronomist

Designs and activates crop plans, applies rotation templates, records treatments and disposals.

Worker

Executes field, warehouse and driving tasks on mobile, online or offline, with photos where the rules ask for them.

Sales Manager

Places orders against available-to-promise stock and forecast, inside the customer’s credit.

Finance Officer

Records payments atomically, runs mixed-pay-type payroll, reads the 12-month projection.

QA / QC Officer

Grades the harvest, records water tests, runs mock recalls and real ones.

RULES, NOT REMINDERS

Gates the system enforces, each with a message.

01

Atomic activation

Rationale, capacity, task generation, seed reservation, notification and audit happen together or not at all. A retry is absorbed by its idempotency key.

02

PHI gate on harvest

A worker opening a harvest task under an active pre-harvest interval sees the exact release date and cannot proceed.

03

Grades must sum

Class A plus Class B plus waste must equal the total kilograms, or the lot is not created.

04

FEFO, or a reason

Lots are offered first-expired-first-out. Scanning another lot is refused; an override needs a reason and leaves an audit record.

05

Credit before confirmation

An order beyond the customer’s limit holds for credit review. Only Finance or the Manager can move it.

06

No document without substance

An invoice needs a complete company profile and at least one line. A document that itemises to nothing is not a document.

07

Offline, but never twice

Work queued without signal syncs with idempotency keys; the earliest start wins, the latest progress wins, and completion never reverts.

08

Certified hands only

A task that needs a licence cannot be assigned to an expired one, and a renewal task is generated 30 days before expiry.

ONE LOT, BOTH DIRECTIONS

A traceability query, answered in seconds.

A mock recall is scheduled every six months; a failed water test is the real thing. Either way, the lot code is enough. Both directions return within ten seconds and the customer notification list is exported.

Backward: where it came from

  • Crop plan, zone, seed batch and seed supplier
  • Every treatment with its PHI status
  • Every irrigation event and the water tests covering them
  • Every worker involved and every piece of equipment used

Forward: where it went

  • Inventory transactions and picking
  • Order items and orders
  • Customers and deliveries
  • Invoices, with the elapsed time recorded

The lot code is written once, at harvest, and never changed. That single decision is what makes the answer fast and the answer complete.

THE FULL DOCUMENT · PDF

Get the full use-case specification.

The complete document, organised by module: every use case with its actors, preconditions, main flow, alternative flows, postconditions and the rules it enforces, plus the matrices a reviewer needs.

  • All 20 use cases with flow diagrams, alternative flows and postconditions
  • The persona and business-rule matrices, and the KPIs the system computes on its own
  • The gates, the lot code and the available-to-promise formula, explained in one page
Download the PDFBook a demo

From crop plan to invoice · 35 pages · 1.8 MB · no sign-up

Also read the textile manufacturing use case: One roll, from delivery to unit cost.