1. TARS-FOLS Interface

2. The TARS Interface Reservation Interface: TARS sends bookings to FOLS
Price Interface:
TARS sends prices to FOLS
Prepayment Interface (APOL):
TARS sends deposits to FOLS
Planning Interface:
FOLS sends availabilities to TARS

3. Reservation Interface
The TARS Interface
ASA
FOLS
PMS
OSA
CRM &
A|Club
TARS
RESA web
DATA web
ATACS web
Report hotel
Reservation Interface
Price Interface
Prepayment Interface
Planning Interface
RMS
Amadeus RMS
Easy RMS

4. The TARS Interface
In FOLS, 2 traffic lights to monitor TARS activity:
Left arrow: download interface, i.e. information coming from TARS – bookings, price updates, APOL deposits.
Right arrow: upload interface, i.e. information transmitted to TARS – availabilities updates.

5. Download Interface: Left Arrow
The TARS Interface
Download Interface: Left Arrow
Green: a booking, a deposit or a price update has been integrated automatically – The green arrow flashes.
Orange: a booking, a deposit or a price update has been rejected.
Red: rejected message have been in the interface for more than 10 minutes.

6. Upload Interface: Right Arrow
The TARS Interface
Upload Interface: Right Arrow
Green: a planning update has been transmitted to TARS, the green arrow flashes.
Red: the system has frozen.
Whenever the right light gets red
Contact Helpdesk Technique TARS – 24/7
+33 (0)

7. Reservation Interface

8. With RESA web, bookings are integrated automatically in FOLS
Booking Integration
With RESA web, bookings are integrated automatically in FOLS
Bookings are deducted instantly form the house inventory
Room products RESA web = Room products FOLS
The booking is integrated on the corresponding room product

9. Room products RESA web ≠ Room products FOLS
Booking Integration
Room products RESA web ≠ Room products FOLS
Without a straight mapping, one will need to change the room product in the Stays tab for some bookings.

10. Booking Search
Find TARS bookings by filling to their File no. or Reservation no. in the Conf Nb filed.

11. Booking Search
On the arrival list, identify RESA web bookings thanks to their File no. from the Res Nb column.

12. Others Tab
Others tab:
Reservation no. and TARS booking origin
TARS rate and reservation code
Contact name entered in TARS

13. Reservation Tab
The Guest info window in the Reservation tab is using information entered in TARS
A new profile is created for each new guest
Details of a profile can be found in Guest info

14. Profiles
Company profile

15. Profiles
Individual profile

16. Profile Matching Profile Matching: automatic matching of profiles
New reservations add information to the profile
Individual guests only
The matching is working according to criterias below:
Loyalty Card no.
Name
Phone no.
Adress 1 X 2 3 4 5
Le tableau indique l’ordre de vérification, de 1 à 5
If no matching happens, a new profile is created

17. Comments RESA web Comments gathered in a single window in FOLS:
« Observations » = GUEST in FOLS
« Remarks » = HOTEL in FOLS

18. Multi-rate
The Substitution TARS Key applies when a given rate is not available for the whole stay.
RESA web applies the most restrictive sale condition to the whole stay.

19. Guest sharing a room = In house guest field in FOLS
Shared Bookings
Guest sharing a room = In house guest field in FOLS

20. Planning Interface

21. FOLS sends OPEN and CLOSE messages to TARS 2 levels
Planning Interface
FOLS sends OPEN and CLOSE messages to TARS
2 levels
House level – OPEN/CLOSE (ROH in FOLS)
Room type levels (existing in TARS) – OPEN/CLOSE
Room products set as CRS Sales in FOLS
OPEN/CLOSE according to thresholds set in FOLS
Manages the availabilities of the property on the Distribution channels

22. Planning Interface The ROH Room type has no real physical capacity
It is mapped with the House level of TARS

23. Open/Close Thresholds
Stock control: set Open and Close Thresholds for House level and Room type levels.

24. Open/Close Thresholds
Parameters > 64-avail control
ROH Room product setting
Open Threshold 1 = House reopens as 1 room is available
Close Threshold 0 = House closes as no more rooms are available
Same kind of settings for the Room types
The Overbook value has an effect on the house inventory.
Thresholds are the same according to the amended inventory.

25. Planning Synchronization
Init. TARS synchronizes TARS with FOLS availabilities
Restricted access to the General Manager
Only if there is a discrepancy between systems
During synchronization, FOLS will slow down

26. CLOSE Room product level
Room product with no availability in FOLS = Room product CLOSE in DATA web.

27. CLOSE House level
No availability House level in FOLS = House CLOSE in DATA web
House level CLOSE in DATA web
Room products lose their OPEN/CLOSE status – grey status.

28. OPEN House level
A cancellation is causing the House level to reopen in FOLS = House level and Rank 1 Room product OPEN in DATA web
Below a cancellation occurs on a DISR Room product in FOLS = TWD Room product OPEN in DATA web

29. OPEN House level
This behaviour is generally causing the hotel staff to chose the largest Room product as the Rank 1 product.
The mapping tables of TARS and FOLS Room products display on Description>Amenities>Products

30. Price Interface

31. Price Interface
Real time, automatic synchronization in FOLS of all pricing update made in DATA web
One file per pricing update is send to FOLS
The Monitor and send prices to PMS screen displays and may generate any pricing update again

32. Price Interface
In DATA web any individual Rate level can be included in the Price Interface
In DATA web the Rate level codes are mapped with those of FOLS:

33. The pricing updates display in FOLS, Change History tab
Price Interface
The pricing updates display in FOLS, Change History tab

34. Pre-requisites in DATA web
Price Interface
Pre-requisites in DATA web
A price must be entered for any paying adult person set for the Room product (No loading for 0 pax).
Status should be Normal. Do not use Hidden, On request or Free statuses.
Unit should be per product. Do not enter prices per person ou per half double room.
Length of Stay should be 1 – Prices by period screen
Any setting different from items 1, 2 and 3 will damage the integration process.

35. Pre-requisites in FOLS
Price Interface
Pre-requisites in FOLS
Rate codes and Room products in FOLS are set by FOLS Admin
Do not use indexation to make price updates easier
TARS Line offers support for any adding of Rate levels to the Price Interface
To add a rate that is shared by DATA web and FOLS
Contact TARS Line 24/7
+ 33 (0)

36. Prepayment Interface

37. Prepayment Interface RESA web sends 2 interface files:
1 file about the booking
1 file about the deposit or garanty
These files still display in Change History in FOLS after integration
No Credit Card details are transmitted
Remember then to ask a CC guaranty to any guest upon check-in

38. Prepayment Interface Prepaid booking with APOL:
The Credit card does not display in FOLS
APOL PREPAYMENT Remark

39. Prepayment Interface Booking guaranteed by APOL:
The Credit Card does not display in FOLS
GARANTED via APOL PREPAYMENT remark

40. Prepayment Interface Booking for many rooms, guaranteed by APOL:
The Credit Card does not display in FOLS
APOL PREPAYMENT_Multiple rooms Remark

41. Prepayment Interface Cases where APOL bookings are cancelled:
Transaction failure
Cancellation of the transaction on Ogone website by the Hotel staff
A transaction is not validated by a guest on accorhotels.com for 30 minutes
The cancellation displays in the Change History tab only - APOL System cancellation

42. Prepayment Interface
Cases where an APOL booking is cancelled for many rooms:
One of the rooms is no longer bookable by the time of the confirmation.
The cancellation displays in the Change History tab only - partially not available.

43. Rejected Messages & Historic

44. Report the error to the FOLS Helpdesk for correction
Rejected Messages
Rejected Messages that do not block the integration process
The booking includes an error but it can be integrated
A TARS code that is not declared in FOLS (e.g. segmentation)
Credit Card details that do not go through the check in FOLS
Select Integrate to force the integration process
The wrong code is ignored or replaced by a default code
Report the error to the FOLS Helpdesk for correction

45. Rejected Messages that block the integration process
The booking cannot be integrated
A modification/cancellation for which the original reservation has not been integrated yet
A booking which has already been cancelled in FOLS
A TARS Room product not mapped with FOLS
A TARS Rate level not mapped with FOLS
The message cannot be forced to integrate
No default value
The Hotel staff can try and correct the error or contact the FOLS Helpdesk

46. TARS Messages: events that have occured in the interface
The TARS Messages screen displays by double-clicking on the traffic lights
TARS Messages: events that have occured in the interface
Receive: rejected messages
Open/Close: OPEN or CLOSE messages sent to DATA web
Change History: history data of the interface
Black arrow: select to display the reject reason

47. Integrate: force the integration of a rejected message
TARS Messages
Integrate: force the integration of a rejected message
See: display the interface file
Delete: delete a message in FOLS
General Manager or FOLS Helpdesk can delete a message
If a message is deleted by mistake, the message can be generated again in RESA web.

48. Historic Monitor the interface activity according to: A precise period
A type of message
A RESA web file no., etc.

49. Historic
See an interface file

50. Historic Select the black arrow to display more info: Message name
Message status: integrated, rejected, deleted
Code related to rejects, integrations or deletions

51. Historic Type of message: Reservation: Booking, Indiv Modif, Cancel
Price Interface: TARS Price
APOL : Prepayment
Planning : OCP (Open Close Product) & OCH (Open Close Hotel)

52. 24-hours a day 7-days a week
Contact
TARS Line
+33 (0)  
24-hours a day 7-days a week