Barcode Scanner Emulator
POS Barcode Testing Guide
Point-of-sale systems combine several scanner-dependent behaviors in one workflow. Testing each field in isolation misses the bugs that only appear during a realistic checkout sequence.
Product lookup
Scan a known-good product barcode into the item entry field and confirm the correct product, price, and available stock are displayed. Test with barcodes representing different symbologies your catalog uses (UPC-A for US retail, EAN-13 for international products) since some POS systems only correctly parse one format.
Invalid barcodes
Scan a barcode with a broken checksum, a barcode not in the product catalog, and a partially-obscured/damaged label. Each case should produce a clear, distinct error message rather than a generic failure or, worse, silently adding a wrong or empty line item.
Quantity handling
Scan the same product multiple times in a row and confirm quantity increments correctly rather than creating duplicate line items. If your workflow supports a "quantity barcode" scanned before the product (e.g., "x3" then the product code), test that sequence specifically, including what happens if the quantity scan is interrupted.
Suffix behavior in a multi-field checkout
Confirm the configured suffix (see ENTER vs TAB Suffixes) does the right thing at each step: adding an item shouldn't submit the whole checkout, but a dedicated "complete sale" barcode (if your workflow uses one) should.
Focus issues during checkout
Test scanning immediately after opening a discount/coupon modal, after a payment dialog appears, and right after the previous item was added (before any UI re-render finishes). Focus loss during these transitions is one of the most common real-world POS bugs, since a scan that lands nowhere is easy to miss until a cashier reports "sometimes items don't get added."
Offline and degraded scenarios
If your POS supports offline mode, test scanning while offline and confirm items queue correctly for later sync. Also test what happens if a product lookup call is slow or fails: does the UI block further scans, or can a cashier scan ahead while a previous lookup is still pending (which can cause out-of-order line items if not handled carefully)?
Recommended tools
Use the Barcode Generator to create valid and deliberately invalid test barcodes (e.g., a broken checksum), and the Barcode Input Tester to verify raw scan capture before testing the full POS flow.