HTSAlert vs monitoring tariffs by hand
Manual monitoring is genuinely free, and done perfectly, every day, without exception, it works. Nobody is charging you to open USITC's site and read a rate. What this page compares, task by task and honestly, is what the manual loop actually costs in time and attention, where it structurally breaks even when done diligently, and when it is the right call to keep doing it by hand rather than paying for a tool.
| Dimension | HTSAlert | The alternative |
|---|---|---|
| Check current rates on watched codes | Automated daily pull of official USITC data for every watched code | Open USITC for each code by hand, every day; minutes per code, easy to defer under deadline pressureNot publicly stated |
| Spot a rate change | Machine diff against yesterday's snapshot — every change caught, none missed to fatigue | Compare today's number against your last note or spreadsheet cell by eyeNot publicly stated |
| Resolve the trade action and 9903 subheading | Governing action and Chapter 99 subheading resolved and shown in the alert automatically | Read the actual Chapter 99 note language and match it to your product by hand — error-prone under time pressure, and some notes run to several paragraphsNot publicly stated |
| Catch retroactive changes | Two-date model records the legal effective date and the detected date on every change, explicitly | Only if you specifically re-read Federal Register notices for past effective dates, not just current onesNot publicly stated |
| Track condition-dependent headings (0% or +100%) | Rendered as an explicit question for the filer to resolve, never as a guessed number | A spreadsheet cell holds one number; it has no native way to express 'depends on whether the goods are X'Not publicly stated |
| Keep evidence for a compliance review | Insert-only timestamped audit record on every detected change; CSV export from Pro and Broker plans | Your own notes and screenshots, if you remembered to keep them, with no independent timestamp authorityNot publicly stated |
| Ongoing cost | $0 to $129/month depending on plan and watchlist size — a flat, predictable line item | No subscription fee, but the time is not free: minutes per code, per day, compounding across a growing watchlistNot publicly stated |
The failure mode isn't effort — it's the skipped day
A broker who checks ten codes daily, diligently, spends real time and mostly stays current. The structural problem isn't diligence — it's that US tariff changes are sometimes published in the Federal Register after they are already legally in effect. A notice dated for a past effective date is easy to miss if you're only scanning for today's changes, and one missed day in months of perfect checking is enough for an entry to go out at the wrong rate with no warning. HTSAlert records two dates on every detected change — the legal effective date and the date the change first became detectable in published data — specifically so a gap like that has a paper trail instead of a shrug.
Why a spreadsheet can't hold a conditional rate
Two live Chapter 99 headings today — 9903.91.12 and 9903.91.14 — don't attach to a code at all; they attach to what the goods physically are. The first adds 100% IEEPA duty on intermodal chassis and related parts, but only if that's genuinely what's being imported under the code, with a sibling heading applying instead when it isn't. The second does the same for ship-to-shore gantry cranes of Chinese origin. A spreadsheet cell can hold '3.4%' or '35.9%'; it cannot natively hold 'zero unless the goods match this description, in which case one hundred percent' without a human re-reading the underlying note by hand, every time, for every code that could plausibly be affected.
This is a narrow problem — most codes don't have a conditional heading attached — but for the ones that do, a static number in a spreadsheet is not merely incomplete, it's actively wrong for half the population of goods filed under that code.
The stacking problem
A single code's effective rate can combine the MFN base rate with Section 301, Section 232, and IEEPA overlays simultaneously, each carrying its own Chapter 99 subheading and its own note language to interpret. Resolving that correctly by hand, for every watched code, every day, is where manual monitoring stops being free time and starts costing billable hours — and where a transcription error in a stacked calculation is easiest to make unnoticed.
When manual monitoring is the better choice
If you import under one or two stable codes, your codes sit in chapters with no history of trade-action churn, and you already have a broker relationship where someone else is watching for changes as part of their job, adding a monitoring tool may genuinely be unnecessary — zero cost with an embedded expert is a legitimate setup, and this page isn't trying to talk you out of it. HTSAlert earns its place when the watchlist grows past what one person can recheck daily, the codes sit in trade-action-heavy chapters, or you need your own timestamped audit trail rather than relying on someone else's memory of what they checked and when.
HTSAlert automates the daily check a manual process depends on getting right every single time: it pulls official USITC data for every watched code, diffs it against yesterday's snapshot, and records both the legal effective date and the date a change first became detectable — a two-date model a spreadsheet cell cannot express on its own. Two live Chapter 99 headings, 9903.91.12 and 9903.91.14, add a 100% duty only when the imported goods match a specific description rather than a specific code, and HTSAlert renders that as a question for the filer instead of a guessed number. Coverage starts free for 5 codes and scales to 25 codes at $19 a month, 100 codes at $49 a month with CSV audit export, or 300 codes at $129 a month, with two months free billed annually.
Frequently asked questions
Isn't checking USITC and the Federal Register myself good enough?
It can be, if you check every watched code every day and specifically re-read Federal Register notices for past effective dates, not just current ones. The risk isn't the checking — it's the day you skip, or the retroactive notice you read as 'not relevant to me right now' because its effective date was already in the past.
What exactly does HTSAlert automate that I'd otherwise do by hand?
The daily loop: pull official USITC data for each watched code, diff it against yesterday's snapshot, resolve the governing trade action and Chapter 99 subheading — including surfacing condition-dependent headings as a question rather than a guess — record the legal effective date and the detection date, and send an alert. Every detected change becomes a permanent, timestamped audit record.
What does the automated option cost?
HTSAlert is free for up to 5 watched HTS codes with email alerts. Paid plans are Starter at $19/month for 25 codes, Pro at $49/month for 100 codes with Telegram alerts and CSV audit export, and Broker at $129/month for 300 codes, with two months free on annual billing.