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
- Data model
The tables behind Salon Management System
Salon Management System ships with 11 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 11
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Booking and Arrival
Bookings records record number, Subject, customer name, starts at, ends at, quoted amount USD, Revision and Status. Organization, Owner and Counterparty reference Organizations, team members and Resources respectively.
Resource Reservations
Booking resources references Parent and Resource. Capacity, reserved units, setup minutes, cleanup minutes and confirmed at describe the reservation claim and its context.
Stylist Appointments
Stylist appointments references Bookings through Parent and Organizations through Organization. Stylist and Service are text; starts at, service minutes, Revision, decision at and Status describe the extension.
Service Completion
Bookings.completed at records the completed visit. Record attachments retains evidence with Parent, uploaded by, evidence type, Visibility and File.
Payment Evidence
Payment evidence links provider events to the booking through Parent. Provider event ID, Type, amount USD, occurred at, Verified and provider reference describe the event.
Changes and Reconciliation
Review decisions retains the reviewer, source revision, reason and operation key. Operation receipts records the action, expected revision, result state, effect references and any failure reason against the parent booking.
Staff and salon context
Team members links each staff identity to Users and Organizations. Resources belongs to Organizations. Active is a boolean on organizations, resources and team members.
Every table, by feature
- Booking and Arrival7
- Resource Reservations5
- Stylist Appointments6
- Service Completion5
- Payment Evidence4
- Changes and Reconciliation6
- Shared and settings1
- Bookings
Salon appointment bookings with lifecycle, schedule and quoted amount
Linked to Organizations, Team members, Resources - Booking resources
Resource reservations and capacity claims attached to a booking
Linked to Bookings, Resources - Resources
Bookable salon resources such as chairs, stations and treatment rooms
Linked to Organizations - Team members
Salon staff and their platform identity and role scope
Linked to Organizations, Users - Organizations
Salon organizations and locations operating in the system
- Record attachments
Uploaded evidence files attached to a booking
Linked to Bookings, Team members - Payment evidence
Provider payment events reconciled against a booking
Linked to Bookings
- Booking resources
Resource reservations and capacity claims attached to a booking
Linked to Bookings, Resources - Resources
Bookable salon resources such as chairs, stations and treatment rooms
Linked to Organizations - Bookings
Salon appointment bookings with lifecycle, schedule and quoted amount
Linked to Organizations, Team members, Resources - Organizations
Salon organizations and locations operating in the system
- Operation receipts
Durable receipts for every guarded operation executed against a booking
Linked to Bookings
- Stylist appointments
Stylist appointment extensions supporting the confirm a stylist appointment operation
Linked to Bookings, Organizations - Bookings
Salon appointment bookings with lifecycle, schedule and quoted amount
Linked to Organizations, Team members, Resources - Organizations
Salon organizations and locations operating in the system
- Review decisions
Independent review decisions recorded against a booking revision
Linked to Bookings, Team members - Operation receipts
Durable receipts for every guarded operation executed against a booking
Linked to Bookings - Record attachments
Uploaded evidence files attached to a booking
Linked to Bookings, Team members
- Bookings
Salon appointment bookings with lifecycle, schedule and quoted amount
Linked to Organizations, Team members, Resources - Team members
Salon staff and their platform identity and role scope
Linked to Organizations, Users - Record attachments
Uploaded evidence files attached to a booking
Linked to Bookings, Team members - Operation receipts
Durable receipts for every guarded operation executed against a booking
Linked to Bookings - Payment evidence
Provider payment events reconciled against a booking
Linked to Bookings
- Payment evidence
Provider payment events reconciled against a booking
Linked to Bookings - Bookings
Salon appointment bookings with lifecycle, schedule and quoted amount
Linked to Organizations, Team members, Resources - Operation receipts
Durable receipts for every guarded operation executed against a booking
Linked to Bookings - Record attachments
Uploaded evidence files attached to a booking
Linked to Bookings, Team members
- Bookings
Salon appointment bookings with lifecycle, schedule and quoted amount
Linked to Organizations, Team members, Resources - Booking resources
Resource reservations and capacity claims attached to a booking
Linked to Bookings, Resources - Operation receipts
Durable receipts for every guarded operation executed against a booking
Linked to Bookings - Review decisions
Independent review decisions recorded against a booking revision
Linked to Bookings, Team members - Payment evidence
Provider payment events reconciled against a booking
Linked to Bookings - Record attachments
Uploaded evidence files attached to a booking
Linked to Bookings, Team members
Keys and references
The model contains 11 tables. Preserve record identities when importing related data. Bookings.Counterparty points to Resources; it is not a customer reference. Customer name is text on the booking. Stylist appointments.Stylist is also text and must not be used as a substitute for team members.User when authorizing an action.
Bookings has starts at and ends at for the schedule. Service minutes belongs to the stylist extension, while setup minutes and cleanup minutes belong to reservation lines. Keep their meanings distinct when defining the occupied interval. Revision, source revision and expected revision identify current work, reviewed work and the operation’s expected input respectively.
Review decisions.Parent references Bookings. When reviewing a stylist extension, preserve the exact extension identity and frozen revision through the supported operation evidence. Operation receipts.Parent likewise references the booking. Provider event ID and provider reference identify payment evidence; a displayed amount alone cannot establish a verified event.
Migration order
- Salon and accounts. Establish Organizations and Users before importing team members and their identity mappings.
- Resources. Import Resources with the correct organization and operating eligibility information.
- Bookings. Import appointment identities, schedules, owners and resource references, preserving recorded lifecycle facts.
- Reservation and service details. Import booking resources and stylist appointments against their exact parent bookings.
- Attachments and decisions. Preserve original upload attribution, visibility, reviewer identity and source revision when importing evidence.
- Provider events. Import payment evidence with authentic provider identities and verification facts; do not infer verification from an amount.
- Operation history. Retain original operation keys and effect references. Keep uncertain outcomes unresolved until evidence supports completion.
Set up Salon Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.