Blog / Connections

Hotel data integration for pre-arrival experience bookings.

Bring the current stay, existing experience reservations and booking confirmation together so the next suggestion reflects the guest’s plans.

In this article

The useful part, first

  • A guest profile, a room charge and an experience reservation answer different questions.
  • Connect each booking to the correct visit and participants.
  • Reading plans and confirming a new booking are separate capabilities; bring confirmations back into the trip.

Hotel data integration connects the systems a property uses so records can support the same guest journey. For a resort trying to book more experiences before arrival, the essential connection is between an upcoming stay, the experiences already reserved, and the system that can confirm the next booking. A guest profile helps identify someone; the details of their current reservations help determine what to suggest.

You do not need every resort system in the first project. You need enough information to make one useful recommendation, a dependable way for the guest to book it, and a way to learn that their plans changed.

Start with the experience you want to make bookable

Consider an illustrative resort stay: two adults arrive on Thursday, one has reserved a pottery workshop on Friday afternoon, and both have a supper reservation that evening. The resort wants to help them consider another experience before arrival.

The lodging reservation tells the team when the travelers will be on property. The workshop reservation tells it something different: one person's afternoon already has a commitment. The supper booking constrains both travelers' evening. Combining those records could help the resort suggest a morning experience they can enjoy together, or an afternoon option for the other traveler if that person wants one.

The distinction is useful even when no offer is sent. Without participant information, blocking the entire party's afternoon loses a possible option; treating the entire party as available creates a conflict. An unrecorded period remains uncertain because guests can have plans elsewhere.

Arcora is being built to help resorts get more experiences booked before guests arrive. Existing lodging and activity bookings are the starting point for understanding what could fit. The connection has a commercial purpose: make the next suggestion more relevant and help the guest act on it.

Ask what the connection actually carries

“Our systems are integrated” can describe several different arrangements. A contact sync may copy names and preferences. A charge-posting connection may put an experience purchase on the room bill. A reservation feed may carry the experience's date, start time, participants and status.

Those records answer different questions. A charge labeled “pottery workshop” does not, by itself, establish who is attending or which session they booked. A prepaid package may include an experience that still needs a time selected. Before using either record to shape an itinerary, check whether it contains the actual appointment or links to one.

Use the map below to identify the records needed for one journey. It describes information to look for, not fields guaranteed to exist in every system.

On a small screen, scroll the table horizontally to read all three columns.

Booking-record map: what each connection contributes
Record to connectWhat it contributesWhat it cannot establish alone
Upcoming lodging reservationProperty, stay dates, active status, party and source reservation IDWhich experiences each traveler has booked
Existing experience reservationSession, local start/end times with the venue time zone, participants, booking reference and current statusWhether the guest wants another activity
Approved experience catalog and booking sourceWhat can be offered, duration, requirements, current terms and a confirmation pathWhether an option fits unrecorded guest plans
Guest/contact recordWho can receive the communication and relevant information the guest has sharedThat the recipient participates in every booking
Booking or cancellation updateWhich confirmed plan changed, when, and in which sourceThat every connected copy has already caught up

Keep the scope tied to the recommendation. A pottery workshop and supper journey needs timing and participant information; it does not need the guest's entire spending history. Our guest personalization guide explains how those details change the experience you suggest.

Link the booking to the right visit and people

For the example above, the integration should retain three relationships: the lodging reservation belongs to this visit, the workshop belongs to one traveler, and supper involves both. Keeping only a name and email can lose that structure.

Preserve the original reservation references and the link between systems where one exists. Where it does not, use an agreed matching process with staff review for ambiguous records. A shared email or matching surname can help find a possible match; it should not silently assign one person's appointment to everyone in the room.

A return guest also needs a new trip context. Their workshop last winter may be relevant history, but it is not a commitment during this stay. Keeping the person, visit and booking distinct prevents old purchases from becoming current plans.

Choose the connection method around the next decision

An export, an API and a change notification solve different parts of the problem. A scheduled export provides a snapshot. An API lets approved software request information or perform supported actions. A change notification alerts a connected service that something happened; the service may still need to retrieve the updated record.

For a small, staff-reviewed pre-arrival trial, scheduled exports can be enough to assemble upcoming stays and existing bookings, provided they include the required records and changes. Staff can check the current source before sending a time-specific suggestion. This is useful when you are still testing which journeys deserve automation.

More frequent API checks or supported event notifications become more useful when booking changes arrive faster than staff can review them, or when a recommendation depends on a specific session. The question is how old the information can be when it is used. An API connected once a night is still a nightly view.

Keep the last successful check visible. If a workshop moves to the morning, the earlier recommendation may no longer fit. If an update fails, pause the affected suggestion or have staff check the source. A missing record in an incomplete export is not reliable evidence of a cancellation.

Common formats can make exchange easier. OpenTravel develops message standards and reference architectures for travel systems. A shared format does not determine which records your connection includes, how quickly changes arrive, or what it is allowed to book.

Separate reading plans from confirming a new booking

Reading an experience reservation and creating one are separate capabilities. A connection that supplies itinerary context does not automatically have permission to take payment, reserve capacity or change a guest's plans.

You can keep the existing booking process. Link a suitable suggestion to the resort's supported checkout, where the guest selects participants and sees current availability and terms. Where checkout is unavailable, offer a staff-assisted request with a clear response expectation. That request remains pending until the responsible system or team confirms it.

The confirmation then needs a path back to the trip record. If the guest books the morning activity, the next interaction should reflect that commitment. The same applies if they cancel or move it. This feedback can be automated where supported or checked by staff in a small trial; what matters is that the next recommendation uses the updated plan.

Begin with one connected booking journey

Choose an experience and follow one sample stay from its source reservations to a possible suggestion, through checkout or staff confirmation, and back to the updated trip. Use test records or appropriately approved examples. A moved session and a booking for only one person will reveal more about the connection than a list of vendor logos.

If the records cannot be linked confidently, narrow the journey or leave that guest for staff assistance. If the link works but confirmations never come back, resolve that missing step before adding more recommendations. If both work, you have a concrete basis for expanding the connection. The pre-arrival upselling guide covers when to make the offer.

Arcora's Weave integration layer is in development to bring this context together; access and supported workflows are scoped with each resort. Start with a booking journey you want guests to complete before arrival, then identify the connections it needs.