Decision accountability in supply chains

Where supply-chain decisions lose their owner

Consequential decisions are now taken by people, by your own algorithms and by vendors' agents, in different systems. A planner approves an expedite by email, an MRP run creates purchase orders, a vendor's procurement agent buys spot. Each system knows its own part. Nobody holds the whole.

Aidecis gives them one authority model and one record: who or what may decide, within which limits, and what each decision led to.

Read the eleven cases

Eleven cases

Where accountability breaks down.

Each case starts as an everyday operating decision. The risk appears when nobody can say who or what was allowed to take it, within which limit, and what it led to. For each case: who took the decision, and what Aidecis does. With enforced control, Aidecis acts before the action runs, where your own integration checks its single-use grant. With observed control, it acts after the action ran.

01

Approval limit exceeded. Decision proceeds anyway.

A reroute costs 40% more than the planner's authority allows. It ships anyway. Finance notices three weeks later.

Who decided: a planner. With enforced control, the booking goes to the right approver first, and your TMS integration runs it only with Aidecis's single-use grant. If the booking was made in the TMS directly, observed control flags it as over the limit within minutes. It does not stop the booking.

02

Local decision. Global consequences nobody saw.

A supplier swap cuts cost at Plant A. It breaks a quality rule at Plant B and a customer specification at Plant C. Nobody sees it until the complaints arrive.

Who decided: a buyer, or the sourcing logic in your ERP. Aidecis checks the swap against the rules and limits you have registered for every site it touches, not only the site that proposed it, and routes it to the owners of those sites. A rule that nobody registered, it cannot check.

03

Missing or stale information. Decision made anyway.

A reroute is approved without current carrier capacity. A production change goes live without the latest quality tolerances.

Who decided: a person, or your own planning algorithm, on data nobody had checked. Aidecis shows how fresh and complete the evidence is for each decision. Where your policy requires current data, a proposal waits for review until the evidence is there.

04

Rule broken. Discovered after execution.

A discount breaks a customer exclusivity clause. A routing breaks a service commitment. An expedite contradicts policy. The damage is done.

Who decided: a person, an algorithm or an agent, each in its own system. Aidecis checks the decision against the policies and limits you have registered. A clause that lives only in a contract is not checked until you register it as a rule.

05

No clear owner. Decision stalls or lands wrong.

An approval bounces between logistics, finance and operations. No one knows who decides. It stalls, or whoever has access decides it quietly.

Who decided: whoever had access. Aidecis registers an owner and a limit for every decision type and site, and for every algorithm and agent that takes part. Where no owner is registered, Aidecis shows the gap and asks for one to be assigned.

06

Same situation, different decisions across sites.

Site A approves expedites at a 15% cost premium. Site B at 8%. Site C does not allow them. No one knows why they differ.

Who decided: people at three sites, under three unwritten rules. In one authority model, each site's limit is written down with its owner. Aidecis shows where sites differ, so justified differences stay and drift becomes visible.

07

Same exception approved five times this month.

People keep overriding the approval process for the same disruption, or bypass compliance because it adds three days to a two-day window.

Who decided: the same approvers, again and again. Every exception is in the decision record with its reason. Aidecis shows recurring exceptions to the process owner, so a workaround becomes a signal to fix the rule.

08

Disruption hits. Wrong trade-off gets made in panic.

A supplier fails. A port closes. The team picks the fastest option, and it costs 40% more or breaks a commitment.

Who decided: a person under time pressure. Aidecis prepares the options your policy allows, weighed against the service, cost and resilience priorities you have set, and routes the choice to the person with the authority to make it. The record keeps the response time, so you can measure it against your baseline.

09

This decision works 47 times. Could a bot handle it now?

Over twelve months, the team takes the same decision with 95% consistent outcomes and few exceptions.

Who decided: people, in every case. Aidecis computes from the run history whether this decision is stable enough to move to a bot, and tells the owner. Nothing changes until the owner accepts it. Where your organisation is still at a basic or digital stage for this kind of decision, it proposes a bounded pilot with people approving, not a bot.

10

Approval given. Order never reaches the warehouse.

Finance approves an expedite. The planner is told. The request never reaches the carrier, because the message format does not match the WMS interface.

Who decided: finance, correctly. The execution failed. Aidecis reads the execution back from your systems and reconciles it against the approval, so the record shows whether it executed. With enforced control, your integration runs only the approved action, with a single-use grant.

11

A vendor's agent raises a PO above its limit.

A vendor's procurement agent raises a purchase order above the limit you would have set. Its own log shows the action. Nobody else sees it against your authority rules.

Who decided: a vendor's agent, with its own credentials in your ERP. With observed control, Aidecis registers the agent with an owner, a role and a limit, reads its writes from the ERP's change records and flags the breach within minutes. It does not stop the order. To hold such orders before they run, you move the agent to enforced control: it submits its proposals to Aidecis, and your ERP integration executes only what carries a valid single-use grant.

The pattern

One authority model. One decision record. Across people, algorithms and every vendor's agents.

The accountability gap no longer sits only between people. It runs across your people, your own algorithms, such as MRP runs, optimisers and replenishment rules, and the agents that vendors now ship into procurement, logistics and planning. Each vendor ships an audit trail for its own agent only. None of them holds a record across the others.

Aidecis holds that record. It sets who or what may take each decision type, within which limits and in which mode, and links every decision to its outcome.

With enforced control, your own integration checks Aidecis's single-use grant before it executes: without a valid grant, the action does not run. For agents and algorithms that write in their own systems, Aidecis detects the write, checks it against the actor's role and limits, and flags it within minutes.

Observed control never prevents an action; it shows it.

You choose which actors move from observed to enforced.

Start with one decision

Build the control pattern that scales across your network.

Start with one consequential decision type. Procurement is often the best first place, because that is where vendors' agents arrive first. The first slice is read-only, and a shadow result is a valid outcome.