Rush order
Say yes to an urgent order only after checking stock, capacity and materials.
The problem
A key customer needs 200 units by Friday. Sales says yes on the call. Production finds out on Wednesday that a component is short and the main line is booked. The order ships late, and the work that was bumped ships late too.
The flow in Sundial
1. Check before you promise. Look at the item’s stock across warehouses and the projected quantity after open orders. Run the bill of materials against stock to see which components are short.
2. Book the order with a real date. Enter the sales order with the date production can meet, not the one that was hoped for.
3. Release the work order now. Create the work order straight from the sales order. Job cards land on the workstations, where the supervisor can see them alongside existing work.
4. Expedite the shortfall. Raise a material request for short components and turn it into a purchase order or a stock transfer from another warehouse.
5. Track and ship. Follow job card progress through the day; when the work order completes, pick and ship against the same order.
What the team sees
Sales sees exactly where the rush order is. The supervisor sees what else is queued on each workstation. Everyone works from the same record instead of phone calls.
Why it holds up
A rush order is handled with the same documents as any other order, so it never leaves the system to be managed by phone. Because availability, components and workstation queues are visible before the promise is made, saying yes is a decision with known trade-offs, and the work it displaces is visible on the same screens to the people affected.
With AI (coming to Sundial)
Sundial is designed so you can ask “can we make 200 units by Friday?” and get an answer drawn from stock, materials and workstation load, with an agent that drafts the work order for approval.

