Variant Pricing

The variant_pricing tag renders a self-updating <span> which can interactively fetch and display up-to-date pricing information for a given variant, provided an adult count/start date/end date combination.

You can use this tag to display up-to-date prices of each variant you’re rendering on the page, responding to user interactions with the calendar and adult count for each displayed variant.

The tag is package-aware; if you use it in a package step template, it will display how much upgrading to that variant will cost, or Included if it is part of the package price.

input

{% variant_pricing variant: variant, class: "my-nice-class", adult_count: 2, start_on: "2023-01-01", start_time: "10:00", end_on: "2023-01-04" %}

output

The <span> tag will initially be rendered empty:

<span class="my-nice-class"
  data-controller="variant-pricing"
  data-variant-pricing-variant-value="<id>"
  data-variant-pricing-adult-count-value="2"
  data-variant-pricing-start-on-value="2023-01-01"
  data-variant-pricing-start-time-value="10:00"
  data-variant-pricing-end-on-value="2023-01-04">
</span>

If rendering in the context of a package booking template, the package step ID is included:

<span class="my-nice-class"
  data-controller="variant-pricing"
  data-variant-pricing-variant-value="<id>"
  data-variant-pricing-adult-count-value="2"
  data-variant-pricing-start-on-value="2023-01-01"
  data-variant-pricing-start-time-value="10:00"
  data-variant-pricing-end-on-value="2023-01-04"
  data-variant-pricing-package-step-id-value="<step id>">
</span>

Per-person and per-night pricing

You can display the price divided per person, per night, or both. This is useful when you want to show a nightly rate or a per-guest rate instead of the total price.

{% variant_pricing variant: variant, class: "my-nice-class", adult_count: 2, start_on: "2023-01-01", end_on: "2023-01-04", show_per_person_price: true, show_per_night_price: true %}

With both parameters enabled, the returned price will be the total divided by the number of guests and the number of nights. For example, a total of £600 for 2 adults over 3 nights would display as £100 (600 / 2 / 3).

Per-night behaviour:

• For accommodation variants, the price is divided by the number of nights derived from the start_on and end_on dates, falling back to the package’s accommodation step if dates are not provided
• For experience and extra variants in a package booking context, the night count is derived from the package’s first accommodation step
• Outside a package booking context, per-night division has no effect on experience and extra variants
• When used with package_total, the total package price is divided by the number of nights from the package’s accommodation step

Per-person behaviour:

• When adult_count is passed, the price is divided by that value
• If adult_count is not passed and a package_booking_id is in context, the price is divided by the package booking’s guest count
• Applies to all variant types (accommodation, experience, and extra)

Tag parameters

Bootstrapping and fetching new prices

The platform provides a Javascript component which automates the triggering of the appropriate server requests for pricing information, interpolating the result into the <span>’s inner HTML.

The component will request up-to-date pricing info when the following data attributes on the <span> are programatically updated:

Important: this tag is initially rendered empty. If you need it to have contents when the page is rendered, you must manually trigger a request by updating the data attributes with default values.

We recommend listening to user-driven changes on the page, and have the event handlers:

• Target the <span> tags by their class
• Assign the chosen values to their data-attributes

To “bootstrap” the contents on initial page load, you might hook onto the DOMContentLoaded event like so:

function bootstrapVariantPricingTags() {
  const defaultStartOn = "2023-01-01"
  const defaultStartTime = "10:00"
  const defaultEndOn = "2023-01-04"
  const defaultAdultCount = "4"

  const variantPricingTag = document.querySelector(".my-nice-class")
  variantPricingTag.dataset.variantPricingAdultCountValue = defaultAdultCount
  variantPricingTag.dataset.variantPricingStartOnValue = defaultStartOn
  variantPricingTag.dataset.variantPricingStartTimeValue = defaultStartTime
  variantPricingTag.dataset.variantPricingEndOnValue = defaultEndOn
}

document.addEventListener('DOMContentLoaded', bootstrapVariantPricingTags)

And to respond to changes to the selected adult count, check-in/out dates, and start time you might hook onto the relevant elements’ events:

document.querySelector(".adult-count-dropdown").addEventListener("change", (e) => {
  const variantPricingTag = document.querySelector(".my-nice-class")

  variantPricingTag.dataset.variantPricingAdultCountValue = e.target.value
})

document.querySelector(".start-on-calendar").addEventListener("change", (e) => {
  const variantPricingTag = document.querySelector(".my-nice-class")

  variantPricingTag.dataset.variantPricingStartOnValue = e.target.value
})

document.querySelector(".start-time-dropdown").addEventListener("change", (e) => {
  const variantPricingTag = document.querySelector(".my-nice-class")

  variantPricingTag.dataset.variantPricingStartTimeValue = e.target.value
})

document.querySelector(".end-on-calendar").addEventListener("change", (e) => {
  const variantPricingTag = document.querySelector(".my-nice-class")

  variantPricingTag.dataset.variantPricingEndOnValue = e.target.value
})

Consideration with packages

When this tag is used in the context of a package step, the user may need to choose from a range of time slots for the variant. In this case we calculate the cheapest possible price of the possible slots. We recommend pre-pending the price with ‘From’ in this case.

The slot which is used to generate the price is included in the data attributes:

<span data-variant-pricing-experience-slot-value="<slot id>">
</span>