This is a trust record for changes that can affect tariff facts, interpretation, calculations, or their presentation. It is not a product release-notes feed.
Entries are limited to tariff data, calculation-engine, HTS revision-ingestion, rule-interpretation, and data-pipeline corrections. Each record separates the correction date from the legal date represented by the underlying source.
Current HTS lookup and hierarchy aligned to 2026 HTS Revision 16
Corrected
2026 HTS Revision 16 effective date
What was wrong
The website lookup and hierarchy generator still read a legacy Revision 15 snapshot even though the calculator export and site-wide data status had advanced to Revision 16. Lookup results could therefore describe the current schedule as Revision 15.
What changed
The website now consumes the atomic Revision 16 HTS snapshot, verifies every row against the single site status, and fails the build if the lookup endpoint, hierarchy, or row revision disagrees. The corrected snapshot contains 29,945 active hierarchy rows and adds the official Revision 16 leaf lines 9903.45.30 and 9903.45.31.
Affected scope
HTS lookup results, generated classification hierarchy, canonical leaf pages, and links into those pages. The calculator-rate export was already on Revision 16.
Should users recheck or recalculate?
Recheck a classification page or saved lookup result viewed before this correction. Recalculate only if the corrected schedule changes the HTS line you select.
Legal dates separated from publication, discovery, milestone, and scoped applicability dates
Corrected
No single legal effective date; each underlying action retains its own date
Varies by source record
What was wrong
Legacy date aliases could make a review deadline look like a scheduled legal decision, and a company- or HTS-specific applicability window could be read as applying to an entire measure. Nine source publication dates also required correction from retained official-source evidence.
What changed
Change records now use typed milestones, explicit decision dates, lifecycle status, corrected publication dates, and scoped applicability windows. A whole measure is marked suspended only when an active suspension window explicitly applies to the entire measure.
Affected scope
Tariff Changes chronology, Upcoming placement, lifecycle badges, filtering, and expanded date evidence. This correction does not change tariff arithmetic by itself.
Should users recheck or recalculate?
Recheck a saved change or timeline interpretation if its timing affected a decision. Verify the linked official notice before acting on a legal deadline.
Country-wide Section 301 and supported FTA fee treatment entered the calculation stack
Corrected
Affected Section 301 action effective date
What was wrong
The prior rule shape favored origin-plus-HTS inclusions. It did not fully represent country-wide rules with exclusion lists, net-of-MFN treatment, or the separate MPF effect of a supported trade-program claim. Estimates could omit represented Canada, Australia, or EU additional duties or retain MPF after a qualifying USMCA or AUFTA claim.
What changed
The calculator now consumes fixed-additional and net-of-MFN rule methods, prefix-scoped inclusions and exclusions, and explicit entry facts. Missing facts fail closed. A fully supported USMCA claim can exclude the Canada rule and MPF; AUFTA can waive MPF but does not remove the Australia Section 301 rule.
Affected scope
Represented country Section 301 entries on or after July 24, 2026, plus supported USMCA and AUFTA entry-fee scenarios. Other unmodeled trade programs remain review-required.
Should users recheck or recalculate?
Recalculate an earlier estimate in the affected scope. Confirm classification, origin, preference eligibility, and entry facts with the official sources or a qualified customs professional.