Product price calculations & visibility

Discover how prices are calculated when utilising a mixture of price strategies - quantity pricing, access driven pricing, multi-currency and regional pricing.

Within this article our examples assume a default account currency in GBP. 

Quantity pricing

Also known as volume pricing, or bulk pricing. Price breaks based on quantity are often found in B2B and offer an incentive for users to increase their purchase volume per order.

Quantity Price per item Currency
1 £10 GBP
5 £9 GBP
10 £8 GBP


Based on the table above, a user adding a quantity of eight items to cart: 8 × £9 = £72

How to add quantity-based pricing

Access driven prices

You may grant prices based on access role. Let’s assume we offer a base price publicly but discounted quantity based prices per item for “Trade” partners. 

First, you’ll need to add a “Trade” access role.

Quantity Price per item Currency
Public
1 £10 GBP
Trade
5 £9 GBP
10 £8 GBP


Based on the above table, consumers will only see the £10 item price. However, your Trade users will be able to see prices for quantities 1, 5, and 10.

  • A consumer adding 8 items to cart receives a price of £10 per item, totalling £80. 
  • A "Trade" partner adding 8 items to cart receives a price of £9 per item, totalling £72.

Can I have more than one trade price?

Yes, you can. It’s fairly common in B2B to introduce trade partner levels. Let’s change our price table by introducing “Trade Silver” and “Trade Gold”:

Quantity Price per item Currency
Public
1 £10 GBP
Trade Silver
5 £9 GBP
10 £8 GBP
Trade Gold
10 £8 GBP


You’ll notice that the “Trade Gold” price only has a price at a quantity of 10.

So how does this appear to each user? Evance will choose the lowest available price across all access permissions granted to the user.

  • Consumers will see a £10 price regardless of quantity.
  • Trade Silver partners will see a £10, £9 and £8 price for quantities 1, 5, and 10 respectively.
  • Trade Gold partners will see a £10 and £7 price for quantities 1 and 10 respectively.
  • A user with both “Trade Silver” and “Trade Gold” access roles will see a £10, £9 and £7 price for quantities 1, 5 and 10 respectively.

How to add access role based prices

Multi-currency

For multi-regional websites utilising Locales, Evance allows you to choose between two currency matching options:

  1. Explicit currency matching
    Requires the currency in product prices to match that of the locale. For example, a locale with a USD currency requires products to have prices in USD. If not, no price will be shown for the product on the locale.

  2. Currency exchange (also known as implied currency matching)
    If no prices are present in the currency of the locale, then your default currency will be converted based on an exchange rate calculation. We’ll discuss exchange rate calculations below.

Explicit currency matching is straight-forward, so the remainder of this section is focused on currency exchange. Consider the following price settings where GBP is the tenant’s default currency:

Quantity Price per item Currency
1 £10 GBP
5 £9 GBP


Adding a new EUR-based Locale with currency exchange enabled will result in the following prices on your website:

Quantity Price per item
GBP EUR
1 £10 €12
5 £9 €10


Based on an exchange rate of 1 GBP = 1.2 EUR.

Evance has a built-in currency converter, which is updated every 6 hours. Utilising automated exchange rates offers convenience - reducing the overall maintenance of your product price. However, the rate is not guaranteed to be equal to that of your payment provider’s exchange rate.

You can adjust the exchange rate based on the following options in your Locale’s settings:

  • Custom rate
    If you would like to stabilise the exchange rate over longer periods, you can set your own custom exchange rate. For example, you may opt for a rate of 1.4 instead of a current rate of 12.01.

  • Offset rates
    Evance allows you to add a percentage and/or fixed offset adjustment to our internal exchange rate. The fixed adjustment is applied after the percentage adjustment. For example, the current exchange rate from GBP to USD is 1.22. A 10% offset would result in a rate of 1.342, and an additional fixed offset of 0.1 would result in a rate of 1.442.

Currency matching priority

In the currency matching example above we introduced a new EUR locale, with currency exchange. But what happens if we add a price to the product in EUR?

Evance prioritizes direct currency matches over the default currency. If the product has any EUR prices, it will ignore the default GBP ones.

Quantity Price per item
GBP EUR
1 £10 €12
5 £9 -


In the table above you’ll notice there is no price for a quantity of 5 or more for EUR. A user on a EUR-based locale adding eight items to cart will not benefit from a discounted item price.

  • A user on a GBP locale will see a £10 and £9 for quantities 1 and 5 respectively. Adding 8 items to cart receives an item price of £9.
  • A user on a EUR locale will only see a  €12 price regardless of quantity. Adding 8 items to cart receives an item price of  €12.

Currency priority versus access roles

Currency matching takes priority over access permissions. Consider the following price settings:

Quantity Price per item
GBP EUR
Public
1 £10 -
Trade Silver
5 £9 -
10 £8 -
Trade Gold
10 £7 -


In the table above there are no prices for Euros. In a locale with “Explicit currency matching”, all users will see no price available. However, for a locale with “Currency exchange” enabled, all users will see a price based on exchange rate. Assuming a exchange rate of 1 GBP = 1.2 EUR:

  • Consumers will see a €12 price.
  • Trade Silver users will see €12, €10.80, and €9.60.
  • Trade Gold will see €12 and €8.40
  • Users with both Trade Silver and Trade Gold access will see €12, €10.80 and €8.40.

Because currency matching takes priority over access roles, adding a single EUR price to our product changes price visibility dramatically.

Let’s introduce a consumer EUR price:

Quantity Price per item
GBP EUR
Public
1 £10 €12
Trade Silver
5 £9 -
10 £8 -
Trade Gold
10 £7 -


Regardless of the Locale's currency exchange rule, all users in a EUR locale will now only see the €12 price, regardless of quantity and access role.

Regional pricing using Geozones

Sometimes currency matching isn’t sufficient where prices differ regionally. Evance allows you to segment prices into country-based zones. A good example in the Eurozone might be to offer lower prices to Eastern European countries - Latvia, Lithuania and Slovakia.

The table below assumes you have a “East Europe” Geozone.

Quantity Price per item
GBP EUR EUR - East Europe
1 £10 €12 €10


We’ll assume that the East Europe zone includes Slovakia.

  • Users visiting a German locale (e.g. /de-de) will see a €12 price.
  • Users visiting a Slovakian locale (e.g. /en-sk) will see a €10 price.

How quantity prices work using Geozones

The following table sets a reduced base price in East Europe, but not for price quantities.

Quantity Price per item
GBP EUR EUR - East Europe
1 £10 €12 €10
5 £9 €10 -
10 £8 €9 -


In this scenario the quantity prices set for EUR cascade into East Europe:

  • Users in a German locale see €12, €10 and €9 prices based on a quantity of 1, 5 and 10 respectively.
  • Users in a Slovakian locale see €10 and €9 prices based on a quantity of 1 and 10 respectively.

To remedy the missing price break at a quantity of 5, you’ll need to explicitly define a new price lower than the international EUR value.

Strict versus lenient regional access

Product prices are categorized by currency and zone. If a price isn't assigned to a specific zone, it's considered the international price for that currency.

Usually Evance will find the lowest available price for the user. However, strict zone price selection prioritizes zone based pricing over international prices.

Let’s add a new zone for Germany with a higher base price.

Quantity Price per item
GBP EUR EUR - Germany
1 £10 €12 €13


How does this affect price visibility:

  • Strict price zones turned on (default)
    Users in a German locale will see a €13 base price.

  • Strict price zones turned off
    Users in a German locale will see a €12 base price.

Why is this useful?

Typically, lenient price zones are more useful for access drive pricing.

Example prices for a product:

  • £100 GBP - Internationally - Trade Access
  • £130 GBP - Internationally - Public Access
  • £120 GBP - United Kingdom - Public Access

With strict price zones enabled (default setting), User A in the United Kingdom with a Trade account sees £120, while User B in another locale with GBP currency and a Trade account sees £100. Removing the £120 price results in User A seeing the lower £100 price.

With strict price zones disabled, both User A and B see £100 - the lowest available price for their currency within matching zones.