Registering a new local group on PGS India, then adding its farmers, is a two-stage process on pgsindia-ncof.gov.in. The group must exist and be approved before any farmer can be attached to it. Most Regional Councils lose time because farmer records are prepared before the group is live, or because location fields do not match the portal's own lists.
This article sets out what a Regional Council needs for each stage, the field rules the portal enforces, and the specific errors that cause farmer records to be rejected.
Stage One: Registering the Local Group
A local group is the unit a Regional Council certifies. Before registration, confirm three things:
- Minimum membership. The group must have enough farmers to function as a peer appraisal body. Members appraise each other, so a group too small cannot run a valid appraisal.
- A named contact. One member acts as group leader and is the point of contact for the Regional Council. This is set on the portal and can be changed later.
- A single revenue location. Groups spanning several sub-districts create problems at appraisal time, because inspection visits and village lists are organised by sub-district.
Register the group first and wait for it to appear in your Regional Council's group list. Only then prepare farmer data. Farmer records prepared against a group ID that does not yet exist cannot be submitted.
Stage Two: Farmer Registration Field Rules
The portal validates several fields strictly and rejects the whole record if any fail. These are the rules worth checking before submission rather than after.
| Field | Rule | Common failure |
|---|---|---|
| Aadhaar number | Exactly 12 digits | Spaces, hyphens, or a leading apostrophe added by Excel |
| Mobile number | Exactly 10 digits, starting 6, 7, 8 or 9 | +91 prefix or a leading zero left in place |
| Pincode | Exactly 6 digits | Excel stripping a leading zero |
| Total area | Positive number | Blank, or zero entered for landless members |
| Area offered for organic | Positive, not exceeding total area | Sum of plots exceeding the declared total |
Excel causes more of these failures than data entry does. A column formatted as Number will drop the leading zero from a pincode and may convert a 12-digit Aadhaar to scientific notation. Format these columns as Text before entering anything.
The area offered for organic certification can never exceed the farmer's declared total area. Where several plots are listed, their combined area is checked against the total, not each plot individually.
Why Location Fields Cause Most Rejections
Location is not free text. The portal holds its own list of states, districts, sub-districts, blocks and villages, and each level is loaded from the level above it. Your entry must match the portal's spelling exactly.
The dependency chain is not what most people assume:
- District is loaded from the selected State
- Sub-district is loaded from the selected District
- Block is loaded from the selected District — not from the sub-district
- Village is loaded from the selected Sub-district — not from the block
That asymmetry matters. A valid block and a valid village can belong to the same district yet fail together, because the village is checked against the sub-district you selected rather than against the block.
Village names are the single most common rejection. Portal spellings often differ from local usage, including hyphenation and transliteration: a village recorded locally as Vadwala Rana may exist on the portal only as Vadwala-Rana. The record is rejected outright, not corrected.
Reducing location failures
- Pull the portal's village list for your sub-district once, and use it as the reference for every submission from that area.
- Keep a mapping of local spellings to portal spellings. The same corrections recur across batches.
- Where a village genuinely does not appear, check whether it is listed under a neighbouring sub-district before raising it with the Regional Council.
Preparing a Batch That Submits Cleanly
Regional Councils registering fifty or more farmers at a time gain most from validating before submission rather than correcting afterwards. A rejected record in a large batch is slow to find and slower to resubmit.
A practical sequence:
- Confirm the group is live on the portal and note its identifier.
- Format Aadhaar, mobile and pincode columns as Text in the spreadsheet before entry.
- Check every location against the portal's own lists, sub-district by sub-district.
- Verify plot areas sum correctly against each farmer's declared total.
- Submit, then reconcile the count registered against the count sent. A silent shortfall usually means rejected records, not a display delay.
Keep the submitted spreadsheet. At peer appraisal and again at renewal, the Regional Council needs the same farmer and plot data, and re-keying it is where inconsistencies enter the record.
Most farmer registration failures are not judgement calls. They are format rules and location lists that can be checked before submission. Confirm the group exists, format the numeric columns as text, and validate locations against the portal's own lists for the correct sub-district.
KrushiFlow validates these fields before anything reaches the portal, resolves village names against the portal's lists, and submits farmer records in bulk for PGS India and APEDA Tracenet. Where a village cannot be matched, it reports the closest portal spelling rather than failing silently.