USE CASE

Make to order

Start production only when a customer has ordered, and plan materials from that order.

The problem

Custom or configured products cannot sit in stock. Each order needs its own materials, its own schedule and a delivery date the shop floor can actually meet. When planning lives in spreadsheets, sales promises dates that production has never seen.

The flow in Sundial

1. Confirm the sales order. The order records the item, quantity and delivery date agreed with the customer.

2. Create a production plan from it. Pull the sales order into a production plan. Sundial explodes the bill of materials and shows which sub-assemblies to make and which raw materials are short.

3. Raise what is missing. From the plan, create material requests for the shortfall; buying turns them into purchase orders.

4. Release work orders. Create work orders linked to the sales order. Their operations become job cards on the workstations that will run them.

5. Finish, deliver, bill. Completing the work order moves finished goods into stock against the order, ready for the delivery note and invoice.

What the team sees

Sales sees the production status of each order it sold. Production sees orders with their due dates and material availability. Buying sees requests tied to a customer order, which makes priorities clear.

Why it holds up

The link from sales order to production plan, work order and material request is kept on every document. That is what lets anyone answer “what is holding up this order?” by following the links instead of asking around. Finished goods are reserved against the order they were made for, so they cannot quietly ship to someone else.

With AI (coming to Sundial)

Sundial is built so an agent can draft the production plan and material requests when an order is confirmed, and wait for the planner’s approval before anything is released.

THE NEXT AGE OF ERP

Run the whole business
in one calm system.

Try the demoTalk to us