Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Agri Supply Chain
- Survey tools
- Field data collection
- Input purchasing and accounting
- Buyer and transport systems
Agri Supply Chain connects agricultural input lots and field work to a crop cycle and its reviewed harvest quantities. Farm Manager maintains the field register, plans crop cycles and approves work for assigned Field Operators.
Crop cycles in one list
Farm Manager approves the field task after checking its operating context and assigned person.
Every feature works on the same records. Pick one to see the screen your team works in.
Identify each field, review its availability and retain the surveyed boundary evidence used in planning.
Field boundaries
| Id | Field | Survey date | Area hectares | Geo JSON | |
|---|---|---|---|---|---|
| CC-2026-014 | South barley field | 11 Oct | 560 | north-ridge-boundary.geojson | |
| FT-2026-082 | Garden block C | 23 Oct | 680 | creekside-plot-boundary.geojson | |
| IS-2026-031 | Lower terrace plot | 20 Oct | 640 | east-bench-boundary.geojson | |
| IA-2026-046 | North ridge field | 14 Oct | 850 | south-field-boundary.geojson | |
| AE-2026-012 | Lower terrace plot | 16 Oct | 750 | lower-terrace-boundary.geojson |
Follow the crop and variety on each field from planning through planting, harvest and the closing review.
Approval waits for the farm manager
| Id | Field | Cycle | Task type | Assigned to | Due date | |
|---|---|---|---|---|---|---|
| CC-2026-014 | North ridge field | Sweet corn, east bench 2026 | Planting | Amara Okafor | 26 Oct | |
| FT-2026-082 | Creekside tomato plot | Spring wheat, north ridge 2026 | Irrigation | Sofia Petrov | 01 Nov | |
| IS-2026-031 | South barley field | Pumpkin, orchard edge 2026 | Feeding | Sofia Petrov | 13 Oct | |
| IA-2026-046 | Garden block C | Roma tomato, creek plot 2026 | Inspection | Priya Nair | 01 Nov | |
| AE-2026-012 | Garden block C | Spring wheat, north ridge 2026 | Harvest | Mateo Silva | 29 Oct |
Assign work to a named team member and review the field, crop cycle and inputs before execution.
Field tasks
| Id | Field | Cycle | Task type | Due date | Completed at | |
|---|---|---|---|---|---|---|
| CC-2026-014 | Lower terrace plot | Sweet corn, east bench 2026 | Planting | 24 Oct | ||
| FT-2026-082 | Orchard edge plot | Winter barley, south field 2026 | Irrigation | 21 Oct | ||
| IS-2026-031 | South barley field | Red onion, lower terrace 2026 | Feeding | 21 Oct | ||
| IA-2026-046 | South barley field | Spring wheat, north ridge 2026 | Inspection | 23 Oct | 23 Oct | |
| AE-2026-012 | South barley field | Red onion, lower terrace 2026 | Harvest | 17 Oct |
Review agricultural input lots and follow the quantity consumed by each approved field task.
Input stocks
| Id | Input name | Lot number | Unit | Quantity on hand | Expiry date | |
|---|---|---|---|---|---|---|
| CC-2026-014 | Granular lime, lot GL-41 | L26-7092 | kg | 900 | 18 Oct | |
| FT-2026-082 | Organic compost, lot OC-18 | L26-6931 | liters | 760 | 27 Oct | |
| IS-2026-031 | Wheat seed, lot WS-26 | L26-1691 | tonnes | 750 | 24 Oct | |
| IA-2026-046 | Drip tape, 16 mm roll | L26-0306 | hectares | 930 | 25 Oct | |
| AE-2026-012 | Potassium blend, lot PB-12 | L26-2394 | bags | 370 | 30 Oct |
Keep dated scouting observations and named input applications available for the field review.
Agronomy evidence
| Id | Field | Observed at | Evidence type | Measured value | Unit | |
|---|---|---|---|---|---|---|
| CC-2026-014 | Creekside tomato plot | 17 Oct | Soil test | 730 | kg | |
| FT-2026-082 | Creekside tomato plot | 18 Oct | Application log | 870 | liters | |
| IS-2026-031 | Lower terrace plot | 21 Oct | Field photograph | 30 | tonnes | |
| IA-2026-046 | Garden block C | 13 Oct | Harvest weigh ticket | 830 | hectares | |
| AE-2026-012 | Dryland west field | 22 Oct | Irrigation record | 350 | bags |
Review the actual harvested quantity, unit and grade against the correct crop cycle before acceptance.
Crop deliveries
| Id | Cycle | Harvested at | Quantity | Unit | Quality grade | |
|---|---|---|---|---|---|---|
| CC-2026-014 | Red onion, lower terrace 2026 | 11 Oct | 770 | kg | Grade A milling wheat | |
| FT-2026-082 | Roma tomato, creek plot 2026 | 15 Oct | 690 | liters | Grade B milling wheat | |
| IS-2026-031 | Leaf lettuce, garden block 2026 | 12 Oct | 750 | tonnes | Fresh market No. 1 | |
| IA-2026-046 | Spring wheat, north ridge 2026 | 13 Oct | 70 | hectares | Processing grade tomato | |
| AE-2026-012 | Chickpea, dryland west 2026 | 21 Oct | 290 | bags | Premium sweet corn |
From field preparation to accepted harvest ships ready to use. 2 steps need a named approval before the work moves on: Work approval (Farm Manager) and Harvest acceptance (Harvest Reviewer).
Confirm the field identity, surveyed evidence and availability before planning the crop.
Set the crop and variety, then attach the planned work to the correct field and cycle.
Review the field, cycle and assigned operator before authorizing the task.
Check the selected lot and record the quantity consumed by the approved work.
Review the actual harvested quantity with its unit, grade and crop cycle.
Review accepted deliveries and outstanding work before closing the crop cycle.
Open any crop cycle to see its crop deliveries, the roles that work on it, its process stages and its approvals on one page.
Crop name, Variety, Field and Planted at.
Each line is linked to this crop cycle.
Admin, Farm Manager and Field Operator, each with their own permissions.
Cycle planning and Harvest acceptance, with the role that acts.
Work approval and Harvest acceptance, with who decides.
Spring wheat, north ridge 2026 · Planned
| Id | Cycle | Harvested at |
|---|---|---|
| CC-2026-014 | Red onion, lower terrace 2026 | 11 Oct |
| FT-2026-082 | Roma tomato, creek plot 2026 | 15 Oct |
| IS-2026-031 | Leaf lettuce, garden block 2026 | 12 Oct |
Farm Manager approves field tasks after reviewing the field, cycle and assigned person. Field Operator carries out the authorized work through the agreed execution path.
Signed in as Farm Manager
| Decision | Approver | |
|---|---|---|
| Work approvalReview the field, cycle and assigned operator before authorizing the task. | Farm Manager | |
| Harvest acceptanceReview the actual harvested quantity with its unit, grade and crop cycle. | Harvest Reviewer | |
| Approve field tasks | Farm Manager | |
| Approve crop deliveries | Harvest Reviewer |
Everyone opens Agri Supply Chain to the work that is theirs. Pick a role to see what it starts with.
Maintains authenticated team identities and configures access for the agricultural operating cycle.
Owns the field register and crop plan and approves assigned field work.
This is the first screen this role sees.
Crop cycles · Farm Manager
Carries out assigned field tasks and records applications and input-use evidence for that work.
This is the first screen this role sees.
Crop cycles · Field Operator
Maintains agricultural input lots and reconciles their quantities with recorded task usage.
This is the first screen this role sees.
Field tasks · Stock Controller
Records field scouting observations and reviews application evidence with the crop team.
This is the first screen this role sees.
Crop cycles · Agronomist
Captures surveyed field boundary evidence for review alongside the field register.
This is the first screen this role sees.
Fields · Field Surveyor
Checks harvested quantities and their cycle references before accepting delivery records.
This is the first screen this role sees.
Crop cycles · Harvest Reviewer
Review field availability, unfinished work, input use and accepted harvest with their underlying records.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Planned | 48 | ||
| Planted | 17 | 35% | |
| Growing | 3 | 18% | |
| Harvesting | 1 | 33% |
Sample counts per stage
Which fields are available, planted, fallow or restricted, and what area does each state represent?
Where is each cycle in its growing stage, and what does the harvest outlook show?
Which tasks need approval or completion, and who is assigned to them?
Which stock quantities remain on hand, and which expiry dates need attention?
Which lots supplied the work on each crop cycle?
What was observed on a field, in which unit and on what date?
What input was applied, by whom and in what quantity?
Which quantities and grades were accepted for the crop cycle?
See how Agri Supply Chain fits your kind of team.
Coordinate planting work, input lots and harvest review across named fields and crop cycles.
Review crop variety, repeated field activity and graded harvest quantities within each growing cycle.
Keep field identity and operator responsibility clear when agricultural work spans several plots.
Each stage, from field preparation to accepted harvest, names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to prepare field, stock and harvest reviews from the records your account can access.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 11 tablesStart with one team and one process, then add the rest once the basics are running.
Farm Manager selects a plot and current crop cycle with work the team understands. Review field code, area and availability before importing related activity.
Admin links operators and reviewers to their actual user accounts. Agree who plans, approves, executes and accepts the work.
Stock Controller checks opening quantity, unit and expiry for the lot used in the pilot. Define how the work request selects that lot and quantity.
Follow a Planned task through Farm Manager’s approval and Field Operator’s execution. Inspect the resulting usage and remaining stock together, including a repeated request.
Record an application and a scouting observation with clear units. Check that their field and dates support the intended operating discussion.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Agri Supply Chain for your business. Begin with a familiar field, its current crop cycle and an input-consuming task. Rehearse work approval and harvest acceptance with the people responsible for those decisions.
It identifies the field, crop and variety with the current stage. Planting, expected harvest and actual harvest dates support the chronological review, with delivery evidence available in Crop Cycles.
Farm Manager assigns the task to a team member and sets its due date. The team member links to an authenticated account so the operator can follow their assigned work and the execution can identify the person correctly.
Farm Manager reviews the field, crop cycle and assigned person before approving the task. Agree the allowed operating states and input checks during setup.
Task input usage links the consumed quantity to its stock lot and field task. Review the lot's unit, expiry and available quantity before execution, then reconcile usage with the remaining balance.
They answer different questions. An application records the input name, quantity and applicator on a field. Task usage connects consumption to a specific stock lot and task. Agree how the team records each without counting the same event twice.
Harvest Reviewer checks the current delivery against its crop cycle and recorded harvest date. The quantity must be a number of zero or more, with its unit and grade. Acceptance records the signed-in reviewer through their linked team record.
Accepted quantities come from the harvest delivery record. Scouting measurements and notes remain field evidence for planning and review, with their own dates and units.
The boundary record links geometry, survey date and area to a field. Field Surveyor and Farm Manager review any area difference before relying on it in the plan.
Farm Manager reviews accepted deliveries and outstanding work, records the actual harvest date using the agreed convention, then marks the cycle Closed. The field's next availability state is reviewed for the next plan.
Start free, then use Proto to change fields, steps and approvals before your team goes live.