Salon POS Launch Checklist: Appointments, Deposits, Staff and Packages

Approve the service and opening-balance records

Confirm which platform owns appointments, service prices, packages and gift balances. Check a service with an add-on and multiple professionals before importing the full catalogue. Reconcile opening package or deposit balances through an agreed process; do not replace missing entitlements with general discounts.

If the booking system remains in place, document the payment handoff and the owner of corrections. If it changes, identify which appointments and historical records transfer and which remain accessible elsewhere. A successful contact import is not proof that every appointment or balance migrated.

Rehearse reception without the installer leading

Use a fictional guest with an existing deposit, an agreed service change and a retail product. Ask reception to confirm the final total, take payment, complete the appointment and arrange another visit. Check that any new deposit belongs to the future appointment rather than the completed service.

Test staff and tip attribution when more than one professional worked on the ticket. Have the payroll owner approve the report and correction process. Reception access should support its tasks without automatically allowing unrestricted price, refund or export changes.

Train the backup and verify the first close

Include a product-only return, an uncertain payment and an unapplied deposit in the training. Staff should know how to check status and escalate without charging twice or reversing a completed service. Keep the relevant non-sensitive references with the exception record.

Review appointment completion, deposits, tenders, tips and product stock after the pilot. Save the report filters and generation time. Resolve discrepancies before removing the previous process, and confirm the subscription and application configuration matches the written proposal rather than the demonstrator’s broader account.

Use this as a launch gate, not another buying list

A launch checklist begins after the required workflow has been chosen. Its purpose is deciding whether the people, records, account and equipment are ready for controlled use. Keep unresolved purchasing questions visible, but do not treat a signed order or delivered box as evidence that the operating setup is complete. Assign an owner to each dependency and record what demonstrates completion.

Create three states: ready, blocked and not applicable with a reason. Avoid marking an integration ready because somebody expects it to work. A provider confirmation establishes a supported arrangement; an observed acceptance test establishes that the intended workflow behaved correctly in the tested configuration. Retain both where needed.

Choose a realistic first operating window and a stop condition. The team should know which unresolved issues prevent launch, which manual steps are temporarily acceptable, and who can authorise rollback. Keep dates conditional on account approval, equipment, configuration and training rather than promising a launch before those dependencies are confirmed.

Prepare access, connections and opening records

Confirm the account is ready for the intended payment channels and that each proposed device is correctly provisioned. Inventory exact hardware models, peripherals, software plans and required applications. Physical connection does not prove compatibility; obtain confirmation for retained equipment and test its actual task.

Give staff individual access appropriate to their work. Separate routine payment collection from refunds, price changes, exports and administration. Name a backup owner for access recovery without sharing unrestricted credentials. Check how a departing employee’s access will be removed.

Document opening balances and required imports before trading. Reconcile a sample after import and preserve the source export securely. Confirm who maintains prices, categories and customer-facing receipt details. A vendor can complete installation while leaving catalogue, ledger or staff-policy decisions unresolved; those still need business approval before launch.

Rehearse the exception as well as the normal sale

Use provider-supported test facilities or a clearly agreed test process. Label records so they do not become unexplained production activity. Complete a normal payment, a decline, an uncertain result and a supported refund. Observe the record after each step instead of accepting only a success message.

Have the employee who will actually perform the task repeat it without the demonstrator leading every click. Check what the next person sees when work changes hands. A setup that depends on one expert remembering an undocumented correction is not ready for a busy shift.

Verify receipts, records and closeout after the relevant cutoff. Document any test payment or refund that affects a real account and reconcile it through the normal records. Never place full card numbers or passwords in the test log. Keep only references needed to trace the result through the approved support route.

Sign off the pilot and first close

Agree who approves the operational workflow and who approves the accounting handoff. A cashier may confirm the device works while the reconciliation owner still finds a missing export. Capture both approvals and unresolved exceptions in the same launch packet.

During the first controlled service period, retain the previous supported arrangement where appropriate and practical. Record any workaround, who used it and whether it changed the records. Review these items before removing the old process or expanding to another location.

Check the first complete statement and recurring software bill against the written proposal. Confirm equipment, application and implementation charges separately. A launch review does not guarantee savings, account approval or a funding time; it establishes whether the tested setup and agreed responsibilities are clear enough to proceed.

Keep appointment balances and staff attribution clear

Identify the booking platform that owns the appointment, client record and service ticket. A payment device should not become an accidental second appointment ledger. If the systems remain separate, write down how reception confirms the amount, checks the payment result and marks the appointment complete. If a connector is proposed, demonstrate its exact supported handoff and correction process.

Show an appointment whose agreed services change during the visit. Reception needs the final amount and service attribution before the guest pays. Confirm who can change a price, how the change reaches the ticket and who approves exceptions. Repeated manager overrides may indicate a service-catalogue problem rather than a reason to replace the payment device.

Apply an existing deposit to the final balance, then book a future appointment with a separate new deposit. The two amounts should remain distinguishable. A booking confirmation showing a deposit does not prove it was applied to the right visit. Test rescheduling and a deposit attached to an incorrect appointment, using the provider’s supported process.

Include a retail product and a product-only return. Confirm stock changes without reversing the service or its staff credit. For packages or gift balances, verify the remaining entitlement rather than substituting an arbitrary discount. Before migration, establish who reconciles opening balances and what historical records remain accessible.

Tips and service charges need distinct records and an approved payroll handoff. Check which professional receives the service and tip attribution when reception takes payment or multiple people serve one guest. The salon’s advisers should confirm treatment and distribution. A software report can support that process without establishing the correct payroll policy by itself.

Run a traceable acceptance exercise

Use an appointment with a deposit, two service professionals and a product-only return as the starting scenario. Keep the records fictional or use the provider’s supported test facilities. Define the expected result before the demonstration: the amount due, responsible employee, payment status and final state of the booking and service ticket. This prevents an impressive screen transition from replacing a meaningful outcome check.

Have the receptionist, service professional, manager and payroll owner each inspect the part they rely on. One person may confirm a device approval while another still sees an unpaid balance or an incorrect operational record. Record those differences rather than assuming the first success proves the entire process. Ask the employee to repeat the workflow under the permissions proposed for normal use.

For this launch-readiness check, capture a normal case, a correction and an interrupted handoff. Record whether each step is automatic, manual or unsupported in the quoted configuration. Include the application and provider that perform the step. A test led by an administrator should be repeated with the intended staff role wherever the task depends on permissions.

Save the relevant non-sensitive references and the report filters. Recheck the result after the applicable business-day or settlement boundary. A later adjustment may change what the first screen showed, so the acceptance record needs a time as well as an amount. Resolve any contradiction before treating the workflow as complete.

Make the evidence usable for the next employee

Keep a short procedure beside the test record. It should tell the next employee how to locate the appointment, confirm its payment status, identify the authoritative booking and service ticket and find the correct support route. Include the stopping point when a result is uncertain. A procedure that merely says “contact the manager” leaves the manager without the references needed to investigate.

The reception manager should approve the closing check and the ownership of unresolved exceptions. Give each open item a description, reference, amount where relevant, responsible person and next action. Retain the original evidence rather than overwriting it with a corrected total. The history should explain why the final record is now considered correct.

Keep credentials, full card details and unnecessary customer information out of the worksheet. Arrange secure document sharing when a provider requires more evidence. A redacted report can still expose sensitive details if identifiers are left in notes or filenames, so review the whole document before sharing it.

After the first operating period, look for repeated exception categories. A recurring manual adjustment may indicate a configuration or training dependency that belongs in the implementation scope. Review that evidence before adding another location, device or sales channel. The objective is a repeatable process your staff can verify, not a one-time demonstration that only the vendor can explain.

Prepare the review without exposing private records

Summarise the business, current software, payment channels, locations and the specific appointment problem you want resolved. Include a non-sensitive example and the outcome you expected. That gives a review more direction than a general request for better rates or a new device. List existing components you want to retain so proposals account for them.

Process Rite helps organise the payment requirements, provider questions and written comparison. Availability, integration, account approval, implementation and service terms need confirmation in the applicable proposal and provider agreement. Hardware, software, applications and processing charges should remain identifiable. Request a custom proposal based on the configuration and channels your business actually needs.

Use the website enquiry for the summary, then arrange document sharing after contact. Do not submit payment credentials, bank logins, passwords or private customer records. Include your town and preferred callback time so the conversation starts with the right context. Consultations and any site work are arranged directly. Confirm the responsible support contact and available service hours in the proposal.

What deserves extra attention during salon migration?

Reconcile appointments, unapplied deposits, package entitlements and gift balances separately from the client contact list. Those records carry different obligations and may not transfer through one import. Assign an owner to each opening balance and preserve the evidence needed to explain it. Test a changed appointment and a product-only return before reception relies on the new arrangement during a busy day.

Continue with a related workflow guide

• Salon POS and appointment payments
• Salon checkout and rebooking
• Salon report mismatch guide
• Salon deposits and online payments

Acceptance record to keep with the decision