Get a demo

Tariff scenario modeling

Run tariff scenarios across your product catalog. Calculate landed cost and margin impact per SKU under multiple rate scenarios in one flow.

Get a demo

The prompt

I want to model tariff scenarios across my product catalog. Can you build me a flow that reads HTS codes and costs from a CSV, runs each SKU through OpenAI to apply multiple tariff rate scenarios, calculates landed cost and margin impact per scenario, and outputs a side-by-side comparison table?

Just copy and paste the prompt into a new Parabola flow to get started.

What Parabola builds

A workflow with seven steps you can edit:

1. Pull the catalog. SKU, HTS code, country of origin, current landed cost components, current sell price. The flow ingests it from a CSV, NetSuite, or your PLM.

2. Standardize the cost stack. Product cost, freight, insurance, duty, fees. One column per component so each scenario can isolate the tariff impact.

3. Apply scenario logic. Baseline rate. Scenario A: 10% across the board. Scenario B: 25% on country of origin X. Scenario C: USMCA preferential treatment. Each scenario is a row in a rules table, not a code change.

4. Calculate landed cost per scenario. Product cost plus the scenario duty plus freight plus fees. Per SKU, per scenario.

5. Calculate margin impact. Compare landed cost to current sell price. Output the margin percentage and the dollar erosion per SKU.

6. Aggregate by category. Roll up to brand, category, country of origin, and supplier. Finance and sourcing read the same view.

7. Output the side-by-side. One row per SKU, one column per scenario, with margin and dollar impact. Filterable to the SKUs the team needs to act on first.

Why teams stop doing this manually

Tariff policy moves faster than the planning cycle. A new rate gets announced on Tuesday. By Thursday, finance, sourcing, and merchandising want to know what it does to margin. The analyst pulls the catalog, looks up the HTS codes, applies the new rate by hand in a spreadsheet, and answers the question by Friday.

Then the rate gets revised. Or a second country gets added. Or sourcing wants to model a shift to a different origin. Each new scenario means another spreadsheet, another set of formulas, another reconciliation against the original. By the third revision, nobody trusts the numbers because the spreadsheet is held together with VLOOKUPs and a prayer.

The work is precise. Get the HTS code wrong and the duty math is wrong. Get the country of origin wrong and the preferential treatment does not apply. Get the cost stack wrong and the margin number is misleading. Putting this into a flow means the rules live in one place, the scenarios run on demand, and the team plans against numbers the audit team can also verify.

How it works

Step 1. Paste the prompt.

Open Parabola, paste the prompt in section 2, and let it ask follow-up questions about your cost stack, your HTS coverage, and the scenarios you want modeled.

Step 2. Connect your data.

Catalog CSV, NetSuite item master, PLM, and the current tariff schedule. Plus any preferential trade program rules that apply.

Step 3. Run it on demand.

Each time policy changes or sourcing wants a new scenario, the flow rebuilds the side-by-side. Save the snapshot for audit. Rerun next week.

Related prompts

FAQ

Can the flow run multiple scenarios at once?

Yes. Add a row per scenario to the rules table. The flow runs each scenario in parallel and outputs the side-by-side. Five or ten scenarios at a time is normal.

What about preferential trade programs like USMCA?

Configure the rule as a scenario. If the SKU meets the country-of-origin and qualifying criteria, the flow applies the preferential rate. Otherwise it applies the standard rate.

How does the flow handle SKUs without an HTS code?

The flagged list. Anything without a code gets pulled into a review queue. Run the HTS classification flow first if you need fresh codes, then feed the output into this flow.

Can finance see the impact in dollars, not just percent?

Yes. The output shows both percent margin change and absolute dollar erosion per SKU. Roll up to category or brand for the planning view.

How is this different from running it in a spreadsheet?

A spreadsheet works for one scenario. It breaks when policy moves three times in a quarter and sourcing wants country shifts on top. The flow runs every scenario on demand against fresh data, with every rule documented so the audit team can verify the math.
Model tariffs before they move.
Paste the prompt, point it at your catalog and cost stack, and run scenarios on demand.
Start for free