Your board just asked a question your ERP can’t answer: what is our tariff exposure, by SKU, by customer, by shipment, right now?
If you make anything that crosses the Canada-U.S. border, that question landed on your desk this month, and it isn’t going away. Most manufacturers can’t answer it, not because the data doesn’t exist, but because it’s scattered across the ERP item master, a customs broker’s records, and a spreadsheet one person maintains. That gap used to be a “someday” modernization item. It’s now an urgent, quantifiable operational problem.
What Changed
On August 22, 50% U.S. tariffs took effect on roughly $20B of Canadian goods, imposed under Section 338 of the Tariff Act of 1930. They apply even to CUSMA-compliant goods, and they carry no expiry date.
The tariffs run across three annexes: dairy, alcoholic beverages, and a list labeled “Motor Vehicles” that contains no vehicles at all. It covers electronics, furniture, building materials, plastics and packaging, apparel, machinery and manufacturing inputs, cosmetics, and agricultural products. If you build things and ship them south, there’s a real chance you’re on that list under a heading that doesn’t describe what you make.
Canada is retaliating “dollar for dollar” on September 8, targeting steel, dairy, appliances, agricultural equipment, pulp and paper, and electronics. Specific lists haven’t been published yet.
And underneath all of it: CUSMA was not extended for another 16-year term. It now goes to annual review. You can’t underwrite a multi-year cross-border capital plan on that kind of ground.
Why This Is a Data Problem, Not a Policy Problem
Answering “what’s our exposure” requires joining HTSUS classification, country of origin, bill-of-materials content, customer, and margin. In most mid-market manufacturers, that data lives in five different places and none of them talk to each other.
The “Motor Vehicles” annex with zero vehicles in it is the proof point. You cannot reason about exposure by industry or product category anymore. It has to be resolved at the code level, line by line, SKU by SKU. That’s an integration and data-modeling job. It is not something your ERP vendor ships as a module, and it’s not something a spreadsheet can hold together once the retaliation lists land on top of the original three annexes.
Three Places This Is Already Costing You
Quoting. A quote you issued last week can be underwater today, and there’s no sunset date to wait out. If your quoting process doesn’t calculate landed cost in real time and re-quote when tariff exposure changes, you’re either eating margin or re-quoting by hand every time the rules shift. This is a narrow, measurable build on top of the ERP you already have. It doesn’t require ripping anything out.
Content and origin tracking. Under the Section 232 regime, a reduced 10% rate applies to steel and aluminum derivatives if at least 85% of content by weight is U.S.-sourced and melted, poured, smelted, or cast in the U.S. Most ERPs don’t track melt origin or content-by-weight at the bill-of-materials level. If you’re anywhere near that threshold, building the tracking pays for itself in the tariff delta alone.
Remission, drawback, and audit trails. Canada runs a remission process. The U.S. offers duty drawback. Both are evidentiary: you need documentation that holds up. CBP issued an enforcement bulletin the day the tariffs took effect. Whatever documentation system was “good enough” before is now the difference between recovering duty you’re owed and just eating it.
Why “Rip and Replace” Isn’t the Answer Right Now
Capital is freezing. Nobody is approving an 18-month ERP replacement into this level of uncertainty, and they shouldn’t. A full ERP replacement takes longer than the next CUSMA review cycle.
What still gets approved is anything with a hard number attached to it: cost recovery, margin protection, exposure quantification. The path that survives a frozen capital environment is the same one that works for operational software generally: start small, prove ROI on one workflow, extend what you already have instead of replacing it.
Who’s Feeling This First
Distilleries, breweries, wineries, and food and beverage manufacturers sit directly against two of the three U.S. annexes. Canadian producers exporting south just took a 50% hit. U.S. producers face Canadian retaliation on September 8. If you’re in one of these verticals, you’re not looking at a future risk, you’re looking at a margin problem this quarter.
Logistics and field operations teams are the second group under pressure: customs coordination, broker handoffs, and documentation that used to be someone’s side task are now a daily operational requirement.
What to Do This Quarter
You don’t need a strategic plan before you can act. You need to know your number.
Start with a fixed-scope exposure map: pull the item master, resolve HTSUS codes against the current annexes, and output exposure by SKU, customer, and margin. That’s a 2-3 week engagement, not a 12-month one, and it gives your board and your finance team the number they’re already being asked for.
From there, triage which accounts and product lines sit closest to the retaliation lists coming September 8, so those conversations aren’t a surprise. And if quoting is where the exposure is hitting margin hardest, that’s usually the highest-leverage place to build next: real-time landed-cost calculation sitting on top of the ERP you already run.
One thing worth saying plainly: software services aren’t tariffed. Building the systems that quantify and manage this exposure doesn’t add to the exposure itself.
We help manufacturers build exactly this kind of tariff exposure mapping and quoting logic on top of existing ERPs, without a rip-and-replace project. If you can’t currently answer what your exposure is by SKU, by customer, by shipment, let’s talk about closing that gap.