Skip to main content

System Architecture

The synchronization process relies on three primary data pillars to feed the revenue management engine. For each pillar, the API requires developers to handle both an initial bulk payload Initialize to establish the baseline, and continuous delta updates Sync to maintain state parity.

System Architecture Diagram

Master Data​

This flow establishes and maintains the foundational configuration of the property within the RatePilot environment.

  • Initialize: A comprehensive initial push of the property setup. This payload must include core property details, room type definitions, physical room counts, rate plan structures, and any necessary mapping identifiers.
  • Sync: Ongoing updates triggered when a property modifies its structural configuration within the PMS, such as adding a new room type, disabling an old rate plan, or altering base capacities.

Reservation​

Accurate pricing forecasts rely on an exact, up-to-the-minute picture of current and future occupancy.

  • Initialize: A bulk data transfer of all existing future reservations, and relevant historical booking data, establishing the property's current occupancy ledger on the day of activation.
  • Sync:Event-driven updates pushed to RatePilot whenever a reservation lifecycle event occurs in the PMS (e.g., new booking creations, modifications to stay dates, or cancellations)

Inventory​

This flow dictates the day-to-day availability limits and current restriction controls.

  • Initialize: A bulk push of the current inventory matrix for the active booking window, including total rooms available to sell per date, base rates, and active restrictions (e.g., Closed to Arrival, Minimum Length of Stay).
  • Sync:Continuous updates to reflect real-time shifts in availability, such as rooms being placed out of order, or manual restriction overrides applied directly within the PMS calendar.