What happens when the wrong part is scanned?
KitProof looks the scanned code up among the exact identifiers and approved aliases of the parts on this kit’s list. A code that is not on the list is rejected with “Not a component of this kit”, and nothing is counted. The operator puts the part back and scans the right one.
The rejected scan is not thrown away: it stays in the kit’s history with the time and station, so a supervisor can see what was tried.
One part too many
Each scan counts as one part. Once a line has all it needs, another of the same part is rejected as not needed, so a kit never gets one too many and a double scan never hides a missing part elsewhere.
When is an alternative part allowed?
Only alternatives set up for that part in the kit’s configuration are recognised. An alternative that needs approval is held for a supervisor and does not count, while the operator carries on with other parts or uses the standard part, which still counts straight away.
The supervisor approves or declines the request with a note, after a recent second-factor check. An approval covers only that kit, slot and quantity, and the operator scans the alternative again for it to count.
Serial-numbered parts
A part that needs a serial number counts only once its serial label is scanned. Scanning the part’s own barcode again in place of the serial is rejected, and so is a serial already recorded on another kit.
Undo a mistaken scan
If a part that was accepted cannot go in the kit, perhaps because it is damaged, the operator reverses their own last scan and gives a reason. The scan no longer counts, but the history keeps it. Other reversals need a supervisor, and nothing can be reversed once the kit is complete.
When scans stop arriving
A scanner that types like a keyboard sends its scan to whatever has focus on the screen. If the scan box loses focus, KitProof shows a warning, because a scan that goes nowhere is never counted. Selecting the warning puts the focus back, and scans are received again.
What the record shows
History finds a kit by its job, kit reference or serial number. Each kit’s evidence page shows the release and order revision it was checked against, the parts and serials accepted and how each was scanned, approvals and exceptions with their notes, and every recorded event, rejected scans included. The evidence can be exported.
What KitProof does not do
- Prove what is physically in the box. A scan records the code supplied; it does not stop someone scanning a part without packing it.
- Weighing, camera vision or RFID. Each part is checked by scanning its barcode, with a keyboard scanner or the device camera.
- Fuzzy matching or shared barcodes. Each part type needs its own identifier, or an approved alias.
- Offline checking. The station needs a network connection to accept a scan.
Common questions
Does a scan prove the item is in the box?
No. KitProof records that the required identifiers and any other permitted evidence were supplied. It does not prove what is physically in the box, or stop someone scanning a part without packing it.
What if someone scans the bin label instead of the part?
By default, each part must be scanned itself, and a bin card is rejected with “This is a bin card. Scan the part itself.” A component can be set up to accept its bin card instead, and the record then shows that the evidence was a bin scan, not the part.
Start free at one station and pay when you grow. While SmartFACT is in early access, we set your first workflow up with you.
