Supplier delays
Know a supplier is late before your customer does.
The problem
A key component is three days late. Production finds out on the morning it was needed. The buyer knew the supplier was "usually a bit late", but that knowledge lives in one person's head and never reaches the plan.
The flow, step by step
1. Dated purchase orders. Every PO line carries a required-by date in Buying. That date is the commitment the supplier is measured against.
2. Pending view. The purchase order analysis report lists open lines with ordered, received and pending quantity, and the days since they were due.
3. Follow up. Buyers update expected dates on the PO after each supplier conversation, and log the note on the PO's timeline.
4. Effect on demand. Inventory's projected quantity reflects what is on order, so planners can see which open sales and work orders depend on the late PO.
5. Scorecard. Supplier scorecards score suppliers on criteria such as on-time delivery and rejected quantity, on a regular period.
6. Standing and action. Each score maps to a standing. A poor standing can warn buyers when they raise a new RFQ or PO for that supplier, or block it.
What the team sees
A list of late purchase order lines, oldest first, with the supplier and the work orders or sales orders waiting on them. A supplier page showing score history period by period.
In the Kestrel Workspace sample, one hardware supplier's on-time score falls from 92 to 71 over two quarters, and new POs to them now show a warning to the buyer.
With AI (coming to Sundial)
Coming to Sundial: ask "what will we miss this week if supplier X is five days late?" and get the affected orders in plain language. An agent could draft the chaser email and wait for the buyer to send it. Roadmap, not shipped.

