Official-source tariff data · 2026 HTS Rev 19 · synced · Operational
SkuWatch tariff intelligence
Why we built SkuWatch

We needed a clearer way to follow tariff changes.

SkuWatch began as an internal research tool for our Canada-based international trade team. The SkuWatch team now shares that work as a source-linked reference for US-bound tariff research.

The trade work behind the product

We work in international trade from Canada. Our own importing experience includes bringing small appliances and accessories from China into Canada. We also support other Canadian trade businesses, including businesses working in fashion and fast-moving apparel.

That background is the reason we care about practical questions: what changed, which products may be in scope, what source supports the answer, and how fresh the underlying information is.

2025 was the turning point

In 2025, tariff changes made the information relevant to our work difficult to track. The records existed across schedules, notices, and agency websites, but collecting them and keeping their dates, scope, and authority organized became a research task of its own.

From internal research to SkuWatch

We later built AI agents to collect and organize that information for our own research. We shared the result as SkuWatch so others could inspect the same source trail instead of starting from scattered records each time.

Our Canadian trade experience explains why we built the product. The tools on this site have a narrower research scope: they organize US tariff and HTS information for US-bound imports. They do not represent Canadian customs guidance.

What SkuWatch is today

The SkuWatch team makes this public Tariff Intelligence site available alongside SkuWatch Tariff Recovery and the separate SkuWatch AI Visibility Agent ↗.

AI helps us collect, organize, and explain research; it is not the authority for a tariff rate, effective date, or legal interpretation. Structured facts remain tied to official records, and missing evidence is kept visible instead of being filled with a guess. Read our methodology, inspect the current data status, or open the source guide.

Data model

This site is built from the project snapshot. The current build includes 1477 measure rows and uses 6857 8-digit HTS entries from 2026 HTS Rev 19.

Each measure record keeps legal basis, current status, linked HTS entries, source URL, and the snapshot timestamp captured during build.

Field Value
HTS revision2026 HTS Rev 19
Tracked measures1477
8-digit entries6857
Tracked headings961
Last ingestion
Last verification

Last ingestion and last verification are checkpoints for the published dataset and its automated contracts. They do not guarantee that every displayed rate is currently legally applicable to a shipment or that every record was individually reviewed by a person.

What SkuWatch does not do

Record boundary

Date-only source fields are treated as fixed UTC midnight at the US Eastern monitoring boundary and are displayed with preserved offsets to keep sorting deterministic.

Missing fields stay explicit: if a source does not provide an effective date or confidence marker, the record keeps the status and source link without extrapolation.

Corrections and questions

If a page appears incomplete or wrong, email service@skuwatch.app with the page URL and what needs to be corrected. Verified corrections that affect tariff facts, interpretation, calculations, or their presentation are documented in the correction log.

Every public statement is designed to be source-linked and verifiable. If you need legal interpretation, consult a customs professional.

Catalog and API planning

Tell us what you want to build.

The SkuWatch API is not publicly available yet. Share the workflow, catalog, or product experience you want to power so we can prioritize useful future access.

10–4,000 characters. Please do not include passwords, payment details, or confidential product data.

The security check loads only when this form is opened.

By submitting, you agree that SkuWatch may store these details and contact you about this API use case. We do not sell this information. See our privacy notice.