What types of forms can be converted into
elloha account?
The SIT records imported into elloha TDR and the products that you can create from the application
are divided into 21 different types.
Only the following types of products can be converted into elloha accounts:
Type Products and SIT sheets | Elloha account type | Services |
Hotel | Accommodation | Offers |
Rental | Accommodation | Offers |
Campsite | Accommodation | Offers |
Sports Leisure | Activities | Resources & Packages |
Cultural Leisure | Activity | Resources & Packages |
Tasting | Activity | Resources & Packages |
Monument and Cultural Heritage | Activity | Resources & Packages |
Internship | Activity | Resources & Packages |
Parties & events | Activity | Resources & Packages |
Transport | Activity | Resources & Packages |
Restaurant | Restaurant | Appointments & Coupons |
Retail & Services | Business & Services | Appointments & Coupons |
Ski resort | Reserved for the JB Concept connector | |
Cruises | Reserved for LS Resa connector |
Important: the choice of type is important for the elloha account to be passed on to the Network Head resa engine. For modelling reasons, it is not possible to change the type once the account has been created. You have to delete the account and recreate it with the correct type. More information about account types in your TDR booking engines:
Who can convert a SIT file or an internal product into an elloha account?
The elloha Network Head SuperAdmin (login: admin_***) or a member with the Administrator profile,
In the case of a CDT/OT network, for example, each Administrator of a Partner TDR (OT) who is the "owner" of the SIT record or product
- if it has created the product itself (with its own Partner TDR access),
- if this file or product has been transferred to it by the TDR (CDT),A TDR can transform an elloha account "belonging" to one of its Partner Network Heads
What are the conditions for converting a listing?
A SIT or Product file can only be converted into an elloha account under the following conditions:
The operation is carried out by a SuperAdmin user (login admin_****) or with the Administrator profile,
The file or Product must belong to one of the types detailed above,
The file must not be deactivated
The file or Product must have the "Owner" contact type filled in, with at least one e-mail in its means of communication: for sending its identifiers and passwords
It is essential to fill in the Owner tab completely, as this information will be used to complete the Account/Contact details section in elloha, and certain fields are compulsory for the account to work properly: surname, first name, address line, postcode, town and... email address.
Important: if you do not fill in all the compulsory fields correctly , the elloha account will not work properly after the conversion because most service providers do not think to fill them in once the elloha account has been opened:
It is necessary towait until D+1 if you modify the Owner contact (adding an email address) for the "Transform into elloha" button to appear so that the application's indexing updates the catalogue data for the transformation.
How is the transformation carried out?
If the conditions detailed above are met, the SuperAdmin will see the"Convert to elloha" button appear on the product listing page of the elloha TDR application,
By clicking on this link, the SuperAdmin activates the conversion of the file into an elloha account,
An email is sent to the service provider (the owner contact entered in the file) with his login/password for connecting to the application on the website
http://portailpartenaire.elloha.com
Note: the login for the transformed elloha account will be generated on the basis of the email address in the Owner tab of the transformed listing
[email protected] for example
if this is already taken for another elloha account, the login generated will be
j.doe
if already taken for another elloha account
j.doe1
j.doe2
....
so that the login remains unique for an elloha account.
Two elloha accounts cannot have the same email address of the pro as their login.
If the pro has a second email address, you can enter it in the Owner tab and this address will be used as the login for his 2nd elloha account.
This principle allows you to convert as many files as necessary with the same email address to Owner. The pro will receive a different login for each change.
If you need to change a login: [email protected]
When you click on the "Convert to elloha" button:
The TDR elloha Admin receives an email notification
The account is taken over by the subscriber, who can change their password the first time they log in,
It is now transformed into an elloha account. The elloha pictogram is displayed next to the title of the form:
The elloha subscriber can then add information relating to their offers,
add or modify their calendar, manage their schedule, edit their booking widget and receive same-day bookings.As long as the service provider has not logged in with the login details sent by email when the listing was converted to elloha, the account will remain closed to sales. The elloha pictogram to the left of the title will be greyed out and the account will not yet be available for sale. You can open it for sale from your TDR by clicking on the red icon on the credit card and wait for a nightly reindexing until the button turns green the next day.
The elloha account is attached to the elloha TDR catalogue (and can be sold via your booking enginesand Offline Sales). If it was the property of a partner TDR at the time of conversion, it can be marketed directly via the booking and offline sales engines of the partner TDR. In other words: the distribution channel of the TDR and the partner TDR are opened up by the elloha conversion process. The availability of the elloha account on these channels is effective on D+1, when the TDR distribution catalogues have been updated. Similarly, the visibility of the elloha pictogram in the TDR application requires indexing, so the elloha status of the transformed record does not appear until D+1.
The SIT connector is regularly programmed to import products in order to synchronise your new records and update those that have already been imported once.
When you transform a SIT file into an elloha account, it is "detached" from the SIT connector so that the information updated by the service provider in the elloha account is not overwritten by the next import.
To avoid confusing the cold file and the elloha account, you can check whether or not the elloha pictogram appears on the file or use the "elloha accounts" filter:
