Last checked: September 4, 2026 · United States · Square Dashboard and advanced booking capabilities.
Quick answer: For a salon with 4–8 stylists, configure a color appointment as a sequence of occupied and potentially bookable staff time, then separately prove that every client has a physical place to receive the service. Start with one repeatable service and one supervised overlap. Do not open every processing gap to online bookings just because it appears free on the stylist’s calendar.
Square documents processing time on eligible Plus and Premium plans and resource management on Premium. Its resource instructions describe reserving one resource from the choices assigned to a service. They do not establish that selecting both chairs and basins reserves one of each, or that equipment is released separately during each phase. Treat those as fit tests before buying or launching. Sources: processing time and resource management.
Who this setup is for—and where it may fall short
This guide is for the owner or front-desk manager of a single-location US color salon with shared stations, a limited basin pool, and several bookable stylists. It assumes you are adopting Square or changing an existing Square booking menu. Your goal is a reliable appointment promise: the right service, worker, station, return time, and payment instructions.
Best fit: a salon willing to standardize a narrow repeat-service menu, keep uncertain work behind a consultation, and have a named manager handle exceptions. A trial of the paid plan is especially useful when you can reproduce a busy morning with fake clients before changing public availability.
Not best for: a business whose required booking model depends on independently reserving several resource types in different phases, simultaneous work by several providers on one service, or separate ownership and payment settlement for independent renters. Those needs require a demonstrated solution; this tutorial does not establish that Square supports them. If you are still choosing a platform, use the scheduling software comparison to define your requirements first.
Research method: We reviewed public US pricing, help, privacy, security, and subscription documentation. We did not access a salon account, perform a booking, measure increased capacity, or test payment collection. The workflow, times, checklist, and pass/fail cases below are original planning examples. Menu labels may differ by account or app; verify the documented behavior in your plan. This is scheduling guidance, not advice on color chemistry or treatment suitability.
Check the plan and the cost before changing settings
| Current US plan | Monthly price per location | Relevance to this workflow |
|---|---|---|
| Square Free | $0, plus payment processing | Basic booking; not the plan for this processing-time/resource configuration. |
| Square Plus | $49 | Processing time and multi-staff booking; shared-resource management is the missing gate. |
| Square Premium | $149 | Resource management as well as processing time and multi-staff booking. |
The US pricing page lists 30-day Plus/Premium trials, cancellation or plan switching, and phone support of 6 a.m.–6 p.m. Pacific weekdays for Plus versus 24/7 for Premium. These are public plan terms, not an account quote or a promised resolution time. Processing, hardware, taxes, and separately purchased services can add cost.
Older “Square Appointments” subscriptions coexist with the newer Square bundles in help articles. Check your Dashboard’s exact plan, advanced booking capabilities, billing date, and feature access. Do not switch merely to follow this guide: Square says you cannot return to your former subscriptions after switching to its new plans. Save your current bill and compare the complete bundle before accepting a change. See Square’s plan-change guidance.
1. Write the service timeline before entering it into Square
Ask the lead colorist and front desk to describe one predictable repeat appointment. Record when the stylist must be available, where the client sits, what happens at the basin, and who owns the finish. Use the service time your team has validated for that client and treatment; do not shorten it to manufacture an extra slot.
The following is a synthetic scheduling example, not a treatment protocol. It models a 120-minute repeat-color visit plus ten minutes of recovery capacity.
| Example interval | Stylist A | Client 1 and physical capacity | Booking decision |
|---|---|---|---|
| 9:00–9:30 · initial work | Occupied | Uses Station 1 | No second appointment with A. |
| 9:30–10:15 · processing | Potential gap, subject to supervision requirements | Still needs an approved place to sit | A second service needs its own space and must finish before the return. |
| 10:15–11:00 · final work | Must return | Needs basin access and finishing space | Protect the return time and physical capacity. |
| 11:00–11:10 · recovery | Unavailable for a new promise | Reset and late-running allowance | Keep the allowance separate from client service duration. |
A 30-minute second service from 9:30 to 10:00 would leave 15 minutes before A returns. That arithmetic is only a candidate: consultation, movement, cleanup, monitoring, and overruns must fit too. A 45-minute service consuming the whole gap leaves no recovery margin. If Client 1 stays in the only available station, neither candidate is physically workable.
Use three separate questions: Is the worker free? Is an appropriate space free? Can the worker return when promised? A yes to one cannot substitute for the other two.
2. Prepare a controlled test and name its owner
Before editing, save the current service names, durations, eligible staff, booking settings, resources, and future appointment list. Record the time of that snapshot and identify the person who can restore the configuration. For a larger move from another system, use the software migration checklist and workbook to reconcile records and choose a cutover time.
Use isolated nonpublic services and time blocks for staff-side tests where available. A test name is not an isolation control, and a hidden service cannot prove online booking. For synthetic end-to-end tests, use a separate authorized test account with a controlled booking URL or arrange a support-assisted demonstration. This guide does not establish a full Square Appointments sandbox. In production, inspect public availability without submitting fake bookings until the owner has arranged a protected pilot. Use team-controlled contact details, suppress unnecessary notifications, and never test in occupied client slots or run unapproved real charges.
Assign an owner, a front-desk tester, and a stylist to walk through the timeline. Agree on a stop rule: any conflict involving a returning client, a missing resource, an unintended public service, or an unexplained payment stops the rollout. Cosmetic calendar preferences can wait.
3. Build a small, understandable service menu
In Dashboard, go to Items & services → Items → Service library → Create service. Set the service name, location, price, and duration. Square supports service variations for different timing/pricing, extra blocked time after a service, and booking add-ons with added price or duration. See creating and managing services.
Start with three distinct customer choices: a consultation for work that needs assessment, a defined repeat-color service, and a finishing service only where it makes sense to book separately. Write the repeat service’s eligibility in ordinary language. Explain whether the finish is included, whether timing varies, and how someone uncertain should contact the desk.
Do not make clients assemble a technical treatment sequence by guessing at a list of components. If an add-on changes the workload, test that both the displayed duration and actual reserved time change. If a first-visit request needs assessment, route it to a consultation or staff review rather than allowing a short repeat-service slot.
Keep this first release deliberately small. Ten confusing variations are harder to verify than two clearly different choices. Record why each variation exists, which workers may perform it, and the source of its duration. If the only difference is a marketing label, consolidate it.
4. Add processing time and protect the finish
Open the service in Dashboard and enable Add processing time under duration. Configure the initial, processing, and final durations; Square defines total service duration as their sum. For the synthetic example, that is 30 + 45 + 45 = 120 minutes. Individual appointments can have their processing time edited or removed. Follow the current processing-time instructions.
Then apply the separate end-of-appointment block if your workflow needs recovery time. A processing gap is a candidate for another booking; a recovery block protects time after the visit. Making the latter bookable would defeat its purpose.
Expected outcome: the calendar preserves the 10:15 return and the 11:00 finish, while any permitted second service fits completely inside the usable gap. Test the same appointment with a longer initial stage and a shorter processing stage. Check the saved start/end times, not just the color or apparent width of a calendar bar.
If the stylist must remain occupied throughout a particular client’s processing stage, keep that visit fully blocked. Online availability is an operational promise; it should not depend on the desk remembering an invisible exception.
5. Model chairs conservatively and test basins separately
Square’s documented path is Items & services → Items → Resources. Create individually named stations at the correct location. In the relevant service or variation, enable Require a resource and select suitable alternatives. The documentation says one assigned resource is booked. See resource setup.
A list containing Station 1, Station 2, and Basin 1 therefore must not be treated as a promise to reserve a station and a basin. Similarly, a visible staff gap does not prove a chair is released. The reviewed instructions do not settle phase-specific occupancy. Write these limitations into your trial questions instead of inventing a workaround.
Choose a deliberately conservative first model: only expose online services whose physical capacity can be proved, and have the desk review basin-dependent overlaps. A resource reserved longer than physically necessary may reduce available appointments; that is a visible tradeoff. A resource not reserved when needed creates a conflict that the client discovers on arrival.
Ask support to demonstrate your exact timeline if you need separate chair, basin, and processing-area reservations. Provide fake clients, times, service variations, and the expected conflict. A generic resource-management demonstration is insufficient. If the result cannot meet the salon’s requirements, retain manual booking for that service or evaluate another platform.
6. Verify staff eligibility and any service handoff
Set the eligible staff for each service variation. Then review recurring availability and the specific test date: a normal weekly schedule does not establish that a worker is present on a vacation or training day. Square documents weekly and one-time availability changes in its staff-schedule instructions.
If color and finish are separate services assigned to different people, enable Allow multiple staff to be booked in a single appointment under Appointments → Settings → Calendar & booking. When creating the appointment, select the assigned worker within each service. Square documents multi-staff booking across services; this does not establish two workers concurrently reserved for the same service. See multi-staff scheduling.
Expected outcome: both workers see their correct commitment, and the client receives a coherent visit time. Check that the finish cannot be scheduled with an ineligible worker or when the receiving stylist is absent. If the finish is included in the first service’s final duration, do not also sell and reserve it as a second service.
Reassignment needs an owner. When a stylist calls out, the desk should review the whole visit and remaining capacity before moving individual components. A technically empty calendar slot may still be unusable because it breaks the client’s sequence.
7. Configure the public booking rules and payment message
Under Appointments → Settings → Calendar & booking, review request acceptance, booking interval, advance notice, multiple-service booking, and the business time zone. For the pilot, manual acceptance can create a deliberate desk review. It is a business booking preference, not proof of a special consultation-only rule. Square also notes that staff can exceed online daily booking limits. See appointment settings.
Keep enough advance notice for the actual reviewer to respond. Specify who clears pending requests and what the client should do if a request has not been accepted. A queue that nobody checks merely relocates the scheduling problem.
In Settings → Payments & cancellations, verify the policy shown to clients. A card held for no-show protection is not a payment or a guarantee that a later charge succeeds. Square distinguishes no requirement, full prepayment for fixed-price services, and a card hold; its documentation contains conflicting descriptions of prepaid self-cancellation. Test your exact acceptance/payment combination and obtain support confirmation before promising self-service changes. See payment and cancellation policies.
Give the desk a separate refund/change checklist. After changing a prepaid service, reconcile the appointment with the payment instead of assuming the amount adjusted automatically. Apply only the policy the client received and accepted; seek qualified local advice if enforceability depends on the client’s circumstances or jurisdiction.
Use the booking page to explain the visit in plain language. For example: “Repeat-color bookings are for an existing service plan. If you want a change or are unsure which option fits, request a consultation. Your confirmation shows the visit time and booking status.” This is original example copy, not a legal policy or a guarantee of eligibility.
8. Limit access and keep client data out of the wrong places
Square distinguishes Service Provider, Front Desk, and Manager access; enabling Dashboard access also exposes customer information. Review the actual permissions of each login. The front desk needs enough access to resolve the team’s bookings; a stylist should not become a Manager simply to solve a setup inconvenience. See bookable team members and permissions.
Use individual logins, inspect access from a worker’s account, and restrict client exports to named people. Treat reassignment and access removal as separate checks when someone leaves: preserve the appointment commitments, move them to an appropriate worker, then remove unnecessary access.
Do not put card numbers or health information in customer notes. Square explicitly warns against this in its Customer Directory guidance. Keep this scheduling worksheet to service codes, timing, resource needs, and review status. Sensitive consultation records need a separately assessed system and access policy.
Document what data you collect, who can export it, and how long you retain local copies. Square’s privacy notice does not establish US-only storage or immediate erasure after account cancellation. Confirm contractual requirements before migrating data that has special restrictions. Appointment communication permission should not be treated as permission for every marketing use.
9. Prove the booking flow with an acceptance worksheet
Copy this matrix into your rollout record. For every case, add the test appointment ID, channel, observed result, evidence location, tester, and retest date. The outcomes are required acceptance criteria, not results we observed. Run public-channel cases signed out on phone and desktop within the controlled test arrangement from Step 2; repeat critical conflicts through front-desk booking because manual paths may behave differently.
| Case | Attempt | Required result before release |
|---|---|---|
| A · baseline | Book the 9:00 repeat-color example. | Correct worker, 120-minute visit, protected return, intended station, correct client message. |
| B · usable gap | Request a 9:30–10:00 service with A and another suitable station. | Permit only if all physical and staff requirements are satisfied; preserve the original finish. |
| C · late return | Request a second service that runs beyond 10:15. | No automatic promise that overlaps A’s required return. |
| D · occupied station | Repeat B when no other suitable station is available. | Block or hold for review. Never claim capacity solely from A’s gap. |
| E · basin collision | Arrange more simultaneous rinses than available basins. | A demonstrated reservation/review control catches the conflict before acceptance. |
| F · staff handoff | Remove the receiving stylist’s availability. | The complete visit cannot be accepted with an uncovered finish. |
| G · changed scope | Add a longer variation or timed add-on. | Price, occupied time, end time, staff, and resource availability all remain consistent. |
| H · reschedule | Move the original visit to another time. | Review both visits and their resources; no orphaned component or duplicate promise. |
| I · public menu | Open every website button, old embed, and booking channel. | Only intended services and variations appear; consultation rules remain visible. |
| J · financial exception | Walk through a prepaid change or failed fee collection without an unapproved real charge. | A named person reconciles the appointment and payment; no repeated blind charge attempt. |
| K · permissions | Use a stylist login and a front-desk login. | Each can perform required work without unnecessary export or account control. |
| L · recovery | Pause online booking and use the saved appointment inventory. | Desk can identify pending/confirmed visits, avoid duplicates, and communicate a manual resolution. |
Record unresolved cases as HOLD, even if every other test passes. The matrix is not a weighted score: eleven passes do not cancel out one double-booked basin. Where a manual control is acceptable, name its operator and response deadline and demonstrate it before release.
10. Launch one service, watch exceptions, and keep a rollback path
Square exposes booking channels under Appointments → Online Booking → Channels. Publish or connect the narrow menu only after the acceptance checks. Test old embeds as well as the new link: Square says advanced widgets show all service variations regardless of online-booking settings. Removing a widget definition also does not remove code embedded elsewhere. See online booking setup.
Use the first ten genuine bookings as a supervised pilot. That is a suggested operational sample, not a performance benchmark. Compare promised and actual start, return, and finish times. Log resource conflicts, manual edits, unaccepted requests, duplicate communications, and payment exceptions. Review daily with the desk and lead stylist. Broaden the menu only when the observed work supports the timing model.
For rollback, pause the affected online offering, record every new or changed booking since the snapshot, and reconcile those changes before restoring settings. If the fault spans channels, Square documents disabling online booking from Channels. Test the result signed out. Do not cancel legitimate client appointments simply to recreate the old calendar.
Restore the last verified service configuration, keep a dated incident record, and have the desk resolve affected visits individually. A rollback of settings cannot reverse a customer message already sent. Confirm the corrected promise with the client once the final appointment is stable.
Cost example: buy the required control, then check the bill
Assume one location takes $30,000 across 200 in-person card payments in a month. At the checked public rates—Plus 2.5% + 15¢ and Premium 2.4% + 15¢—the arithmetic is:
- Plus: $49 subscription + $750 percentage fees + $30 transaction fees = $829.
- Premium: $149 subscription + $720 percentage fees + $30 transaction fees = $899.
The difference is $70 in this synthetic case, before subscription taxes, hardware, other payment types, or add-ons. Treat $30,000 as total processed volume, including any collected tax and tips; Square applies processing fees to the transaction total. This is not measured savings or a revenue forecast. Use your account’s rates, payment mix, and bill. Choose Premium here for a proven resource control, rather than assuming a lower processing rate pays for the subscription. Rates and fee basis: Square’s US fee guide.
Also budget staff setup and verification time. For example, six hours at an internal planning cost of $30/hour adds $180 once; substitute your own assumption. Review renewal dates and downgrade timing in subscription management. Square’s general terms, section 10, generally provide access through the paid period after cancellation rather than a refund of fees already paid or due, subject to applicable service terms. Keep your actual agreement with the rollout record.
Troubleshooting, calendar connections, and export
| Symptom | What to inspect | Conservative response |
|---|---|---|
| Processing/resources option missing | Exact plan, Bookings capability, login permissions, and Dashboard versus app. | Check entitlement before changing the subscription. |
| A gap exists but a client cannot book | Service eligibility, start interval, total duration, recovery allowance, staff absence, and resource occupancy. | Resolve the limiting requirement; do not shorten the visit blindly. |
| Two clients need the same chair/basin | Assigned resource and actual physical occupancy at each phase. | Pause automatic overlap until a reliable control passes case D/E. |
| The wrong service appears online | Every variation, advanced widget, old embed, and channel. | Remove the exposed path and repeat signed-out tests. |
| A change creates conflicting messages | Appointment status, notification choices, connected calendars, and duplicate records. | Choose one booking record and one human owner before sending a correction. |
If the capability is missing, Square documents adding Bookings capabilities; activation does not bypass the paid feature tier. Give support your exact plan, location, service variation, fake timeline, and reproducible expected/actual result. Keep their answer and the date with your test evidence.
For Google Calendar, choose the required import/export direction and test a busy event. Square says changes belong in the calendar where an event originated; Square personal blocks do not export, and events added directly to the synced Appointments calendar in Google can disappear after resync. Check the destination’s sharing permissions before exposing appointment details. This is a connection to test, not a substitute for appointment reconciliation. See Google Calendar sync.
Export appointment history through Appointments → Settings → History → Export. Export customer records separately through Customer Directory. A CSV download does not prove that future bookings, resources, attachments, and permissions can be restored. Inspect fields and reconcile a known sample, then inventory anything missing. Saved payment credentials require a separate supported processor-transfer process, not an ordinary customer CSV. Sources: history export and customer/card portability.
Keep automated work bounded: reminders follow a verified appointment; a calendar change requires availability checks; a failed action returns to a named person. Do not let a text generator infer treatment duration, resource capacity, or permission to charge. For a broader record-ownership design, see the scheduling, CRM, and invoicing integration guide.
Reusable launch checklist and next steps
Copy this compact record alongside the acceptance matrix. Fill every field with the salon’s real configuration before approving launch.
- Scope: location; plan; capability; service/variation; owner; check date.
- Timing: initial minutes; processing minutes; final minutes; recovery minutes; hard return time; person approving the durations.
- Capacity: worker; eligible stations; basin needs; client location during processing; any constraint handled manually.
- Public promise: eligible client; displayed price/duration; included finish; acceptance status; payment/cancellation message; all channel links.
- Evidence: cases A–L; observed result; fake appointment reference; tester; unresolved HOLDs; support confirmation where required.
- Recovery: snapshot date; future-booking reconciliation; pause procedure; exception owner; next review; accessible export sample.
- Decision: GO only when required tests pass and any manual review has a working owner. Otherwise keep the affected service on HOLD.
Start with the timeline and the occupied-station test. If the salon cannot prove those two pieces, defer overlapping online color bookings. Once they work, add the staff handoff, payment exception, and channel tests, then supervise the first bookings. The ToolBuyerDesk software guides hub connects the wider selection and implementation work.
Sources and freshness
All linked vendor material was checked September 4, 2026 for the US market. Square is continuously updated SaaS; these pages did not expose a numbered Dashboard build. Help/pricing revision dates were not shown. The general terms were updated June 1, 2026, applying to all sellers from July 1; the privacy notice was updated March 16 and effective April 16, 2026. Recheck plan gates, prices, policies, and menu paths before purchase or rollout. Documentation is evidence of stated capability; the acceptance matrix supplies the account-specific proof still needed.