Use case · Feedstock shock repricing
Turn a feedstock shock into a reviewable repricing path
A feedstock move becomes a defensible repricing action only after the affected product and account relationships are identified, contract eligibility and notice timing are checked, exposure is calculated from approved inputs, and a commercial owner approves the proposed action. Northra is designed to keep that evidence path together; it does not turn a market movement into an automatic customer price change.
- Content owner
- Northra
- Last reviewed
- 2026-08-03
Trigger
When this workflow starts
An agreed feedstock or market series moves outside the operating range that the commercial team uses for review, or a material supplier change creates a new cost exposure.
Operational gap
Why the manual path breaks down
Teams often hold market data, formulation or product relationships, contracts, ERP extracts, and account ownership in separate systems. The difficult work is not spotting the market move; it is proving which customer actions are permitted, timely, economically material, and supported by the same evidence.
Required evidence
Inputs that must be named before analysis
- INPUT 01The agreed market or feedstock series, observation date, unit, currency, and licence boundary.
- INPUT 02A curated dependency path from feedstock or intermediate to product family, SKU, contract, and customer account.
- INPUT 03Relevant price-adjustment clauses, index references, lags, caps or floors, notice windows, and approved extraction versions.
- INPUT 04The approved volume, current price, cost, currency, period, and account scope needed for the commercial calculation.
Decision path
A reviewable workflow, not an automatic action
- 01
Qualify the signal
Confirm the series, observation, unit, currency, timing, and materiality rule before using the movement commercially.
Evidence retained: Source identifier, observation time, value, unit, licence status, and review rule.
- 02
Trace dependency exposure
Follow curated feedstock-to-product relationships and identify the contracts and accounts inside the approved scope.
Evidence retained: Dependency-map version, relationship status, affected products, and account scope.
- 03
Check contractual eligibility
Evaluate the applicable clause, reference index, lag, threshold, cap or floor, and notice requirement before proposing action.
Evidence retained: Contract version, clause basis, confirmation state, eligibility result, and next valid window.
- 04
Prepare the action case
Calculate the scoped exposure and rank candidate actions without presenting an estimate as booked or recovered value.
Evidence retained: Calculation version, assumptions, affected volume, current state, and uncertainty notes.
- 05
Route to the owner
Give the accountable commercial owner the rationale, evidence, caveats, and proposed next step for review.
Evidence retained: Owner, decision state, approval record, and any rejected or deferred reason.
Decision output
What the owner receives
A ranked, source-linked action brief showing the affected product and account, contractual basis, timing, calculation assumptions, uncertainty, accountable owner, and approval state. It is an internal decision aid until a person approves the permitted export or customer action.
Human gate
Where authority remains
A domain or commercial owner verifies the dependency, clause interpretation, calculation inputs, customer context, and timing. Northra does not autonomously approve, send, or write a price change back to a source system.
Uncertainty
What the result must not hide
- Unconfirmed dependency links remain review items rather than assumed exposure.
- Unconfirmed or missing clause evidence produces an ineligible or needs-review state, not a confident recommendation.
- Missing volume, cost, currency, or period context is shown as unavailable; it is not filled with a model guess.
- A market movement can support a review without proving that a customer will accept a change or that value will be realized.
Measurement
How to tell whether the workflow created value
Sources and boundaries
Public references used on this page
- Producer Price Indexes (opens in a new tab)
U.S. Bureau of Labor Statistics. Example of a public, versioned price-index source; a customer pilot uses only agreed series and licence terms.
- Industrial producer price index overview (opens in a new tab)
Eurostat. Public context for how producer-price movements are defined and published.
- Northra trust center
Northra. Public operating boundaries for source traceability, data handling, bounded AI, and human authority.
Continue the review