Tariff pricing for distributors: using price-change and landed-cost history

Why tariff rounds expose weak price-change records#

Tariff rounds expose weak price-change records because distributors must pass cost changes through quickly, repeatedly and differently by customer, while most ERPs only remember the current price. When a supplier increase lands, the old cost is overwritten, the reason lives in an email, and the customer notice sits in someone's sent folder.

The next round then starts from scratch. Finance cannot show which customers accepted the last increase, which contract accounts were exempt, or whether a surcharge was removed when a duty changed. Sales reps negotiate from memory, and margin leaks surface only at month-end close.

The price-change record: what to keep#

The price-change record is a structured entry for each cost or price event, kept outside the ERP's current-price field so history is never overwritten. A spreadsheet works if it is disciplined; a table in the ERP or a data warehouse is better if IT can build one.

Keep the record at the level the decision was made. If a tariff hits a whole product family, one record per family with the item list attached is easier to maintain than one per SKU.

Building landed cost history from the ERP and broker entries#

Landed cost history comes from records most distributors already have but rarely join: purchase orders, receipts, freight invoices, customs broker entry documents and the ERP's cost layers. Many distribution ERPs can allocate landed cost to receipts, but check how your system stores it and whether history survives a cost update.

Classification and origin matter because a tariff change usually applies by tariff classification and country of origin. When those fields are stored with the cost, finance can answer which items a new tariff touches without rebuilding the analysis each time.

• 1Pull purchase order and receipt history with item, quantity, supplier and date.
• 2Attach inbound freight invoices to receipts, including drayage or transload charges.
• 3Add duty and broker fees from customs entry documents, by entry and line.
• 4Record the tariff classification and country of origin used for each item.
• 5Calculate landed cost per unit per receipt, keeping components separate.
• 6Store each period's result so later cost changes cannot overwrite it.

Surcharge or list price increase? A decision table#

The choice between a surcharge and a list price increase depends on whether the cost is likely to last, what customer contracts allow and whether the systems can manage a surcharge cleanly. Whatever the choice, the decision and its reason belong in the price-change record.

A surcharge that nobody can remove later turns into a hidden price increase, which customers notice and remember at the next negotiation.

How AI pricing tools use price-change history#

AI pricing tools use price-change history to learn how customers respond to increases, which no list price file can show. With linked records, a model can estimate which segments accept an increase, which negotiate and which move volume elsewhere.

The same records support narrower tools: an agent that drafts customer notices consistent with past wording, a checker that flags orders shipped at an old price after the effective date, and a quote assistant that warns a rep when a quoted margin falls below current landed cost. Developers building finance and pricing agents look for exactly this kind of linked history.

The weak point is usually the acceptance outcome. A log that records the new price but not whether the customer accepted, pushed back or quietly moved volume to a competitor shows what the distributor tried, not what worked. Asking reps to close each notice with a one-word outcome fixes most of the gap.

Illustrative: an electrical distributor through repeated tariff rounds#

Illustrative: a fictional regional electrical distributor runs Epicor for orders and inventory, keeps contract pricing in the ERP and handles price increases in spreadsheets emailed between purchasing and sales. Customer notices go out from reps' inboxes using whatever template each rep has saved.

After a tariff round in which several contract accounts kept buying at old prices, the CFO sets up a price-change log, adds classification and origin to the item master, and links freight and broker invoices to receipts. Notices move to a shared template with a version number, and reps record each customer's response.

In the next round, finance identifies affected items quickly, applies a surcharge to the items most likely to reverse, and catches orders shipped below current landed cost before month-end close. The log later becomes the core of a pricing history the company considers licensing.

Licensing price-change history: what SourceX looks for#

Price-change and landed-cost histories can be licensed when supplier and customer agreements allow it, because they show real pricing decisions and their outcomes. The distributor licenses the history rather than selling it, and keeps ownership throughout. Supplier costs and price lists are often confidential, so preparation usually tokenizes suppliers and customers, generalizes items to categories and may express costs as changes rather than absolute values.

Counsel may also weigh competition-law questions, since current, competitor-identifiable prices shared through a common tool can draw scrutiny. Older, aggregated histories generally raise fewer concerns than current item-level prices, which is one reason many packages exclude recent periods.

SourceX reviews such a history through the SourceX five-step transaction and uses the SourceX Enterprise Data Value Framework to describe it. The relevant drivers include human-generated signal in the pricing decisions, recency, data cleanliness and rights, weighed against the preparation cost of masking supplier terms. The SourceX Evidence Packet then records the rights relied on, the permitted use and what was masked.