Tariffs Changed. Which Orders Are Exposed?

A supplier emails a revised price list: a new tariff on a machined component, effective next month. Three POs for that part are still open, and one shipment is already on the water.

Purchasing sees the email first. Finance sees it weeks later, when an invoice doesn't match its PO, and sales hears about it when the margin report comes in.

A tariff change is a chain of exceptions

The new rate is rarely the hard part. The hard part is working out what it touches among the commitments you've already made:

• Open purchase orders priced on the old cost
• Shipments in transit that may land under new terms
• Production runs that depend on the affected parts
• Invoices that won't match their POs
• Customer orders and contracts priced on old assumptions

Each lives somewhere different: the ERP, supplier email, a carrier update, an invoice, a contract. Nobody sees the whole chain, so people rebuild it by hand, one spreadsheet at a time.

Five places tariff impact shows up

1. Supplier price changes on open POs. Which open POs does the new price apply to, which have already shipped, and does an agreement cover them? The goal is a short list of POs to confirm or renegotiate, not a folder of price notices.

2. Sourcing decisions. An alternative supplier is only an option if it meets the spec, is qualified and can deliver in time for the jobs that need it. Price alone doesn't decide it.

3. Inventory and production. Which jobs depend on the affected parts, how long current stock covers them, and when a delay or a supplier switch turns into a shortage.

4. Invoice and landed-cost variances. When an invoice doesn't match the PO, finance needs to know why: tariff, supplier price change, freight or a PO error. Each one has a different fix.

5. Customer commitments and margin. Which open orders and contracts are exposed, whether a price-adjustment clause applies, and who decides to absorb, pass through or re-source.

These five are connected. One tariff change can start in procurement and end in a conversation with a customer.

An example

Illustrative composite, not a customer case.

A supplier announces a 12% price increase on a machined housing, effective the first of the month. Of five open POs, two have already shipped, one is covered by a fixed-price agreement through year end, and two are exposed.

One of the exposed POs feeds a run for a customer order priced last spring. Working that out means checking the ERP, the agreement, the carrier update and the production schedule, then emailing finance and sales.

Done once, it's an afternoon. Done for every affected part, every time rates move, it becomes someone's full-time job.

How LevelOneAI helps

LevelOneAI works across the ERP, email and documents you already use. It doesn't replace them.

• Connect the evidence. Supplier notices, POs, shipments, invoices and agreements come together for each affected item.
• See what's exposed. Which POs, jobs and customer orders a change affects, and what they're worth.
• Decide with context. The options side by side, and who needs to approve.
• Resolve it as a team. Each issue has an owner and tracked follow-ups, and it closes when there's evidence it's resolved. Nothing changes in your ERP without approval.

What it doesn't do: tariff classification and country-of-origin decisions stay with your trade documentation and compliance experts. LevelOneAI connects their answer to the operational work it sets off.

Try this week

• Pick one part hit by a recent tariff or price change. List its open POs, shipments in transit and the customer orders it feeds, and time how long it takes.
• Pull last month's invoice variances and tag each with a cause: tariff, price, freight or PO error.
• Ask who owns the decision to absorb or pass on a cost increase, and how they find out it's needed.

See how this works for supplier operations, or walk through the supplier delivery demo.

Connect the evidence. See what needs attention. Resolve it as a team.