Compare the customs and tariff treatment of the same HTS code across the country-of-origin scenarios you supply. Surfaces known duty, additional measures, and government fees for each origin; never ranks or recommends a sourcing country.
Enter an HTS code, destination, entry date, and at least 2 origins, then submit. You will see:
Tariff origin comparison runs the same HTS code through the Canonical Resolver for each origin you supply and shows what is currently resolvable in the TariffCatalog Tier-1 canonical data state. The result is a side-by-side view of customs treatment — not a sourcing recommendation. Origins that the Resolver cannot fully resolve are not ranked against origins that are.
For each origin, the Canonical Resolver runs against the supplied HTS, destination, and entry date. Per-origin outputs return one of: resolved (duty, additional measures, and government fees all computable from canonical data), resolved_with_warnings (computable, with caveats), needs_verification (canonical data is incomplete for that origin on that HTS/date), or unsupported (no verified measure applies). Numeric delta between two origins is only emitted when both sides return resolved with matching currency and customs value basis. The overall comparability is COMPARABLE, PARTIALLY_COMPARABLE, NOT_COMPARABLE, or NEEDS_VERIFICATION.
Use it when you want a customs-treatment comparison only: same HTS, same destination, same entry date, two or more origins. Free for up to eight origins per query. It does not provide supplier rankings, lead-time comparisons, MOQ comparisons, or procurement advice.
Per-origin results come exclusively from the TariffCatalog Canonical Resolver against the production Tier-1 canonical data store. No origin-specific rate table, country average, or sourcing recommendation is used or implied. Always verify origin treatment with your customs broker, the official HTS, the USTR Federal Register, and CBP.
Official source notes and calculator assumptions should be reviewed before shipment, label purchase, invoice filing, or customs entry.
Official Harmonized Tariff Schedule of the United States — verify the HTS line and general rate column.
USTR Section 301Section 301 tariff actions, current operative Chapter 99 headings, and exclusions.
CBP — Country of OriginCBP guidance on country-of-origin marking and substantial transformation.
CBP — Tariff InformationOfficial tariff and customs duty information for US imports.
MethodologyHow TariffCatalog compares origins and what the canonical resolver does and does not cover.
| Origin A | Origin B | Result | Comparable amount delta | Comparable rate delta | Notes |
|---|
No pairwise differences available — all supplied origins returned the same canonical treatment.
TariffCatalog is not a customs authority or customs broker. A comparison output is a customs-treatment snapshot from the canonical resolver, not a sourcing recommendation or supplier ranking. Verify origin treatment with your broker, CBP, USTR, and the official HTS line before acting on it.
Running origin comparison\u2026
For each origin, the Canonical Resolver runs against the supplied HTS, destination, and entry date. Per-origin outputs return one of: resolved (duty, additional measures, and government fees all computable from canonical data), resolved_with_warnings (computable, with caveats), needs_verification (canonical data is incomplete for that origin on that HTS/date), or unsupported (no verified measure applies). Numeric delta between two origins is only emitted when both sides return resolved with matching currency and customs value basis. The overall comparability is COMPARABLE, PARTIALLY_COMPARABLE, NOT_COMPARABLE, or NEEDS_VERIFICATION.
For HTS 9903.88.01 (Section 301 List 1) entering the US on 2026-08-15 at a customs value of $5,000: China returns resolved with a List 1 additional measure plus base duty and MPF/HMF; Vietnam returns needs_verification (no Section 301 layer stored for Vietnam on this date); Mexico returns needs_verification with the same conservative outcome. Numeric delta is not emitted because not all origins are resolved. The page surfaces what is currently known and never ranks unresolved origins.
Per-origin results come exclusively from the TariffCatalog Canonical Resolver against the production Tier-1 canonical data store. No origin-specific rate table, country average, or sourcing recommendation is used or implied. Always verify origin treatment with your customs broker, the official HTS, the USTR Federal Register, and CBP.
TariffCatalog is not a customs authority, customs broker, procurement advisor, or supplier-ranking service. The comparison output is a customs-treatment snapshot drawn from currently-resolvable canonical data. It is not a sourcing recommendation, a supplier scorecard, a lead-time estimate, an MOQ analysis, a quality assessment, or a guarantee of duty owed. Verify all results with your customs broker, CBP, USTR, and the official HTS line before acting on them.
No. TariffCatalog is not a procurement or supplier-ranking service. The tool only shows what is currently resolvable in the canonical tariff data for each origin. A lower known customs-cost layer for one origin does not by itself make it a better business choice — lead time, MOQ, quality, freight, IP risk, and total landed cost are not covered here.
Each origin is resolved independently against the same canonical data store. The current Tier-1 canonical data covers China → US most completely (Section 301, FYR, Forced Labor, MPF, HMF). Other origins may have partial coverage — for example, only MFN, MPF, HMF, and De Minimis apply — which is a conservative resolvable outcome, not a zero. The page surfaces each origin’s actual coverage state rather than faking a comparison.
It means at least one of: applicable layer count differs, total resolvable amount differs, ordinary/additional/fee rate differs. The page shows the per-origin resolver output and the structural differences. It does not convert or normalize across different additional-measure stacks.
Yes. Up to 8 origins per query in the free tier. The page shows per-origin cards plus a pairwise matrix and an overall comparability state.
Numeric amount-delta is only emitted when both sides are fully resolved, with the same currency, and the same customs value basis. If any origin is needs_verification, unsupported, or currency-mismatched, the page shows the per-origin treatment but does not invent a numeric delta.
It is an as-of comparison for the entry date you supply. Past dates return historical Resolver output; future dates return the canonical measure as-of that future date (with the same conservative treatment of PLEDGED / PROPOSED / POLITICAL_STATEMENT statuses as the rest of the Resolver). It is not a second timeline product.
Phase 10 ships the comparison experience only. Persistence and export rely on existing saved-cases / export architecture and are not expanded by Phase 10. Re-running the query with the same inputs reproduces the same output deterministically.
No. TariffCatalog is not a customs authority or customs broker. Verify all origin treatment, scope of additional measures, exclusions, and MPF/HMF applicability with your broker, CBP, USTR, and the official HTS line before filing.
Use the AI HS Code Finder, CSV Catalog Checker, and Import Duty Calculator to prepare customs data before shipping.
