Planning Use SEO page 353

Duty Stack calculator for importers

Planning Use only. Broker review required for Entry Use.

A duty stack calculator is useful only when the inputs are real. Base duty, Section 301, antidumping or countervailing duty flags, fees, origin, value adjustments, and shipment timing can all change the number. A fast calculator that skips classification and origin is a guess with a neat interface.

Use this page to turn calculator intent into a source-backed Planning Use file.

quick answer

For "duty stack calculator", collect the product description, HTS candidate, origin evidence, customs value, assists, freight and insurance treatment, quantity, shipment date, trade-remedy flags, supplier code, and source notes. Then calculate ranges for Planning Use and route the record to broker review before Entry Use.

Do not show one duty number when the HTS candidate or origin is still unsupported.

facts to collect for a duty stack

Collect:

Product name, SKU, model, photos, specs, composition, function, and intended use.
HTS candidate family, supplier HS or HTS code, and rejected alternatives.
Country of origin evidence and any manufacturing steps that affect origin.
Invoice value, currency, quantity, assists, royalties, freight, insurance, and Incoterms.
Base duty, merchandise processing fee, harbor maintenance fee when relevant, and any preferential claim.
Section 301, AD/CVD, safeguard, quota, exclusion, or special duty question that needs review.
Authority sources checked and the date of the check.
Broker review status and Missing Facts that can change the stack.

Keep the calculator output tied to the evidence snapshot that created it.

missing facts

Mark the file incomplete when:

HTS candidate support is weak.
Origin is assumed from the ship-from country.
Value adjustments outside the invoice are unknown.
Trade-remedy exposure has not been checked.
The supplier code is six digits or unsupported.
The shipment date may change the applicable treatment.
No authority source has been logged.

These gaps can make a calculator output look cleaner than the file deserves.

HTS candidate notes

Build candidate rows before calculating. Each row should show base duty, origin treatment, trade-remedy notes, value assumptions, and Missing Facts. If two candidate families remain plausible, show both ranges instead of forcing one result.

Rejected candidates should stay in the file with the fact that rejected them.

authority sources

Use USITC HTS for duty text. Use CBP CROSS for classification support. Use USTR for Section 301 treatment. Use CBP guidance and 19 CFR 177.2 when the issue needs a ruling packet.

planning path

Start with product evidence, then HTS candidates, origin, customs value, fees, and trade remedies. Calculate only after those inputs are tied to sources.

For TariffCase, the useful output is not "duty is X" by itself. It is "duty is X if these facts hold; here are the facts that still need review."

Save the assumptions beside the number: candidate line, origin, value basis, fees included, and trade remedies checked. Without that, a calculator result cannot be reviewed later.

Keep the version date visible.

questions importers ask

Why avoid the supplier duty rate by itself?

Because supplier codes often miss origin, value, and trade-remedy facts.

Should the calculator show ranges?

Yes, when candidate codes or origin facts are still open.

internal links

planning boundary

This duty stack calculator page 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 →