What Cashiers Experience

From a cashier's perspective, scanning a masked barcode is indistinguishable from scanning any other barcode. There is no extra step, no confirmation prompt, and no visual indicator that a mask was applied. The cashier scans the barcode. The item appears in the cart with the correct price, quantity, and — where applicable — serial or batch number already populated. The transaction continues as normal.

This invisibility is deliberate. The value of barcode masking is that it eliminates manual data entry without creating new workflows for cashiers to learn. The complexity of parsing an embedded barcode is handled entirely by the system. The cashier's job remains exactly what it was: scan the item and move to the next one.

Understanding what happens behind the scenes is more relevant for store managers, retail operations teams, and supervisors who need to know when and how masked data appears on transactions, how to investigate if something looks wrong, and what audit information is available.

---

The Scan Flow at the POS

When a cashier scans a barcode at an iVendNext POS terminal, the barcode string is passed immediately to the masking pre-processor before anything else happens. The pre-processor reads the first two characters of the scanned string and checks them against all active, non-disabled mask templates currently loaded in the system.

If the first two characters match the start sentinel of an active mask, the masking engine takes over. It parses the full barcode string according to the mask definition — extracting each segment in the configured sequence, applying scale factors to price and quantity values, and assembling the results into a resolution package: item identifier, scanned price, scanned quantity, and serial or batch value if present.

The item identifier from the parsed barcode is then passed to iVendNext POS's standard barcode resolution engine, which looks up the item in the usual way. The scanned price, quantity, and serial or batch from the mask are held alongside the resolved item and applied to the cart line once the item is identified.

If no mask matches the first two characters of the scanned barcode, the barcode is passed directly to the standard resolution engine without any masking step. The cashier and the transaction are completely unaffected.

How Masked Data Is Applied to the Cart Line

When a mask is applied successfully, the data extracted from the barcode overrides or supplements the default values that would otherwise come from the item master.

Embedded price: If the barcode contains a price segment, the extracted price is applied to the cart line as the selling price for that transaction only. The item master price is not changed. The next time the same item is scanned without a masked barcode — or at a different till where no mask applies — the standard selling price from the item master is used as normal. This means that a pre-weighed produce item labelled and scanned at $2.50 appears at $2.50 on the receipt, even if the item master has a price-per-kilogram that would calculate differently.

Embedded quantity: If the barcode contains a quantity segment, the extracted quantity is applied to the cart line. For pre-weighed items, this means the weight measured at the time of labelling is captured exactly — 0.752 kg is 0.752 kg on the transaction, not rounded or estimated.

Embedded serial or batch: If the barcode contains a serial or batch segment, the extracted value is pre-populated on the transaction line. For items that require serial or batch tracking for compliance or traceability purposes, this eliminates the separate manual entry step that would otherwise be needed.

If the mask extracts a price or quantity but the item lookup fails — the item code or barcode in the mask's item segment does not resolve to a known item — the masking result is discarded and the system falls back to standard resolution with the original scanned string.

The Barcode Masked Flag

Every POS invoice line item in iVendNext carries a field called Barcode Masked. When a mask is applied during a scan — meaning the rate or quantity on that line was derived from the barcode rather than from the item master or a price list — this flag is set to Yes on the line.

This flag is stored on the POS Invoice Item and is carried through to the Sales Invoice Item when the POS session is merged. It is visible on the invoice form and can be filtered in reports.

The Barcode Masked flag serves an important audit purpose. It allows supervisors and finance teams to identify, at a glance, which lines on a transaction had their price or quantity set by a barcode scan rather than by a standard pricing rule.

This is particularly relevant in environments where price-embedded barcodes are used for fresh produce or deli items, where the scanned price may differ from any standard price in the system.

Silent Fallback Behaviour

One of the most operationally important aspects of barcode masking is that it never disrupts the scan flow when something goes wrong. If the masking engine encounters a problem — the barcode string is shorter than the declared mask length, the delimiter produces fewer tokens than expected, the item identifier segment does not resolve to a known item, or any other parse failure — the system silently abandons the masking attempt and passes the original barcode string to the standard resolution engine.

The cashier sees no error message. The scan either resolves normally through standard resolution, or it fails in the usual way if the barcode is not in the system at all. No exception is thrown, no workflow is interrupted, and no special action is required from the cashier.

This fallback behaviour is critical for high-volume scan environments. In a grocery checkout, a scanning issue that requires cashier intervention on every third item is operationally unacceptable.

The silent fallback ensures that a misconfigured mask or an unexpected barcode format affects at most the individual line that failed to parse — and even then, the cashier handles it exactly as they would any other unrecognised barcode.

Offline Operation

Barcode masking works fully when the POS is operating offline. During the POS initialisation process, all active mask definitions are downloaded from iVendNext Desk and cached in the browser's local storage on the POS device. The masking pre-processor runs entirely in the browser using this cached data — no network request is needed to apply a mask during a scan.

This means that in stores with intermittent connectivity, or in the event of a network outage during trading hours, masked barcode scanning continues to work exactly as it does online. The same sentinel matching, segment parsing, and data extraction all happen client-side against the cached mask definitions.

When the POS reconnects and the session syncs, any transactions processed during the offline period are merged as normal, with the Barcode Masked flags preserved on all relevant lines.

Keeping Masks in Sync

When a mask is created, edited, or disabled in iVendNext Desk, the change takes effect for new POS sessions the next time a terminal initialises. Active POS sessions that have already loaded their mask cache will use the previous version of the masks until the session is refreshed or reopened.

For time-sensitive mask changes — such as correcting a mask that is producing wrong prices — the store manager should ask cashiers to close and reopen their POS sessions to pick up the updated mask definitions. This is a brief interruption and is the standard approach for any POS configuration change that needs to take effect immediately.

When to Review Mask Performance

Store managers should monitor masked barcode scanning the same way they monitor any other scanning-related issue. If cashiers report that a particular product is not scanning correctly — or is scanning but showing the wrong price or quantity — the first step is to check whether a mask applies to that product's barcode format and whether the mask configuration is correct for the current barcode specification.

The Test Mask tool in iVendNext Desk is the fastest way to diagnose a mask issue: enter the actual scanned barcode string and review the parsed segment output. If the values are wrong, the mask definition can be corrected and retested without any impact on live transactions until the change is saved and sessions are refreshed.