The highest applicable 18+ or 21+ requirement governs the restricted basket.
The strictest restricted item sets the cart rule
Products carry no restriction, 18+, or 21+. When restricted items are present, the checkout decision uses the highest applicable age requirement, so a mixed basket follows the strictest item in it instead of whichever restricted product the cashier notices first.
Make the physical-ID check visible at the decision
The workflow asks the cashier to inspect physical ID and enter date-of-birth information for the decision. This is a physical-ID procedure, not an automatic ID scanner. The operator follows the merchant's identification policy, training, and escalation procedure at the counter.
Keep date of birth out of the sale record
LiftedPOS computes the age decision in the browser. The entered date of birth is not stored or logged as customer data. The service records the age-check outcome and can retain a computed-age result for the control record without turning DOB into a customer-profile field.
Review exceptions instead of hiding them
The operating record distinguishes verified, bypassed, and missing attestation outcomes. Merchant procedure should define when a manager may intervene, which identification is acceptable, and how that exception is reviewed afterward rather than advertising the gate as impossible to bypass.
Connect the restriction to the exact product
Age rules live beside the SKU, variant, price, tax, inventory, customer, loyalty, and transaction context already used at the register. LiftedPOS reinforces the store's procedure; the merchant remains responsible for applicable law, staff training, acceptable identification, and jurisdiction-specific policy.
Test the decision, the exception, and the retained record
Use safe test products marked unrestricted, 18+, and 21+. Build a mixed cart, inspect the required age, follow the physical-ID prompt, and verify the recorded outcome without entering real customer data. An authorized merchant should also test its approved manager-exception path and confirm how verified, bypassed, and missing outcomes appear for later review. Document the result with the store's own escalation owner and training language. Repeat the test for every restricted product category the merchant plans to sell.
Inspect in the live demo
Add a seeded 21+ item and inspect the physical-ID and DOB decision before completing a safe cash sale. Availability can depend on enabled modules, hardware, payment setup, role, location, and rollout configuration.
Move from the feature to the operation
This capability shares customer, employee, product, location, transaction, and reporting context with the rest of LiftedPOS. The value is not a checked box. It is the handoff the operation no longer has to rebuild.