Dynamics 365 SCM
Open purchase orders, planned receipts, supplier lead times and delivery performance, stock across locations.
Supply Chain
Find out a shipment is at risk while alternatives still exist
A disruption only becomes your problem when it touches an order you have already promised. The knowledge that a supplier is slipping usually exists somewhere: a late confirmation, a lead time that quietly grew, a delivery that missed its window. Coheed screens your open order book against those signals every morning and tells you which customer promises are exposed, while you can still re-source, re-plan, or warn.
- Systems combined
- Dynamics 365 SCMExact (ERP)
- Runs
- Daily at 6am
Sound familiar?
Teams bring us this use case when one or more of these is true.
- You learn about a supplier delay when the goods do not arrive.
- Nobody can quickly answer which customer orders depend on a specific supplier or article.
- Late deliveries are explained after the fact instead of anticipated.
- Re-sourcing starts once the delay is certain, which is exactly when it costs most.
How it works
Coheed runs this every morning across the whole open order book, not on a sample.
- 1
The open order book is assembled
Open purchase orders, planned receipts, and the customer orders that depend on them are linked across SCM and ERP, so every incoming shipment has a visible downstream promise attached to it.
- 2
Risk signals are matched to it
Slipping confirmation dates, lead times drifting above their norm, suppliers with a deteriorating delivery record, and any external disruption feed you connect are matched against those open orders.
- 3
Exposure is calculated per customer order
The result is not a general risk score but a list: these customer orders are exposed, through these articles, because of this supply signal, by roughly this many days.
- 4
Alternatives are proposed
Where an alternative exists, whether stock in another location, another supplier, or a partial shipment that protects the deadline, it is proposed alongside the risk instead of leaving the planner to find it.
Which data it uses
Only the fields this use case needs are read. Nothing is copied that the insight does not use.
Exact (ERP)
Open customer orders, confirmed delivery dates, article master data, supplier records.
Coheed
The link between incoming supply and outgoing promises, plus the lead-time baseline that makes drift detectable.
What changes
What a team notices once this runs. No invented percentages: the effect depends on your data and your process.
- Exposed customer orders are identified days or weeks before the delay lands.
- Customers are warned proactively, which is a very different conversation from an apology.
- Re-sourcing happens while there is still a choice.
- Supplier performance becomes measurable instead of anecdotal.
From insight to action
Supply Risk Agent
Available as an agent
Promoted from this insight, the agent prepares the mitigation: which orders are exposed, which alternatives exist, and which customers should be warned. Re-sourcing and customer communication are proposed for approval.
Mode: Human-in-the-loop
Every insight can stay read-only, run with human approval, or run autonomously. You decide per action type, and you can change it later.
FAQ
Frequently asked questions
Where do the disruption signals come from?
Two places. Internal signals, such as drifting lead times and slipping confirmations, come from your own systems and need no extra setup. External feeds, such as carrier or port disruption data, are connected per customer where you have a source.
Does this work without an SCM system?
Partly. With ERP alone you still get lead-time drift and supplier reliability on purchase orders; the stock and capacity side of the analysis needs SCM data.
How is 'exposed' decided?
By whether the projected receipt lands after the date you already confirmed to the customer, allowing for your handling time. That threshold is configurable per product group.
Can it warn the customer automatically?
It can prepare the message, and sending stays a human decision by default. Most teams want to review the first dozen before widening that.
Built on these maturity levels
Other use cases
Predictive Customer Lifetime Value
Score churn risk and future value per account by combining CRM engagement decline with ERP order frequency and value trends.
Lead-to-Quote Readiness
Surface correct ERP pricing, live stock, discounts, and customer agreements on every new CRM lead so sales can quote immediately.
Order Exception Monitoring
Catch stock gaps, unrealistic delivery dates, pricing errors, and missed agreements after the order, before the customer notices.
See this on your own data
Tell us your ERP, CRM, and SCM stack and we will show what this use case looks like on your systems.