1. Agriculture ERP
  2. Features
  3. Input lots and usage
Feature · Input lots and usage

Input lots and usage

Check an input lot's unit, expiry and remaining quantity before posting field use.

OverviewAvailable Input Lots
Agriculture ERP · Input lots and usage

Available Input Lots

Input stocks

New
IdInput nameLot numberUnitQuantity on handExpiry date
IDD-437Input 890L26-8620UNT-17726015 Oct
IDD-255Input 491L26-1292UNT-94121023 Oct
IDD-270Input 895L26-0874UNT-77043013 Oct
IDD-210Input 348L26-9459UNT-29987012 Oct
IDD-301Input 718L26-3134UNT-46292017 Oct
6 of 6 records
IDD-437Input stocks · IS-18136
Input nameInput 890
Lot numberL26-8620
UnitUNT-177
Quantity on hand260
Expiry date15 Oct
Example screen with sample data

What you can do

Keep an application connected to its input lot

Input stock records keep the input name, lot number, unit, quantity on hand and expiry date together. An application records the actual quantity and applied date against the field task and exact lot. Those links let the team follow a field application back to both the instruction and the stock it consumed.

The field-work command checks every submitted lot before writing. Resolve a missing lot, incompatible unit, expiry problem or insufficient quantity before execution. Once the request passes, the command posts usage and reduces stock once per lot. Farm Manager checks the lot number and unit alongside its name when reviewing the remaining quantity.

How the work is organized

  • Lot information. Farm Manager maintains the lot identity and recorded balance. Agree the unit before operators enter applications. Confirm the opening quantity from the farm’s reviewed stock position and resolve unclear lot labels before they appear in assigned work.
  • Application evidence. Field Operator submits the actual quantity and applied date through task execution. Each usage record retains the task and input references. Follow the task to the field and crop cycle when reviewing where the material was applied.
  • Guarded deduction. Check every submitted lot before any write. The workflow deducts stock once per lot and returns the original saved result on a repeat. Include requests using the same lot more than once in the setup rehearsal and compare the saved usage with the balance.

What to agree during setup

Agree the lot naming convention and opening quantity from a physical stock review. Decide how staff enter units and who checks uncertain expiry information. Rehearse the unit and expiry rules with actual lot examples so operators know which issue to take back to Farm Manager after a refusal.

Name the person who resolves a stock discrepancy before an operator retries. Document how Farm Manager reviews and maintains the lot information. Keep the original application linked to its task when investigating a balance. Agree how a corrected measurement or mistaken lot selection will be handled separately from repeating the original execution request.

Check the handoff on an actual case

For a rehearsal, prepare a fertilizer lot with 100 kilograms on hand and an approved Feeding task. The assigned Field Operator records an application of 20 kilograms. Follow the saved usage to the correct task and input lot, then check that the recorded balance is 80 kilograms and the task carries the actual applied date.

Repeat the execution and confirm that the saved result and balance stay unchanged. Next include an expired lot alongside a valid lot in a request. Refusal should preserve every lot, usage record and task. Rehearse an application above the available balance and a mismatched unit as separate cases. Farm Manager reviews the unchanged records and agrees how the lot issue will be resolved before another attempt.

What your team sees

  • Available Input Lots — Positive recorded quantities by input, lot and unit for application planning.
  • Expiring Input Lots — Lots expiring within the review window or already expired for manager follow-up.
  • Input Application Log — Actual applications with their task, lot and applied date.

Follow the work through

Use approved field work for execution, and yield evidence to season review when reviewing the crop’s outcomes.

What it keeps track of

Data model
Input stocks
Agricultural input lots with quantity on hand and expiry
Input usage
Input quantities applied against a field task
Field tasks
Assigned field work with lifecycle status and completion date
Fields
Farm fields and plots with area and operational status
Crop cycles
Crop cycles planted on a field from planning through closure

Who uses it

Permissions
Farm Manager
Maintains input stock and resolves lot information.
Field Operator
Records usage through approved field work.
Admin
Configures the agreed read access and rehearses command access with the operator.

Set up Agriculture ERP your way.

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

How to get started