Health Canada API Profile Mapped HS Codes: When Your Industrial Chemical Gets Flagged as Pharmaceutical

The Problem

Health Canada maintains an Active Pharmaceutical Ingredient profile in the Single Window Addendum that maps to dozens of HS codes at the six-digit level. If you import a chemical substance that falls under one of those mapped codes but you’re not bringing it in for pharmaceutical use — industrial feedstock, lab reagent, educational sample — the system still tags it as an API and triggers the full Health Canada OGD release process. You can’t file the eManifest data without addressing the profile.

This comes up most often with importers of fine chemicals, industrial solvents, R&D samples, and educational institutions running science curricula. The HS code is correct, the goods are not pharmaceuticals, and there’s no practical way to sever the link in advance.

What the April Webinar Clarified

During a CSCB webinar earlier this year reviewing the 2026 Single Window Addendum Changes, brokers asked whether Health Canada would introduce an exemption code or excipient flag to handle non-pharmaceutical goods falling under API-mapped HS codes. The answer: Health Canada is aware of the issue and has received similar enquiries, but no exemption mechanism exists yet.

That puts the burden back on the importer’s commercial documentation and the broker’s eManifest filing. If the system sees an API-mapped code, it expects API-compliant data. You can’t leave the OGD field blank. You can’t enter a generic exemption note. The workflow expects a Health Canada reference number or a statement of non-applicability that Health Canada will accept on review.

Filing Strategy Until Health Canada Publishes Guidance

Most brokers handling non-pharmaceutical imports under API-mapped codes do one of three things:

Option one: contact Health Canada’s import division before the goods arrive, explain the industrial end-use, and ask for written confirmation that the shipment does not require an API establishment licence or drug identification number. Attach that confirmation to the commercial invoice, reference it in the eManifest OGD data field, and include it in the CAD documentation package. This works, but it adds three to five business days to your pre-arrival timeline and requires someone at the importer’s end who can articulate end-use in language Health Canada recognizes.

Option two: classify the goods under a more specific eight-digit or ten-digit code that does not trigger the API profile, if the tariff structure permits it. This is not tariff shopping — it’s using the full specificity of the HS to separate pharmaceutical-grade API from industrial-grade chemical. If the goods qualify for a narrower subheading that Health Canada has not mapped, the eManifest system won’t flag them. Review with your customs compliance team before you make the switch, because CBSA will verify the classification on examination and a downgrade to industrial-use does not automatically mean a different tariff treatment under CUSMA or MFN.

Option three: file the eManifest with a note in the OGD field stating “Industrial use, not for pharmaceutical manufacture or human consumption, end-use documentation on file,” and include a letter from the importer’s quality or regulatory department confirming end-use. This approach has worked on RMD releases where the CBSA officer and Health Canada liaison accept the statement at face value, but it does not eliminate the risk of a full examination or a follow-up verification request. If Health Canada decides to escalate, you’re looking at a hold until the importer provides additional evidence.

None of these are perfect. The first option is the cleanest but slow. The second works only if the tariff structure cooperates. The third is fast but carries examination risk.

What It Means for CAD Filing Under CARM

When you file the Commercial Accounting Declaration post-release, the OGD reference you used in the eManifest has to match the supporting documentation you upload to the CARM Client Portal. If you told the system “not for pharmaceutical use” at eManifest, the importer’s end-use letter or Health Canada confirmation has to be in the document set. CBSA’s verification team pulls CAD packages for OGD compliance review on a routine basis, and mismatched OGD claims are one of the faster ways to trigger a post-release adjustment or an AMPS penalty assessment.

If your importer is an NRI without a Canadian business number, the documentation burden sits with the broker of record, and Health Canada will expect you to produce end-use evidence on request. That’s another reason to get the pre-arrival confirmation in writing rather than relying on a one-line note in the manifest.

Timeline Impact

If you’re filing PARS with an API-mapped HS code and you don’t have Health Canada’s advance clearance, expect the release to default to full examination. That’s two to four business days minimum at most CBSA service areas, longer if Health Canada’s import team is backlogged. If you’re working with time-sensitive lab samples or production feedstock on a just-in-time schedule, that delay is not trivial.

For freight arriving at the Port of Montreal and moving through sufferance warehouses in Lachine or Saint-Laurent, the examination hold eats into your container free time and pushes drayage into the next billing cycle. If your goods sit on our Montreal dock waiting for Health Canada sign-off, you’re paying daily storage and the risk of detention charges once the steamship line’s free period expires. Most NVOCCs give five calendar days. After that, it’s per-diem.

What Health Canada Needs to Publish

The cleanest fix is an exemption code in the Single Window Addendum that importers and brokers can apply at eManifest when the goods fall under an API-mapped HS code but the end-use is non-pharmaceutical. That code would bypass the API profile logic and let the goods clear without a pre-arrival consultation or a post-release verification dance.

Until Health Canada builds that into the system, the workaround is manual, document-heavy, and slow. If you’re importing under Chapter 28, 29, or 38 and the goods are not pharmaceuticals, check the HS code against Health Canada’s API mapping before the goods ship. If it’s flagged, get your end-use documentation together early.

We run this scenario weekly with lab supply importers and industrial chemical buyers. The answer is never fast, but it is predictable once you know which path Health Canada expects. Get in touch if your next shipment is sitting in this gap.

Source: CSCB