Thynk - Opera PMS Integration Guide

Thynk - Opera PMS Integration Guide

Thynk - Opera Integration Guide


Introduction & Benefits


The two-way integration between Thynk and Opera is facilitated by Hapi Cloud, the cloud data hub and integration platform. Hapi is based on an open model, to which multiple layers of encryption, authentication and governance are added. Hapi now serves 5,000 hotels globally


This guide outlines the various steps of the integration between Thynk.Cloud and Opera PMS.



Benefits of Installing a PMS Integration Include… 

  • Increased visibility for Sales/Events teams into most up to date guest room availability, which in turns helps the team sell efficiently and maximize revenue.

  • Reduction in manual tasks and double entry, giving your sales team time to sell and interact with guests and customers.

  • Provides the most accurate information to various departments so they can make informed decisions, and act quickly to guest and group needs.

  • More comprehensive reporting and dashboards as the data includes PMS information, as well as, CRM data.



Configuration 

Once the customer has signed contracts with the various interface components (Hapi, Oxi, Thynk), the Thynk technical team will start configuring the new Thynk.Cloud org with Hapi. 


Thynk will ask customers to provide them their Opera configuration in form of an Excel ‘Integration Preparation Workbook’ specifically, the following details from Opera PMS:


  • Opera Status Code Definition. To open the Status Definition screen in Opera, select Configuration>Reservations>Business Blocks>Status Codes:

    • Status (Code used to define a status (INT, TENT, DEF, CXL))

    • Description (Description for the status code (initial, tentative, definite, canceled).

    • Room Status Type (Room status type selected for status code.)

    • Deduct* and Non-Deduct statuses in Opera

    • Block Starting Status in Opera

    • Definition Reservation Type (Default reservation type to be used for this status code. The reservation type and status code must have the same deduct/no deduct status.)

    • Reason (OPERA requires a reason for every block reservation cancellation. Block Cancellation Reason, Block Refused Reasons, and Block Lost Reasons are set up in System Configuration>Reservations>Business Blocks. Default reason type to be used for this status code.

  • Block Cancellation Statuses

  • Block Cancellation Reason Code 

  • Number of PMS Database used for PMS Accounts

  • Opera Revenue Bucket Codes


*Deduct - Opera allows more than one deduct status in general. But only one deduct status applies to a Thynk Closed Won (or Definite status). 


Note:  Ideally, please supply Thynk a screenshot showing the Status Code Definitions in Opera. 


Thynk will also obtain the following information from Hapi: 

  • Repository access id + key

  • Chain code

  • Rate tax%

  • Hotel Code




There are four possible results of when a PMS Account is matched with a Thynk Account:



Condition

Result

Case 1

Sync Account is selected on PMS Account and PMS Account Field Match #1 is same as Account Field Match #1

PMS Account is related to the Account

Sync Account is selected on PMS Account and PMS Account Field Match #2 is same as Account Field Match #2 

Case 2

Sync Account is selected on PMS Account PMS Account Field Match #1 is same as Account Field Match #1 and Update Fields is selected on Account

Account fields are updated with PMS Account details

Sync Account is selected on PMS Account, PMS Account Field Match #2 is same as Account Field Match #2 and Update Fields is selected on Account

Case 3 

Sync Account is selected on PMS Account, PMS Account Field Match #1 is same as Account Field Match #1

PMS Account will need to be manually related by the user* to the Account via the Account lookup field on the PMS Account record.

Sync Account is selected on PMS Account, PMS Account Field Match #2 is different than Account Field Match #2

Case 4 

Sync Account is selected on PMS Account, PMS Account Field Match #1 is different than Account Field Match #2 and Create Account on PMS Account is selected

Account is created, fields are updated and PMS Account is related to Account

Sync Account is selected on PMS Account, PMS Account Field Match #2 is different than Account Field Match #2 and Create Account on PMS Account is selected


* This manual task will depend on the property; some hotels will have onsite admins.



Fields Available for Matching

Two matching fields can be set up and for each matching field, a default value is set from custom.  Matching fields will be determined during the project as part of the configuration.

 

PMS Account

Account

thn__BillingCity__c

BillingCity

thn__BillingCountryCode__c

BillingCountryCode

thn__BillingPostalCode__c

BillingPostalCode

thn__BillingStateCode__c

BillingStateCode

thn__BillingStreet__c

BillingStreet

thn__Fax__c

Fax

thn__IATANumber__c

thn__IATA__c

thn__Phone__c

Phone

thn__ShippingCity__c

ShippingCity

thn__ShippingCountryCode__c

ShippingCountryCode

thn__ShippingPostalCode__c

ShippingPostalCode

thn__ShippingStateCode__c

ShippingStateCode

thn__ShippingStreet__c

ShippingStreet

thn__SicCode__c

Sic

thn__SicDescription__c

SicDesc

thn__Website__c

Website



Field Mapping Guide (Thynk - Opera)


Thynk PMS Block ←→ Opera Business Block


Thynk users create a group booking (or MICE quote).  This group booking (quote) generates a PMS Block in Thynk, which is sent to Opera PMS to create a new Business Block in Opera. Any further updates to the room block, rates, etc. in Thynk will automatically update the already created business block in Opera. 


Similarly, any updates from Opera will be reflected in Thynk in PMS Block, thereby giving the sales team the most updated information. The Quote remains unchanged as this was the original booking (quote) created in Thynk.



Along with the room block and booking details, the account, agency, contacts affiliated to these bookings will also be updated in the PMS via the interface. 


To further explain the flow of these fields: 

Thynk Quote.stage/closed status => in Thynk PMS Block.status => Opera.Block.Status

Opera.block.status => Thynk block.status



PMS Block Field Mapping



Field Mapping

Thynk

Opera

Object

MYCE_Quote_c

PMS_Block_c 


Name

Name


Shoulder_Start_Date_c

StartShoulderDate_c


Shoulder_End_Date_c

EndShoulderDate_c


Arrival_Date_c

Start_c


Departure_Date_c

End_c


Release_Date_c

PMS_Release_Date_Time_c


Source_c

SegementationSource_c


Market_Segment_c

SegmentationMarket_c


Id

MYCE_Quote_c


Hotel_r.HotelCode_c

PropertyDetailsCode_c


Hapi_Connector_mdt.Chain_code_c

PropertyDetailsChainCode_c


CurrencyIsoCode

CurrencyCode_c

Object

Quote_Hotel_Room_c

PMS_Block_Inventory_c


Space_Area_c

RoomType_c


Space_Area_r.Code_c

RoomTypeCode_c


Arrival_Date_c

Start_c


Departure_Date_c

End_c


Type_of_Occupancy_c==’Single’

Occupancy_1_Blocked_c


Type_of_Occupancy_c==’Double’ or ‘Twin’ 

Occupancy_2_Blocked_c


Type_of_Occupancy_c==’Triple’

Occupancy_3_Blocked_c


Type_of_Occupancy_c==’Quadruple’

Occupancy_4_Blocked_c



TotalBlocked_c

Object

Quote_Hotel_Room_Price_c

BlockRate_c


Quote_Hotel_Room_r.Space_Area_c

RoomType_c


Quote_Hotel_Room_r.Space_Area.Code_c

RoomTypeCode_c


Quote_Hotel_Room_r.Rate_Plan_c

Rate_c


Quote_Hotel_Room_r.Rate_Plan_r.Code_c

RateCode_c


Date_c

Start_c


Date_c+1

End_c


Type_of_Occupancy_c==’Single’

Occupancy_1_price_c


Type_of_Occupancy_c==’Double’ or ‘Twin’

Occupancy_2_price_c


Type_of_Occupancy_c==’Triple’

Occupancy_3_price_c


Type_of_Occupancy_c==’Quadruple’’

Occupancy_4_price_c






The following fields from the Room Block and Group Booking (Quote) in Thynk’s PMS Block will be sent to Opera Business Block: 


Field Mapping

Thynk

Opera

Comments

Object

PMS Block

Business Block 



PMS Block Name

Name



PMS Account Company

Company



PMS Account Travel Agent

Travel Agent



PMS Account Group

Group



PMS Account Source

Account Source



Rate

Rate (1/2/3/4)



Block Type




Guarantee Code

Reservation Type



Code

Block Code



Reservation Pick Up Method

Res Method



Inventory Block Type

Inv. Control 

elastic, non elastic

Dates

PMS Release Date Time

Cutoff Date



Release Days Before Stays Date

Cutoff Days



Absolute Cutoff Date

Cut Off Date



Start Shoulder Date

Shoulder Begin Date



End Shoulder Date

Shoulder End Date



Start Date

Start Date



End Date

End Date



Created Date Time



Status

PMS Status

Status



thn__Block_Status__c

Status



thn__PMS_Block_Status__c


Not used


Status


Not used


Cancellation Reason Code

Cancellation Reason Code



Cancellation Reason Text

Cancel comments


Segmentation

Segmentation Channel

Segmentation Channel



Origin

Segmentation Origin 



Market Segment 

Segmentation Market



Source

Segmentation Source


Technical IDs

PMS ID

Confirmation Number



PMS Response 


Tech information: field is used for the interface. No action needed by users


PMS System ID


Tech information: field is used for the interface. No action needed by users


PMS System Type


Tech information: field is used for the interface. No action needed by users


Send to PMS (checkbox)


This is a checkbox to send the booking to PMS.


Outbound Request


This is deleted once the outbound request to PMS is successful. No action needed by users.


Created by


Tech information: field is used for the interface. No action needed by users


Last Modified by


Tech information: field is used for the interface. No action needed by users


HAPI Id


Tech information: field is used for the interface. No action needed by users


PMS Response Date/ Time 


Tech information: field is used for the interface. No action needed by users


Property


Tech information: field is used for the interface. No action needed by users


Property Details Brand Code


Tech information: field is used for the interface. No action needed by users


Property Details Chain Code

Property Details Chain Code

Tech information: field is used for the interface. No action needed by users


Property Details Code

Property Details Code

Tech information: field is used for the interface. No action needed by users


Property Details ID


Tech information: field is used for the interface. No action needed by users


Payment Method Code

Payment Method Code 

Tech information: field is used for the interface. No action needed by users


Currency

Currency







PMS Account from Thynk ←→ Opera Group Profile, Company Profile, Travel Agent Profile, or Source Profile





The following fields in the accounts record in Thynk will be mapped over to the Opera Company Profile. If in Thynk the account is denoted as a Travel Agent, this will interface with the Travel Agent Profile in Opera.  Note: the matching criteria in Opera will determine if the details coming from Thynk match an existing company profile, or if a new profile will be created.

A PMS Account is an account from the PMS database. An account can have multiple PMS Accounts.



Field Mapping

Thynk

Opera

Comments

Object Name

PMS Account Name

Account



Secondary Name




Tertiary Name




Email




Phone 

Phone Number Business



Website

Website



Type 

Type

Company, travel agent, etc.

Address

PMS Address Type

Address Type



Primary Street

Shipping Street 



Primary Street Line 2




Primary Street Line 3




Primary Street Line 4




Primary City

Shipping City



Primary Country

Shipping Country



Primary State

Shipping State



Primary Zip/Postal Code

Shipping Postal Code



Primary Country Code

Shipping Country Code



Primary State Code

Shipping State Code



Corporate ID

Corporate ID



Hapi ID


Tech information: field is used for the interface. No action needed by users.


PMS System ID


Tech info: field is used for the interface. No action needed by users


PMS ID

Company Profile ID



Outbound Request 


Tech info: field is used for the interface. No action needed by users


Territory 

Territory



Property Details Chain Code

Property Details Chain Code

Tech info: field is used for the interface. No action needed by users


Property Details Code

Property Details Code

Tech info: field is used for the interface. No action needed by users


IATA Number

IATA



Tax ID

Tax Id





Thynk Contacts  ←→  Opera Guest


A guest is a customer from the PMS database. A contact can have multiple guests.


Field Mapping

Thynk

Opera


Title

Title


First Name

First Name


Last Name

Last Name


Birthday

Date of Birth


Nationality

Nationality 


Language

Language


Email

Email


Phone

Phone




Thynk Guest ←→ Opera Guest Profile


  





Object

Thynk

Opera

Comments

Guest

First Name

First



Last Name

Last



Title

Title



Phone

Business Phone



Email

Email


Address

Mailing Street

Address 1



Mailing Street 2

Address 2



Mailing Street 3

Address 3



Postal Code

Postal Code



Mailing City

City



Mailing Country Code

Country Code


Additional Information

Gender


Not used


Notes

Comments



Birth Date

Date of Birth


Opera

Salutation

Title



Type

Profile type

Guest


PMS ID

Individual Profile ID



Property Details Chain Code

Property Details Chain Code

Tech info: field is used for the interface. No action needed by users


Property Details Code

Property Details Code

Tech info: field is used for the interface. No action needed by users


Send to PMS (checkbox only)


This is a checkbox to send the booking to PMS.


Outbound Request




Home Phone

Home Phone



Mobile Phone

Mobile Phone



Phone Opt Out

Phone YN

if Profile.PrivacyOption.mfAllowPhone then "Phone"


Email Opt Out

Email YN


if Profile.PrivacyOption.mfAllowEMail then "EMail" else





Thynk Reservation ← → Opera Reservation



Field Mapping

Thynk

Opera

Comment

Reservations

Reservation Name




Customer 

Guest



State

Status 



Guarantee Method

Res Type



Property

Property ID


General Information

Channel Code

Origin



Market Code

Market



Source Code

Source


Date & Occupancy

Arrival

Arrival



Adult Count

Adults



Child Count

Child



Departure

Departure



Nights




Number of Nights



Rooms

Room Count

Unit Count



Room Type Code

Room Type Code



Room Number



Pricing

Rate  (lookup)

Used for rate code

Used for rate code


Revenue

Room Revenue



Gross Value

Amount After Tax



Net Value

Amount Before Tax



Rate Code

Rate Code



Rate Amount

Rate



Total Rate Amount


Calculation based on rate amount * nights


Payment Method

Payment Method Code


Block

PMS Block



Agile Hospitality 

Quote Hotel Room




MYCE Quote



Opera

Send to PMS (checkbox)


This is a checkbox to send the booking to PMS


Opera Room Number

Room



Opera Block Code

Block Code



Opera Confirmation #

Reservation Number/ID



PMS Made Date

Created Date Time



Reason Update




Rate Code Opera




Reservation Created By

Created By






Thynk Availability ← Opera Inventory 




Field Mapping

Thynk

Opera


Date



Number of Availabilities



Number of Definite Sold



Number of Out of Order



Number of Physical



Number of Tentative Sold



Number of Unknown



Inventory 



Remaining Inventory



SF Ext ID



Availability Name



Room Type

Room Type





Thynk Rate  ← Opera Rate



Field Mapping

Thynk

Opera

Comments

Rate

Rate Name

Rate



Code

Rate Code



Category Code




Category Name




Is Active

Check 



Is Public




Get Prices 


Tech info related to process: field is used for the interface. No action needed by users 


Not in Myce


Not used for the interface. When set to true, it means that the rate cannot be added to a quote hotel room


Property




Tax Rate




Is Tax Inclusive

Tax Included



Is Non Refundable

Is Non Refundable



Is Complimentary

Is Complimentary



Is Confidential

Is Confidential



Is House use

Is House Use



Is Negotiated

Is Negotiated



Is Commissionable

Is Commissionable





Support

For Thynk support, please contact:  support@thynk.cloud 


For Knowledge Base Articles, please refer to the Thynk.Cloud website. 








    • Related Articles

    • Thynk - Mews PMS Integration Guide

      Thynk - Mews PMS Integration Guide Introduction & Benefits This guideline document explains the two-way integration between Mews PMS and Thynk.Cloud.  Benefits of Installing a PMS Integration Include…  Increased visibility for Sales/Events teams into ...
    • PMS Account <> Account Mapping

      This article will review the mapping of fields between PMS Accounts and Accounts in Thynk. There are a few scenarios when this mapping is used:  When an Account is created manually from a PMS Account by checking “Create Account”  When a PMS Account ...
    • Upload a Rooming List into Thynk

      How to Upload a Rooming List into Thynk Once a quote/booking is confirmed in Thynk, Thynk can generate reservations and send them to the PMS. When the client sends you a rooming list to the hotel, the Thynk user can generate a rooming list ...
    • Common Mews Errors - Troubleshooting Guide

      Common Mews Errors - Troubleshooting Guide The following are Mews/Thynk Integration common errors.  Please check if your error is listed here, and follow these simple instructions. If you require further assistance, contact Thynk Support.    Orders ...
    • PMS Account Overview

      Overview  Thynk centralizes POS and PMS data to offer a holistic view of every corporate account and direct contact, however, duplicate accounts and contacts, and ‘dirty data’ are often the unfortunate reality of any PMS or POS. Thynk offers a ...