A small panel opened from the order header. Enter the new date and the reason ('mill backorder', 'truck breakdown') and the order records a revised expected delivery, keeps the FIRST promised date untouched, and appends to a delay history of promised → revised → reason → when. The header then shows 'due 22 Sep · originally 4 Sep' and how many times it has moved.
Also called: supplier keeps pushing the date · late delivery · delivery date moved · reschedule delivery
- 1original_expected is set once, from the first promise, and never overwritten
- 2delay_history is an append-only list of every move
- 3The order status becomes 'delayed'
- 4The panel opens directly under the button that summoned it
- 5Three dates are kept apart: when the order was sent, what was promised, and when it actually arrived
Migration 217: 'expected_delivery is overwritten in place, which erases the original promise — exactly the record you need to show a supplier is habitually late.' Migration 220 adds why three dates are needed: 'The gap between the last two is the supplier's real reliability, and you cannot compute it from a status.' The panel placement is 'This used to open three sections down… so clicking "Report a delay" appeared to do nothing until you scrolled. A panel belongs where the control that summoned it is.'
- Overwriting the promised date erases the evidence of habitual lateness
- A supplier who moves a date four times looks identical to one who delivers on time
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →