1. Agri Supply Chain
  2. Features
  3. Input Stocks and Usage
Feature · Input Stocks and Usage

Input Stocks and Usage

Review agricultural input lots and follow the quantity consumed by each approved field task.

OverviewInput Lot Position
Agri Supply Chain · Input Stocks and Usage

Input Lot Position

Input stocks

New
IdInput nameLot numberUnitQuantity on handExpiry date
IDD-489Input 208L26-7092UNT-42790010 Oct
IDD-206Input 881L26-6931UNT-22976019 Oct
IDD-533Input 541L26-1691UNT-31775016 Oct
IDD-239Input 574L26-0306UNT-31893017 Oct
IDD-641Input 648L26-2394UNT-89037022 Oct
6 of 6 records
IDD-489Input stocks · IS-49836
Input nameInput 208
Lot numberL26-7092
UnitUNT-427
Quantity on hand900
Expiry date10 Oct
Example screen with sample data

What you can do

Follow the lot into the work

Stock Controller maintains the input name and lot number with its unit, quantity on hand and expiry date. These details matter when Farm Manager approves work that will consume an agricultural input. The selected lot needs to exist, remain within its expiry and hold enough stock in the matching unit before execution proceeds.

The resulting usage record connects a quantity to the input lot and the field task. Follow the task to its field and crop cycle when reviewing where the input was used. Keep that connection intact when several fields use the same product or the store holds different lots of it.

How the work is organized

  • Lot position. Review stock by input name and lot number. Quantity on hand has meaning only with its unit. Expiry review helps Stock Controller find lots that need attention before the next work approval.
  • Consumption evidence. Usage retains the selected input lot, task, quantity and application date. This gives the team a direct path from a stock deduction to the work that consumed it.
  • Execution checks. The work process checks available quantity and the matching unit before recording consumption. A repeated execution request needs review against the original usage so the same work does not consume the lot again.

What to agree during setup

Agree the units used for each input and how opening quantities will be checked. Keep distinct lot numbers when the same input arrives with different expiry dates. Decide who maintains stock records and who resolves an expired or insufficient lot before an approved task is carried out.

Define how the execution request selects the lot and quantity. Field Operator needs to understand which stock has been approved for the work. Agree how Stock Controller reconciles consumption against the remaining quantity and how a correction is handled if the original usage needs investigation. Keep the input application history separate when it records field activity without a stock-lot reference.

Check the handoff on an actual case

Use a practice lot holding 120 kilograms of an input. A feeding task requires 15 kilograms. Stock Controller checks the lot and expiry, and Farm Manager reviews the linked work. A successful execution records the usage against that task and leaves 105 kilograms on hand.

Repeat the approval message in the rehearsal. The same work should retain its original consumption result, with no further deduction. Then request more than the remaining quantity and check that the task cannot consume stock the lot does not hold.

Finally, send a request expressed in liters against the kilogram lot. Resolve the unit mismatch before execution. Do not combine unlike units when reviewing usage across fields. The operating report should keep the lot’s unit visible when it follows consumption through tasks to crop cycles.

What your team sees

  • Input Lot Position — Lots with stock on hand show their quantity, unit and expiry date.
  • Input Expiry Review — Expired lots remain visible for the next stock decision.
  • Task Input Usage — Recorded quantities link the consumed lot to the field task.

Follow the work through

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
Fields
Farm fields and plots with area, location and availability status
Crop cycles
Crop cycles per field from planned planting through growing, harvesting and close

Who uses it

Permissions
Stock Controller
Maintains and reconciles lots.
Farm Manager
Reviews the work decision.
Field Operator
Uses the selected input during assigned work.
Agronomist
Reviews usage in its field context.

Set up Agri Supply Chain your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started