Relation Tags & Rules

Relation TAG system allows you to make precise provider setup.

When you have an account with big number of provider, and you want him sell only number of providers to exact client, you can set it up with relation tags.

Usage and interface

Each Account relation now have the Relation Tags Tab(Account->Setup->Relations list->Edit relation->Relation Tags)

You can issue an action to add a relation tag:

Name field - name of a tag. It is plain text field, you can write any word or string here.

Action field - can be only Include or Exclude

Include: This action adding tag named “Name” to this relation chain.

Example: You can add tag “b2b” to b2b account relations, so it will get results only from providers working with b2b.

Exclude: This action excluding from the relation chain reactions with tag “Name”.

Example: You are setting relations for b2c Account, so you can exclude all the “b2b” related accounts, and this client will only get info from b2c providers.

Exclude all: You can exclude ALL the relations for this relation, adding “*” as Name field

After relation is sat, you can delete or edit it.

To make relation tag work, it should be sat up on relation between provider and re-seller and re-seller and buyer. Tag with same name should be on both relations.

Logic and use cases:

Include tag is searching for providers with this exact Name field

Here b2c client will get info from b2c Provider 1 and b2c Provider 2

We can get the same result with excluding tags we don’t want to get results from.

With this set of Relation Tags, b2c client will get results only from b2c Provider 1 and b2c Provider 2.

Please, note, if provider relations have a number of tags, and you exclude only one of them, you will exclude the whole relation.

In this example, b2c client will get results only from b2c Provider 1.

Please, note: Exclude has more priority than include.

Tag naming recommendations

The system is very simple, any name is just plain text, which is

case insensitive. So, “B2B” and “b2b” and “B2b” are the same relation tag.

But in order to make this system work properly, all the names at all stages must be identical.

We suggest using short, easy to read names and to have some tag name list with definitions for each tag name.

For example:

allprov - tagging all providers to include or exclude them at once
ProviderName - tagging every provider with its account name for further usage

Tag Rules

There is a feature to add conditions for relation tag usage. It's called Rules. You can add Rule when your tag is added and submitted:

You can add to the rule conditions from the list of Account Country, Account Market, Check In date, Destination ID, Customer Country, Hotel ID, destination country, account ID.

Rule Basics

Basically, it works this way:

If there is no Rule for Relation Tag - it works all the time and filters providers for this relation.

If there is a Rule for Relation Tag - it works only in conditions described by Rule, for example, Rule is that

Account Country = AU

Then this relation Tag will work only for accounts from Australia.

If the relation tag has a number of Rules - it Works only in case that all of the rules are completed.

So, if we have a relation tag with name “goglobal”, which refers to provider goglobal, two rules:

Account Country = AU

Destination ID = 5252

So, this relation tag will work only in cases when an account from Australia is searching for Rome(destination 5252). So, this kind of client will get results from goglobal.

Setting the rule

First of all, we setting property, choosing from the following:

Account Country: This is the country, set up for buying accounts. Note, this is not a customer country.
Account Market: This is the market, set up for buying accounts.
Check In: Check in date. You can choose constant check in dates, for example “15-02-2021”, or relative dates, for example +4 weeks. This is the hardest property to set up, if you need precise setup here, please, ask the dev team manager for help.
Destination ID: Destination IDs, used for search. Using this rule you can exclude one provider for a number of destinations, for example.
Customer country: Guest country. You can exclude or include some providers for guests from particular countries.
Hotel ID: Hotel ID, used for search. Using this rule you can exclude some providers from searching some hotels.
Destination country: The country that client is searching for.
Account ID: buyer account ID.

Second, we setting action and value, which will define the condition.

Less: The condition will work if property is less than value. For example, we are setting property Account ID, setting action Less and value “50000” - this tag will work only for accounts with ID less than 50 000 in our system.
More: The condition will work if property is more than value
Equal: The condition will work if property is equal to value. For example, we are setting property Customer country, action Equal and value - “ID” (this is country code for Indonesia). This tag will work only for customers from Indonesia.
Between: The condition will work if property is between two values. For example, we are setting property Check in, action Between and value “15-09-2020,15-12-2020” - the tag will work only for searches where check in date is between 15 September 2020 and 15 December 2020.
In: The condition will work if property is in the list of values. For example, we want to exclude a provider from some countries. We are setting property Customer country, action In and value - “ID,BE,AF,IL”. This tag will work only for customers from Indonesia, Belgia, Afghanistan and Israel.

Out: The condition will work if property is out of the list of values.

The last field in Rule setup is status field.

It is simple - if status is enabled, then the rule is applying, if disabled - the rule is not applying.

Report abuse