Official-source tariff data · 2026 HTS Rev 19 · synced · Operational
SkuWatch tariff intelligence
Import workflow

From HTS Code to Landed Cost: A Verification Workflow

A landed-cost estimate becomes useful when every material input has an owner, a source, and a clear review state.

A landed-cost workflow should not begin by typing a vague product name into a calculator and accepting the first code. It should begin with a compact product record, advance through classification and origin review, and stop when a material fact cannot be supported.

This checklist produces a reference estimate, not a customs filing or binding classification.

Step 1: freeze the product facts

Create a dated product record before researching the HTS:

Save the source for each fact. A supplier email, specification sheet, laboratory record, and marketing page do not carry the same reliability.

Step 2: build a classification path

Use the current USITC Harmonized Tariff Schedule to move through the hierarchy. Record the candidate heading, subheading, full statistical line, relevant legal notes, and any required units.

Then search CBP CROSS for rulings involving materially similar goods. Compare the facts, not only the product name. CBP's rulings overview explains the ruling program and the role of published rulings.

Stop when the available facts cannot distinguish between plausible provisions. A calculator should not be used to hide a classification gap.

Step 3: establish origin separately

Country of shipment, supplier location, and country of origin are not interchangeable fields. Record the manufacturing steps and the origin basis used for the estimate. If a preference claim is contemplated, review the relevant program and supporting documentation through official sources such as CBP's trade-agreement guidance.

Mark the estimate “origin unresolved” if the conclusion depends on missing production facts.

Step 4: choose the calculation date

Tariff measures and fees have time windows. Save:

If the calculator does not expose a time state, record that as a review gap.

Step 5: define value, quantity, and transport assumptions

Write down the exact value basis used for the scenario. Record quantity in both the commercial unit and any HTS statistical unit. Keep freight and insurance visible even when the customs-value assumption treats them separately.

For fees, specify the modeled entry type and transport mode. Do not treat broker charges, port costs, taxes, fulfillment fees, or domestic delivery as included unless the tool explicitly models them.

Step 6: inspect every line item

The review worksheet should look like this:

Layer Input/source Formula or rule state Estimated amount Review state
Base HTS duty classification + general/special rate visible confirmed / review
Additional measure origin + legal scope + date visible confirmed / review
User fee entry and transport scenario visible confirmed / review
Freight/insurance commercial assumption visible confirmed / review
Other cost quote or business assumption visible included / excluded

The dashes are intentional: this article does not invent a sample rate or amount. Populate the worksheet from the actual shipment scenario and cited sources.

Step 7: apply stop conditions

Do not promote the result from “draft” to “reviewed” when any of these remain material:

The correct system behavior is to surface the boundary, not silently choose a cheaper or simpler total.

Step 8: preserve the review packet

Save the product facts, source links, calculator input snapshot, result breakdown, status/version, reviewer, and review date together. Rerun the scenario when the product, supplier, origin facts, entry date, or underlying source state changes.

SkuWatch's HTS reference, tariff calculator, accuracy verification method, methodology, and data-status page are designed to keep those steps connected. They remain reference tools; material classifications and entries should be confirmed with official sources and, where appropriate, a qualified 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.