Aeion Hospitality + Booking.com
Booking.com drives 30-60% of bookings for most independent hotels. Aeion's Booking.com connection is a first-class channel — bidirectional inventory + rate sync via OTA-standard XML, reservation pull via webhooks, automatic failure isolation, safe retries, and per-connection rate pacing. No third-party channel manager required.
What Connects
`
Setup
Three prerequisites + three connect steps.
Sync Mechanics
- Inventory push: availability updates are sent to Booking.com's Connectivity endpoint as standard OTA XML messages, with each response verified for a valid acknowledgment. Errors are classified automatically — a rate limit backs off and retries, an authentication problem stops and alerts you, and a transient failure retries safely.
Common Issues + Resolution
`
FAQ
For Europe + global metros: Booking.com #1 by volume. For US business travel: Expedia. For APAC: Agoda. For vacation rentals: Airbnb + VRBO. Aeion ships all four (and 14 others); enable per-property.
Genius + Mobile + preferred-rate plans configured in Booking.com Extranet are respected automatically and priced accordingly. Aeion's pricing engine can also push different per-channel rates if your business model requires it.
Read-only sync: reviews are pulled in and surfaced in the admin UI + CRM. Replies are posted back to Booking.com via Extranet (manual; their API doesn't support automated review responses).
If you use Booking.com Payments (their hold-and-charge product), payment confirmation arrives with the reservation. If you process payments directly (most common), Booking sends the reservation and you charge via Stripe/Adyen.
Cancellation policies set in Aeion sync to Booking.com; refund decisions follow the policy automatically, and Aeion's payments engine handles the refund mechanics.
Aeion automatically isolates a broken connection so it can't propagate bad updates. If there's an extended outage, Booking.com Extranet manual updates remain available as a fallback; sync resumes automatically once Aeion recovers.
Yes. Each property is a separate Booking.com hotel ID with its own independent connection.
Yes once Booking.com XML API credentials are in hand (Booking.com's approval is the slow step, 3-5 business days). Setup in Aeion + initial sync + verification typically 60-90 minutes.
Booking.com gives notice via their Connectivity newsletter; Aeion tracks these announcements and updates the integration. Typical lag: within 14 days of announcement.