Official-source data, with transparent verification and corrections.
SkuWatch separates official tariff facts, deterministic calculations, and explanatory content so that missing evidence remains visible instead of becoming a guessed rate.
2026 HTS Rev 19 Synced Rules verified Operational
Seven stages from source to page
-
01
Official ingestion
Schedules, notices, actions, fee guidance, and operational messages are retained from the issuing government source with source identity and retrieval evidence.
-
02
Structured parsing
HTS lines, legal scope, rates, dates, origins, exclusions, milestones, and source references are parsed into typed records without treating prose as a numeric rate.
-
03
Normalization
Codes use canonical digit forms internally and dotted display routes publicly. Dates keep their legal meaning: publication, discovery, effective date, deadline, and scoped applicability are separate fields.
-
04
Automated validation
Schema, provenance, counts, revision consistency, HTS hierarchy, rule coverage, source fields, and rate resolution are checked before a dataset can build the site.
-
05
Human review where required
Ambiguous legal scope, unsupported units, conditional entry facts, conflicting evidence, and classifications that cannot be resolved numerically are marked for review. No fixed percentage of records is claimed.
-
06
Regression checks
Independent formulas and browser matrices test representative tariff methods, country rules, fees, dates, routing, shared calculator output, accessibility, and fail-closed behavior.
-
07
Published correction log
Verified data, interpretation, calculation, revision-ingestion, and pipeline corrections are recorded with scope, dates, user action, and evidence in the correction log.
Field-level source precedence
There is no single source that controls every field. SkuWatch uses the authority responsible for the fact being modeled:
- USITC for the current HTS hierarchy, tariff text, rate columns, units, and Chapter 99 provisions.
- USTR and the Federal Register for trade-action scope, modifications, legal dates, and exclusions they publish.
- CBP for entry administration, user fees, trade-program procedure, and operational guidance.
If authorities or fields cannot be reconciled from evidence, the system does not silently choose the cheaper result. It reports a conflict or manual-review state.
Fail closed when the evidence is incomplete
A blank rate is never converted to Free. Column 2 origins, specific and compound rates, required quantity units, conditional exclusions, trade-program claims, entry-fee facts, and special Chapter 98/99 classifications must have the evidence their calculation requires.
When that evidence is missing or cannot be reduced to a defensible numeric equivalent, the calculator returns an incomplete or manual-review state and withholds a definitive total.
AI assists explanation, not authority
Machine-assisted language may help summarize or organize source-backed records. It is subordinate to structured official facts, deterministic tariff math, source citations, and validation gates. It is not an official legal interpretation and is never evidence for a rate or effective date.
Users should confirm material classifications and filings with the cited authority and, where appropriate, a licensed customs professional.
How corrections are published
A published correction identifies the problem, the change, affected scope, correction date, relevant legal effective date, whether users should recalculate or recheck, and the evidence available. Product feature announcements and ordinary interface release notes do not belong in that record.