Export health certificates explained: phytosanitary, veterinary and seafood

Three frameworks, not one certificate type

For plant products, the relevant international framework is the International Plant Protection Convention (IPPC). A phytosanitary certificate attests that a consignment meets the importing country's phytosanitary import requirements, and under the IPPC's own standard (ISPM 12), it must be issued by, or under the authority of, the exporting country's official National Plant Protection Organization (NPPO) — and only by officers technically qualified and duly authorized by that NPPO. Critically, ISPM 12 states explicitly that phytosanitary certificates should contain only phytosanitary information — not animal or human health matters, pesticide residues, radioactivity, commercial terms, or quality attestations. If you're used to a single all-purpose export certificate, this framework doesn't work that way.

For meat and animal products, the World Organisation for Animal Health (WOAH) frames veterinary certification as government-to-government: the exporting country's Competent Authority certifies to the importing country's Competent Authority, via a certificate signed by an official veterinarian. Seafood is less uniform — a catch certificate (verifying the catch itself was legal, typically validated by the flag state under fisheries law) is a different document from a food-safety health certificate, and depending on the destination market, you may need both, issued by different authorities.

What actually goes on the certificate

The IPPC's model phytosanitary certificate is built around a Description of Consignment section (exporter, consignee, package details, origin, quantity, botanical name) that carries a standard Certifying Statement that the goods have been inspected and are considered free from the specified quarantine pests, followed by an Additional Declaration section for import-country-specific attestations and a Disinfestation/Disinfection Treatment section recording any treatment applied (chemical, duration, temperature, concentration).

WOAH's model veterinary certificate splits into two parts: Part I covers consignment details — consignor/consignee, country and zone of origin and destination with ISO codes, the establishment's official approval/registration number (the abattoir, cutting plant or cold store, specifically), transport details, and identification of the commodities themselves (species, breed, treatment, lot). Part II is the zoosanitary information — WOAH's own model explicitly states this section is completed 'in accordance with the requirements agreed between the Veterinary Authorities of the importing and exporting countries,' meaning the actual attestation wording is a bilateral negotiation outcome, not a fixed universal text.

How your destination's specific requirements actually get attached

Neither framework works by handing you a blank template and asking you to write in whatever the destination wants. For phytosanitary certificates, the Additional Declaration section draws from a bank of standard wording specified in the importing country's own phytosanitary regulations, import permits, or bilateral arrangements — examples include statements like 'the consignment was produced in a pest-free area for [pest]' or '[pest] is not known to occur in [country/area].' Which of these apply to your shipment is set by the importing country's NPPO for that specific commodity-origin pairing, not chosen freely by the exporter.

For veterinary certificates, the same idea applies through direct bilateral negotiation between the two countries' Competent Authorities — WOAH's model certificates are explicitly a starting template for that negotiation, not a finished product. In Australia's system specifically, DAFF's Manual of Importing Country Requirements (MICOR) is where the actual, current, country-specific certificate codes and attestation wording live — it's a login-gated lookup system, not something publicly reproducible in a guide like this, which is itself informative: the specific requirements change often enough, and are specific enough per country and commodity, that they're maintained as a live database rather than static published text.

Australia's system: EXDOC, and its transition to NEXDOC

DAFF issues Australian export certification through EXDOC (Export Documentation System), covering dairy, eggs, grain, horticulture, inedible meat products, meat, seafood, skins and hides, and wool. You register as an Exporter, an EDI user (using accredited third-party software to interface directly with EXDOC), or both, and registered EDI users can generate their own certificates electronically.

DAFF is transitioning this system commodity by commodity to a successor platform, NEXDOC, which adds a QR code for verification and drops the old security-paper format. Seafood and animal by-products moved first, in 2025; meat and meat products followed on 6 July 2026 — a date that has already passed as of this guide's publication, so certificates for edible meat and meat products issued today should be coming through NEXDOC, not EXDOC, aside from a transition window for goods already in circulation. If your own documentation, systems, or supplier communications still reference EXDOC for meat specifically, check whether that's now out of date.

Certificate vs. import permit: two documents, opposite ends of the trade

This distinction causes more confusion than almost anything else in export documentation, and it's worth stating plainly: the export health certificate is issued by, and is the responsibility of, the exporting country's authority, proving the consignment meets the importing country's stated conditions at the moment of dispatch. An import permit, where the destination country requires one, is a separate authorization issued by the importing country itself, typically obtained by the importer or consignee, governing whether the goods may enter at all. ISPM 12 addresses this directly: import requirements are prescribed 'in advance by the NPPO of the importing country in legislation, regulations or elsewhere (e.g. import permits and bilateral and other arrangements)' — the permit is one mechanism by which the destination sets its own requirements, and where one exists, its number can be cross-referenced on the phytosanitary certificate's Additional Declaration, but the two remain separate documents from separate authorities.

Practically: having a valid export certificate does not guarantee your shipment clears the destination's own import-permit requirement, and having an import permit doesn't substitute for the export certificate your own country's authority has to issue. Confirm both requirements independently for a new lane rather than assuming one implies the other.

Validity, language, electronic certification, and fixing errors

There's no single universal validity period for a phytosanitary certificate — either the exporting country's NPPO or the importing country's own import requirements can set a specific duration, so check both sides rather than assuming a standard window. Language requirements are set by the importing country too; where none is specified, English is the encouraged fallback under FAO/IPPC practice.

Electronic certification exists but at different levels of maturity: ePhyto (the electronic phytosanitary certificate, in a standardized XML format built on ISPM 12) runs through the IPPC's own Hub for direct NPPO-to-NPPO transfer, with a free web-based tool (GeNS) available to countries without their own system — a genuinely operational, IPPC-run infrastructure. Electronic veterinary certification is less standardized: WOAH doesn't operate its own transfer platform, and instead publishes model certificates for countries and Single Window systems to build on individually.

If a certificate needs correcting after issuance, the mechanics matter: under ISPM 12, replacements can only be issued by the original issuing NPPO, must carry a new certificate number that never reuses the old one, and the original must be returned and cancelled — if it can't be returned, the replacement references the original by number and date instead. Alterations follow a similarly strict path: only the issuing NPPO can make them, and they must be minimal, stamped, dated and countersigned. A certificate with unauthorized alterations, missing required information, or issued by someone not authorized to do so is treated as invalid outright — know this before you're tempted to hand-correct a minor error yourself rather than going back to the issuing authority.