How to set up receiving inspection
Define the handoffs from receipt to inspection, quality hold and release before automating them. Use a practical lot example to choose the fields, responsibilities and exception rules your operation needs.
Sign in to explore the sample App. Install it with sample data to assign your team and try the review tasks.
Agree the decisions before choosing fields
| Work | Practical owner | Ready for the next person when… |
|---|---|---|
| Identify the receipt | Receiving staff | Item, supplier lot, order reference and quantity are clear. |
| Choose inspection requirements | Quality or inspection lead | The active requirement and applicable revision match the received item. |
| Record observations | Inspector | Required checks, sample readings and evidence explain the result. |
| Review the report | Assigned quality reviewer | The report is complete and discrepancies have an explicit next action. |
| Authorize disposition | Authorized quality reviewer | The proposed release, hold, return or scrap decision has sufficient evidence. |
| Follow recurring supplier problems | Supplier-quality owner | Actions are implemented and effectiveness has been reviewed. |
These are starting responsibilities, not a staffing mandate. One small team may cover several roles, but it still needs clear authority for inspection, exceptions and release. Configure the installed workflow to match your policy.
Keep each fact in the record where it belongs
Stable reference data
Use an inspection requirement for item code, revision, inspection family, dimensional limits and required documents. Retire superseded requirements explicitly. A received lot references the delivery identity and quantity; it should not become an editable copy of every inspection specification.
Auto-numbered records and native linked selections reduce ambiguous references. Do not use a free-text supplier lot as the only identity for several unrelated receipts.
Events and decisions
Each inspection retains its requirement revision, sample observations and review. A retest is a new event, not a replacement of the original. A lot decision references the reviewed evidence, and a SCAR references the problem and later effectiveness checks.
This structure makes history understandable: “the second inspection passed” is different from “this delivery never failed.”
Design the exceptions that otherwise end up in email
Missing certificate, passing dimensions
Keep the material on hold if the certificate is required. Give someone responsibility for obtaining a matching document. Do not let one passing characteristic override an incomplete acceptance requirement.
Changed or retired inspection requirement
Recheck the selected requirement when the inspector submits and before release. If its revision or availability changed, review the evidence against the correct requirement rather than silently approving a stale selection.
Correction followed by retest
Record what was corrected and reference the original failure. Keep new sample readings in a separate report, then review the proposed lot disposition. Continue any systemic supplier action independently.
Only part of a shipment can be accepted
Define traceable sublots, quantities and physical locations before building partial-release automation. This demonstration makes whole-lot decisions. It does not subtract an accepted quantity or post inventory movements.
Measure the queue without hiding the failures
| Measure | Define it clearly | Avoid this mistake |
|---|---|---|
| Lots awaiting inspection | Received lots with no completed initial inspection at the review time. | Counting individual sample rows as separate waiting lots. |
| Age of unresolved holds | Elapsed time since a lot entered hold, for lots still held. | Using the latest comment date and concealing old holds. |
| Receipt-to-disposition time | Time between receipt and the authorized lot decision. | Stopping the clock at a passing inspection before release review. |
| First-pass lot acceptance | Lots passing their initial inspection ÷ lots with an initial inspection in the defined period. | Including passing retests in the first-pass numerator. |
| Repeated supplier failure | Subsequent inspected lots with the same defined failure after a corrective action. | Treating an accepted action plan as proof that recurrence stopped. |
Choose measures your team will act on. The sample dashboard shows fictional operational records, not a benchmark for acceptable supplier performance or a claim of measured business improvement.
Start with one item family and a complete decision path
Use the receiving checklist to define one family’s checks. Try a normal receipt, failed characteristic, missing document and corrected retest. Confirm that the reviewer can return incomplete work and that only an authorized decision changes the correct lot.
Then add other families and supplier follow-up. Keep warehouse stock movements in the receiving process and broader checks in quality control. Integrations should have explicit ownership of lot identity and stock status; a status label in a separate App is not a physical stock restriction.
Put the receiving process into use
Incoming inspection
Explore a working lot queue, inspection history and separate quality decisions.
Receiving checklist
Choose the arrival and item-specific checks an inspector actually needs.
Inspection report
Keep the sample readings, conclusions and retest history traceable.
Supplier corrective action
Define a supplier response that distinguishes containment from recurrence prevention.
Receiving process design questions
Who owns the receipt, inspection and release records?
A practical starting point is receiving staff for delivery identity and quantity, an inspector for observations and evidence, and a quality reviewer for acceptance and disposition. Adapt the roles to your operation and document who may authorize an exception.
How should I handle partial acceptance of a delivery?
Identify the accepted and held quantities and make their physical locations and traceability clear. The demonstration App makes a whole-lot decision, not a partial stock transaction. Split the delivery into traceable sublots or design quantity-controlled disposition records before using it for partial releases.
What happens if the specification changes during inspection?
Do not silently relabel an old result as an inspection against the new revision. Review whether the existing evidence remains applicable. The example rechecks the current requirement at submission and release, so a stale selection needs to be corrected.
Which incoming-quality measures are useful to start with?
Track lots awaiting inspection, age of unresolved holds, elapsed time from receipt to disposition, first-pass lot acceptance and repeated supplier failures. Define the denominator and time window. Do not mix initial inspections and retests when calculating first-pass acceptance.
Should this process replace my warehouse receiving system?
No. Receiving controls quantities and inventory transactions; incoming quality controls inspection evidence and quality decisions. Connect the two using stable lot and order references. Any automatic stock restriction or release needs a designed and tested integration.