These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Greenhouse Management
- Features
- Input stock and usage
Input stock and usage
Connect consumed input quantities to the work and lot they came from.
OverviewExpired input lots×
Greenhouse Management · Input stock and usage
New
Expired input lots
Input stocks
| Id | Input name | Lot number | Unit | Quantity on hand | Expiry date | |
|---|---|---|---|---|---|---|
| IDD-737 | Input 265 | L26-1107 | UNT-487 | 590 | 09 Oct | |
| IDD-689 | Input 757 | L26-1093 | UNT-748 | 630 | 10 Oct | |
| IDD-539 | Input 540 | L26-9156 | UNT-635 | 250 | 10 Oct | |
| IDD-706 | Input 523 | L26-0403 | UNT-211 | 70 | 11 Oct | |
| IDD-383 | Input 397 | L26-9824 | UNT-614 | 320 | 09 Oct |
6 of 6 records
IDD-737Input stocks · IS-47976
Input nameInput 265
Lot numberL26-1107
UnitUNT-487
Quantity on hand590
Expiry date09 Oct
What you can do
Keep the lot beside the task
Input stock records identify an agricultural input, its lot number, unit, quantity on hand and expiry date. Usage records carry a quantity and application date, linked to both an input lot and a field task. That link lets the stock controller answer which approved work consumed a lot and gives the manager a way to compare field work with remaining stock.
When a grower records feeding or another input-consuming activity, the task context matters. A quantity entered against the wrong task can make both the cycle history and the lot balance misleading. Work through the task first, then choose the specific lot used. The operating team should retain the same unit in the lot and use records rather than silently converting between measures.
How the work is organized
- Maintain lots. Record the input name, lot number, unit, on-hand quantity and expiry.
- Link use. Attach each applied quantity to a field task and the actual stock lot.
- Reconcile. Compare consumption against the available quantity before the next task uses the lot.
The approval of field work is an important checkpoint for input usage. The manager reviews the task, field and cycle; the stock controller checks lot identity, expiry and quantity. A dated usage record then becomes evidence of consumption against that task.
What to agree during setup
Decide how units are written and who may correct a lot’s on-hand quantity. Agree how operators identify the lot at the point of application, especially if the same input name appears on several stock rows. Define whether use is recorded at the time of application or during an end-of-day review. Both approaches need the actual applied date and task link.
The team should also decide how to handle a partially used lot near expiry. The stock controller can view lots by expiry date, but a date on a record is not a substitute for physical stock checks. Reconcile imported starting quantities before opening input use to the team.
Check the handoff on an actual case
A manager approves a feeding task for a growing crop cycle. The stock controller finds a lot with the expected input name and a usable expiry date, then confirms that the planned quantity fits the recorded balance in the same unit. After application, the grower gives the controller the task and lot used. The controller records the input use with the applied date and quantity and checks the remaining stock. A manager can later follow the task back to the cycle and field.
Rehearse a second application that would exceed the remaining lot quantity. The controller should resolve the stock discrepancy or select a different verified lot before recording consumption. Keep the first application’s task and lot link intact so the history remains understandable.
What your team sees
- Expired input lots — Check lots whose expiry date has arrived before another use.
- Approved and active field work — Locate work that may need an input record.
- Field work board — Find the assigned task behind an application.
Follow the work through
See field work for the task checkpoint and implementation for a first lot reconciliation.
What it keeps track of
Data model- Input stocks
- Agricultural input stock lots with quantity on hand, unit and expiry
- Input usage
- Input quantities consumed against a field task
- Field tasks
- Planned and executed field work assigned to a person for a specific cycle
- Crop cycles
- Crop cycles per field from planned planting through growing, harvesting and close
- Fields
- Farm fields and plots with area, location and availability status
Who uses it
Permissions- Stock Controller
- Owns lot and use records, Greenhouse Manager approves the work, and Grower identifies what was applied.
- Admin
- Maintains access.
Set up Greenhouse Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.