Restriction follows the product
Products can be marked none, 18, or 21. When a cart contains restricted items, the checkout workflow evaluates the highest required age and presents the verification gate before the sale can continue. Mixed carts therefore follow the strictest product in the transaction.
A physical-ID workflow, described honestly
The cashier is instructed to inspect a physical ID and enter the date of birth. LiftedPOS computes whether the customer meets the required age. The entered DOB stays in the browser for the decision; the system records the verification outcome rather than retaining that DOB. We do not call this automatic ID scanning.
One control in a broader operation
Age restrictions work alongside deep SKU catalogs, variants, suppliers, purchase orders, inventory, customers, loyalty, and transactions. The gate helps reinforce store procedure, but merchants remain responsible for applicable law, training, and acceptable identification policy.
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.