Inspecting goods on receipt and after a build
Flagging an item for inspection, checklists and specs to check, deciding what passes, and what to do with what fails.
Watch it done: Inspect what comes in
Some goods should not reach the shelf until someone has looked at them. In BeanDish an item can be flagged for inspection when it is received, after it is built, or both. Flagged goods wait in their own bin, where nothing can sell them, until an inspector decides what passes.
Flagging an item
Open the item and go to its Specs tab. The Quality row has two switches: Inspect on receipt and Inspect after build. Beside each, you can pick a Receipt checklist or a Build checklist. Without one, the inspection checks the item's own specs only.
Any spec row on the same tab can be ticked QC, and then every inspection of the item checks it. A number or quantity spec ticked QC can carry a tolerance, and the inspector types a reading that is judged against the value plus or minus it. A cost can never be a check.
Checklists
Checklists are under Inventory – WMS › QC checklists. Write the checks once and name the checklist on as many items as you like. Each check has a type — Pass / fail, Measurement (with a minimum and maximum), Text answer, or Photo or document — and can be marked Required. The Items tab lists every item that uses the checklist.
An inspection copies its checks when it opens, so changing a checklist later never changes an inspection already waiting.
What happens when goods arrive
When a flagged item is received on a purchase order, or a work order builds one, the receive and build screens say so: the goods go to inspection, in a bin called QC-HOLD, and passed goods are put away to the bin shown. BeanDish creates a QC-HOLD bin and a QC-REJECT bin in each warehouse the first time it needs them.
Goods in either bin count as on hand, but not as available: no sales order, build or transfer can take them. MRP counts goods in QC-HOLD as coming.
Inspecting
Open Inventory – WMS › Inspections. The list shows what is waiting, for how long, and what happened to everything already inspected. Open one to inspect it.
- Checks — type the Sample size and answer each check. Required checks must be answered before you decide.
- Notes & files — notes, and photos or documents of the goods as a whole.
- Decide — split the quantity into Accepted and Rejected (by lot for a lot item; tick the failed serials for a serial item), and choose where accepted goods are put away.
Save keeps your answers so far. Decide asks you to confirm, because the decision is final: accepted goods are put away and rejected goods move to QC-REJECT. If any check failed, at least one unit must be rejected.
To record and decide inspections, a person's role needs Quality. Admins always have it; other roles have to be given it.
Dealing with rejects
A decided inspection shows a Rejected goods card with what is left to deal with.
- Return to supplier — for goods that came in on a purchase order. Record the quantity, the supplier's RMA, carrier and tracking. The goods leave stock on a supplier return (RTV), listed under Purchases – A/P › Supplier returns. If the supplier has already billed the delivery, a debit memo is created and posted with it.
- Scrap — writes the goods off.
- Mark for rework — for goods you built. They stay in QC-REJECT until you press Ready for re-inspection, which opens a new inspection.
- Break down — for built goods whose item is a kit, taking it apart into its components.
Every action is listed on the card with who did it and when.
How your suppliers are doing
Inventory – WMS › Reports has Supplier Quality - Summary and Supplier Quality - Detail: for each supplier, what was received, inspected, rejected, returned and scrapped, with a reject percentage. Goods inspected after a build are shown separately.
See it happen
The video above follows a delivery held for inspection, checked against a checklist, part accepted and part returned to the supplier, and the supplier quality report.