Planning Use SEO page 2

Tariff calculator for US import planning

Planning Use only. Broker review required for Entry Use.

A tariff calculator is useful when it tells you what assumptions went into the number. Most calculators do not.

They ask for a code, a country, and a value. Then they return a neat percentage or a landed-cost estimate. That feels helpful, especially when a shipment is moving and someone wants a quick answer. But the number can be wrong for boring reasons: the code is weak, the origin is not proven, Section 301 applies, the invoice value misses assists, or the product is described too loosely.

The calculator is not the problem. The hidden assumptions are.

TariffCase should treat a calculator result as a Planning Use estimate with a file attached to it, not as a filing answer.

quick answer

Use a tariff calculator to estimate duty exposure before the shipment moves. Do not use it as Entry Use classification. A good calculator should show the HTS Candidate, country of origin, customs value, base duty, extra tariff programs, fees, and the facts that still need review.

If any of those inputs are uncertain, the output should say so.

That is the whole difference between a helpful calculator and a false sense of control. The helpful version says, "Here is the current estimate, and here is what could break it."

what the calculator needs

A tariff calculation is only as good as the product file behind it.

Collect these inputs before trusting the estimate:

HTS Candidate or supplier HS code.
Full product description, not a short SKU title alone.
Country of origin and the facts behind that origin claim.
Invoice value, currency, quantity, and unit of measure.
Freight, insurance, assists, royalties, tooling, or packing charges when they affect customs value.
Shipment date or expected entry window.
Product photos, spec sheet, bill of materials, or product page.
Any known Section 301, AD/CVD, quota, PGA, or special program exposure.
Past broker entry or ruling reference, if one exists.

If the calculator does not ask for these facts, it should at least warn the importer that the result is thin.

the duty stack

The duty stack is the set of charges that may sit on top of the product.

Start with base duty from the HTS line. Then check whether the origin and HTS line trigger an extra tariff program. China-origin goods may need Section 301 review. Some products may need AD/CVD checks. Certain goods may have quotas, special program rules, or agency requirements. Merchandise Processing Fee may also matter.

This is why one landed-cost number can be misleading. Two products with similar names can sit in different HTS families. Two shipments with the same code can have different exposure if the origin changes.

The estimate should show the stack, not hide it.

missing facts

Mark the estimate incomplete when one of these facts is missing:

HTS Candidate has not been checked against product facts.
Supplier provided only a six-digit HS code.
Country of origin is copied from the invoice but not supported.
Product composition is unknown.
Product function is ambiguous.
Customs value excludes costs that may need to be added.
Section 301 or another trade remedy has not been checked.
A prior shipment used a code, but the product version changed.

An incomplete estimate is still useful. It tells the team where the risk sits.

The bad outcome is a clean-looking landed-cost number that nobody can explain later.

authority sources

Use official sources before treating the estimate as reliable:

USITC gives the tariff language. CROSS can show how CBP handled similar facts. USTR pages matter when Section 301 exposure is in play. CBP guidance helps keep the ruling and review boundary clear.

Vendor calculators and freight tools can be useful for comparison. Do not treat them as authority.

what TariffCase should calculate

For Planning Use, TariffCase should calculate a range or estimate that is tied to evidence.

The output should show:

Product summary.
HTS Candidate used for the estimate.
Base duty.
Origin assumption.
Trade remedy checks.
Value assumptions.
Missing Facts.
Authority Sources.
Broker review status.

That last line matters. A calculator that says "review needed" is more honest than one that pretends every input is settled.

when the number changes

Expect the tariff estimate to change when the facts change.

The product material changes. The supplier ships a kit instead of a single item. The origin moves from one country to another. A new ruling points away from the old code. The invoice value leaves out tooling. USTR treatment changes. A broker spots a chapter note that nobody on the ecommerce team knew existed.

None of that means the first estimate was useless. It means the estimate was planning work, not the final word.

internal links

questions importers ask

Can a tariff calculator tell me the exact duty I will pay?

It can estimate duty exposure for Planning Use. The number depends on classification, origin, value, shipment facts, and current tariff programs. Broker review is needed before Entry Use.

Why does the supplier's code change the estimate so much?

Because the HTS line drives the base duty and can affect trade remedies. If the supplier code is wrong or too broad, the calculator is doing math on a weak input.

Should I calculate duty before or after ordering?

Before ordering, if the margin is tight. A duty surprise after the purchase order can turn a profitable SKU into a bad shipment.

What should the calculator output include?

It should include the estimate, the inputs, the Missing Facts, Authority Sources, and the review status. A number without that context is too easy to misuse.

planning boundary

This tariff calculation is a planning artifact. It is not an Entry Use classification, not a binding ruling, and not a legal opinion. The importer remains responsible for reasonable care and must obtain broker or customs authority review before filing.

Turn this search into a file

Run a free Duty Surprise Scan, then build a Planning Use Classification Record when the Missing Facts matter.

Start scan today →