When a farmer group sells both in India and abroad, the same farmer data must satisfy several sets of rules. This episode sets out the core data every standard needs, the extra requirements for export markets, and how to keep the data consistent.
The short version
- Build one core record per farmer that every standard draws on.
- Export markets add their own requirements: USDA certification, EU e-COI, GB COI.
- Keep Tracenet records identical to the physical records.
- Check export rules again before each season's contracts.
The Core Record
Identity, address, land, location, crops and land ownership, recorded once and used everywhere.
- Name, father's or husband's name, and gender, as on Aadhaar.
- Mobile number.
- Address with village, district, state and pin code.
- Survey numbers, area in hectares, and GPS location.
- Crops, with sowing and harvest periods.
- Land record or lease.
What Export Markets Add
Each market has its own rule; check the current position for the destination before contracting.
| Market | Requirement (checked 24 September 2026) |
|---|---|
| European Union | An e-COI in TRACES for every consignment; India's recognition covers unprocessed plant products only |
| United States | USDA organic certification as well as NPOP, and an NOP Import Certificate per shipment |
| United Kingdom | A GB certificate of inspection for every consignment |
Details are in exporting to the EU and exporting to the US, UK, Switzerland and Taiwan.
Keeping Data Consistent
One source of truth, a second-person check, fixed spellings, and a comparison with last season.
- One source of truth for farmer data; every form and portal is filled from it.
- A second person checks entries before submission.
- Fixed spellings for villages, crops and inputs.
- Compare with the previous season, and explain every change.
- Tracenet entries must match the physical records.
Illustrative workload. At about a minute per farmer to check spellings, 200 farmers take over 3 hours per cycle.
Check yourself
Tap an answer to see whether you are right, and why.
What does every organic consignment to the EU need?
- Nothing extra
- An e-COI in TRACES
- A USDA certificate
No e-COI, no release at the EU port.
Why keep one core record per farmer?
- It looks tidy
- So every standard uses the same, consistent data
- Tracenet requires it
Differences between records cause queries.
Remember these things
- One core record per farmer.
- Know each market's rule.
- Tracenet matches the physical records.
- Recheck export rules each season.
One consistent core record serves every standard a farmer needs. KrushiFlow validates these fields and submits farmer records to the portal in bulk.