← All ten chapters

Chapter 09 of 10 · The systems around the platform

Integrations and shared technology

A marketplace is only as good as the systems it talks to. The principle is to integrate where the member already is, keep the platform as the source of truth for what it sells, and make sync health visible so failures are found before a guest is double booked.

Inventory and channels

Property management systems, channel managers and external booking channels each need a defined relationship with the availability ledger.

  • Two-way inventory and rate sync
  • Channel manager connections for members who sell elsewhere
  • Import of existing calendar blocks
  • Conflict detection and an exception queue

Money, messaging and marketing

Payments, email and SMS delivery, CRM and marketing automation, and advertising and analytics platforms, connected through a small number of well-documented interfaces.

  • Payment provider and payout accounts
  • Transactional email and SMS delivery
  • CRM and marketing automation
  • Advertising, analytics and consent management
  • Accounting software and financial exports

Identity, service and place

Single sign-on for staff and members, identity for guests, a service desk, review platforms, maps and route information.

  • Role-based access and single sign-on for staff
  • Customer service and review platforms
  • Maps, geolocation and travel information
  • Consent management and website analytics

How integrations are run

Every connection is treated as a product with an owner, a health signal and a fallback, because integrations fail quietly by default.

  • An integration health dashboard
  • Alerting on failed syncs and expiring credentials
  • Documented fallbacks for each critical connection
  • A register of what data moves where

The design decision

Integrate to the systems members already trust, and never require a farm to run two calendars. If a sync cannot be trusted, the platform should refuse the booking rather than guess.