ExportSonar Search

Home / Alerts / Sample digest

Sample — real records, not a mock-up

What a Pro alert digest actually looks like

Pro watches your codes and raises an alert the moment one of their rates moves. This page is the digest a subscriber reads, rendered from the records we really hold: 24 rows across 22 HTS codes and 10 AD/CVD case numbers, dated 2026-08-22 to 2026-11-12. Every row links to the Federal Register notice or the USITC change record it came from — nothing here is written for the demo. The one thing a sample cannot show is your own watchlist, so we picked the codes.

24rows in this sample
22HTS codes
5949records in the same window, across 1774 codes
11564records in the corpus, 2025-03-07 – 2026-11-12

Most recent of the 6 rate moves in this sample: 7306.40.50.90 · 0.5% → 8.35% (2026-10-22)

Dates are printed with the field they come from: Published is the date the notice was published in the Federal Register, Effective is the effective date the change record states. We never compute either one.

How this sample was chosen

The digest window is the 180 days from 2026-05-16 to 2026-11-12 — counted back from the newest date in our corpus, not from today, so the page does not drift every midnight. The rows above span 2026-08-22 to 2026-11-12, inside it, and that window holds 5949 records over 1774 codes; this page prints 24 of them: the newest few of each kind (6 × rate changed · 5 × new provision · 4 × no rate change · 5 × one side only · 4 × no rate published). A plain "newest 24" would have been a worse sample, and the corpus says exactly how much worse: those rows carry 24 trade-remedy record(s) over just 1 case number, against the 10 this sample spans — so the quota is what makes this page show every kind of record the digest can carry, including the rate moves a subscriber pays to be told about.

  • Rate changed — the published rate column really changed between two HTS revisions. Values are printed exactly as each extractor recorded them: one reads the bare rate column ("10 → 0"), the other the printed Chapter 99 token ("10% → 0%") -- adding a unit the document does not state would be inventing one.
  • New provision — the heading is new in this revision; the right-hand side is whatever the change record prints for it — a rate, the schedule's own "No change", or the word "Established".
  • No rate change — the same number is restated under a new basis label, so the value did not move.
  • One side only — one document states a rate and the other does not; we print the gap instead of filling it.
  • No rate published — the document behind the row publishes no deposit rate at all.

Check any row yourself

Every row is a record, and the record is linked. Federal Register rows link to the notice itself (its document number is in the label); Chapter 99 rows link to the USITC Change Record for the release named. This page is generated from the same corpus the paid feed is built from — the USITC Change Record releases and the Federal Register AD/CVD orders we archive — each stamped with the date we read it. Before publishing, the generator re-reads the finished HTML and requires every HS code and date on it to be present in that corpus. A row it cannot trace is never printed.

What the paid digest adds

Start free — no card Compare the plans

A free account watches 3 codes and reads their changes — in its inbox, in its own JSON feed, and as CSV — for the last 30 days. Pro is the same three surfaces without the caps: up to 100 watched codes, the full history, and an email for every change. The log this sample is drawn from stays public either way.

Price a shipment with these ratesEnter a code, an origin and a value to see the duty the current schedule charges. Look up any HS code in the scheduleThe full HTS tree, with the rate every line carries.

Want the same rows for your own codes? Create a free account and add them to your watchlist — the sample above is what the digest looks like once they start moving.