See what syncs in the Apaleo 2-way integration with Duve: rooms, reservations, and folio payments come into Duve, and pre-check-in and check-out data go back.
Integration Type
2 Way Integration
How to Connect to Apaleo
1-Way Sync (from PMS to Duve)
Room Information
- Customer’s Room/Rental Information (as long as it exists in the PMS)
- Room Name
- Unit Type
- Room Description
- Room Type
- Room Number
- Max number of guests
Reservation Information
- Reservation Dates
- Room Allocation (or Room Type allocation)
- Contact information (Name, Phone Number, email address)
- Country by phone is pulled from the country code of the phone number
- Only Adults will be synced
- Sub Reservations logic is supported
- Reservation Number
- Apaleo Reservation ID
- OTA IDs (Airbnb/Booking.com/etc.)
- Booking Source
- Booking Source 2nd label
- Reservation statuses (from the PMS)
- Confirmed
- Checked-in (In House)
- Checked-out (Post Stay)
- Canceled
- Group Name
- Block ID
- Notes from the PMS
- Cancellation and no-show policy (from the reservation's rate)
- City tax total (calculated from the city tax charges on the Apaleo folio)
Payments (Folio)
- Guest Payment for Stay (Live Folio Sync)
- Guest Currency Supported
- No Routing
- Room and Tax for the Guest will show on the Payments section (Paid and Unpaid)
- Outstanding folio balance: during online check-in, the guest can be asked to pay what is still owed on the Apaleo folio. Duve uses the folio balance (what remains after each recorded payment), not the reservation total.
- For OTA bookings paid by a virtual card, the remaining balance is usually city tax.
- If the balance is zero or below, the guest is not asked to pay anything.
- The payment is recorded on the folio as one amount. Duve does not post city tax to Apaleo as a separate line.
- For example:
Dynamic Parameters & Conditions
Apaleo-connected accounts can use the following in messages, emails, and automations:
-
{{cancellationPolicyByReservation}}: Shows the cancellation policy of the guest's rate, in the guest's language. For example: "Cancel until 36 hours before the arrival time. After that, a fee of €180.02 applies."
- If the reservation has no policy, nothing is shown (no empty line and no default text).
- If the policy can't be turned into Duve's standard sentence, Duve shows Apaleo's own policy description, in English.
- Policies with a percentage-based fee are not supported. Fixed-amount fees and non-refundable rates are supported.
- If the policy changes in Apaleo, the new policy is used after the next sync.
- Cancellation Policies settings tab: Now available for Apaleo accounts, under Settings.
- City tax parameter: Shows the city tax total for the stay, including all nights, even before they are posted.
- City tax trigger condition: Lets you send or skip automated messages based on the city tax amount, for example, to skip a message when the city tax is zero.
OTA Integrations
Connect Airbnb accounts directly to sync messages to Duve Communication Hub
2 Way Sync (from Duve to PMS)
Pre Check-in
- Summary uploaded as a comment
- Guest Email, Phone Number, ETA uploaded as a comment
- Uploaded to Guest Profile in the PMS
- Updated Guest Contact information
- Phone Number
- Summary Note with all pre-check-in information that was filled (Custom Question answers are included in this)
- Custom Question Field Match
- Passport ID Number
- Must be set as a Free Text question
- Type of Document
- Must be set as a multiple-choice question -
- Passport Issue Date
- Must be set as a date question
- Date of Issue
- Must be set as a date question
- Birth Date
- Must be set as a date question
- Nationality
- Must be set as a multiple-choice question - list of countries
- Address
- City
- Country
- Must be set as a multiple-choice question - list of countries
- Zipcode
- Gender
- Must be set as a multiple-choice question - with 'Female' & 'Male' as the choices
- Billing Company Name
- Passport ID Number
- Opt-in marketing as a comment
- Guest Billing (Payment for Stay)
- Additional Hold
-
Upsell purchases synced to Apaleo:
- Upsells connected to an Apaleo service are booked as that service on the reservation, on the delivery date. Apaleo posts them to the folio automatically.
- All other upsells are added to the guest folio as a charge, itemized with payment type.
- URL to Required Documents section
Pre Checkout
- Departure Time - uploaded as a comment
- Note with link to reservation in Duve (to see Satisfaction Ratings)
Upsells
The following upsells are synced back to Apaleo:
- Custom products
- Early Check-in
- Late Check-out
How they are synced:
- Custom products connected to an Apaleo service: Booked as that service on the reservation, on the date the guest receives it (or the check-in date, if the upsell has no date). Apaleo posts the service to the folio automatically. Before showing these upsells to the guest, Duve checks with Apaleo that the reservation can book the service, and hides the upsell if it can't. See Apaleo: Map Upsells to Apaleo Services.
- All other upsells: Added to the guest folio as a charge, itemized with payment type.
Related Articles
Comments
0 comments
Article is closed for comments.