Supply Chain & Post-Harvest
Traceability & Provenance
One step back, one step forward, and a recall you can actually execute.
Traceability is a legal requirement and a commercial asset. This module maintains lot-level records forward and backward through every process step, supports a timed recall exercise that actually works, and turns the same underlying data into consumer-facing provenance that is substantiated rather than asserted.
- 12 capabilities
- 2 linked schemes
- Offline capable
- 12
- Capabilities in this module
- 5
- Interactive tools
- 2
- Linked support schemes
- 5
- Data integrations
- 5
- Measures reported
The ground reality
What is actually happening in traceability in the UK
Food law requires businesses to identify their immediate suppliers and immediate customers, and to withdraw or recall unsafe food. Beyond the legal minimum, supply chain customers increasingly require lot-level traceability with carbon and assurance attributes attached, and deforestation-related due diligence applies to defined regulated commodities.
Figures are as published at the time of writing. Farm policy and payment rates change frequently — verify against the primary source before relying on any number here.
Capabilities
What Traceability does
Every capability below is built on the same underlying record, so entering something once is enough for it to appear wherever it is needed.
Record and plan
- Lot creation and splitting through every process step
- One-step-back and one-step-forward supplier and customer linkage
- Field-to-pack traceability using the platform production record
Operate and monitor
- Batch and lot coding with label generation
- Mock recall exercise with timing and completeness measurement
- Real recall execution with affected lot identification and notification
Comply and evidence
- Consumer-facing provenance pages generated from verified records
- QR and code-based provenance access at pack level
- Deforestation and land conversion due diligence records for regulated commodities
Analyse and improve
- Carbon and assurance attribute carriage through the chain
- Supplier approval and specification records
- Chain of custody for certified and segregated products
Interactive
Tools you actually use, not screens you read
These are working interfaces inside the module — maps, calculators, planners and dashboards that respond to your own holding data.
Traceability tree showing every input and every output for a chosen lot
Traceability tree showing every input and every output for a chosen lot
ToolMock recall simulator reporting time to identify and completeness
Mock recall simulator reporting time to identify and completeness
ToolProvenance page preview as the consumer will see it
Provenance page preview as the consumer will see it
ToolChain of custody map for certified product
Chain of custody map for certified product
MapAttribute carriage viewer showing which claims survive each process step
Attribute carriage viewer showing which claims survive each process step
ToolEnd to end
How Traceability runs, start to finish
The module is modelled as a state machine, so at any point the business knows exactly which stage every record is at and what has to happen next.
-
1
Define lots at every process step
This is where the record starts, and getting it right here removes work at every later stage.
-
2
Record inputs and outputs against each lot
The platform prompts only for what this stage genuinely needs, and carries everything forward.
-
3
Code and label with the lot identity
Conflicts with scheme rules, regulatory windows and existing commitments are flagged here rather than discovered later.
-
4
Link suppliers and customers one step each way
Capture works offline, so this stage is completed in the field rather than remembered afterwards.
-
5
Carry attributes through processing
Everything recorded at this point becomes evidence automatically, in every format that will later ask for it.
-
6
Publish provenance to the consumer
This is the stage most businesses currently do twice, once for the operation and once for the paperwork.
-
7
Run mock recalls on a schedule
Results feed the whole-farm view, so the effect of this stage is visible against the rest of the business.
-
8
Execute a real recall if required
The cycle closes here, and what is learned is carried into next season's plan rather than lost.
Who uses it
Built around four real jobs, not one generic user
Each of these people needs something different from the same record. The module is designed so none of them has to work around the others.
Food business operator
Processing and packing
Needs a recall exercise that completes inside the target time.
Producer
Supplying a branded chain
Needs provenance claims backed by the production record.
Retail technical manager
Supply chain assurance
Needs lot-level traceability on demand.
Enforcement officer
Food safety
Needs immediate supplier and customer records without delay.
Schemes and funding
Support schemes this module works with
Agrivencia holds these schemes as data, so eligibility, payment rates, caps and windows update the day they change rather than at the next software release.
Adding Value Grant
Support investment in processing, packing and marketing that adds value to primary agricultural products.
Defra / Rural Payments Agency EnglandFarming Transformation Fund
Fund larger capital projects that transform farm productivity, water management or value addition.
Defra / Rural Payments AgencyRates, caps and windows change frequently and sometimes without notice. Always confirm against the current published scheme rules before applying.
Measurement
How you will know it is working
The module reports against these measures from the day it is switched on, so the value is demonstrable rather than assumed.
- 01Mock recall completion time
- 02Recall completeness percentage
- 03Lots with full linkage
- 04Provenance page engagement
- 05Attribute claims substantiated
Questions answered
What people ask about Traceability
Does this replace the software I already use?
Not necessarily. Agrivencia integrates with authoritative sources and mainstream packages rather than insisting on replacing them. Where an incumbent does one job well, the platform connects to it; where the job spans several systems and nobody does it, the platform does it.
Will it work where I have no signal?
Yes. Field capture in Traceability is offline first, storing locally and synchronising when a connection returns. Only around a fifth of UK farms report reliable signal across the whole holding, so this is a design assumption rather than a feature.
What happens when the scheme rules change?
Scheme rules are held as data rather than code, so a rate change, a cap change or a window closure is a content update that takes effect the same day. The platform also alerts you to what the change does to your own position.
Who owns the data I put in?
You do. The Farm Data Charter gives you a complete export in open formats at any time, and every instance of data sharing requires an explicit, revocable consent that is visible in your account.
Does it work if I farm across a border?
Yes, and that is one of the main reasons the platform exists. A business with land in more than one nation sees one reconciled view rather than two portals, with obligations and deadlines from both administrations in a single calendar.
Can my agronomist or land agent use it too?
Yes. You grant scoped, time-limited access per holding and per module, and you can revoke it in one click. Advisers never get a shared password or a blanket view.
What is the biggest limitation of this module?
Broken linkage at a process step. Mitigated by mandatory lot capture. We would rather state that plainly than let you discover it after signing.
See Traceability running on your own holding
Thirty minutes, using your parcels, your schemes and your enterprises rather than a sample farm. No obligation and no sales script — if it does not fit your business we will say so.
- Free tier available
- No card required
- Your data stays yours