Trade, Compliance & Delivery
Tariff-Change and Landed-Cost Scenario Planning
Tariff and landed-cost planning should use dated scenarios, not a permanent rate. Hold the assembly, quantity, classification facts, origin facts, value basis, destination, and delivery scope constant; then vary current treatment, freight, insurance, brokerage, taxes, fees, currency, inventory, and timing with a source and owner for each input.
Published: Updated:
Decision summary
What to carry into the decision
- Use the current official tariff schedule and responsible customs advice for the actual product and shipment.
- Separate classification, origin, customs value, duty treatment, and delivery term because each can change a different part of the model.
- Show base, changed-tariff, and logistics alternatives with the same product and demand baseline.
- Set triggers and owners for refreshing the model when policy, route, cost, or product facts change.
In this guide
- 1Freeze the product and transaction baseline
- 2Landed‑cost model
- 3Build comparable scenarios
- 4Do not treat classification as a price lever
- 5Set refresh triggers
- 6Common scenario errors
Use the sections in sequence, then turn the open items into one controlled build or sourcing package.
Freeze the product and transaction baseline
Record the assembly part and revision, construction, quantity and cadence, destination, importer instructions, classification and origin facts, customs-value basis, currency date, Incoterms rule and named place, package dimensions and weight, and shipment mode.
Do not compare tariff scenarios that also change the BOM, quantity, route, or delivery scope unless those differences are shown as separate variables.
Landed-cost model
Give every variable a source, date, owner, and refresh trigger.
| Product and transaction | Unit and tooling scope, quantity, value basis, currency, packing, shipping term, destination, importer, and timing. |
|---|---|
| Trade treatment | Classification, origin, current tariff schedule and measures, preferential or special-program analysis where applicable, duties, taxes, and fees. |
| Logistics | Pickup, inland legs, main carriage, fuel or accessorial assumptions, insurance, brokerage, terminal and destination charges, and delivery cadence. |
| Program effects | Inventory, safety stock, financing or working capital, minimum purchases, delay exposure, requalification, route change, and unused material. |
Build comparable scenarios
Use a small number of named scenarios that answer a decision.
- Base: current official and commercial inputs for the released assembly and planned route.
- Tariff change: alternative current treatment supplied by the responsible trade party while other variables remain fixed.
- Logistics change: another mode, cadence, handoff, or destination route with the same product and trade assumptions.
- Sourcing or design response: a controlled component, origin, or assembly change with its own validation, tooling, inventory, and effective-point cost.
Do not treat classification as a price lever
Classification follows the actual article and applicable rules. Give the importer or customs professional the product function, construction, connectors, voltage context, materials, origin facts, value, and supporting documents needed for a defensible determination.
If a design or sourcing change alters those facts, reopen the classification and origin inputs instead of carrying the old treatment into the new scenario.
Set refresh triggers
Refresh the model when the official tariff schedule, trade measure, customs ruling, or professional advice changes. Reopen it when the drawing, BOM, origin facts, delivery term, route, freight, currency, or review date reaches its agreed trigger.
Keep a version history so management can see which decision used which source and date.
Common scenario errors
Avoid publishing or using an undated fixed rate, combining duty and tax into one unexplained percentage, comparing different Incoterms scopes, or treating a broad country average as the cost for the assembly. Another error is showing precise totals while classification, origin, value, and route remain open.
Use ranges or clearly labeled assumptions where the underlying input is not yet confirmed, and assign the confirmation to the responsible trade or logistics party.