• Blog
  • Changelog
  • Roadmap
  • Pricing
  • FAQ
  • Getting started
    • Key concepts
    • Sign in
    • Create and switch organisations
    • Dashboard
  • Registers
    • Create and change a register
    • Upload and download entries
    • Add, edit and deactivate entries
    • Groups
    • Claims
    • Challenge codes
    • Connect and test an external register
    • Register activity
  • Membership definition
    • Add and order register assignments
    • Filters and outcomes
    • Preview before saving
    • Save and version history
  • Member code query
  • Members directory
    • Find a member
    • Look up the checks of a member code
    • Deactivate a membership
    • Anonymize a membership
  • Communities
    • Create, rename and delete a community
    • Filter by register, status, groups and claims
  • Frontends
    • Create a frontend
    • Frontend keys
    • Released claims
    • Sign-in settings
    • Guest access
    • Sign-in branding
  • Login with appsolut
    • Sign-up and onboarding
    • Sign-in and sign-out
    • Support requests
  • Frontend users
    • Find a frontend user
    • Membership and activations
    • Block a frontend user
    • Export a frontend user's data
    • Disconnect a frontend
  • Membership check
    • Check modes
    • Results and the check log
    • Rate limits
    • Grace rule
  • Vouchers
    • Partners
    • Create a voucher offer
    • Voucher pools
    • Activate, pause and end a voucher offer
    • Voucher settings
    • Import from the Portal
  • Redemptions
    • Handle a redemption
    • Redemption settings
  • Organisation settings
    • Organisation profile
    • Studio users and roles
    • Permissions
    • Billing
    • Roadmap and feature requests

appsolut ONE – enterprise community server. One platform for your internal and external communities, with membership and sign-in built in.

About
  • Blog
  • Contact
Documentation
  • Studio
  • Portal
  • Developers
Product
  • Roadmap
Legal
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Impressum

© Copyright 2026 appsolut ONE. All Rights Reserved.

  • Blog
  • Changelog
  • Roadmap
    1. Documentation
    2. Studio
    3. Vouchers
    Studio

    Vouchers

    The partners who honour your organisation's vouchers, the voucher offers for your members, and their codes.

    Under "Vouchers" your organisation runs its voucher programme: the partners who honour vouchers, and the voucher offers, one per deal for your members, with the code each member is given when redeeming. Frontends, such as a Community Portal, show the offer as their own content and run the redemption; the Studio decides which code a member gets and how often.

    The Voucher offers page of Pannoniqa AG, listing its offers with partner, offer status, validity, the masked static codes, a voucher pool with low stock and the redemptions of the last 30 daysThe Voucher offers page of Pannoniqa AG, listing its offers with partner, offer status, validity, the masked static codes, a voucher pool with low stock and the redemptions of the last 30 days

    Search the list by name, and narrow it by partner, offer status or category. Ended offers are hidden until you tick "Show ended", and only then does the status filter offer "Ended"; a link that filters by "Ended" ticks it for you. "Clear filters" also takes the tick away. The list counts only the offers it shows. The offers on a partner's page hide their ended ones in the same way, with a "Show ended" of their own.

    Offers that need your attention always come first, whatever column you sort by, whatever you search for and filter: first an offer with an empty voucher pool, then one whose pool is at or below its low-stock threshold, then an active offer past its "Valid until", which frontends already show as ended although nobody has ended it. Their badges mark them: "Empty", "Low stock" and "Past its validity". Within each of these groups, and among all other offers, the list follows the order you chose. Ended offers are never moved up. The offers on a partner's page come in the same order.

    The list counts each offer's redemptions of the last 30 days. An offer's page shows under "Redeemed by" the content on your frontends through which members redeemed it, named as the frontend showed it, with its redemptions and when it was last redeemed. With "Redemptions: manage", "All redemptions" opens the redemptions of the offer.

    Terms

    • A partner is a business that honours your vouchers, such as "Thermalbad Pannonia". It has contact persons and may have a redemption address: the email address members' messages about a redemption go to.
    • A voucher offer is one deal: its partner, its validity, its offer status, its voucher sources and its redemption limit. Frontends show their own texts and images for it.
    • A voucher source is where the code comes from for one customer kind: new customers, and optionally existing customers of the partner. A source is a static code, one code every member is given, or a voucher pool: a stock of unique codes your partner supplied, one for each member.
    • The offer status is what you set: "Draft", "Active", "Paused" or "Ended". Only an active offer within its validity gives out codes. "Ended" is final.
    • The redemption limit says how often one person may redeem the offer: once, a number of times per calendar month or year, or unlimited, counted across all your frontends.
    • An offer category is an entry in your organisation's own list that groups voucher offers, such as "Mobility" or "Leisure", named in German and in English. An offer is in none, one or several categories. Categories help you and Portal editors find offers; members never see them.

    Static codes and pool codes show masked in every list, with their first three characters only. A Studio user who manages vouchers sees static codes in full on the offer's own page, and shows a pool code in full one at a time.

    Who can do this

    Studio roles: "Owner" and "Administrator", and Studio users with a permission set that holds "Vouchers: read" or "Vouchers: manage". With only "Vouchers: read" they see the partners, voucher offers and voucher pools, with the codes masked, without changing them, and not the voucher settings. Other Studio users do not see "Voucher offers" and "Partners" in the sidebar. A Studio user whose permission sets hold "Redemptions: manage" but no voucher permission sees only "Redemptions" under "Vouchers". Permissions lists which permission each page and action needs.

    In this section

    • Partners: add the businesses that honour your vouchers, with their contact persons and redemption address.
    • Create a voucher offer: its partner, validity, voucher sources and redemption limit.
    • Voucher pools: import your partner's codes, watch the stock and withdraw codes.
    • Activate, pause and end a voucher offer.
    • Voucher settings: the default redemption address, the benefits alert address and the offer categories.
    • Import from the Portal: move a Community Portal's partners, static codes and voucher pools into the Studio.
    Previous pageGrace ruleNext pagePartners