USE CASE

Incoming inspection

Inspect goods at receipt so bad material never reaches the line.

The problem

A batch of out-of-spec material passes the gate because inspection is a paper form nobody connects to the receipt. Three days later it is inside finished goods, and the cost of the defect has multiplied.

The flow in Sundial

1. Define what to check. Create an inspection template per item with the parameters, acceptable ranges and whether each is a numeric reading or a pass/fail check.

2. Require inspection on receipt. Mark the item as needing inspection before purchase; the purchase receipt cannot be submitted until an inspection is recorded.

3. Record readings. The inspector enters readings against the template. Sundial marks each parameter, and the inspection, as accepted or rejected.

4. Separate rejected stock. Rejected quantity goes to a rejected warehouse on the receipt, so it is never available for production or sale.

5. Close the loop with the supplier. Return the rejected quantity to the supplier and debit them, from the same receipt.

What the team sees

Quality sees inspections due and their results. Stores sees only accepted material as usable stock. Buying sees rejection history per supplier when choosing who to order from next.

Why it holds up

Inspection is a gate on the receipt itself, not a separate form, so it cannot be skipped by accident. The template sets the standard once and every inspector records against it. Accepted and rejected quantities flow into stock and supplier records directly, which keeps the warehouse, quality and buying working from the same facts about each delivery.

With AI (coming to Sundial)

Coming to Sundial: ask “which suppliers had the most rejections this quarter?” in plain language, with an agent that drafts the return and debit note for approval.

THE NEXT AGE OF ERP

Run the whole business
in one calm system.

Try the demoTalk to us