1. Plantation Management
  2. Features
  3. Input lots and usage
Feature · Input lots and usage

Input lots and usage

Relate applied field quantities to the input lot that supplied them.

OverviewInput Stocks Register
Plantation Management · Input lots and usage

Input Stocks Register

Input stocks

New
Input nameLot numberUnitQuantity on handExpiry date
Input 804L26-9079UNT-52545008 Oct
Input 780L26-5956UNT-52364005 Oct
Input 768L26-9408UNT-70092015 Oct
Input 637L26-0176UNT-29620010 Oct
Input 220L26-4008UNT-57030008 Oct
6 of 6 records
Input 804Input stocks · IS-24772
Lot numberL26-9079
UnitUNT-525
Quantity on hand450
Expiry date08 Oct
Example screen with sample data

What you can do

Keep the lot visible at application

Input stock records identify an agricultural input by name, lot number, unit, quantity on hand and expiry date. The stores clerk uses those details to distinguish one lot from another even when the input name is the same. An input usage entry records the quantity and application date and links back to both the field task and the input stock lot. The lot number and unit are visible on the usage record for review.

This connection lets a manager start with a completed field task and find the lot used for it. The stock record also exposes usage count and total issued quantity, while the task exposes input usage count and total input quantity. Those totals are useful for reconciliation only when staff use consistent units and record each actual application once. A field supervisor and stores clerk should review differences before treating the balance as a purchasing signal.

How the work is organized

  • Lot register. Stores Clerk enters the input name, lot number, unit, balance and expiry date for each stock lot.
  • Application. Field Operator executes an approved task; an eligible lot with the earliest expiry supplies the recorded quantity and date.
  • Reconciliation. Stores Clerk compares usage entries, issued quantity and stock on hand with physical stock.

What to agree during setup

Decide whether an input lot number is unique across locations and which unit the plantation uses for each input. Agree how a partial container is measured and how a physical stock correction is approved. Set the review interval for lots approaching expiry; expiry dates should inform selection before application. Decide who can edit an application after a task is complete and how the team documents a correction. Keep the task’s input quantity aligned with the usage rows that describe actual applications.

Check the handoff on an actual case

A feeding task for North Ridge calls for a measured quantity of an input held in two lots. Check both lot numbers, their expiry dates and balances before executing the approved task against the first-expiry eligible lot. The usage entry should point to the feeding task and the exact lot, show the applied date and retain the unit. The stores clerk then compares the task’s input total with usage and the stock lot’s issued quantity. An expired or insufficient lot must be skipped; if no eligible lot can supply the quantity, the task remains open. Later, the manager can trace that field task back to the source lot without guessing from a product name.

What your team sees

  • Input Stocks Register — Review lots, quantities on hand and expiry dates.
  • Input Usage Log — Trace applied quantity and date to task and stock lot.
  • Open Field Tasks — Find work waiting for an application record or completion.

Follow the work through

What it keeps track of

Data model
Input stocks
Agricultural input inventory lots with quantity on hand and expiry.
Input usage
Input quantities applied against field tasks, with lot traceability.
Field tasks
Scheduled and executed field work assigned to plantation staff.
Crop cycles
Crop cycles planted on a field, from planning through harvest closure.
Fields
Registered plantation fields with area, location and operational status.

Who uses it

Permissions
Stores Clerk
, Field Operator and Plantation Manager.

Set up Plantation Management your way.

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

How to get started