GearChain buying guide: how do you avoid counting one delivery twice after scanning and manual entry?
Use invented receipt numbers to separate item identity from transaction identity and reconcile two records for the same delivery.
GearChain's item entry guide describes entering an item manually when it cannot be scanned. Its inventory field guide lists a secondary barcode that can hold an additional item code. Barcodes and SKUs answer “what item is this?” To establish whether it was received once or twice, identify the transaction separately. Compare whether both paths can be reconciled to the same master item and delivery record; one field is not an automatic duplicate rule.
The same SKU can arrive twice; the same receipt line should not be counted twice
A fictional bindery receives two deliveries of the same blue ribbon. Its item record is B-06 and the carton has an additional barcode. Paper entry A uses that barcode and says “receipt R-214, one box.” Entry B was typed after a label became unreadable: “B-06, R-214, one box.” They point to the same delivery slip and line, so a human reviewer counts them once. Another box arrives the next day as R-215. Despite the same SKU, barcode and pack size, it is a second delivery. If a manual entry has an item code but no original receipt number, leave it pending. Do not infer one transaction from one item or add another blindly. Nothing was scanned or added to inventory and no location data was collected.
Specify what a person needs to verify on paper: the master item, the source receipt number and whether both entries are for the same line. Pass only if both cases can be told apart. This does not assert a fixed transaction key or automatic deduplication. Scanning with manual review is worth comparing if there are many items and some labels often fail. With few deliveries and a simple searchable ledger, consistent receipt numbers and someone responsible for review may be more direct.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:gearchain.io