...
Table of Contents |
---|
Overview
When customers send bookings in xls they can be imported to the system
Using the importing process to create bookings
Open the shuttle booking screen
Select the Booking Entity
Note - The cash debtor entity allows bookings to be imported across Booking Entitities
Must have a Booking Entity column mapped
If the Hotel column mapping does NOT find a hotel
Then it will look for a suburb / postcode combination in the Hotel column
setting the booking as a private address booking if found.
Drag and drop the XLS on the screen
Edit > Import “name” > Import from Mapped XLS file
If any required columns do not exist
NO bookings will be created
The user will be notified of the columns missing
All lines that are successful will create bookings
All lines that are not successful will not create bookings > a yellow note with a list of all bookings that failed will be provided
user will need to either
Fix these bookings in the sheet > remove successful bookings > reupload
or enter manually
Mapping the columns in the XLS sheet
Shuttle bookings may be provided in XLS so map the xls columns in the mapping screen.
Booking Entities must be Inbound Delegates (flagged on the Debtor)
Booking entities typically have collected money for the booking and must later pay for it.
Hotels will typically use their address for all bookings > so will not provide addresses
Tick use inbound delegate address
Booking Websites have agreements with different booking entities - this requires a partnership link if addresses are not set
Addresses may be inbound delegate partner address
Hotel column
Looks for an exact match on the hotel name (fuzzy not possible)
if none found - will look for a suburb / postcode combination > if found will set the booking as to or from a private address
Cash debtor is a special mapping that allows imports across multiple booking entities.
Booking entity is a required column
Partnerships
When a booking entity takes bookings on behalf of another entity - they are a partner. Example a travel agency that handles all the bookings for a hotel.
The Travel Agency is the inbound delegate that will pay for the booking - however the address comes from the linked Partner Address
...
Logical Flow
This is how the system uses the data provided
Travel Date provided (is mandatory)
Date is today or in the future
Flight time
Flight number provided
Yes
Infer other fields > by looking at shuttle booking history (most common in last 180 days)
Destination
Direction of Travel
Flight Time (only if flight time was NOT provided)
No
Destination must be provided
compare with lookup table for this customer
Terminal must be provided
Flight time must be provided
Direction of Travel must be provided
PAX
if not provided then use default value (1)
Children will be added to Adults if separate columns
Excess Bags
Only if provided
Passenger name options
Single field
combine Fname / Lname fields
Passenger phone
passenger email
Address
May be provided line by line
May be provided in a single field > decompose
Hotel name may be provided
Look up in customer name fields (all customers) > use address found
May not be provided = use customer address on the booking
External Reference
May not be provided
Inbound Delegate company from Booking Entity
Pickup time may be provided