Software for salon bookings, customers and counter sales

They are related workflows with different records. Solo covers a business website, appointments and customer administration, while Solo POS covers counter products, stock and daily sales. Follow one customer through a service booking and a retail purchase, then confirm the product combination and any shared details required. BookSolo is a separate public discovery listing.

Use your actual service durations, staff availability and booking rules in a demonstration. Check a new booking, a changed appointment, the customer record and any required payment arrangement. Separately agree how future appointments and customer details will be transferred and reconciled. A successful new booking does not establish a complete migration from your existing system.

Choose a service with its real duration and required resources, then try bookings that compete for the same staff member or room. Confirm the availability behaviour in the proposed Solo setup. A free staff calendar alone may not establish that the treatment room or equipment is available for the entire appointment.

Follow a fictional customer through the service booking and a separate retail purchase. Review which record holds the service charge, which holds the product sale and how the owner sees the results. Confirm any intended connection between Solo and SOLO POS; do not add overlapping reports together without checking what each includes.

Start with upcoming appointments, service definitions, staff assignments and the contact details needed for the first working week. Identify sensitive notes separately and agree what should transfer. Review a sample with the salon team before scheduling the move, and confirm the supported import method and ownership of corrections with the supplier.

Start once from the public listing and once from the salon website, then follow both journeys to a completed test booking. Compare the service, price, availability and business identity the customer sees. Record the current commercial terms for each channel separately; being discoverable does not guarantee that a visitor completes an appointment.

List which staff deliver each service and the required duration. Test a normal booking and an unsuitable staff choice in the proposed setup.

Review the new time, staff, service and customer details. Follow the changed booking through the business workspace and intended confirmation process.

Follow each record through its own workflow and confirm any supported connection. Do not assume a booking automatically creates a counter sale or matches every customer detail.

Agree required fields, duplicate handling and the transfer method. Reconcile a small sample with the source before selecting a full migration date.

Start from a service page and complete the intended booking route. Check text, customer fields and the resulting appointment using the proposed configuration.

Itemise the website and booking plan, any POS add-on, hardware, setup and payment-provider charges. Compare the same service and retail requirements.

Use a new booking, a reschedule and a product purchase. Have the actual staff find the resulting records and explain who handles an exception.

A listing supports discovery and booking options. Agree any appointment migration separately with the booking-workspace setup rather than inferring it from marketplace access.

Separate visits, booking-route clicks, completed appointments and repeat customers. Compare similar service periods and use actual booking evidence before claiming an increase.

Evaluate Solo against the required customer and staff journey first. Discuss separately scoped StartSimple work when design or integration requirements need a custom approach.