Information exists but is reconciled after downgrade, loss or service difficulty.
Agriculture & food guide
Manage campaign, batch, quality and value from field to customer
Choose the right tracking granularity to explain origin, yield, quality, loss, inventory and customer commitment.
For: Agriculture, livestock, food, packing, quality, commerce and IT leadersWhat to clarify before discussing a solution
When should a field event become a quality, packing, inventory or sales decision?
The answer does not lie in an isolated feature: it is built by connecting rules, actors, data and evidence.A proportionate data chain from field to sale, centred on decisions that protect quality and value.
Four decisions to make before configuration
These decisions make the scope testable and prevent structural choices from being discovered during the project.
Choose granularity by crop, cycle and stage
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Place controls before irreversible transformations
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Connect losses and downgrades to their cause
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Align available inventory and commercial commitments
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
A readable end-to-end flow
Scope is not a list of modules. It is a chain of events, ownership and decisions.
1Campaign and resource
2Field intervention
3Harvest and batch
4Quality and packing
5Inventory, sales and service
In the first scoping
- One representative flow and its useful variants
- Authoritative events and minimum data
- Roles, decisions and escalation times
- Acceptance criteria and baseline measurement
To sequence in waves
- Additional sites, activities or populations
- Rare variants that do not condition the pilot
- Automations whose rule is not yet stable
- Advanced dashboards after source reliability
To decide explicitly
- Choose granularity by crop, cycle and stage
- Place controls before irreversible transformations
- Connect losses and downgrades to their cause
- Align available inventory and commercial commitments
From direction to measured improvement
- 1Navigator
- 2Personalised review
- 3Scoping workshop
- 4Wave-based deployment
- 5KPI measurement
Each stage produces a decision or evidence reusable in the next. Deployment remains business-led and verifiable.
Measure to decide, not to fill a dashboard
Every KPI needs a definition, a source, a cadence and an associated decision.
KPIFormulaSourceDecision
Traceability completenessBatches with usable genealogy ÷ batches checkedBatches, movements, transformations and evidenceClose chain breaks and clarify evidence
YieldConforming output ÷ input committedInputs, outputs, losses and qualityAddress losses by stage and batch
Losses and downgradesLost or downgraded quantity ÷ harvested quantityHarvest, sorting, quality, storage and packingIdentify where value is lost
Service rateDemand served to commitment ÷ total demandDemand, commitments and actualsAlign priority, capacity and promise
06 · Business scenario
A batch tracked because a decision depends on it
- Situation
- The chain collects data across several media but cannot quickly explain the gap between expected yield and delivered value.
- Approach
- The pilot follows one product and campaign, connects interventions, quality, transformations, loss and service, then limits data entry to what is necessary.
- Target outcome
- Sorting, packing, inventory and sales decisions rely on usable genealogy.
Useful answers before the first discussion
01Where should we start in practical terms?
Choose a representative scope spanning “Campaign and resource” and “Field intervention”, then document one normal case and one frequent exception. The first flow should be important enough to matter but contained enough to observe end to end.
02Do all existing systems need replacing?
No. Scoping starts with decisions, authoritative events and ownership. It then determines what should be retained, integrated, replaced or simply better governed, wave by wave.
03What data should be prepared before a workshop?
Prepare a few real cases, the volumes shaping the operation, the main variance reasons and the sources used to measure Traceability completeness. The quality of examples matters more than the quantity of documents.
04How should the right pilot scope be chosen?
Choose a scope with an available owner, accessible data, a meaningful exception and a measurable outcome. Avoid both an overly simple case that proves nothing and an overly broad scope that dilutes learning.
05How can scope changes during the project be limited?
Make assumptions, interfaces, variants, exceptions and acceptance criteria explicit. Every new request can then be classified: essential to the wave, suitable for a later wave, or outside the objective. Discussion focuses on impact rather than intuition.
Next step
Turn this guide into a personalised review
Complete Navigator to position your context, then use the review as the starting point for a scoping workshop.
- 1Navigator
- 2Personalised review
- 3Scoping workshop
- 4Wave-based deployment
- 5KPI measurement
Complementary guides
Guides by suite
EMS Logistics suite
Transform transport & logistics
Connect order, warehouse, transport, delivery and invoicing around the same events and responsibilities.
- Service promise
- Warehouse execution
- Transport plan
Guides by suite
EMS Industry suite
Connect planning to the shop floor
Build decision continuity across demand, materials, capacity, execution, quality, maintenance and cost.
- Demand and schedule
- Materials and capacity
- Execution and WIP
Guides by suite
EMS Commerce suite
Unify omnichannel commerce
Connect catalogue, availability, order, payment, fulfilment, delivery, return and customer relationship.
- Catalogue and pricing
- Available-to-promise inventory
- Order and allocation