NPOP Certificate Issuance: Manual Checks for CB Approval

Under NPOP, the Certification Body itself issues the scope certificate on Tracenet, in the prescribed format, once a year. There is no separate APEDA approval of each certificate, so the CB's own checks are what keep certificates right. This episode sets out the checks on data, on the decision, and on the certificate itself.

Checking the Data Before Deciding

Identity, land, crops, dates, conversion status, inputs and group membership must all agree with the inspection report.

1. Operator or farmer names match identity documents.
2. Land parcels and areas match the inspection report.
3. Crops and areas as inspected.
4. Inspection dates recorded correctly.
5. Conversion status for each plot, from its history.
6. Inputs used are permitted, with evidence.
7. For grower groups, every member listed with their plots.

The Certification Decision

The decision covers the operator, the area and the products, and is taken by people other than the inspector.

• The decision is made after examining the inspection and review reports.
• It covers approval of the operator, the area, the products, and any disciplinary measures.
• It is taken by person(s) different from those who inspected and reviewed.
• For grower groups, inspection follows only after the ICS has inspected every member twice in the year.

Checking the Certificate Before Issuing

Operator details, products, scope, validity, numbering and annexures must all be correct.

1. Operator name and address as in the approved inspection report.
2. Products and their organic status.
3. Scope: production, processing or trade.
4. Validity dates in line with the inspection cycle.
5. Certificate number and date of issue.
6. Annexures complete and referenced.

A certificate checked at every stage is one that holds up at surveillance. KrushiFlow validates these fields and submits farmer records to the portal in bulk.