'Village not found' stops farmer registration on the PGS-India portal. It means the name or code you entered doesn't match the portal's database. This guide covers the causes, the resolution path and when to escalate.
The short version
- It is a mismatch, not a missing farmer.
- Check the land record and Aadhaar for the exact name.
- Search district and block first, then the village.
- Escalate to the Regional Council with a list of affected farmers.
Understanding 'Village Not Found' Errors on PGS India
The village name or code doesn't match the portal's database — usually spelling, transliteration or a renamed village.
The 'Village Not Found' error on the pgsindia-ncof.gov.in portal indicates a mismatch: the village name or code entered does not correspond with the portal's existing database. This is a common challenge for groups managing PKVY farmer registration issues.
Common Causes of Mismatch
- Data Mismatch: The village name in physical land records differs from the portal's entry. This often occurs due to spelling variations or regional language transliterations.
- Incorrect Spelling: Even minor spelling errors prevent the system from recognizing the village. The portal requires exact matches.
- Outdated Codes: Administrative reorganizations or village mergers can render older village codes invalid. This is a frequent cause of the PGS India village not found error.
The Resolution Path
Follow the path: physical records, then portal search by district and block, then alternative spellings, then escalation.
Addressing these errors requires a systematic approach — cross-reference multiple sources before assuming the portal is at fault:
7/12, Patta, Aadhaar"] B --> C["2 · Search the portal
district and block first"] C --> D{"Village found
under a variant
spelling?"} D -->|"Yes"| E["Correct your records
and re-submit"] D -->|"No"| F["Check Census of India
and APEDA lists"] F --> G{"Officially exists
but absent from
the portal?"} G -->|"Yes"| H["3 · Escalate to NCOF
with documentation"] G -->|"No"| I["Resolve the record
locally first"]
Step 1: Cross-referencing Physical Records
Begin by verifying the village details against official documents. Use land records (7/12 Utara or Patta), Aadhaar cards, or voter IDs for accuracy.
- Confirm the exact spelling of the village name.
- Note any associated village codes from these documents.
- Record the block, district, and state for each farmer's location.
Step 2: Using Official Portals for Validation
The next step involves checking official government databases. These sources can help resolve APEDA village mapping issues and other data problems.
- Access the National Centre for Organic and Natural Farming portal at pgsindia-ncof.gov.in. Navigate to the 'Find Village' or 'Search Village' function.
- Enter the district and block first. Then, try various spellings of the village name.
- Consult the APEDA (Agricultural and Processed Food Products Export Development Authority) apeda.gov.in or Tracenet portal if your scheme is export-oriented. These portals often have updated village lists.
- Check the Census of India website for official village names and codes. This provides an authoritative reference.
Manually checking each village spelling and code takes about 1-2 minutes per farmer record. For a 50-farmer group, this requires 1-2 hours of focused effort. For 500 farmers across multiple blocks, this task can consume several days, and it repeats with each scheme renewal cycle.
Step 3: Correcting Farmer Records
Once the correct village name and code are identified, update your farmer data before re-attempting registration.
- Edit the village name and code in your local database or spreadsheet.
- Confirm that the block, district, and state also match the portal's structure.
Escalation for Unresolved Village Data Issues
If the village genuinely isn't listed, escalate to your Regional Council with the affected farmers and official records.
Despite thorough manual checks, some villages may still not appear. This indicates a deeper data mismatch requiring official intervention.
| Escalate when… | Include in your request |
|---|---|
| A village is officially recognised but absent from the PGS India portal | List of affected farmers |
| The portal lists incorrect details for a known village | Official documents — land records, Gram Panchayat certificates — showing the correct name and code |
| Errors persist despite verified spellings and codes | Block, district and state stated clearly, plus a note of your portal verification attempts |
All data mismatches submitted to NCOF or APEDA must include verifiable proof. Submissions without proper documentation will not be processed — a request without attached records simply restarts the wait.
Submitting to NCOF/APEDA
Direct your request to the appropriate authority — usually NCOF or the relevant APEDA Regional Office for certified organic schemes.
- Draft an official letter detailing the issue and attaching all supporting documents.
- Send the request via email or registered post to the NCOF helpdesk or APEDA regional office.
- Follow up periodically, noting reference numbers for tracking.
Resolving 'Village Not Found' errors requires careful data verification and compliance with official procedures. Accurate village data is fundamental for successful farmer registration and scheme implementation.
Check yourself
Tap an answer to see whether you are right, and why.
What does 'village not found' usually mean?
- The farmer isn't eligible
- A name or code mismatch with the portal database
- The portal is down
It's almost always a spelling, transliteration or naming difference.
Remember these things
- It's a data mismatch.
- Search from district down.
- Escalate with evidence.
Resolving village mismatches unblocks registration for the whole group. KrushiFlow validates these fields and submits farmer records to the portal in bulk.