The Redemptions section in the Dashboard consists of four tabs: Redemptions, Validations, Sessions, and Stacking Rules. The Redemptions tab lists every redemption attempt of any code created within Voucherify. Its goal is to help you track what happens to your codes. Thanks to the filter panel and export tool, you can analyze and draw insights from redemption data.


  1. Redemptions
    1. Filters
    2. Redemption details
    3. Failed redemptions
    4. Detailed logs
  2. Validations
  3. Sessions
  4. Stacking rules
    1. Discounts’ application rules
    2. Limit settings for stackable discounts
    3. Campaigns stacking eligibility
    4. Discounts calculations by category


Whether succeeded, rolled back, or failed, each redemption attempt is saved in Voucherify.

Redemptions view in Voucherify dashboard, showing succeeded, rolled back, and failed redemptions.


Redemptions view provides you with a set of filters to track every redemption based on:

Click the Find and apply filters button to create a search query.

Redemption details

You can click on any redemption to display all the details. The basic view contains:

  • Created date
  • Voucher and campaign details
  • Customer who has redeemed the code
  • Metadata (optional)
  • Events
  • Activities

Depending on the campaign the voucher comes from, the details view can additionally include:

  • Order summary
  • Customer details

You can also access the redemption details by going to the voucher details and the Redemptions history tab in the Vouchers section of the dashboard.

Failed redemptions

Because Voucherify supports complex coupon validation rules, the redemption can fail for multiple reasons. Click on the ID of a failed redemption attempt to see the failure code and failure message. The following list shows all of the failure messages:

  • Voucher did not exist
  • Voucher was not active yet
  • Voucher expired
  • Voucher was disabled
  • Redemption quantity exceeded
  • Gift voucher amount exceeded
  • Order does not match validation rules
  • Customer does not match to the segment
  • Redemption conditions not met
  • Order was specified incorrectly
  • Order amount was specified incorrectly
  • Order amount was not specified
  • Order items were not specified
  • Customer was not specified
  • Invalid input data 

Here is an example of a failed redemption: 

Detailed view of a failed redemption

Remember 💡

Successful redemptions can be reversed with the process called “Rollback”. You can rollback each redemption using the API or with the Rollback button in the redemption details screen. Note, however, that you can roll back a redemption up to 3 months back.

Detailed logs

If you want more information about the history of the voucher, go to the detailed view of the redemption and the  Events section.

A successful redemption event

Click on the event to see the following details:
  • Id
  • Type
  • Occurrence date
  • Log ID
  • Channel
  • Event data

Redemption event details

Event data contains all the information about the event in JSON format.
Click the log id to see more details about the event. The log includes the following sections:
  • HTTP method
  • Related Events
  • Request Body
  • Response Body
  • Query Parameters

You can also access this view by going to the Audit Log section in the dashboard and by clicking the relevant log id.

Data export

You can download a CSV file with redemptions data. You can apply filters and browse data you are interested in or download the complete redemptions history. 

In the Redemptions tab, click the export tool button to open the export manager.

Choose which redemption details you want to include in your CSV file. You can choose options from Redemption attributes and Custom attributes (metadata).

Export tool for redemptions, showing redemption attributes and custom attributes (metadata)

Click the Export button.

When the CSV file is ready to download, you can see it in your notifications center. Click the notification to download the file.

Notifications view with an export file ready for download


This tab shows the complete overview of voucher validations and their session keys.

Validations tab showing a filtered list of validations


In the Sessions tab, you can to unlock validation sessions. ClickChoose the triple dots under Actions and then click Release next to the session.

Releasing a validation session

Stacking rules

This tab includes settings for applying discounts in stacks. A stack groups several validations and redemptions under a single API request. For a more in-depth description, read the Stacking Rules article.

Discounts’ application rules

Application rules define which redeemables need to be valid in order for a redeemable stack to be successfully applied. There are two options:

All – all provided redeemables must be in a valid state and be redeemed together. If any single redeemable is not in a valid state, the stack as a whole cannot be redeemed.

Partial – this allows partial redemption. If some provided redeemables are in a valid state while others are not, only the provided redeemables that are in the valid state will be redeemed. The inapplicable discounts where the redemption criteria are not met are discarded.

Sorting rules define the hierarchy order in which redeemables are applied. There are two options:

Requested order – this is the default order in which the redeemables are sent in the request. In some campaigns, this tier hierarchy can be defined in the dashboard. Otherwise, the default order of the request is applied.

Category hierarchy – the request is sent in the order of category hierarchy and rank, as defined by the hierarchy (number) when creating a new category in a campaign. If the redeemables do not have a category, their order will not change.

Limit settings for stackable discounts API

You can set up how many redeemables can be supported in one API request. The maximum is 30 redeemables that can now be supported at once. These maximum limits can be configured here.

Maximum count of redeemables in API request – this is the maximum number of redeemables in one stack that can be sent in a single API request to Voucherify. This will include all redeemable options.

Maximum count of valid promotions to apply in a request – of the total redeemable options defined in the API request, this determines the maximum amount of valid redeemables that can actually be applied in a single request to an order. The number can be the same as the Maximum count of redeemables in API request, meaning all redeemables being sent in the request would be applied if valid.

Maximum count of valid exclusive promotions to apply in a request – this provides the same function as the Maximum count of valid promotions to apply in a request, but only for the redeemables with Never Stackable (exclusive) stacking eligibility.

Campaigns stacking eligibility

These rules define whether redeemable categories should never be stackable (exclusive redeemables), always stackable (joint redeemables that will always be stacked with others), or optionally stackable (regular and flexible stack eligibility based on the hierarchy order).

Never Stackable (Exclusive) – the redeemables within this category can be redeemed only with other exclusive redeemables. The Maximum count of valid exclusive promotions to apply in a request limits how many exclusive redeemables can be applied at the same time. Voucherify will apply the redeemables with the highest hierarchy first.

Note: The Always Stackable (Joint) redeemables are an exception and they can be combined with exclusive redeemables.

Always Stackable/Joint – the redeemables with this category will always be added to the redemption stack, regardless if an exclusive redeemable is in the stack.

If a category is not defined as Never Stackable (Exclusive) or Always Stackable/Joint, this means it will be treated with regular stacking eligibility. It will be applied in the hierarchy sort order (see above) defined in the Maximum count of valid promotions to apply in a request.

Discounts calculations by category

Here you can define the default system mode for how the discounts are calculated and with different default settings according to the category.

Default – this is the default mode of calculating discounts across the system for any redeemables without categories or with the categories which do not have defined discount calculations by either Initial Amount or Discounted Amount below.

Initial Amount – all the selected campaign categories will override the default setting and always calculate discounts by the initial amount. A stacked discount based on the initial amount means that each additional redeemable applied after the first one will still base that redeemable on the initial pre-discounted order total.

Discounted Amount – all the selected campaign categories will override the default setting and always calculate discounts by the discounted amount. A stacked discount based on the discounted amount means that each additional redeemable applied after the first one will base that redeemable on the new discounted order total.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us