Reward details

An overview of reward details, covering both the marketing and operational components of rewards, including user-facing elements and system functions like cost, category, and code types.

A reward's details include both the content users see—like the name, description, and image—and the settings that control how the reward behaves in your program, such as cost, category, and expiry.

---

Reward presentation

Reward presentation refers to the content users see when browsing or redeeming rewards. This includes the reward’s name, description, imagery, and other details that help communicate what the reward is and why it’s valuable. These elements play a key role in driving engagement and should be clear, consistent, and aligned with your brand.

Mockup of a reward details modal using details from the Loyalty Engine

For each reward, you can specify:

• Name (required) The main title for a reward.

• Summary An optional 'subtitle' to give a little more info.

• Description (required) The description gives more detailed information about what the reward offers and any specific instructions or insights for the user.

• Redemption message The redemption message is only applicable to voucher or gift card rewards and is intended to provide instructions on how to redeem or use the the reward.

• Terms & conditions Reward-specific terms and conditions, detailing any restrictions or rules related to redeeming or using the reward.

• Reward category Categorising rewards helps users navigate and find relevant rewards more easily.

• Picture (required) The picture is the primary image or visual that is intended to represent the reward in a user interface.

• Brand logo Supplemental artwork intended to complement the primary reward artwork for some use cases – for example showing an image of a brand gift card along with the brand logo side by side.

The Loyalty Engine is not a user interface.

As an API-first product, there are no fixed dimensions or requirements for reward artwork. You should upload assets in a format and size that suit how rewards are displayed in your user interface.

You can upload artwork when creating or editing a reward in the Loyalty Console, which is then served from the WLL CDN (we use Uploadcare). Alternatively, you can host your own images and specify your own URL.

If you’re using one of our white label customer interfaces: the Loyalty Microsite, Mobile App or the Tiles SDK, refer to Reward artwork guidelines for asset dimension requirements.

---

Reward configuration

Reward configuration defines how a reward functions within your program—including cost, availability, usage limits, fulfilment method, and other settings that control how and when it can be used.

The available configuration options vary depending on the reward type, but the following settings apply to all rewards:

Price

The price field sets the cost of a reward in points. For voucher-type rewards, users must have enough points to redeem the reward, and the points are deducted when it’s purchased. Setting the price to 0 makes the reward free, subject to the user meeting any reward availability constraints set.

Even for non-purchasable rewards (like offer-type rewards), a price is still required. This can be set to 0 or used to visually show the value of the promotion (e.g. “Refer a friend to earn 500 points”). In these cases, the price is just for display and does not control how many points the user earns—that’s handled by the associated reactor.

You may choose to take inspiration from the logic we use to display the price field in our own white-label customer interface products, the Loyalty Mobile App and Microsite:

• Purchasable rewards

  • If the cost is 0, a “FREE” badge is displayed.

  • If the cost is greater than 0, an “X points” badge is displayed.

• Non-purchasable rewards

  • If the cost is 0, no price is displayed.

  • If the cost is greater than 0, an “Earn X points” badge is displayed.

Priority

The priority determines the order in which a reward appears in the end-user’s reward list. A higher number places the reward higher in the list.

If no priority is set, the order of rewards in the list will be arbitrary.

Value

Only relevant for purchasable rewards, the value field is optional and represents the cost to your business to procure and deliver the reward in your tenant's default currency. It helps track the “loyalty cost” of users, shown in the Wallet tab of a user profile in the Loyalty Console.

This information is not intended to be shown to the end-user.

Example: If a reward costs £15 to procure and deliver, you would enter 15. If a user purchases five of these rewards, their loyalty cost would be £75 (5 * £15).

Availability

A reward’s availability defines when, where, and to whom a reward is visible or purchasable. See Reward availability for more details.

Making a reward temporarily unavailable

To hide a reward from users and prevent it from being purchased, set the Purchasable toggle to OFF in the reward’s Availability tab in the Loyalty Console.

Incentive configuration

A reward's incentive configuration defines the type and amount of discount it offers, as well as any applicable SKUs. This information can be communicated to a POS or e-commerce platform using the Validate a Voucher Code API endpoint, enabling the system to apply the correct discount.

For more information, see Discount configuration.

Reward type-specific configuraton options

Additional configuration options are available depending on a reward's type. See the relevant offer type articles for more information.

Offers

Vouchers

---

Reward details FAQs

Can I format reward details, like descriptions, redemption messages or terms and conditions, as rich text?

Reward details are stored as plain text in the Loyalty Engine. However, you can implement HTML rendering or markdown support in your customer interface to format any of a reward’s data points. This allows you to include rich text or other elements, such as:

• Formatting text and adding additional images and links to your reward description

• Adding links to your redemption message or terms & conditions

If using our white-label customer interface, the Loyalty Microsite, markdown support is included for the reward description field. See Format reward descriptions with markdown for more information.

Can I update reward details after a reward is created?

Yes, you can edit most reward details, including the name, description, artwork, and price. However, some details, like the code type and URL type, cannot be changed once set.

Is it possible to show different artwork for different audiences or users?

No, each reward can only have one set of artwork, which is shown to all users who can view the reward, regardless of audience or tier. If you want to show different artwork for different audiences, you must create separate rewards and apply an audience visibility constraint.

Can I include external links in the reward description?

Yes, while the description field stores plain text, you can implement HTML rendering or markdown support in your interface to include external links in the reward description (as mentioned in the first FAQ).

Can I adjust the order of rewards displayed to users?

Yes, the priority field allows you to control the order in which rewards appear. Higher priority rewards are displayed at the top of the list. Make sure to implement logic in your front-end customer interface to respect the priority field.

Is there a limit to the number of rewards I can create?

No, there is no fixed limit–within reason–to the number of rewards you can create within the Loyalty Engine.

Does the Loyalty Engine support different languages for reward details?

Yes, the Loyalty Engine supports multiple locales for most of the user-facing details through the module. You can provide translations for reward details like the name, description, and terms & conditions, allowing users to see rewards in their preferred language.

Can I create subcategories?

Yes, categories can include subcategories by assigning a “parent” category.

Can a single reward belong to multiple categories?

No. A reward can only belong to one category at a time.

Can I apply reward availability settings to an entire reward category?

You cannot apply audience or tier constraints to an entire category—these must be set at the individual reward level.