Give every sellable item its own identity
A simple product can retain UPC, custom SKU, and numeric SKU values alongside its name, price, cost, category, brand, tax, and inventory detail. For a configurable product, those identifiers belong to the individual sellable variant, so a size, color, flavor, or strength can resolve independently instead of deducting stock from a generic parent.
Scan into a register built for the code
The retail sale screen includes a dedicated barcode input. A compatible scanner can send its code into that field, or the cashier can enter the code manually and submit it. Scanner behavior and connection method should be verified with the merchant's chosen station and hardware before rollout; LiftedPOS does not promise universal scanner compatibility.
Resolve one exact match—or stop
The lookup compares the submitted code exactly against UPC and custom SKU, and against numeric SKU when the code is numeric. One match returns that sellable item to the register. No match produces a not-found result. Multiple exact matches produce an ambiguity error rather than silently ringing an alphabetically convenient product.
Carry the item from the cart into operations
Once the exact item or variant is in the cart, the sale retains its product identity through the transaction and inventory record. Product search can also use name, SKU, or barcode when a scan is not the best path, while pricing, customer assignment, discounts, tax, card, cash, split tender, and receipts remain part of the same checkout.
Use inventory pressure to drive the next action
Low-stock visibility helps surface products that need attention. Suppliers, purchase orders, full or partial receiving, inventory history, and transfers between locations provide the operational path after the sale. Those workflows remain connected to the product catalog, but they should not be described as scanner-driven unless that exact behavior is demonstrated.
Know what this barcode claim does not include
LiftedPOS does not currently advertise product barcode generation, product-label printing, scan-to-receive, scan-to-count, weighted or price-embedded barcodes, serial or lot tracking, or mobile-camera scanning. Merchants that require those workflows should verify the exact process, hardware, symbology, and integration scope before choosing a rollout.
Use the actual workflow, inspect the resulting record, and ask how the behavior is configured for your locations. Availability can depend on enabled modules, hardware, and payment setup.
Move from the feature to the operation
LiftedPOS is designed so this capability does not sit alone. It shares customer, employee, product, location, transaction, and reporting context with the rest of the system. That is the difference between checking a feature box and removing a handoff from the day.