Salon POS Guide: Appointments, Tips, Retail and Closeout

Start with your booking system

Write down the scheduling software you use and whether it owns client profiles, packages, deposits and appointment reminders. Ask a proposed POS provider to demonstrate the exact connector and supported version. If the systems remain separate, define how reception transfers the amount due and records payment without creating duplicate balances.

For a salon with independent booth renters, establish which legal business receives each payment before selecting equipment. One shared terminal is not proof that funds, records or reporting can be separated correctly. Confirm the proposed account arrangement with the provider.

Demonstrate a real service ticket

1. Book a haircut and colour service with different staff members.
2. Apply an appointment deposit and add a retail product.
3. Show the final total and let the customer select a tip through the supported workflow.
4. Confirm which employee receives service credit and how the tip is recorded.
5. Issue a receipt and check the appointment is marked paid.
6. Refund only the retail product and verify inventory and the remaining service records.

This demonstration reveals more than a feature list. Record any manual work and identify who corrects mistakes.

Terminal or full POS?

A standalone terminal may fit when your booking platform already handles tickets, staff and products, and the manual payment handoff is manageable. A full POS may fit when reception needs a shared service catalogue, product inventory and controlled refunds. Compare the cost of maintaining two systems with a verified integrated arrangement.

For Clover^® options, compare the actual software, apps and device configuration in the Clover buying guide. Appointment management and commission functionality must be confirmed separately; a device name alone does not establish support.

Protect the closeout and the transition

At day end, reconcile service sales, product sales, tips, refunds and each tender against processor activity. A staff-sales report is not necessarily a payroll calculation, and approved card sales are not necessarily the same day’s bank deposit.

Before switching, export the records you need and agree how unused packages, gift cards and appointment deposits will be honoured. Confirm cancellation terms and whether stored payment credentials can move through a provider-approved process. Train reception on split payments, failed payments and partial refunds before go-live.

Resolve the appointment-to-payment handoff

Follow the booking record from the moment a client arrives. Confirm who checks the services performed, records an approved add-on and transfers the amount due to reception. The payment system should collect the correct balance and leave the booking record in a clear state.

Test a service that changes during the appointment. If the stylist updates the booking tool but the cashier uses an old ticket, a fast payment device will still collect the wrong amount. Identify the final approval step and make it visible to both roles. A reliable handoff matters more than a decorative customer display.

When scheduling and payments remain separate, document the manual reference and daily reconciliation. That arrangement can be practical if staff understand it. If a vendor proposes an integration, demonstrate the exact posting result and the recovery procedure when one system updates but the other does not.

Distinguish employees, renters and shared reception

A salon with employees and a salon with independent booth renters may require different account and reporting arrangements. Establish which business sells each service, receives the payment and handles the refund before choosing a shared checkout. Ask the provider to confirm the supported arrangement rather than assuming one terminal can separate every business relationship.

For employees, demonstrate service credit, tips, product sales and a refund where more than one staff member contributed. Decide which outputs the salon uses for management and which require a separate payroll or accounting process. Have the person responsible for staff payments approve those reports.

For shared reception, define who can view each record and which tasks the receptionist may perform. Use individual accounts where supported and an approved procedure for changing access. The technology should follow the actual operating structure, not force staff to share administrative credentials simply to collect a payment.

Treat deposits, packages and gift cards as distinct balances

A deposit reduces an agreed amount due; a package represents services under the salon’s terms; a gift card creates another balance to honour. Ask the proposed system to demonstrate each function you need. Do not accept a generic discount button as proof that all three can be accounted for correctly.

Use an invented client who has paid a deposit, redeems part of a package and purchases a product. Inspect the receipt, remaining balances and staff reports. Then cancel or partially refund the transaction under the salon’s approved policy and check what happens to each balance.

Before changing systems, export the outstanding liabilities and decide how they will be honoured. Keep the previous reports accessible. The new provider may not be able to import every historical package or stored credential, so the migration plan needs an explicit method for handling those exceptions.

Make retail products work at the same checkout

Bring a product with a barcode, a size or colour variant and a promotional item to the demonstration. Confirm that reception can find the right item without confusing it with a similarly named service. A service sale and a product sale may need different stock and reporting treatment.

Test receiving new stock, correcting a quantity and returning a damaged product. The stock count should reflect what is physically available for sale. A refund does not necessarily mean an opened or damaged item belongs back on the shelf.

If the salon sells products online, identify which system owns the catalogue and stock. Demonstrate a website order, cancellation and refund alongside an in-salon sale of the same item. Use the ecommerce planning guide to define synchronisation, fulfilment and support responsibilities before adding another subscription.

Verify tips and split payments before training the team

Demonstrate the tip experience the client will actually see. Check when the prompt appears, how staff identify the correct service provider and what happens when a client pays part of the balance in another tender. Confirm the supported workflow for adjustments rather than relying on staff to reconstruct tips later.

Test a ticket involving two staff members and a product refund after the service has been completed. Inspect service sales, tips, refunded products and tender totals separately. Decide how the salon uses those records and which calculations belong in another system.

Keep the customer’s choices clear and the final total visible. Staff should not need to explain a confusing screen or skip a required confirmation to keep the queue moving. Include the receipt, the client’s view and the manager’s report in the same demonstration so all three agree.

Build an exception procedure for a busy reception desk

Define what happens when a card is declined, the device loses its connection or a payment result is uncertain. Staff should check the authoritative transaction status before retrying. A missing receipt or frozen screen alone does not prove that the first charge failed.

Give reception a short support checklist: identify the device and software, capture the transaction reference without card details, record the amount and expected result, and contact the responsible provider. Separate payment, booking and integration issues so the problem reaches the right owner.

Also establish an approved fallback when the normal checkout cannot be used. Confirm the supported method with the provider and train staff on it. Do not assume offline collection or a phone-based workaround is available simply because it sounds convenient during a demonstration.

Compare proposals using a normal month of salon activity

Gather card sales, transaction count, average ticket, refunds and the split between in-person, remote deposit and recurring activity. Compare proposals against that same month. Keep POS, booking and marketing subscriptions visible instead of treating them as part of one unexplained bundle.

Include hardware, accessories, paid apps, connectors, installation, catalogue work and training. Ask which charges are per device, location or account and what remains payable if the salon changes service. Confirm equipment ownership and the scope of replacement or support arrangements.

A useful comparison also records the manual work. A lower subscription can be poor value if reception must duplicate every ticket and reconcile unexplained differences daily. Describe the demonstrated time-saving task without turning it into a guaranteed financial claim. The owner should see both the price and the work the proposed setup removes.

Give each implementation task an owner

Before installation, agree who prepares services, prices, product barcodes, staff roles, receipt wording and reporting categories. Identify the person authorised to approve changes. A vendor cannot reliably configure a salon from an incomplete list of services or an unreviewed price sheet.

Run a short pilot with reception and a representative staff member. Test the normal appointment, a changed service, split payment, deposit redemption, product refund and day close. Record the expected result and unresolved issues. Confirm the first settlement and the booking-to-payment reconciliation before broad use.

Use the official Clover salon overview to explore the product category, then verify the exact devices, plan and apps in your proposal. The support guide helps separate hardware, payment and software responsibilities; the review enquiry starts the discussion around your existing setup.

Questions worth resolving before you sign

Can we keep our booking software? Start by testing its existing payment options and the proposed connector. Keep a working booking system unless the replacement solves a documented need. Ask who supports the connection and what happens when either vendor changes its software.

Will a full POS calculate staff pay? Require a demonstration of the exact reports and have the payroll owner approve their use. Staff-sales attribution, tip reporting and payroll calculation are separate requirements. Do not assume that one feature proves the others are included.

What happens to existing client balances? List deposits, packages, gift cards and unresolved refunds before migration. Agree how they move or remain accessible and test sample balances. A new checkout should not leave reception guessing what a returning client is entitled to redeem.

Do we need to replace every device? Confirm the model, ownership, provisioning, peripherals and required workflow. Device reuse can only be assessed against the actual proposed arrangement. Make hardware purchases after the software and payment requirements are clear.

Use one client journey to score two proposals

Run the same illustrative appointment through both demonstrations: a service booked with a deposit, an approved add-on, a retail product and a product-only return. Give each vendor the same starting balance and staff roles. Record the result rather than scoring the presentation or the number of advertised features.

For each step, mark whether it is automatic, manual or unsupported. If it is automatic, ask which connector or application performs the action and where a failure becomes visible. If it is manual, write down who completes it and how reception checks it at day end. If it is unsupported, decide whether that limitation is acceptable before comparing prices.

Then ask the receptionist to repeat the workflow without the demonstrator leading each click. Observe whether the amount due, selected employee, product and remaining package balance stay clear. A configuration can look efficient when an expert operates it and still be difficult for the team using it during a busy shift.

Keep the scorecard with the written proposal. Include a column for the responsible vendor and a column for the evidence: screen, receipt, report or confirmed specification. A verbal answer such as “that should work” remains unresolved until the provider can demonstrate it or document the supported arrangement.

This exercise also helps the owner recognise when a simpler setup is sufficient. If existing booking software already owns the ticket correctly and a terminal handoff is reliable, replacing the whole system needs a stronger reason than a new design.