PROCESS RITE · PRACTICAL OPERATING GUIDE
Salon Online Payments: Booking Deposits, Retail Orders and Packages
Use the right transaction flow for an appointment, a product order or a prepaid service instead of treating them as the same checkout.
In this guide: Name what the guest is buying · Keep booking acceptance separate from payment status · Work a rescheduled deposit example · Define fulfillment for retail orders · Track prepaid balances explicitly · Inspect forms and outstanding exceptions · A three-flow review before launch
Name what the guest is buying
An appointment deposit reserves or contributes toward a service under the salon’s policy. A retail purchase buys a product. A prepaid package creates a different balance to track. A single generic payment link can obscure these differences if the business record does not identify the purpose.
Choose a reference that links each payment to the appointment, product order or package record. Confirm which system owns the balance and what the guest sees after completion. Do not describe an appointment as fully paid when only a deposit has been collected.
Keep booking acceptance separate from payment status
Clarify whether a booking is provisional, confirmed or awaiting payment. Define who reviews a booking when payment is completed but the appointment is not confirmed. Staff should have an exception queue rather than relying on the guest to notice the mismatch.
If the booking application and payment page are separate, ask how the result is returned. Confirm the behavior when the guest closes the browser or a notification is delayed. A browser success page is useful feedback, but the salon needs a provider-confirmed payment record linked to the booking.
Work a rescheduled deposit example
Suppose a fictional guest pays a $25 deposit for an appointment that moves from Tuesday to Friday. The staff member should be able to find the original payment and show its treatment on the rescheduled booking. A calendar move should not create a second deposit request by accident.
At checkout, apply the appropriate credit to the service balance under the salon’s policy. If cancellation or transfer rules affect that credit, use the salon’s published, adviser-reviewed terms. This guide does not establish a universal refund entitlement or deposit policy.
Define fulfillment for retail orders
For online products, distinguish order received, payment confirmed, ready for pickup and collected. Decide who checks stock and who tells the guest about a shortage. A salon that also sells the same products at the counter needs a clear availability owner.
If a product is returned, record both the payment correction and whether the product is resalable. Keep product refunds separate from appointment changes. An order number and a booking number may look similar while referring to different obligations.
Track prepaid balances explicitly
Before offering packages or stored credits, confirm what the chosen application records, how redemptions work and how an outstanding balance is reported. Ask the appropriate adviser to review the terms and requirements for the particular offer.
Do not model a package as an ordinary sale followed by undocumented free services. The salon needs a way to explain what remains, which appointment used it and how corrections are approved. If the application cannot support that record clearly, reduce the initial scope rather than inventing an untraceable workaround.
Inspect forms and outstanding exceptions
On a phone, check the service description, amount, guest contact fields, optional choices and confirmation. Avoid collecting unrelated personal information. Let staff locate the transaction using its reference without needing the guest to forward sensitive screenshots.
Review paid-but-unconfirmed bookings, unpaid confirmed bookings, uncollected product orders and unexplained package balances regularly. Assign an owner to each. Launch one clear flow first and expand only after its records and correction route work reliably in the actual configuration.
A three-flow review before launch
Create separate sample records for a booking deposit, retail product pickup and prepaid package if offered. Each needs a clear purpose, balance owner, payment reference, fulfillment or redemption event and correction route. If one cannot be explained without a private spreadsheet, resolve the record design before selling it publicly.
For the booking, test a reschedule. For the product, test a shortage. For the package, test one permitted redemption and find the remaining balance. Use synthetic data and the application’s approved evaluation procedure. Do not claim these proposed checks are hands-on tests of every product.
Should all three flows share one generic confirmation? Tailor the wording to what was actually purchased. Does a paid deposit establish the whole appointment is paid? Show its credit and remaining balance. Can package functionality be improvised with a discount button? Confirm a supported balance and redemption record first, together with appropriate review of the offer’s terms.
Reference: Clover® hosted payment integration documentation. Reviewed October 17, 2026. The exercises above are proposed operating checks using fictional records, not claims of hands-on testing of every product. Confirm the actual plan, application, account and written proposal.
Continue: POS workflow for salons · Support routes · Request a free payments review
Request a Focused Payments Review
Tell us your current software, business type and the workflow you want to improve. Arrange document sharing after contact.
