CanFlow Global
← All insights
cfiaseafood-importsogd-requirementshs-classificationcold-chain

CFIA Adds OGD Extensions for Two Oyster Species—What Changes at Clearance

CFIA just added species-level import requirements for Crested and Dwarf oysters, with separate classifications for ready-to-eat status and shell handling. If your broker doesn't have the TSN and processing state before filing the CAD, expect CFIA holds on fresh seafood shipments.

CFIA just added OGD extensions for two oyster species—Ostrea equestris (Crested oyster) and Ostrea stentina (Dwarf oyster). Both went live in Chapter 03 on October 5, with separate classifications for ready-to-eat vs non-ready-to-eat, shell-on vs shell-off, live vs processed.

If you import either of these species, your broker now needs the Taxonomic Serial Number (TSN) and the ready-to-eat status before filing the CAD. If they don’t flag it correctly, CFIA puts a hold on the cargo until you provide the documentation.

For fresh or chilled seafood, that hold is expensive. Cold chain doesn’t pause.

What an OGD Extension Actually Does

When CFIA adds an OGD extension at the HS code level, they’re telling CBSA: this specific product needs CFIA review before release. The extension ties to a combination of HS code, species (via TSN), and processing state (ready-to-eat, shell-on, fresh vs frozen).

Your broker files the CAD with the HS code, the TSN, and the OGD flag. CBSA’s system sees the flag and routes the entry to CFIA. If CFIA is satisfied with the documentation—or if the product qualifies for release prior to payment under their risk model—the cargo clears. If not, it sits until CFIA gets what they need: import permits, Safe Food for Canadians licensing, lot codes, processing plant registration, whatever the extension requires.

The two new oyster extensions are typical. CFIA maintains hundreds of species-level requirements for Chapter 03, 02, and 04. They add more every quarter. Most importers find out the hard way.

The Ready-to-Eat Problem

The Crested oyster extensions break out three handling states: live or non-ready-to-eat with shell on, non-ready-to-eat with shell off, and ready-to-eat. Each gets a different OGD code.

Ready-to-eat is a CFIA regulatory definition, not a marketing one. It means the product is safe for human consumption without further cooking or processing. Shucked oysters sold for raw bar service are ready-to-eat. Live oysters in-shell are not, even though restaurants serve them raw, because CFIA considers the consumer’s shucking and handling as an intervening step.

Most supplier invoices and packing lists don’t use CFIA’s terminology. They’ll say “fresh shucked” or “live in-shell” or “half-shell ready,” and your broker has to map that to the right OGD code. If the mapping is wrong, CFIA kicks it back.

We see this most often with processed seafood that sits in the grey zone. Cooked shrimp, cold-smoked salmon, marinated octopus all have ready-to-eat variants and non-ready-to-eat variants, and the difference is usually in the processing plant’s HACCP plan, not the product’s appearance. The supplier knows which one they’re shipping. The importer often doesn’t ask until CFIA puts the hold on.

TSN Requirements and Why They’re a Pain

The Taxonomic Serial Number is a species identifier from ITIS (Integrated Taxonomic Information System). CFIA uses it to enforce species-specific import requirements, particularly for conservation-listed species, invasive species, and high-risk seafood.

Ostrea equestris is TSN 79897. Ostrea stentina is TSN 821139. If your supplier ships either of these and your broker files the CAD with just the HS code and a generic “oysters” description, CBSA’s system won’t auto-release it. CFIA needs the TSN to confirm the species and apply the right OGD extension.

Most seafood suppliers don’t include the TSN on their commercial documents. They’ll list the common name, maybe the Latin binomial, sometimes a regional trade name that doesn’t match anything in ITIS. Your broker either looks it up (which adds time and risk of error) or asks you to get it from the supplier (which adds a round trip).

The clean way to handle this: get the TSN from your supplier during onboarding, add it to your product master, and pass it to your broker as part of the standing instructions for that SKU. CFIA’s Automated Import Reference System (AIRS) publishes the full list of species-level requirements at inspection.canada.ca. If your product is on the list, the TSN is mandatory, not optional.

What Changes at Clearance

If you’re bringing in Crested oysters or Dwarf oysters, nothing changes if your broker already flags Chapter 03 OGD requirements correctly. CFIA was inspecting oysters before this update. The new extensions just formalize the species-level requirements that were already being applied on a case-by-case basis.

If you’re bringing in other specialty oysters, check the AIRS list. CFIA adds species constantly. The oyster section of Chapter 03 now has dozens of TSN-specific extensions. If your species is on there and your broker isn’t flagging it, you’re rolling dice on release timing.

For fresh or chilled seafood, release timing is the whole game. Most brokerage workflows assume PARS or RMD with release prior to payment. When CFIA puts a hold on the cargo, that timeline breaks. You go from same-day or next-day release to “whenever CFIA clears the documentation,” which can be 24 to 72 hours if they need to escalate to a specialist.

If the cargo is sitting in a port or airport cold chain facility, that’s extra dwell fees. If it’s already on a truck to a Montreal sufferance warehouse and CFIA tags it after arrival, it sits in the reefer dock until the hold lifts. Either way, cold chain costs are running.

The fix is upstream: make sure your broker has the TSN and the ready-to-eat status before the first shipment. Once it’s in the system as a standing instruction, every subsequent CAD files clean.

Broader CFIA Seafood Reality

The two oyster species are a footnote. The bigger pattern is that CFIA’s AIRS system is moving toward species-level and processing-level granularity for all high-risk food imports, and seafood is the testing ground.

Chapter 03 already has the most OGD extensions of any HS chapter. CFIA adds more every quarter, usually for species that are either conservation-sensitive, disease vectors, or fraud-prone (lionfish, certain tuna species, anything that gets mislabeled as higher-value product).

If you import seafood regularly, the standing instruction workflow is the only scalable answer. Treating every shipment as a one-off and expecting your broker to research the TSN and ready-to-eat status per-entry doesn’t work once you’re above a few shipments a month.

Most of the seafood clearance problems we see come down to missing or inconsistent product data. The HS code is there, the supplier name is there, but the TSN is missing, the ready-to-eat status is ambiguous, and the broker has to guess. CFIA doesn’t release on guesses.

If your current seafood clearance process doesn’t include TSN capture and ready-to-eat confirmation as part of supplier onboarding, this is the year to fix it. CFIA is expanding AIRS coverage, not contracting it.

If you’re not sure whether your products are flagged, or if you’re seeing inconsistent hold patterns on seafood imports, that’s the kind of file review we do weekly. Get in touch.

Source: CSCB

Talk to a broker