Functioning diagram of an elloha network head with a DMO SIT
Elloha/SIT operating diagram for a DMO network (CDT,OT)
Combined with a marketplace such as elloha, the SIT feeds DMO websites offering online bookings
On the website, at the level of a listing, the SIT feeds cold information and provides the link with hot information (offers, rates, availability) from the elloha account.
The SIT makes it possible to link the cold file and the elloha account by recording the idOI, the unique identifier of the elloha account.
The web service provider using the SIT data can then add the online booking to the website.
By querying the TIS, it will retrieve the cold information and the idOI, which will enable it to dynamically build a booking widget (a booking button/link, a calendar of availability, etc.) for online sales.
Here's how to retrieve the idOI of an account in elloha:
In the vast majority of cases (around 95%), the SIT record corresponds directly to the elloha account for a hotel, campsite, furnished accommodation, bed and breakfast, sports or cultural leisure activity, event, etc
In SIT Tourinsoft, Raccourci, Constellation, Ayaline, LEI, SITLOR..
dMOs enter the idOI of the elloha account (or that of another marketplace) in the SIT file using a field dedicated to the booking ID, which can easily be used by web agencies who are familiar with how this works.
Detailed operation in this article from the elloha knowledge base:
In the 95% of cases where the SIT record corresponds to an elloha account,
the APIDAE SIT offers automatic uploading of idOI in the metadata of SIT records without manual input.
This is provided that the elloha accounts come from APIDAE records that have already been imported into the elloha network head.
If this is not the case, the DMO can manually edit the metadata in APIDAE to fill in the idOI.
APIDAE article dedicated to manual editing of metadata: https: //aide.apidae-tourisme.com/hc/fr/articles/360020375760-%C3%89diteur-de-m%C3%A9tadonn%C3%A9es-Apidae
How this works is explained in this knowledge base article:https://elloha.zendesk.com/hc/fr/articles/360015584537-APIDAE-renvoi-de-l-idOI-du-compte-elloha-dans-les-m%C3%A9tadonn%C3%A9es-APIDAE
In 5% of cases, for web editorial reasons or because of SIT data entry rules, the record does not correspond to an elloha account but to one of the offers in the elloha account: each flat in a tourist residence is a web record, each of Mrs So-and-so's rooms is a record, each of the guided tours offered by a tourist office is a record, etc
All the offers are managed in a single elloha account for the sake of efficiency and simplicity for the pro or the need for OTA connectivity, but on the website the DMO wants to display one web sheet per offer.
In the SIT Tourinsoft, Raccourci, Constellation, Ayaline, LEI, SITLOR..
the DMOs enter the idOI of the elloha account and the id of the offer (productid) in the SIT file in the same field dedicated to the booking ID.
In 5% of cases, when the SIT record does not correspond to an elloha account but to one of the offers in the elloha account, on the Metadata side of the APIDAE SIT, elloha cannot automatically recognise the SIT records to link them to the offers that a pro has entered in his elloha account.
If the DMO wants to ensure the correspondence between an APIDAE cold record and one of the offers contained in the elloha account, the solution is to enter the idOI of the elloha account and the id of the offer (productid) in APIDAE by manually editing the metadata (depending on the licence level).
APIDAE article dedicated to manual editing of metadata: https: //aide.apidae-tourisme.com/hc/fr/articles/360020375760-%C3%89diteur-de-m%C3%A9tadonn%C3%A9es-Apidae
How it works is explained in this article from the elloha knowledge base: https://elloha.zendesk.com/hc/fr/articles/360015555657-APIDAE-cas-d-un-compte-elloha-correspondant-%C3%A0-plusieurs-fiches-SIT-APIDAE
