In May 2026, procurement teams are operating in an environment where the underlying policy assumptions change faster than sourcing contracts can be renegotiated. The court ruling that invalidated one set of tariffs in February was followed by another ruling invalidating a different set in May. An active investigation against sixteen trading partners is underway. A US-China trade truce is set to expire in November. No procurement model built on stable tariff assumptions is fit for this environment.
The instinct is to build better scenario models. More scenarios. More sensitivity analysis. More what-if planning. This instinct is understandable but misses the structural problem: the bottleneck is not modelling — it is the decision process. Procurement teams can generate twenty tariff scenarios by Tuesday afternoon. What they cannot do is make a documented, approved, auditable sourcing decision in response to those scenarios before the board meeting on Wednesday.
The real problem is not forecasting — it is decision governance
A procurement decision under tariff uncertainty has several components: the exposure assessment (which inputs, which suppliers, which tariff rates), the alternative analysis (alternative suppliers, reshoring options, inventory buffers), the cost-benefit calculation, the approval chain (who authorises a sourcing shift of what magnitude), and the documentation trail (what was decided, by whom, on what data, at what time).
Most procurement teams have the first two components reasonably covered — they have the modelling tools and the supplier relationships. What they consistently lack is the decision infrastructure: the structured process that moves from scenario analysis to approved, documented decision in a defined timeframe, with accountability at each step.
When policy changes weekly, the organisations that manage best are not those with the best models. They are those with the most disciplined decision processes — the ones where every sourcing decision has a named owner, a structured approval pathway, and a documented rationale that can be reviewed six months later when a regulator, auditor, or board asks why a particular sourcing decision was made in May 2026.
The 90-day planning horizon
One practical frame that has proven useful with procurement teams in this environment: assume no tariff assumption is reliable beyond 90 days. Court rulings, executive orders, and bilateral negotiations are all operating on cycles shorter than most sourcing contracts. The planning job is not to predict what tariffs will be in Q3 — it is to build a decision process that can respond to a policy change within 48–72 hours without a governance breakdown.
That timeline is not a reason for paralysis. It is a reason to build procurement decision infrastructure that is designed for volatility — where the process does not depend on policy stability to function.
Three things procurement teams need in this environment
1. Named decision owners with response SLAs
Every tariff-triggered procurement decision needs a named owner — not a team, not a committee, a person — who is responsible for evaluating it within a defined timeframe. When a policy change triggers an exposure alert, the question "who is handling this?" should have an immediate answer. Ambiguity about ownership is the single most common reason procurement responses are slow. Define ownership by category and decision type before the next policy event, not during it.
2. Documented decision rationale at every step
When a sourcing decision is made under tariff uncertainty, the rationale should be documented at the moment of decision: what the exposure assessment showed, what alternatives were considered, what the cost-benefit calculation produced, who approved it, and at what level of authority. This documentation is not an overhead — it is the operational record that allows you to learn from decisions, defend them in audits, and adjust when the next policy shift occurs.
Procurement teams that make decisions through email chains and verbal approvals in meetings cannot reconstruct this record six months later. Teams that make decisions through a structured, ERP-connected workflow can.
3. A direct connection from decision to ERP execution
The most common point of failure in procurement governance is the gap between an approved decision and ERP execution. The approval happens in an email thread. Someone then has to log into the ERP, navigate to the procurement module, and manually initiate the purchase order or supplier change. In a fast-moving tariff environment, this gap introduces both execution latency (the decision was approved but not executed before the next policy change) and governance risk (the approved decision and the ERP action are not connected in a way that can be audited).
Closing this gap means connecting the approval workflow directly to ERP execution — so that an approved procurement decision initiates the ERP write immediately, with the approval context, data inputs, and authorisation chain all captured in the same record.
What this means for ERP-connected procurement teams
For mid-market manufacturers and distributors running on Dynamics 365 Business Central, the infrastructure for tariff-resilient procurement governance is available today. OpsGrid — in live beta — is IntelliconnectQ's decision infrastructure layer for Business Central, providing the structured decision workflow — signal to owner to approval to ERP execution — with full audit trail at every step.
When a tariff exposure signal fires, OpsGrid routes it to the named decision owner with the relevant BC data: affected suppliers, current inventory levels, open purchase orders, and cost exposure. The owner evaluates, initiates the corrective action within the governed approval tier, and the ERP write happens — all in one connected workflow, all logged to a decision audit trail.
The tariff environment of 2026 will not stabilise quickly. The procurement teams that navigate it best will not be those with the most sophisticated forecasting models. They will be those whose decision process can respond to a policy change in hours rather than days, with governance documentation that survives any audit. That is an operational infrastructure problem, and it is solvable.
If your procurement team is currently making tariff-response decisions through email and weekly review meetings, start a conversation with us about what a governed decision workflow would look like in your Business Central environment.