Discount configuration

Specify the value a reward provides by adding one or more discounts. Discounts communicate reward value to external systems like POS.

Discounts (referred to as Incentive Configuration in the Loyalty Console) define the actual incentive a reward provides—such as a discount or price override—and is primarily used to communicate that logic to external systems, like point-of-sale (POS) platforms, when a voucher code is validated.

Discounts can be added and managed after a reward is created. You can add one or more discounts per reward to define what the voucher entitles the user to—such as “£5 off your next order” or “20% off a specific product.”

Using discounts

Discounts are primarily used when integrating your point-of-sale (POS) system or e-commerce store with the Loyalty Engine to validate Vouchers as described in the Redeeming vouchers guide in our developer docs.

The property descriptions listed below (such as type, value, sku, and venues) are recommended interpretations designed to support common use cases. However, the Loyalty Engine does not enforce how these fields are used—your integration must handle and interpret them appropriately, as you dictate.

For example, the sku field can technically support a list of SKUs if your POS system is built to recognize a specific delimiter of your choosing (we recommend a comma), or even a SKU category code to support a group of SKUs in a predefined category in your POS. The same flexibility applies to other fields. It’s your responsibility to ensure the integration interprets discounts correctly.

---

Adding discounts

Each discount has a few key settings:

Discount types

This defines the kind of discount the reward offers. Three types exist:

Discount type	Description	Example
Absolute	An absolute discount, entered in the lowest currency denomination	'Get a $5 discount on your next dessert!' Entered as '500' in the value field
Percentage	A percentage discount, enter as a percentage amount	'Get a a 50% discount on your next dessert!' Entered as '50' in the value field
Fixed Price	A fixed price override, entered in the lowest currency denomination	'Get your next dessert for just $5!' Entered as 500 in the value field

SKU (optional)

Some POS systems use discount SKUs to apply discounts. This field allows you to specify a SKU in your POS system that represents the discount itself. This is useful when:

• You’ve already configured the discount logic in your POS and have an associated SKU for it, that when added to a transaction applies the relevant discount logic

• You need more complex behaviour (e.g. buy one get one free)

Product SKU (optional)

This field allows you to limit the discount to one or more specific product SKUs.

• Enter one or more SKUs, comma-separated.

• Leave blank to apply the discount to the entire transaction.

Venues (optional)

Defines which venues the discount is applicable at.

• This setting is different from venue availability in reward configuration, which controls where a reward can be redeemed.

• Use venue-specific discounts when the same reward should apply different benefits depending on where it’s redeemed. For example, a voucher might give £5 off in one store but 10% off in another. This allows for fine-tuned control over how a reward behaves at different locations.

Example discount configuration

Imagine a reward offering '$5 off your next purchase'. You want this to apply at all venues and to the whole basket:

• Discount type: Absolute

• Value: 500

• SKU: (leave blank)

• Product SKU: (leave blank)

• Venues: (leave blank)

---

Editing discounts

Discounts can be edited at any time after they have been created, by visiting the Incentive Configuration tab of the reward edit screen.

Editing a discount is immediate and applies to all voucher validations associated with that reward regardless of when purchased

The discount is stored in the reward's configuration, not in the associated benefit that is created whenever a user purchases the reward.

As such, the Validate voucher code endpoint will always return the current, live discount(s) specified in the reward configuration—not the discount that was applicable at the time a benefit was actually created/issued.

This means when you edit a discount in a reward, any benefits created by that reward which have not yet been redeemed or validated, will receive the new discount.

As such, the general recommendation is that if you want to change a discount you should archive the existing reward and create a new one with the new discount on offer.