Understand the words that change the workflow.

A reserved period connecting a customer or attendee to a service, provider, place, and any required resources.

Why it matters

Changing one part can invalidate the whole reservation.

Common mistake

Treating it as only a calendar event.

Booking software described around one-to-one or staff-led services, such as consultations, treatments, lessons, and visits.

Why it matters

The wording usually emphasizes matching a customer, service, provider, and time rather than reserving a standalone asset.

Common mistake

Assuming the label proves support for every staff, location, payment, or resource rule.

A slot that remains valid only when staff, service, location, resource, duration, buffer, travel, time-off, and existing-booking rules all agree.

Why it matters

It is the core double-booking control model.

Common mistake

Showing a location's open hours as bookable staff time.

An umbrella term for a system that lets a customer request or reserve an allowed service, time, place, person, class place, or resource while enforcing the business's booking rules.

Why it matters

It keeps the complete customer-to-staff workflow in view instead of reducing the job to a calendar link.

Common mistake

Assuming the label guarantees the particular staff, payment, capacity, change, or recovery behavior you need.

Blocked time before or after a service for preparation, cleanup, recovery, or travel.

Why it matters

The buffer consumes availability even though the customer may not see it as service time.

Common mistake

Adding a note without blocking the time.

The maximum number of bookings or attendees that a class, room, staff pool, or resource can accept at the same time.

Why it matters

Capacity can belong to more than one object in the same booking.

Common mistake

Using class seats to represent a scarce room or employee.

One scheduled occurrence with multiple attendee places, usually controlled by capacity and attendee-level states.

Why it matters

A class cancellation and an attendee cancellation have different consequences.

Common mistake

Calling several recurring private appointments a class.

The minimum notice required before a customer may create, change, or cancel a booking.

Why it matters

Creation, rescheduling, and cancellation may need separate limits.

Common mistake

Testing only new bookings and assuming edits follow the same rule.

A group of interchangeable rooms, chairs, vehicles, or equipment from which one available unit can satisfy a booking.

Why it matters

It avoids forcing the customer to select an irrelevant individual asset.

Common mistake

Counting the pool without reserving a specific unit at confirmation.

Multiple linked occurrences created from one repeating rule, with both occurrence-level and series-level changes.

Why it matters

One unavailable date should not silently corrupt every occurrence.

Common mistake

Assuming recurrence is the same as a class, package, or membership.

Software that allocates limited time, capacity, rooms, equipment, places, or other resources to a customer or attendee.

Why it matters

The word reservation often signals that capacity or an asset matters alongside the calendar time.

Common mistake

Treating booking, appointment, and reservation labels as proof of different capabilities without testing the workflow.

An assignment rule that distributes eligible bookings among multiple providers using a defined availability or fairness policy.

Why it matters

The assignment policy changes which slots are offered and who owns the booking.

Common mistake

Assuming all round-robin methods distribute work identically.

The rule connecting a service to the staff, location, duration, equipment, and delivery mode allowed to perform it.

Why it matters

A free employee is not necessarily qualified or correctly located.

Common mistake

Making every service available to every employee and location.

Time reserved between appointments so a mobile provider can move between locations or service addresses.

Why it matters

Travel changes real availability and may vary by route.

Common mistake

Allowing back-to-back appointments in different places.

A queue of customers interested in a currently unavailable class, slot, or provider, with rules for offers, expiry, and confirmation.

Why it matters

A waitlist place is not yet a confirmed booking.

Common mistake

Overbooking capacity when notifying several people at once.

A payment-provider hold or approval that reserves spending capacity without necessarily completing the final charge.

Why it matters

It is a different money state from a captured payment.

Common mistake

Reporting an authorization as settled revenue.

A provider-managed reusable payment credential or token associated with a customer, subject to consent and gateway rules.

Why it matters

The booking system should not handle raw card details itself.

Common mistake

Assuming a saved token can move freely between payment providers.

An amount collected before final service completion and linked to the remaining balance, cancellation policy, refund, and receipt trail.

Why it matters

A deposit must reconcile through every later money state.

Common mistake

Treating it as a separate sale with no link to checkout.

A count or value entitlement consumed when an eligible booking is confirmed and restored only under defined cancellation rules.

Why it matters

The customer and staff need an explainable credit ledger.

Common mistake

Using payment status as the credit balance.

Matching booking, deposit, balance, fee, tip, tax, refund, receipt, gateway, and accounting records to explain the final money state.

Why it matters

Disconnected totals hide duplicate or missing money movement.

Common mistake

Checking only that a charge succeeded.

A refund returns value through a payment route; a credit preserves value for future use under business rules.

Why it matters

They affect cash, customer entitlement, reporting, and expiry differently.

Common mistake

Using the terms interchangeably.

An external calendar event whose availability status should prevent conflicting booking slots when included in conflict rules.

Why it matters

Not every visible event is necessarily marked busy.

Common mistake

Assuming event presence alone blocks booking.

A record of events and time that may supply availability or receive confirmed appointments but does not by itself enforce a customer booking workflow.

Why it matters

Its role, direction, and source-of-truth rules determine whether an event blocks or merely records a booking.

Common mistake

Treating any calendar connection as a complete booking system or proven two-way synchronization.

The system designated as authoritative for a particular appointment or availability state when several calendars are connected.

Why it matters

Ownership determines which edit should win after conflict.

Common mistake

Allowing every connected calendar to behave as the master.

A URL or file using the iCalendar format to publish event data, often as a one-way subscription rather than live two-way control.

Why it matters

Refresh timing and direction affect conflict protection.

Common mistake

Calling every ICS feed two-way synchronization.

A connection where changes travel from one system to another but not necessarily back again.

Why it matters

The direction must match the intended source of truth.

Common mistake

Editing the destination and expecting the booking record to update.

A connection that can propagate defined changes in both directions, subject to ownership, mapping, latency, and conflict rules.

Why it matters

Two-way does not mean every field or action is supported.

Common mistake

Treating the label as proof of identical real-time behavior.

The explicit rule for which zone stores, displays, edits, and communicates a booking time for customer, provider, location, and calendar.

Why it matters

Daylight-saving and cross-zone edits can otherwise shift appointments.

Common mistake

Using the viewer's browser zone as the only rule.

A defined interface through which software can read or change permitted data and actions.

Why it matters

Coverage, authentication, limits, versions, and errors determine whether an integration is workable.

Common mistake

Assuming an API exposes every action available in the user interface.

A property that lets a repeated request produce the intended single effect rather than a duplicate booking, charge, or message.

Why it matters

Networks retry after timeouts even when the first attempt may have succeeded.

Common mistake

Retrying create or charge requests without a stable key.

A service rule limiting how many API actions may occur within a period or concurrency window.

Why it matters

Imports and automations need pacing, queues, and recovery.

Common mistake

Treating a throttled request as permanently failed.

A durable unique value used to connect the same customer, booking, payment, or resource across exports and systems.

Why it matters

Names, email addresses, and row numbers can change or collide.

Common mistake

Matching migrated records by display text alone.

An event message sent to another system when a defined change occurs, usually requiring authentication, retries, and duplicate handling.

Why it matters

Delivery can be delayed, repeated, or arrive out of order.

Common mistake

Assuming one delivery attempt proves reliable synchronization.

A dated record of who or what changed a state, from which path, and often what changed before and after.

Why it matters

It supports investigation, correction, permissions review, and accountability.

Common mistake

Using a generic activity feed as proof of complete audit coverage.

The practical ability to export usable records, relationships, identifiers, files, and history into another process or system.

Why it matters

A download is useful only when the important meaning survives.

Common mistake

Counting a customer CSV as a complete exit path.

Giving each customer, provider, receptionist, manager, integration, or administrator only the access required for their role.

Why it matters

Booking data can include sensitive operational and personal information.

Common mistake

Making every staff user an administrator for convenience.

A delegated authorization method that lets a service access defined parts of another account without receiving the user's password.

Why it matters

Scopes, token ownership, expiry, revocation, and refresh behavior affect the integration.

Common mistake

Treating authorization as permanent or unlimited access.

A defined period and process for keeping, archiving, anonymizing, or deleting a category of data.

Why it matters

Operational, contractual, and qualified legal requirements may differ by record type.

Common mistake

Keeping everything forever because storage is available.

The system or record designated as authoritative when copies disagree.

Why it matters

Every integration and migration needs a conflict owner.

Common mistake

Declaring two editable systems equally authoritative without reconciliation rules.