Make inspection a step the receipt cannot skip for the items that need it, encode acceptance criteria in templates, route rejects to their own warehouse, and turn repeated failures into non-conformance records with owners.
Inspect at the point of entry
Quality problems are cheapest to catch at the door. A bad batch of components found at goods receipt costs a phone call and a return. The same batch found after it has been machined, assembled and shipped costs a recall, a customer and a long week.
Yet many companies inspect on paper, separately from the receipt. Stores receive the material, it shows up as available stock, and the inspection sheet arrives later, if at all. By then someone has already issued half the batch to production. The inspection is a record of what went wrong rather than a control that prevents it.
The fix is structural: the inspection has to be part of the receipt itself, and the stock should not count as usable until the inspection says so.
Decide which items need it
Not everything needs inspecting. Fasteners from a long-standing supplier may not; a critical machined part, a raw material with a certificate of analysis, or anything with a safety function almost certainly does. Make the decision per item, write down why, and revisit it when a supplier's record changes.
In Sundial, an item can be marked as requiring inspection before purchase, before delivery, or both. When it is, a purchase receipt or delivery note for that item needs a submitted quality inspection. Stock settings decide how strict this is: whether the system warns or blocks when the inspection is missing, and whether a rejected inspection stops the document.
Templates that encode the specification
An inspection is only as good as its criteria. "Looks fine" is not a criterion. A quality inspection template lists the parameters you check for an item and what counts as acceptable: a numeric range for a dimension, a minimum for a hardness reading, a pass or fail for a visual check, a value that must match the supplier's certificate.
When the inspector records readings against the template, Sundial evaluates each one against its acceptance criteria and the inspection carries an accepted or rejected status. The inspector does not have to remember the drawing tolerance; the template does. When the specification changes, you change the template once and every future inspection uses the new limits.
Sample sizes belong in the template too. Record how many units were checked from the received lot. That single field turns an inspection from a signature into evidence: it shows what was actually examined when someone later asks how a defect got through.
Keep rejected material separate
A purchase receipt in Sundial records accepted and rejected quantities separately, and rejected quantities go to a rejected warehouse rather than the main store. That one design choice matters more than any report: rejected material cannot be picked by accident because it is not in the place people pick from.
For material that needs a decision rather than an immediate reject, use a quarantine or hold warehouse. Stock sits there, counted and valued, until quality releases it with a stock transfer or sends it back to the supplier with a return. The stock ledger then tells the full story of every unit: received, held, released or returned.
Apply the same logic inside the plant. In-process inspections on manufacture entries and final inspections before delivery use the same templates and the same statuses, so a quality hold on a finished batch works the same way as a hold on incoming material.
When something fails: non-conformance
A single rejected lot is an event. The same rejection three times from the same supplier is a pattern, and patterns need a different record. Sundial's Quality module includes non-conformance records, quality procedures, quality goals and reviews, so a repeated failure becomes a tracked issue with a description, an owner, a root cause and a corrective action, rather than a complaint that lives in one person's inbox.
Close the loop with buying. Rejection history per supplier is exactly what a supplier scorecard should include, and it is a far better basis for a supplier conversation than a general feeling that quality has slipped.
This is a place where an assistant can help without taking a decision away from anyone. Sundial is designed so an agent could notice a third rejection from the same supplier, draft the non-conformance record with the three inspections attached, and leave it for the quality lead to confirm. The inspector still inspects. The pattern just stops depending on someone remembering it.





