UC-435
Input Traceability & Residue Limits
Holds every input applied to every field, checks pre-harvest intervals and residue limits per market, and clears each load for despatch.
TBDBuild Duration
XXXXIndicative ROI
XXXXBuild Cost
XXXXValue
The Challenge
A load is rejected at the packhouse because one spray fell inside the pre-harvest interval for that market. It persists because application records, residue rules and harvest plans sit in unlinked systems.
How It Works
- Reads application records, product labels, harvest plans and destination residue rule sets.
- Checks each field's input history against pre-harvest intervals and per-market residue limits.
- Clears or holds each harvest load at despatch and issues the traceability sheet with it.
What It Removes
- Manual cross-checking of spray dates against harvest
- Rebuilding input history for each buyer audit
- Chasing contractors for missing application sheets
Input Data RequirementsSpray and fertiliser application records, product label data, contractor job sheets, harvest and despatch plans, market residue rule sets
Output FormatA clear or hold decision per harvest load, a traceability sheet per consignment, and a register of fields still inside a pre-harvest interval
“One rejected load costs more than the whole spray programme and we find out at the buyer's gate”