There are three methods of interpreting a barcode scan, which the system performs in the following order:

The first way of interpreting the barcode input is to compare it against a list of predefined text values that represent actions to be performed. These predefined text values begin and end with a $ character to distinguish them from other barcode inputs. For example, $NEW_PACK$ creates a new pack.

For a full list of predefined text values, see Master Barcodes. You can add more predefined text values using the system value key SCANNER_CONFIG. For more details, see Shortcuts and Master Barcode Scans. You can add further predefined text values using the system value key SCANNER_CONFIG.

The second way of interpreting barcode input is to compare it against a list of predefined regular expressions. You can do this when barcode inputs that match a regular expression are always to be treated in the same manner. For example, you can specify that all barcode input beginning with ORD and ten characters in length is to be treated as order reference numbers. This avoids the need to set the barcode input context to Order Reference before scanning an order reference. You can set up a list of regular expressions using the system value key SCANNER_CONFIG.

The third way of interpreting the barcode input is to use the method selected in the barcode scan context input field. For example, if the selected barcode context value is set to Pack by Product, the scanned barcode is treated as the product code of an item you want to append to the current open pack. The list of barcode scan contexts is predefined. You can alter the list using the system value key SCANNER_CONFIG.