Age checks at the counter, built into every sale

Square Age Verification in your operation

Age checks belong at the point where a restricted sale is accepted. Roots helps plan Square checkout prompts and staff identification procedures around the products you sell, keeping the item setup, employee training and customer interaction consistent.

Build review rules into the sale workflow

Verification works best as a defined step with a responsible person. Decide when the check happens, what information staff examine and what causes the transaction to pause. Use ordinary and exceptional sales so employees can apply the procedure consistently rather than guessing from an alert alone.

Escalation needs a named role and an outcome staff can record. A sale may proceed, be declined or wait for further review. Keep enough transaction context to understand the decision later, and review repeated exceptions to see whether catalog setup, checkout design or training should change.

Decisions to make before setup

Choose a restricted item and walk through the sale with a new staff member. Confirm when identification is checked, what to do when the requirement is not met and who can resolve a checkout exception.

Use the setup discussion to settle restricted item categories, checkout prompts and staff ID procedures. Put the decisions into the staff procedure and test transactions, so the configuration can be checked against actual work. Identify which records already exist in your software and which will need to be created, imported or connected during the project.

Reporting and day-to-day review

Focus the review on restricted-item setup, staff training, refused sales and checkout exceptions. Decide who checks those records, which exceptions require action and where the final totals are reconciled. Keep a payment or order reference attached to every correction so the next employee can understand the history rather than reconstructing it from an amount and a date.

Plan the setup around your business

Prepare a representative transaction and the records your team uses today, including the reports that must match after a payment. Roots uses the free review to define the workflow, the systems involved and the handoffs that need to improve. A concrete transaction is more useful than starting with a list of unrelated features.

Request a quote for the setup or project you need. The scope should identify configuration, migration or development work, staff training and the checks used to confirm readiness. Agree the operating owner for each handoff before launch, then review the first working period against the same cases used in the setup.