Vouchers — sale, issue and redemption
The module covers public sales, manual issuing, delivery, balance checks, redemption, voiding and operation history. Every voucher has a code, status, initial value, remaining balance, redemption rules and a snapshot of the offer at the time of purchase.
Verified 2026-07-15
The module covers public sales, manual issuing, delivery, balance checks, redemption, voiding and operation history. Every voucher has a code, status, initial value, remaining balance, redemption rules and a snapshot of the offer at the time of purchase.
What can be sold
- Open amount — a set of denominations, optional custom amount, minimum, maximum and amount step.
- Fixed value — a defined voucher value; the sale price can differ from the value.
- Offer — a service, product, dish, bundle or experience with a name, description, category, image, duration, price and translations.
A restaurant offer can be linked to a menu item. In exact item mode, the voucher grants entitlement to the specified item, also identified by SKU; in value mode, it works as a defined amount.
Configuration
In Settings → Vouchers, the owner or an authorised manager configures:
- the offer and item order;
- denominations and custom amount;
- validity: no expiry, a number of days after purchase or a fixed date;
- partial or single-use redemption;
- voucher types allowed as a benefit in Ordering;
- logo, colours, message, background, images, PDF layouts and palettes;
- content translated into public languages;
- reminders before expiry.
The public link is /{slug}/voucher. The balance page for an individual voucher uses its code and shows its current state. Links containing a private token must not be published or sent to third parties.
Sale and delivery
For an online purchase, Reven creates a pending purchase and redirects to the configured payment flow. The voucher is created only after the correct amount, currency and payment have been confirmed. The customer receives an email and PDF according to the configuration. Issuing multiple vouchers must complete for the full expected quantity, not only the first item.
Staff with vouchers:issue can create a voucher manually for an in-person, telephone or compensatory issue. Record the source and do not manually mark as paid a purchase that may still be confirmed by the provider.
Redemption
In Vouchers → Scan, staff enter or scan the code, check status and balance, and then confirm the redemption amount. Partial mode leaves a balance; single-use mode uses the whole voucher according to the offer rules. The operation should be performed only once and recorded in the history.
In Ordering, a customer can apply a supported voucher to the basket. The server recalculates the benefit value, prices, delivery and amount due. If the voucher does not cover the whole amount, the remainder can be paid by card. For a refund combined with a card payment, the voucher balance should be restored only after confirmation of the corresponding refund operation.
Wallet, messages and expiry
A voucher can be saved to Apple Wallet or Google Wallet when the integration is configured for the business and product. A message sent to the saved card does not replace an email or formally change the terms. Expiry and reminders are processed by system jobs; the business should maintain correct contact details and terms content.
Common checks
| Symptom | Check first |
|---|---|
| Customer cannot purchase | active module, active offer, currency and ready payment provider |
| Email/PDF is missing | payment status, voucher creation, address, send history and spam |
| Code does not work | exact code, status, validity, balance and offer mode |
| Cannot be used in Ordering | allowed type, menu/SKU link and basket contents |
| Balance after refund is incorrect | payment refund state, redemption history and benefit-restoration history |
For a financial discrepancy, do not create a second voucher or manual correction before checking the transaction and operation history.