PROCESS RITE · PAYMENT WORKFLOW GUIDE
Salon Online Payments: Deposits, Products and Gift Sales
Plan appointment deposits, retail orders and gift sales as distinct workflows. Verify what reception sees, what the customer pays and how each collection reaches your reports.
In this guide
Separate booking payments from product orders
A salon website may collect appointment deposits, sell retail products, issue gift cards and offer packages. Those are different workflows even when customers reach them from the same homepage. Begin by identifying which system owns each record. The booking platform should know the appointment and any deposit; the store should know the product order and fulfilment status; the gift system should know the remaining balance.
Draw the customer journey for each purchase before selecting a gateway. A successful website charge is only one step. Reception must recognise the deposit when the client arrives, staff must know which products to prepare, and the owner must reconcile payment activity without counting the same sale twice. Require the proposed solution to demonstrate those outcomes rather than treating all online transactions as a single feature.
Document the existing website and account relationships
List the website platform, booking software, online store, gift-card service, processor and any gateway. Record the exact plan and supported connector for each. Establish who controls domain access, platform administration, billing and technical maintenance. A designer having access to the website does not necessarily mean that person can change payment-account settings or resolve a settlement issue.
Ask the provider to identify the supported connection for your actual platform and account. Do not assume an existing processor can be attached to every hosted store or booking product. Changing a website theme is different from changing a payment connection, but either can affect checkout presentation. Before updates, record the current working paths and a rollback owner so customers are not left on an unfinished payment page.
Make appointment deposits visible at reception
Choose an appointment example and define the amount collected online, the remaining balance and the system that posts both. Reception should see whether the deposit is confirmed, refunded or still pending under the actual platform’s terminology. A confirmation email is useful evidence but should not be the only method of deciding what to charge at the appointment.
In an illustrative example, a $120 service with a $30 deposit leaves $90 before any approved changes or tip. Demonstrate the appointment checkout and inspect the final receipt and reports. If the POS and booking platform are separate, document how staff apply the deposit without recording another $30 sale. This example is arithmetic for testing; it does not set the salon’s prices, deposit policy or accounting treatment.
Put cancellation terms beside the relevant decision
Clients should understand the salon’s policy before completing a booking or purchase. Have the salon approve the wording and obtain appropriate advice for cancellation, rescheduling, refunds and any no-show charges. The payment setup should record the customer’s action and the applicable policy version where supported. A saved card or an initial payment should not be treated as unrestricted permission for later charges.
Test the operational consequences of a rescheduled appointment. Confirm whether the deposit follows the appointment, remains as account credit or requires a separate action. Demonstrate a cancellation before and after the salon’s policy deadline using synthetic examples. Staff need a clear procedure and approval limits. Avoid telling clients that a refund is complete until the relevant system confirms that the refund has been submitted through its supported process.
Build product checkout around stock and fulfilment
A salon selling shampoo online needs more than a payment button. Define which location fulfils the order, how stock is reserved and who confirms dispatch or pickup. Test a product that is available online but also sold at reception. If stock synchronisation is delayed or unsupported, assign a practical buffer or manual review rather than promising real-time availability that the systems do not provide.
Use a demonstration with a single bottle, a multipack and a product variant if relevant. Check price, quantity, tax configuration and delivery or pickup charges against the owner’s approved setup. Confirm how discounts interact with bundles and whether returning one item changes the original discount. The employee preparing the parcel should see the order contents without needing access to unnecessary payment or customer information.
Test the entire checkout on a phone
Use an ordinary mobile browser and the same links a customer sees from the salon’s website, social profile or booking reminder. Check that the page identifies the business, shows the total before payment and presents readable fields without sideways scrolling. Labels, error messages and the final action should remain visible when the keyboard is open. Test returning from any external booking or payment page.
Where supported and configured, mobile wallets may shorten entry, but verify them on the actual device and browser combinations used in testing. Do not advertise a payment method merely because the gateway mentions it generally. Test a declined payment and a customer abandoning checkout. The order must not appear fully paid when no confirmed payment exists, and refreshing a confirmation page should not create another charge.
Keep gift cards distinct from packages and memberships
A gift card represents a stored balance in its issuing system. A package may represent a set of services, while a membership may involve recurring access or benefits. Write down what each product entitles the customer to receive, where it can be used and which system manages it. Confirm redemption across online and in-person channels rather than assuming a shared brand means a shared balance.
Test partial gift-card redemption, a remaining balance, a mixed payment and a return. For packages, demonstrate redemption by a different employee and how the remaining entitlement is checked. For recurring arrangements, confirm authorisation, cancellation and failed-payment procedures with the provider. A general ecommerce checkout does not establish that appointment entitlements, recurring billing and payroll reporting are all connected.
Decide how tips and staff attribution work
A retail product order does not necessarily belong in a service-tip workflow. Decide which online paths should offer tips and which should not, then test the exact configuration. If a client prepays for a service, show how an optional tip can be handled at the appointment without collecting the service balance again. The customer should be able to understand what has already been paid.
For staff reporting, distinguish who performed the service, who sold a product and who processed the checkout. Those may be different people. Confirm whether the software tracks each role and which report supports the salon’s own compensation rules. Do not describe a sales-attribution report as an automatic commission or payroll system unless that specific function and its calculation have been verified.
Give every refund an identifiable source record
Employees should begin with the original order or payment reference. Demonstrate a product refund, a booking-deposit refund and a gift-card-related adjustment separately. Confirm which application initiates each action and whether it updates the other records. Refunding a processor transaction may not automatically cancel an appointment, release stock or restore a gift balance.
Record the reason, approver and resulting status. Tell the customer what the system confirms, without guaranteeing a bank posting date that has not been established. If an integration fails after a refund request, assign someone to inspect the source system before retrying. A second click can create more confusion when the first action succeeded but the receiving application did not update its display.
Reconcile by channel before comparing deposits
Separate appointment deposits, final service payments, shipped products, pickup orders and gift activity. Choose consistent report periods and identify the business date used by each system. Compare the source ledger with processor activity, then processor settlement with the bank. Keep refunds, tips and adjustments visible so unexplained differences are investigated rather than hidden in a single monthly total.
For example, collecting $300 of deposits for future appointments and $500 for completed services is not the same operating story as $800 of completed service sales. The correct financial treatment should be agreed with the salon’s accountant. For payment reconciliation, preserve the references that connect each collection to its source. Ask the provider to demonstrate export fields before committing to a reporting workflow.
Limit customer data and access to what staff need
Use the provider’s supported payment entry and storage arrangements. Do not ask clients to email card numbers or put them in booking notes, contact forms or messaging threads. Clarify which service hosts checkout and which organisation handles account security. Tokenisation is not permission to export raw card details, and a website owner should not assume stored credentials can move freely to another provider.
Give reception, fulfilment staff and administrators appropriate individual access where supported. Remove departing staff promptly and establish an owner for permission reviews. For a demonstration or support request, use synthetic orders or redact unnecessary customer details. The Process Rite enquiry form should contain the setup problem and a way to contact you, not payment credentials or a client database.
Compare online costs with the actual channel mix
Prepare the same transaction assumptions for every proposal: online deposit count, product-order count, average amounts, refunds and any recurring collections. Separate transaction pricing from gateway, platform, app, monthly and annual charges. Include implementation, data preparation and ongoing maintenance. Do not compare a counter-payment headline rate directly with a complete online checkout proposal without explaining the different services and transaction mix.
Ask who bills for each layer and whether charges continue if the salon pauses online sales. Check contract term, cancellation, renewal, equipment ownership and portability. Hardware is separately quoted when required; a website payment discussion does not include a terminal. The pricing guide provides a framework for a complete comparison, while the final written proposal determines the actual commercial terms.
Plan migration around open appointments and balances
List future appointments with deposits, unfulfilled product orders, unredeemed gifts, unused packages and unresolved refunds before changing services. Decide which records remain in the old system and which can be moved through a supported process. Confirm export formats and the period for retaining access. Do not cancel the previous account merely because the new homepage is live.
Run a limited launch with a responsible person checking each new order. Keep the old and new references distinguishable and prevent customers reaching two active payment links for the same balance. Test old links from social profiles and automated emails. Changing the booking button on the homepage does not update every historical reminder, search result or bookmarked checkout path.
Prepare a support route for each failure
A client unable to book, an approved payment missing from an appointment and a missing deposit are different incidents. The booking provider may own the first, the integration provider the second and the processor the third. Write down the first contact, required reference and escalation owner for each. Confirm human-support availability directly instead of assuming it from a provider’s marketing language.
When contacting Process Rite support, describe the affected channel, time, system, visible status and business impact. Include safe reference information and a callback number. Do not send full card information. Staff should check the source transaction status before charging again and avoid making promises about refunds or settlement until the responsible provider has verified the result.
Use a launch checklist that reception can repeat
Choose six acceptance scenarios: a new appointment deposit, rescheduling that appointment, a product pickup, a partial product refund, a gift redemption and a failed payment. Write the expected customer message, source-system status and manager report before testing. The process passes when a second employee can follow it and reach the same result without relying on the person who configured the website.
After launch, review the first settlement and the first complete statement, then revisit manual work discovered during the trial. For the wider in-person workflow, use the salon POS guide and the terminal-versus-POS comparison. Request a free payments review with the systems and problem you want examined. A review supplies questions and options; it does not guarantee savings, integration or approval.
Discuss your actual setup
Tell Process Rite your business type, current software, payment channels and the problem you want resolved. We arrange document sharing after contact. Do not include card details, bank credentials or customer records in the enquiry.
Request a free payments review · Understand the complete cost · Find the right support route
Hardware, software, apps and implementation are separately quoted. Availability, integration, pricing and approval require confirmation in the written proposal. A review does not guarantee savings or approval.