Booking HandbookSearch
Guides by topic

Integrations and data flow

Keep calendars, websites, payments, notifications, automation, and exports consistent when data crosses system boundaries.

Browse this topic in Guides
Synthetic booking B-204 moves from 2:00 to 2:30 while retaining its link to external event E-77; a timeout retry updates the same event and reconciliation confirms one booking and one event.
A retry should repair the linked event, not create another one.Preserve booking identity, external-event identity, direction, revision, attempt, and final comparison separately.

Open a detailed guide

Choose the task that matches what you need to decide or fix now.

Before you compare software

Start with these five checks

  1. Direction and source of truth
  2. Stable identifiers
  3. Latency and retry behavior
  4. Disconnect/reconnect recovery
  5. Complete export and ownership

Four connected areas

Use these four areas to see which part of the booking setup needs attention.

Calendar and video synchronization

Separate one-way display from two-way conflict blocking, then test edits, cancels, latency, reconnects, zones, and meeting links.

Which system owns availability after a disconnect?

Websites, WordPress and embedding

Compare hosted pages, widgets, iframes, blocks, shortcodes, APIs, themes, caches, accessibility, and error recovery.

Can customers still complete the task on the actual site?

Payments, commerce and POS

Map gateways, geography, POS, taxes, tips, discounts, refunds, webhooks, retries, and duplicate-payment protection.

Do online and staff-side money records reconcile?

Notifications, automation and data

Define templates, timing, deliverability, APIs, webhooks, retries, logs, import/export, identifiers, backups, and ownership.

Can the business recover the complete record when automation fails?