modèle

  1. We use the GET availablebreaks method to collect the pricing.

  2. In each collection, we look for the price passed in the "totalprice" element.

  3. The price is divided by the number passed in the "days" element of this collection.

  4. The calculated price is the price per day for any number of guests in a given stay.

LOS2: 507 / 2 = 253.50

LOS3: 548 / 3 = 182.67

LOS4: 637 / 4 = 159.25

 

 GET https://***.api.tabs-software.co.uk/legacy/property/2161_NO/availablebreaks { "fromdate": "2024-01-05", "todate": "2024-01-07", "days": 2, "currency": "GBP", "price": 456, "compulsoryextras": 51, "changesbrochurepriceextrasprice": 0, "additionalextrasprice": 51, "specialoffersaving": 0, "totalprice": 507 }, { "fromdate": "2024-01-04", "todate": "2024-01-07", "days": 3, "currency": "GBP", "price": 497, "compulsoryextras": 51, "changesbrochurepriceextrasprice": 0, "additionalextrasprice": 51, "specialoffersaving": 0, "totalprice": 548 }, { "fromdate": "2024-01-03", "todate": "2024-01-07", "days": 4, "currency": "GBP", "price": 586, "compulsoryextras": 51, "changesbrochurepriceextrasprice": 0, "additionalextrasprice": 51, "specialoffersaving": 0, "totalprice": 637 }, { "fromdate": "2024-01-02", "todate": "2024-01-07", "days": 5, "currency": "GBP", "price": 635, "compulsoryextras": 51, "changesbrochurepriceextrasprice": 0, "additionalextrasprice": 51, "specialoffersaving": 0, "totalprice": 686 }, ...

where:

  • "days" indicates the stay length

  • "totalprice" indicates the rent and booking fees amount from

modèle

Dans cette intégration, elle n' est pas synchronisée par défaut avec . Si vous êtes prêt à travailler avec le site , pour vérifier si cela est possible pour votre installation.

Support Team: is currently synchronised only for one user: mfilewood@corncott.com and below you can find the detailed explanation how FSP pricing calculation works. If there is any other user willing to work with , open a bitbucket with the Dev Team and check the possible options.

For stays up to 7 days, we take the price from the "TotalPrice" field of the matching stay length "days": 1 to "days": 7 .

 

GET availablebreaks

 { "fromdate": "2024-12-01", "todate": "2024-12-04", "days": 3, "price": 549, "compulsoryextras": 0, "currency": "GBP", "totalprice": 549 }, { "fromdate": "2024-12-01", "todate": "2024-12-05", "days": 4, "price": 583, "compulsoryextras": 0, "currency": "GBP", "totalprice": 583 }, { "fromdate": "2024-12-01", "todate": "2024-12-06", "days": 5, "price": 617, "compulsoryextras": 0, "currency": "GBP", "totalprice": 617 }, { "fromdate": "2024-12-01", "todate": "2024-12-07", "days": 6, "price": 686, "compulsoryextras": 0, "currency": "GBP", "totalprice": 686 }, { "fromdate": "2024-12-01", "todate": "2024-12-08", "days": 7, "price": 686, "compulsoryextras": 0, "currency": "GBP", "totalprice": 686

For stays above 7 days, we take the sum of the "TotalPrice" for every full week ("days": 7). Then, add the remainder for the rest of the days (more or equal to 8 and less or equal than 13).

 

GET availablebreaks

 { "fromdate": "2024-12-01", "todate": "2024-12-08", "days": 7, "price": 686, "compulsoryextras": 0, "currency": "GBP", "totalprice": 686 }, { "fromdate": "2024-12-01", "todate": "2024-12-09", "days": 8, "price": 549, "compulsoryextras": 0, "currency": "GBP", "totalprice": 549 }, { "fromdate": "2024-12-01", "todate": "2024-12-10", "days": 9, "price": 549, "compulsoryextras": 0, "currency": "GBP", "totalprice": 549 }, { "fromdate": "2024-12-01", "todate": "2024-12-11", "days": 10, "price": 549, "compulsoryextras": 0, "currency": "GBP", "totalprice": 549 }, { "fromdate": "2024-12-01", "todate": "2024-12-12", "days": 11, "price": 583, "compulsoryextras": 0, "currency": "GBP", "totalprice": 583 }, { "fromdate": "2024-12-01", "todate": "2024-12-13", "days": 12, "price": 617, "compulsoryextras": 0, "currency": "GBP", "totalprice": 617 }, { "fromdate": "2024-12-01", "todate": "2024-12-14", "days": 13, "price": 738, "compulsoryextras": 0, "currency": "GBP", "totalprice": 738 },

Example: Calculate the price for the 24-day stay starting at “2024-12-01”.

7-day period starting from “2024-12-01” = 686 GBP

7-day period starting from “2024-12-08” = 775 GBP

7-day period starting from “2024-12-15” = 997 GBP

10-day period starting from “2024-12-15” = 798 GBP

Total: 3256 GBP

GET availablebreaks

 [ { "fromdate": "2024-12-01", "todate": "2024-12-08", "days": 7, "price": 686, "compulsoryextras": 0, "currency": "GBP", "totalprice": 686 }, { "fromdate": "2024-12-08", "todate": "2024-12-15", "days": 7, "price": 775, "compulsoryextras": 0, "currency": "GBP", "totalprice": 775 }, { "fromdate": "2024-12-15", "todate": "2024-12-22", "days": 7, "price": 997, "compulsoryextras": 0, "currency": "GBP", "totalprice": 997 }, { "fromdate": "2024-12-15", "todate": "2024-12-25", "days": 10, "price": 798, "compulsoryextras": 0, "currency": "GBP", "totalprice": 798 } ]
The maximum stay period is 35 days. If there is a missing period required for the above calculation, the FSP price for the whole stay will not be created

modèle

Le calcul du modèle de prix journalier est basé sur les valeurs extraites de différents champs de données. Il permet de définir des paramètres de tarification détaillés s'ils sont définis avec soin. Par ailleurs, le modèle est basé sur les saisons.

est extrait de à l'aide de la méthode GET daterangeprice.

  1. The GET daterangeprice method collects the pricing data. This method returns prices for 7 days. See the code snippet below.

  2. takes the "price" amount and adds a fixed booking fee. In the case of 2022/2/23 - "price": 648 and the booking fee amount is 40.

    : 648 + 40 = 688

    Note: The booking fee is a fixed charge, but it differs across the clients. The exact amount may be checked by the Development Team.

  3. The calculated amount is divided by 7 to receive price per night and rounded to two decimal points.

    : 688 / 7 = 98.29

  4. Some clients may use mark-up. If this is true, then the calculated value is multiplied by the mark-up value and rounded to two decimal points. In this case, the mark-up is 7%.

    : 98.29 x 1.07 = 105.17

  5. The calculated price (105.17) is saved in as only if there is no greater LOS price available. Otherwise, the highest available LOS price is set as .

    Note: In this example, LOS2 (248.50) is higher than the calculated price (105.17), hence is set to 248.50.

 

 

 GET https://***.api.tabs-software.co.uk/legacy/property/2161_NO/daterangeprice/2022 { "fromDate": "2022-02-12", "toDate": "2022-02-19", "dateRangeName": "Band F", "priceBand": "F", "price": 757 }, { "fromDate": "2022-02-19", "toDate": "2022-02-26", "dateRangeName": "Band G", "priceBand": "G", "price": 648 }, { "fromDate": "2022-02-26", "toDate": "2022-03-05", "dateRangeName": "Band H", "priceBand": "H", "price": 648 }, ...

"accommodates":5

(N/A)

est récupérée à l'aide de la méthode GET availabilitybreaks. Ensuite, il est fixé en fonction du séjour le plus court possible dans cette propriété. Elle peut être lue à partir du point de données "days". Dans ce cas, le séjour le plus court possible est de deux nuits, c'est pourquoi le séjour minimum est fixé à 2.

 

 

 GET https://***.api.tabs-software.co.uk/legacy/property/2161_NO/availablebreaks { "fromdate": "2022-02-23", "todate": "2022-02-25", "days": 2, "price": 411, "compulsoryextras": 86 }, { "fromdate": "2022-02-23", "todate": "2022-02-26", "days": 3, "price": 411, "compulsoryextras": 86 }, { "fromdate": "2022-02-23", "todate": "2022-02-27", "days": 4, "price": 466, "compulsoryextras": 92 }, ...

(N/A)

(N/A)

Thèmes complémentaires

Remises (N/A)

Calendrier

vérifie le paramètre "allowBookingOnWeb" lors de la synchronisation des disponibilités. Si une année comporte "allowBookingOnWeb": false, la disponibilité pour l'année entière est fermée. This information is available in the GET property request in the GetProperties folder.

"pricing": { "bookingBrand": "LB", "ranges": { "2022": { "high": 2275, "compulsoryextraspricehigh": 35, "low": 785, "compulsoryextraspricelow": 35, "allowBookingOnWeb": true, "showPricesOnWeb": true }, "2023": { "high": 1535, "compulsoryextraspricehigh": 35, "low": 1535, "compulsoryextraspricelow": 35, "allowBookingOnWeb": false, "showPricesOnWeb": false } ...

La disponibilité est générée à partir du point de terminaison GET availablebreaks. Chaque fois qu'une disponibilité est demandée à , la reçoit dans le format suivant. Lorsque des fourchettes de prix sont définies, cela signifie que le bien est disponible à la réservation.

 

 

 GET https://***.api.tabs-software.co.uk/legacy/property/CT016_KS/availablebreaks [ { "fromdate":"2022-02-21", "todate":"2022-03-01", "days":8, "price":169, "compulsoryextras":17 }, { "fromdate":"2022-02-21", "todate":"2022-03-02", "days":9, "price":339, "compulsoryextras":34 }, { "fromdate":"2022-02-21", "todate":"2022-03-03", "days":10, "price":508, "compulsoryextras":51 }, ...

(N/A)

sont extraits de à l'aide de la méthode GET availabilitybreaks. Ils sont fixés pour toutes les saisons selon les règles suivantes :

  • par défaut, l'enregistrement et les changements ne sont pas possibles

  • si le prix est "0", les conversions ne sont pas possibles

  • si le prix est supérieur à 0, l'enregistrement est possible à la date "fromdate" et le départ est possible à la date "todate".

Voir comment les changements sont réglés {"fromdate":"2019-02-12", "todate":"2019-02-13", "days":"1", "price":"0"},

  • Séjour impossible

{"fromdate":"2019-02-12", "todate":"2019-02-14", "days":"2", "price":"393"},

  • 2019-02-12 : (arrival) > Nous venons de le mettre à NONE dans la ligne précédente, mais maintenant le séjour est possible, donc CHECK IN

  • 2019-02-14 : (départ) > CHECK OUT

{"fromdate":"2019-02-12", "todate":"2019-02-15", "days":"3", "price":"465"},

  • 2019-02-12 (A) > ENREGISTREMENT

  • 2019-02-15 (D) > CHECK OUT

{"fromdate":"2019-02-12", "todate":"2019-02-16", "days":"4", "price":"557"},

  • 2019-02-12 (A) > ENREGISTREMENT

  • 2019-02-16 (D) > PASSER À LA CAISSE

{"fromdate":"2019-02-13", "todate":"2019-02-14", "days":"1", "price":"0"},

  • 2019-02-13 (A), séjour impossible > AUCUNE

  • 2019-02-14 (D) > NONE, mais nous l'avons précédemment réglé sur CHECK OUT, donc CHECKOUT

{"fromdate":"2019-02-13", "todate":"2019-02-15", "days":"2", "price":"393"},

  • 2019-02-12 (A) > ENREGISTREMENT

  • 2019-02-15 (D) -> CHECK OUT, mais c'était déjà CHECK OUT, donc pas de changement

{"fromdate":"2019-02-13", "todate":"2019-02-16", "days":"3", "price":"465"},

  • 2019-02-13 (A) > ENREGISTREMENT

  • 2019-02-16 (D) > CHECK OUT, mais c'était déjà CHECK OUT, donc pas de changement

{"fromdate":"2019-02-14", "todate":"2019-02-15", "days":"1", "price":"0"},

  • Séjour impossible.

{"fromdate":"2019-02-14", "todate":"2019-02-16", "days":"2", "price":"447"},

  • 2019-02-14 (A) > CHECK IN, mais nous nous souvenons que nous l'avons réglé sur CHECK OUT auparavant (un séjour de 2 nuits du 12), donc CHECK IN et CHECK OUT

  • 2019-02-16 (D) > CHECK OUT, mais c'était déjà CHECK OUT avant, donc pas de changement

(N/A)

(N/A)

(N/A)

 

 GET https://***.api.tabs-software.co.uk/legacy/property/382585_BW/securitydeposit?APIKEY=... [ { "id":1749, "type":"Property", ... "amount":150 ...

Monnaie (N/A)

La devise de tous les biens immobiliers récupérés sur est toujours fixée à la livre sterling. Soyez conscient de cette condition lorsque vous introduisez la tarification directement dans . Si vous avez une devise différente dans , la valeur sera synchronisée, mais affectée à la devise GBP, ce qui peut entraîner des divergences dans les recettes.