These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Salon Management System
- Features
- Changes and Reconciliation
Changes and Reconciliation
Handle cancellations, no-shows and corrections without losing the evidence behind completed salon work.
OverviewOperation Exceptions×
Salon Management System · Changes and Reconciliation
New
Operation Exceptions
Operation receipts
| Parent | Action | Operation key | Expected revision | Result state | Occurred at | |
|---|---|---|---|---|---|---|
| BKN-59147 | ACT-279 | OK-594 | 800 | Pending | 15 Oct | |
| BKN-68504 | ACT-762 | OK-210 | 610 | Failed | 14 Oct | |
| BKN-25004 | ACT-297 | OK-439 | 840 | Needs review | 21 Oct | |
| BKN-56291 | ACT-562 | OK-606 | 160 | Pending | 16 Oct | |
| BKN-88850 | ACT-599 | OK-642 | 580 | Failed | 22 Oct |
6 of 6 records
ACT-279Operation receipts · OR-93828
PendingParentBKN-59147
Operation keyOK-594
Expected revision800
Occurred at15 Oct
External referenceER-128
What you can do
Make the next action depend on what already happened
A booking change can affect a held resource, a customer who has not arrived or a service already performed. Booking Coordinator first identifies the current booking revision and its recorded effects. The authorized cancellation or correction route then handles the appropriate scope while preserving the earlier history.
A customer who cancels before service and a customer recorded as a no-show need different explanations. A no-show is recorded only after the appointment threshold agreed by the salon. Neither event should erase a completed service or the provider’s payment evidence, and any capacity release needs a traceable result.
How the work is organized
- Eligible cancellation. Validate organization, actor and expected revision before cancelling the booking. Release still-reserved capacity once and retain the operation receipt that explains the effect.
- Correction after completion. Booking Supervisor approves the required compensating action when the work has already been carried out. Keep the original source identity and evidence so the correction remains understandable.
- Outcome reconciliation. Examine pending or failed receipts against the linked effects. Record completion only when the expected scope, identity, quantities and revision agree; otherwise retain a concrete discrepancy for review.
What to agree during setup
Agree which booking states allow cancellation and how the salon defines its no-show threshold. Staff should know when to contact the customer and when the authorized operation can record the outcome. Keep that timing policy separate from any payment-provider refund decision.
Define how the team reviews a correction after execution. Identify the independent Booking Supervisor and the evidence required for compensation. Also assign an owner for unresolved receipts so a pending result is investigated rather than repeatedly executed by different staff members.
Check the handoff on an actual case
Cancel an eligible held appointment with a resource claim. Follow the cancellation receipt and confirm that the still-reserved capacity is released. Retry the original cancellation request and verify that it returns the recorded release without releasing the reservation again.
Then rehearse an absent customer before and after the agreed no-show threshold. The early attempt should not establish a no-show. The eligible later operation should preserve the booking’s schedule and payment evidence so the front desk can explain the outcome.
Finally, prepare a correction to work already carried out. Booking Supervisor reviews the corrective action against the original booking and its history. After the operation, compare the receipt with the actual effects. If they disagree, retain a needs-review outcome with the discrepancy rather than presenting completion as established. Reconciliation checks evidence; it does not blindly repeat an external action to make an uncertain result disappear.
What your team sees
- Operation Exceptions — Pending, failed and needs-review outcomes with the references needed to investigate them.
- Cancellation and No-show History — Appointment outcomes retained with their scheduled interval.
- Booking Decision History — Revision-specific reviewer decisions and their reasons.
Follow the work through
Rehearse cancellation and correction, then use payment and outcome reconciliation for unresolved effects.
What it keeps track of
Data model- Bookings
- Salon appointment bookings with lifecycle, schedule and quoted amount
- Booking resources
- Resource reservations and capacity claims attached to a booking
- Operation receipts
- Durable receipts for every guarded operation executed against a booking
- Review decisions
- Independent review decisions recorded against a booking revision
- Payment evidence
- Provider payment events reconciled against a booking
- Record attachments
- Uploaded evidence files attached to a booking
Who uses it
Permissions- Booking Coordinator
- Requests eligible changes.
- Booking Supervisor
- Approves required compensation and reconciles outcomes.
- Payment Reviewer
- Examines provider evidence.
- Auditor
- Reads the history.
Set up Salon Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.