Canada's Forced-Labor Watchdog Shift Raises the Bar for Import Compliance Data

Canada's forced-labor import compliance environment is moving in two directions at once: one institution is being wound down, while enforcement tools are being sharpened. That combination should get the attention of every importer, freight forwarder, customs broker, and compliance team moving goods into North America.

According to SupplyChainBrain, Canada is eliminating the Canadian Ombudsperson for Responsible Enterprise, known as CORE, the human-rights watchdog created in 2019 to investigate alleged abuses connected to Canadian companies operating abroad. Prime Minister Mark Carney called the office ineffective. Over roughly six years, the watchdog launched only five investigations and issued formal recommendations against two companies.

On its face, that sounds like deregulation. It is not that simple. Canada also introduced legislation on June 12 to strengthen forced-labor import restrictions. In a separate SupplyChainBrain report, Bill C-35 would allow Canada's foreign affairs minister to create a list of "high risk goods" by region, entity, and individual where there are reasonable grounds to suspect forced-labor production. The bill would also require importers of certain high-risk goods to provide better supply chain tracing data to customs officials.

That is the real operational story: compliance is becoming less about annual policy statements and more about shipment-level evidence.

Why the watchdog change does not reduce compliance risk

The end of CORE may remove one investigative channel, but it does not remove the underlying enforcement pressure. In fact, the timing points in the opposite direction. SupplyChainBrain reported that the U.S. Trade Representative determined 60 countries, including Canada, had failed to effectively guard against forced labor and warned of potential 10% to 12.5% tariffs, depending on whether those countries had forced-labor prohibitions in place at all.

That creates a trade-policy squeeze. Canada is trying to demonstrate stronger enforcement, while importers are being asked to prove more about where goods came from, who touched them, and whether supplier documentation can survive scrutiny. For logistics teams, this is where vague compliance language becomes operationally dangerous.

A supplier code of conduct is useful. A signed annual attestation is useful. But neither helps much if a shipment is flagged and the team cannot quickly connect the purchase order, supplier, country of origin, harmonized tariff code, production site, bill of lading, commercial invoice, packing list, and supporting traceability documents.

Forced-labor compliance is becoming a data problem hiding inside a customs problem.

The evidence importers need before enforcement lands

Bill C-35 is still early-stage legislation and must move through Canada's House of Commons and Senate. That gives companies time, but not much comfort. Enforcement programs tend to expose weak documentation long before new processes are fully mature.

Importers should start with four categories of data.

Supplier evidence is the first layer. Companies need to know not just the direct vendor, but also the upstream parties tied to production, sourcing, assembly, and raw materials where risk is material. That evidence should include supplier declarations, audit records, remediation plans, and dated confirmations of responsible sourcing practices.

Country-of-origin data is the second layer. Origin should be captured at the item and shipment level, not buried in email attachments or recreated after the fact. If a product is assembled in one country using inputs from another, the compliance team needs a clean way to explain that chain.

Product classification is the third layer. High-risk goods lists, tariff exposure, and customs enforcement all depend on accurate product classification. A weak HTS or HS-code process can turn a documentation request into a full-blown customs delay because teams cannot confidently map goods to the rules being applied.

Document retention is the fourth layer. The practical question is simple: if customs asks for support six months after import, can the company retrieve the complete file in minutes? If the answer is "someone in purchasing probably has it," the process is not ready.

Static PDFs are not a compliance system

Many companies still treat trade compliance as a folder of PDFs: supplier certificates, audit reports, invoices, origin statements, and email approvals. That worked when compliance was mostly periodic and reactive. It breaks when enforcement becomes data-driven and shipment-specific.

PDFs are not the enemy. The problem is when documents are disconnected from the shipments they are supposed to support. A customs broker should not have to search through inboxes to determine whether a supplier declaration applies to a specific SKU on a specific import entry. A compliance manager should not have to rebuild the shipment history manually when a high-risk region, supplier, or commodity is identified.

The better model is operational compliance data. Supplier risk records should connect to purchase orders. Purchase orders should connect to shipments. Shipments should connect to customs entries and document packets. Exceptions should trigger workflows before cargo is stuck at the border.

That is where transportation and trade operations need to work together. Customs compliance cannot live in one system while transportation execution lives in another and supplier risk lives in a spreadsheet. Forced-labor enforcement cuts across all three.

What freight forwarders and importers should do now

The immediate playbook is not complicated, but it does require discipline.

First, identify products and suppliers that would likely fall into a high-risk review if Canada or another trade authority created risk lists by region, entity, or individual. Do not wait for a formal list to begin mapping exposure.

Second, standardize the document packet needed for each risk category. For some goods, that may include origin certificates, supplier declarations, production-location details, audit summaries, and materials traceability. For others, the requirement may be lighter. The key is consistency.

Third, tie compliance evidence to shipment milestones. If documentation is missing, the system should raise the issue before pickup, export filing, vessel departure, or customs entry—not after a hold is issued.

Fourth, measure exception cycle time. How long does it take to answer a forced-labor documentation request? How often are records incomplete? Which suppliers create repeat gaps? Those are logistics performance metrics now, not just legal department concerns.

CXTMS helps turn that messy handoff into a controlled workflow. Customs documentation, supplier-risk records, shipment milestones, and exception alerts should be part of the operating layer, not scattered across static PDFs and last-minute emails. When enforcement changes, the companies that can produce evidence quickly will move freight with fewer surprises.

If your import compliance process still depends on disconnected files and tribal knowledge, now is the time to tighten it. Schedule a CXTMS demo to see how connected transportation workflows can support cleaner customs documentation, faster exception handling, and better supplier-risk visibility.