Tariff alerts by HS code

Monitoring at the category level produces alerts you cannot act on. Monitoring at the HS code level produces a list of SKUs and a dollar figure. The difference is entirely in the mapping underneath.

Why category monitoring fails

An alert that says footwear may be affected leaves you exactly where you started: you still have to determine which of your products are in the covered headings.

Headings do not align with how you merchandise. Two products in the same collection on your site can sit in different subheadings with different treatment. Any alert that does not resolve to specific SKUs is news, not monitoring.

What a useful alert contains

The affected SKUs by name and variant.

The heading, the previous rate and the new rate.

The effective date, and whether goods in transit are treated differently.

Whether CUSMA-qualifying goods are affected, because that often decides whether you care at all.

Your monthly units and the resulting monthly cost, so the alert carries a decision rather than a research task.

The mapping is the hard part

Alerts are easy once every SKU has a correct, documented classification. Building and maintaining that mapping across a few hundred variants, as you add products and change suppliers, is the actual work.

It also decays. New SKUs arrive unclassified, colourways inherit the wrong origin, and a bundle gets created with no code at all. Monitoring without maintenance degrades quietly until an alert misses the SKU that mattered.

Running it as a standing capability

Treat the classification table as a maintained asset with an owner, the way you treat your inventory data.

Then monitoring is cheap and the alerts are trustworthy, which means you can act on them the same week instead of verifying them first.

TariffPulse maintains the mapping and the monitoring together, because either one alone does not produce an alert you would act on.