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 + Booking + CRM + Inventory
- Salon booking data model
The tables behind Salon + Booking + CRM + Inventory
Salon + Booking + CRM + Inventory ships with 12 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
- 12
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Appointments and Customer Context
Bookings stores record number, customer name, Subject, starts at, ends at, quoted amount USD, Status and Revision. Organization references Organizations, Owner references team members and Counterparty references Resources.
Resource Holds
Resources belongs to Organizations. Booking resources links Parent to Bookings and Resource to Resources, recording Capacity, reserved units, setup minutes, cleanup minutes and confirmed at on the reservation line.
Consent and Payment Evidence
Record attachments links a File, evidence type and Visibility to the booking through Parent and the uploader through uploaded by. Payment evidence retains provider event ID, Type, amount USD, Verified and provider reference under Parent. Exchange rates supplies read-only Currency, effective from and Rate reference data.
Service and Product Use
Service consumption links to Bookings and Organizations. Service, product lot and consumed units describe actual use, with Status, Revision, decision at and completed at supporting close-out review.
Revision Decisions and Corrections
Review decisions links Parent to Bookings and Reviewer to team members. Source revision, Decision, Reason and operation key identify the decision context.
Completion and Exceptions
Operation receipts links to Bookings through Parent and records Action, expected revision, result state, effect references and failure reason. Team members links each operating identity to Organizations and Users.
Every table, by feature
- Appointments and Customer Context5
- Resource Holds5
- Consent and Payment Evidence5
- Service and Product Use5
- Revision Decisions and Corrections5
- Completion and Exceptions6
- Shared and settings1
- Bookings
Appointment bookings with lifecycle, quoted amount and resource counterparty.
Linked to Organizations, Team members, Resources - Organizations
Salon organizations / locations operating within the platform.
- Team members
Salon staff and platform identities, scoped to an organization.
Linked to Organizations, Users - Resources
Bookable salon resources: styling chairs, treatment rooms, equipment.
Linked to Organizations - Record attachments
Files attached to bookings as supporting evidence.
Linked to Bookings, Team members
- Resources
Bookable salon resources: styling chairs, treatment rooms, equipment.
Linked to Organizations - Booking resources
Reservation lines attaching resources to a booking parent.
Linked to Bookings, Resources - Bookings
Appointment bookings with lifecycle, quoted amount and resource counterparty.
Linked to Organizations, Team members, Resources - Operation receipts
Idempotent operation receipts for guarded workflow commands.
Linked to Bookings - Organizations
Salon organizations / locations operating within the platform.
- Payment evidence
Verified provider payment events reconciled against bookings.
Linked to Bookings - Record attachments
Files attached to bookings as supporting evidence.
Linked to Bookings, Team members - Bookings
Appointment bookings with lifecycle, quoted amount and resource counterparty.
Linked to Organizations, Team members, Resources - Operation receipts
Idempotent operation receipts for guarded workflow commands.
Linked to Bookings - Exchange rates
Read-only effective exchange rates for this app.
- Service consumption
Service close-out extensions recording actual product and service use.
Linked to Bookings, Organizations - Bookings
Appointment bookings with lifecycle, quoted amount and resource counterparty.
Linked to Organizations, Team members, Resources - Review decisions
Independent review decisions recorded against a source revision.
Linked to Bookings, Team members - Operation receipts
Idempotent operation receipts for guarded workflow commands.
Linked to Bookings - Record attachments
Files attached to bookings as supporting evidence.
Linked to Bookings, Team members
- Review decisions
Independent review decisions recorded against a source revision.
Linked to Bookings, Team members - Bookings
Appointment bookings with lifecycle, quoted amount and resource counterparty.
Linked to Organizations, Team members, Resources - Service consumption
Service close-out extensions recording actual product and service use.
Linked to Bookings, Organizations - Operation receipts
Idempotent operation receipts for guarded workflow commands.
Linked to Bookings - Payment evidence
Verified provider payment events reconciled against bookings.
Linked to Bookings
- Operation receipts
Idempotent operation receipts for guarded workflow commands.
Linked to Bookings - Bookings
Appointment bookings with lifecycle, quoted amount and resource counterparty.
Linked to Organizations, Team members, Resources - Service consumption
Service close-out extensions recording actual product and service use.
Linked to Bookings, Organizations - Review decisions
Independent review decisions recorded against a source revision.
Linked to Bookings, Team members - Payment evidence
Verified provider payment events reconciled against bookings.
Linked to Bookings - Record attachments
Files attached to bookings as supporting evidence.
Linked to Bookings, Team members
Keys and references
Preserve Id values when mapping operational records; exchange rates uses ID. Use record number for appointment discussions and provider event ID when tracing an external payment event. Customer name is booking text, while product lot is text on service consumption. Agree their source conventions before matching records across systems.
Resolve Bookings.Owner through team members.User for a signed-in personal view. Retain the Users.User self-reference when mapping platform accounts. Review decisions.source revision refers to the source decision context; it should not be assumed to equal a child service-use Revision. Use the configured decision and close-out contract to identify the accepted version.
Migration order
- Establish Users identities, Organizations and team members with correct account and organization references.
- Load Resources with their organization, code and eligibility note.
- Create Bookings with the appropriate owner and resource counterparty, retaining actual appointment dates.
- Attach booking resources and record attachments after their booking, resource and uploader references are mapped.
- Connect provider events to payment evidence and retain read-only exchange rates reference data through the supported source process.
- Use the configured operating paths for new service consumption, review decisions and operation receipts. Import historical evidence through the supported migration path, preserving source identities and accepted versions without running old close-out or payment actions again.
Set up Salon + Booking + CRM + Inventory your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.