The Despegar import feature in RideSuite allows users to quickly upload and process bookings directly from the Despegar portal.
How to Import Bookings
-
Export from Despegar
Log in to the Despegar portal and export the booking file. Make sure to download the raw, untouched version of the file.
-
Upload to RideSuite
Navigate to RideInbox > Upload in RideSuite and upload the file.
-
View New Orders
After a few minutes, the bookings will appear in RideInbox > New Orders. Please allow a couple of minutes for all records to be created.
For details on how imported booking data is validated and displayed in RideSuite, see this article.
Handling Changes
The current policy in Despegar restricts direct changes; the end customer must cancel and rebook or coordinate with you to manage changes manually. Because manual updates to routes or vehicles can create pricing conflicts and sync issues with Despegar, please confirm their preferred change process before taking action.
Handling Cancellations
RideSuite supports handling cancellations directly from Despegar imports. Orders with cancellations appear in RideInbox > Cancelled Orders.
For more details on how to handle external cancellations, see this article.
Vehicle Mapping
To ensure bookings are processed correctly, Despegar service categories and vehicle types are mapped to specific RideSuite Vehicle Categories.
Important Note on Shared Services
RideSuite does not currently support shared transportation. Any products designated as Shared within the Despegar platform will be mapped and fulfilled as Private transfers within the RideSuite platform. Furthermore, RideSuite's maximum capacity for these vehicles is determined by the total number of passengers.
| Despegar Product Name | RideSuite Vehicle Category |
| Private Car Express | Economy Car |
| Private Car Standard | Economy Car |
| Private Car Premium | Premium Car |
| Private Car Deluxe | Luxury Car |
| Private Minivan Express | Economy Minivan |
| Private Minivan Standard | Economy Minivan |
| Private Minivan Premium | Premium Minivan |
| Private Minivan Deluxe | Luxury Minivan |
| Private SUV Express | Economy SUV |
| Private SUV Standard | Economy SUV |
| Private SUV Premium | Premium SUV |
| Private SUV Deluxe | Luxury SUV |
| Private Limousine Express | Economy Limousine |
| Private Limousine Standard | Economy Limousine |
| Private Limousine Premium | Premium Limousine |
| Private Limousine Deluxe | Luxury Limousine |
| Private Minibus Express | Economy Minibus |
| Private Minibus Standard | Economy Minibus |
| Private Minibus Premium | Premium Minibus |
| Private Minibus Deluxe | Luxury Minibus |
| Private Bus Express | Economy Coach |
| Private Bus Standard | Economy Coach |
| Private Bus Premium | Premium Coach |
| Private Bus Deluxe | Luxury Coach |
| Shared Car Express | Economy Car |
| Shared Car Standard | Economy Car |
| Shared Car Premium | Premium Car |
| Shared Car Deluxe | Luxury Car |
| Shared Minivan Express | Economy Minivan |
| Shared Minivan Standard | Economy Minivan |
| Shared Minivan Premium | Premium Minivan |
| Shared Minivan Deluxe | Luxury Minivan |
| Shared SUV Express | Economy SUV |
| Shared SUV Standard | Economy SUV |
| Shared SUV Premium | Premium SUV |
| Shared SUV Deluxe | Luxury SUV |
| Shared Limousine Express | Economy Limousine |
| Shared Limousine Standard | Economy Limousine |
| Shared Limousine Premium | Premium Limousine |
| Shared Limousine Deluxe | Luxury Limousine |
| Shared Minibus Express | Economy Minibus |
| Shared Minibus Standard | Economy Minibus |
| Shared Minibus Premium | Premium Minibus |
| Shared Minibus Deluxe | Luxury Minibus |
| Shared Bus Express | Economy Coach |
| Shared Bus Standard | Economy Coach |
| Shared Bus Premium | Premium Coach |
| Shared Bus Deluxe | Luxury Coach
|
Mapping Assumptions
To maintain consistent integration behaviour between Despegar and RideSuite, we apply several specific mapping rules. Understanding these assumptions will help you manage your bookings and identify when manual intervention is required.
Agency Reference: The Fenix ID is mapped as the primary agency booking reference.
Unique Ride IDs: For return bookings (which share the same Fenix ID), we use the Modality column:
IN = Reference + _1
OUT = Reference + _2
Internal IDs: Reservation ID and Product ID are captured and stored but hidden from the order form.
Pickup Date & Time Logic: The source of the pickup time depends entirely on the direction of the transfer:
From the Airport: We map the Flight Arrival Date & Time as the pickup time in the order form.
To the Airport: We map the pickup time from the Transfer Date and Transfer Pickup Time fields.
Ignored Data Fields: To keep the order form clean and focused, the following columns are not imported:
Financials: Price, Opaque rate, Penalty over net rate, IVA/ISR retention, IVA rate, Legal Entity, Fiscal situation.
Logistics Details: Country of purchase, Reservation type, Activity Start Date/City, Origin/Destination city or area.
Redundant Location Data: Origin hotel/address/POI, Latitude and Longitude.Personal/Billing Info: Billing name, Address, Identification type/number, Check date.
Reporting Changes
Please notify us immediately if you become aware of any updates to the formatting or data structure provided by the agency. Changes to the source data can break the import process and disrupt the workflow.