Barcode receiving: test labels, lots and duplicate events

What does the system know after a scan?

A scanner supplies characters; software must interpret them using the catalog and configured rules. A product code may contain no lot or expiry date. Another code may identify a twelve-piece case, one piece or an individual logistics unit. Ask to see the raw value and interpreted fields before stock increases. A scanner beep proves a read, not that the goods were correctly recognized or received. These are separate steps to observe.

Odoo documents product-level tracking prerequisites and mandatory or optional lot/serial scanning. Optional scanning permits manual entry; the described GS1 lot/serial codes need compatible equipment, including 2D capability in that case. Lot and barcode reference. Test your actual labels and scanners rather than assuming every device interprets every symbology.

Does one read add one piece or one case?

That depends on the recognized packaging. Odoo describes scanning configured packaging to add its contained units, with packaging belonging to a specific product. Packaging reference. Confirm the factor with the supplier first. The unit conversion guide covers changed contents; here the question is whether a read selects the right presentation rather than a similar item code.

Worked example: three cases and four loose pieces

Do not discard E02 and E03 because their raw values match: they represent different cases and intentional scans. Resending E03 after losing its response does not represent another case. Require retained event and receipt identities, or equivalent verifiable protection. If a button simply adds each incoming message, a communication failure may add twelve pieces that never arrived. Check the resulting movement history, not just the screen’s running count.

How do you proceed with a damaged or incomplete label?

Agree a controlled alternative: manual entry, document lookup or authorized relabelling. Retain available original data, who completed a field and how they checked product and lot. A label identifying only BAR-A must not generate L01 by assumption. If a required lot cannot be confirmed, receive as pending under policy without releasing it for sale. Also test similar labels for different products and a label belonging to another order.

• Normal: three cases and four pieces reconcile to 40, with the selected lot and one confirmed receipt.
• Exception: a fourth case would bring entry to 52; excess requires the agreed decision rather than silent acceptance as 40.
• Retry: repeating E03 or RC40 preserves one effect per identity; querying a lost confirmation shows whether the receipt exists.
• Correction: rectify a read of the wrong pack before confirmation, retaining a reason if it already created a movement.

What should you bring to a scanner test?

Use the barcode receiving worksheet with normal, damaged and different-pack labels. Retain raw reads, recognized fields and the final movement; hide sensitive details without changing the format. See partial purchase receipts for outstanding quantities and lot traceability for later movements. An inventory management system should test this flow with the equipment and connectivity receiving staff will actually use.