Skip to main content

【FAQ】When switching from a channel manager to AirHost, when will existing reservations be imported?

J
Written by Joelly See Toh

When switching from a channel manager (e.g. TEMAIRAZU, NEPPAN, Siteminder etc.) to AirHost, the scope of existing reservation imports and synchronization timing may vary depending on each connected OTA.

Therefore, immediately after the switch, some reservations may not be reflected instantly and may be imported with a delay.

Initial import and resynchronization specifications for each OTA.

OTA

Initial import range

Resynchronization / Updates

Booking.com

All reservations with future checkout dates

Notifications sent within approx. 1 minute from OTA

Airbnb

Past 6 months to 2 years in the future

Continuous synchronization

Expedia

Next 30 days

Retrieved up to 1 year ahead at 1:00 JST the following day

Agoda

Past 89 days

Normal synchronization

Rakuten Travel

Past 24 months to the next 12 months

Every 10 minutes + 1:00 JST daily

Jalan

Past 24 months to the next 12 months

Retrieves notifications from the past 2 weeks

Rurubu Travel

Past 89 days

Normal synchronization

STAYSEE

Past 12 months to the next 6 months

Synchronizes from today up to 6 months ahead

AsiaYo

Past 7 months

Syncs data from 5 days before the last successful sync

Example: Expedia Import Behavior

On Expedia, when the initial connection is made, reservations with a check-in date within 30 days are imported immediately.

Reservations with a check-in date beyond 30 days will be imported during the automatic synchronization process early the following morning.

Example:

If Expedia is first connected on May 1, 2026:

  • Reservation with check-in on May 20, 2026 (within 30 days) → Imported immediately

  • Reservation with check-in on July 1, 2026 (more than 30 days) → Imported during the automatic sync early the next morning

Channels Where Reservations Are Received via Notifications (Push Notifications) from Channel Managers / OTAs

For some channels, AirHost does not periodically retrieve reservation data. Instead, reservation information is received via push notifications sent from the connected system.

Examples:

  • TEMAIRAZU

  • NEPPAN

  • RAKUTSU

  • Yahoo! Travel (Ikkyu)

  • Hostelworld

  • Trip.com

  • Traveloka

  • Tiket.com

Import of Pre-Connection Reservations (Existing Reservations)

Channel

Pre-Connection Reservations (Existing Reservations)

TEMAIRAZU

Depends on channel manager specifications

Neppan

Depends on channel manager specifications

Rakutsu

Depends on channel manager specifications

Yahoo! Travel (Ikyu)

Depends on channel manager specifications

Hostelworld

Depends on channel manager specifications

Trip.com

Pre-connection reservations will not be automatically imported.

Traveloka

Pre-connection reservations will not be automatically imported.

Tiket.com

Pre-connection reservations will not be automatically imported.

Notes

Because reservation retrieval methods and synchronization timing vary by channel, immediately after switching from a channel manager to AirHost, some reservations may take time to be reflected in the system. If a reservation does not appear, please contact support with the OTA name, reservation number, and connection date/time.

※ OTA integration specifications and reservation retrieval scope may change due to updates on either the OTA side or AirHost side. The information on this page is based on the status as of June 3, 2026, and may differ from the latest system behavior.


Did this answer your question?