The purpose of A/B Compare is to compare two barcode scans. If the second scan matches the first scan then a Valid response is shown to the app-user. If they don’t match then an Invalid response is shown to the app user. For this option internet connectivity is currently required.

Application examples

The packer scans the barcode on a pick, pack or delivery list and then scan the barcode on the target item to validate they match. If they match the app user can be optionally prompted to scan each item to be part of that formal scan record.

<< For detailed instructions in PDF form please click A/B Barcode Compare. >>

Here’s a video showing a barcode scanning sled in action. It does not use or show A/B Compare but will give you an idea how fast you can scan and alternatives for sequentially scanning multiple barcodes.

Option 1: Scan the ‘parent’ barcode ID (i.e. the pick. pack or delivery ID), then use a multiline short form for scanning items belonging to that parent list. These item barcodes are saved within the scan record of the parent ID. All item barcodes are listed in one field next to the parent ID.

Option 2:  Scan the ‘parent’ barcode ID then scan individual form fields. This is an option provided there are not too many items to be scanned (generally less that 10). These item barcodes are also saved within the scan record of the parent ID but have their own field when exported.

Option 3: Scan only the item barcodes.  The app user could scan the parent barcode before scanning the item barcode and then scan it again when done. Every parent and item scanned are individual records.

Email our support team if you need any help.


in Best Practices with Instructions