Short Answer
International trade in plants and plant products is a high‑value, high‑risk activity. Before a shipment leaves the country of origin, exporters must confirm that the commodity does not harbor pests classified as A1 (high‑risk) or A2 (moderate‑risk) by the importing nation’s National Plant Protection Organization (NPPO). A pre‑export risk assessment (PERA) is the systematic process that identifies, evaluates, and mitigates those risks, ensuring that the phytosanitary certificate issued by the exporting NPPO is valid and that the consignment clears customs without delay.
Overview
A PERA for A1 and A2 pest compliance is a documented analysis that answers three core questions:
- Is the commodity a known host for any A1 or A2 pest listed by the destination country?
- What is the likelihood that the pest is present in the consignment?
- What mitigation measures (treatment, inspection, certification) are required to reduce the risk to an acceptable level?
The outcome is a risk‑assessment report that accompanies the phytosanitary certificate (PC) and serves as evidence to customs officials and import inspectors.
Why it matters (real stakes for exporters/importers)
Failure to conduct a proper PERA can lead to:
- Shipment rejection or destruction – costly loss of product and possible fines.
- Delay in market entry – missed sales windows, especially for perishable goods.
- Reputational damage – loss of trust with buyers and import authorities.
- Legal penalties – violations of the International Plant Protection Convention (IPPC) can attract sanctions.
Conversely, a well‑executed PERA demonstrates due diligence, speeds clearance, and can be a competitive advantage.
How it works
The PERA follows a logical workflow that aligns with the IPPC’s ISPM 5 (Pest Risk Analysis) and ISPM 12 (Phytosanitary Certification). The main phases are:
| Phase | Key Activities |
|---|---|
| 1. Data Gathering | Collect commodity description, origin, production practices, and previous inspection records. |
| 2. Host‑Pest Matching | Cross‑reference host lists with the importing country’s A1/A2 pest catalogue. |
| 3. Likelihood Assessment | Use prevalence data, surveillance reports, and seasonal factors to estimate pest presence probability. |
| 4. Impact Evaluation | Consider economic, environmental, and social consequences if the pest were introduced. |
| 5. Mitigation Planning | Determine required treatments, inspections, or certification conditions. |
| 6. Documentation & Reporting | Prepare the PERA report, attach supporting evidence, and submit to the NPPO. |
Each phase must be documented, signed by a qualified plant‑health officer, and retained for audit purposes.
Regulatory authority & contact
The primary bodies governing A1/A2 pest compliance are:
- International Plant Protection Convention (IPPC) – sets the global framework and publishes the International Standards for Phytosanitary Measures (ISPMs).
- National Plant Protection Organization (NPPO) of the exporting country – issues phytosanitary certificates and validates the PERA.
- NPPO of the importing country – publishes the A‑list of regulated pests and may request additional evidence.
Typical contact points include the NPPO’s Plant Health Certification Division (phone, email) and the IPPC Secretariat (info@ippc.int). Most NPPO websites provide downloadable pest lists and template PERA forms.
Required documents
When submitting a PERA, exporters should assemble the following package:
- Completed PERA report (signed by a certified plant‑health officer).
- Phytosanitary certificate application form (NPPO‑specific).
- Commodity description sheet (HS code, scientific name, quantity).
- Production and handling records (e.g., seed source, field sanitation logs).
- Treatment certificates (if post‑harvest treatments are applied).
- Laboratory test results (e.g., ELISA, PCR) confirming pest‑free status, when required.
- Export permit (if the commodity is subject to a national export control).
All documents must be in the language accepted by the importing NPPO (often English or the official language of the destination).
Step‑by‑step checklist (How‑to trigger)
The following checklist helps exporters initiate a PERA before the commodity leaves the farm or factory:
- 1. Identify destination requirements
- Visit the importing NPPO’s website.
- Download the latest A1/A2 pest list for the target commodity.
- 2. Verify host status
- Match the scientific name of the commodity against the host list.
- If a match exists, flag the pest for further analysis.
- 3. Gather field data
- Collect recent pest surveillance reports from the production area.
- Document cultural practices that reduce pest pressure (e.g., crop rotation).
- 4. Conduct likelihood assessment
- Use a risk matrix (Low/Medium/High) based on prevalence and detection limits.
- 5. Determine mitigation
- Choose an approved treatment (e.g., hot water, fumigation) if required.
- Schedule a pre‑shipment inspection by the NPPO inspector.
- 6. Compile documentation
- Prepare the PERA report using the NPPO template.
- Attach all supporting certificates and test results.
- 7. Submit to NPPO
- Upload the package via the NPPO’s electronic portal or deliver in person.
- Obtain the phytosanitary certificate with any conditional statements.
Common mistakes & rejection reasons
Even seasoned exporters stumble over a few recurring pitfalls:
- Out‑of‑date pest lists – Importing NPPOs update A‑lists annually; using an older version leads to non‑compliance.
- Incorrect scientific nomenclature – Misspelling the genus or species can cause the PERA to be ignored.
- Missing treatment proof – If a required post‑harvest treatment is not documented, the consignment is rejected.
- Insufficient inspection scope – A single spot‑check may not satisfy the importing NPPO’s sampling plan for high‑risk pests.
- Failure to address conditional statements – Ignoring “Phytosanitary certificate valid only if no symptoms observed at arrival” results in detention.
Addressing these issues early in the PERA saves time and money.
Real‑world example/scenario
“A U.S. avocado exporter planned a shipment to Mexico in July 2023. The Mexican NPPO listed *Xylella fastidiosa* subsp. *pauca* as an A1 pest for avocado. The exporter’s PERA identified the host match, consulted recent surveillance data showing zero detections in California’s San Joaquin Valley for the past two years, and applied a certified hot‑water treatment. The NPPO accepted the PERA, issued a phytosanitary certificate with a conditional statement, and the consignment cleared customs without delay. Had the exporter omitted the hot‑water treatment record, the shipment would have been rejected at the border, costing $250,000 in lost sales.”
This scenario illustrates how a concise, evidence‑based PERA can turn a potential barrier into a smooth export.
Requirements & standards (cite primary source)
The PERA must comply with the following internationally recognised standards:
- ISPM 5 – Pest Risk Analysis (FAO, 2019). It defines the methodology for assessing likelihood and consequences of pest introduction.
- ISPM 12 – Phytosanitary Certification (FAO, 2020). It outlines the documentation, inspection, and certification procedures for export.
- IPPC Annex II – A‑list of Regulated Pests. The annex provides the official A1/A2 classification for each importing country.
Exporting NPPOs often incorporate these ISPMs into national regulations; therefore, the PERA template must reference the exact article numbers (e.g., ISPM 5.1, ISPM 12.3) to demonstrate compliance.
Conclusion
Conducting a pre‑export risk assessment for A1 and A2 pest compliance is not optional—it is a critical risk‑management step that protects markets, preserves biodiversity, and upholds the integrity of the global plant‑health system. By following the structured workflow, using current pest lists, and documenting every mitigation measure, exporters can secure phytosanitary certification, avoid costly rejections, and maintain strong trade relationships.
FAQ
Do I need a PERA for every export shipment?
A PERA is required whenever the destination country lists any A1 or A2 pest that could affect your commodity. If the importing NPPO has no such listing, a PERA may not be mandatory, but many exporters still perform one as best practice.
Can I use a PERA prepared for one destination for another country?
No. Each NPPO maintains its own A‑list and may have different treatment requirements. A PERA must be tailored to the specific pest list and regulatory conditions of the importing country.
What if a pest is detected after the shipment has cleared customs?
The importing NPPO may issue a quarantine, require re‑treatment, or destroy the consignment. The exporter could be held liable for damages and may face future restrictions on shipments to that market.
Leave a Reply