Documentation/Studio
Back
  • Getting started
    • Key concepts
    • Sign in
    • Create and switch organisations
  • 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
  • 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
  • Redemptions
    • Redemption settings
  • Organisation settings
    • Organisation profile
    • Studio users and roles
    • Billing
    • Roadmap and feature requests

Activate, pause and end a voucher offer

Decide when a voucher offer gives out codes, and end it for good.

Studio roles: "Owner" and "Administrator", and Studio users with the permission set "Voucher manager".

The offer status decides whether a voucher offer gives out codes. Open the offer and use the buttons at the top of its page; each asks you to confirm.

Offer statusWhat it meansWhat you can do
"Draft"A new offer. Frontends may already link it, but it gives out no codes."Activate", "End"
"Active"It gives out codes within its validity."Pause", "End"
"Paused"Your stop button: no codes until you activate it again."Activate", "End"
"Ended"Final: it gives out no more codes and can neither be activated nor changed again.Nothing

An active offer outside its validity gives out no codes either: before "Valid from" it has not started, after "Valid until" it is over.

What your frontends see

Your frontends' backends read your offers through the Service API, never their codes:

  • To link content to an offer, they list every offer whose status is not "Ended", with its name, partner, offer status and validity. A draft is listed as a draft; an ended offer is no longer listed. An active offer after "Valid until" is still listed, and reads as ended on its page.
  • On a page, they read the offer's availability for new and for existing customers: available, not started (a draft, or before "Valid from"), paused, ended (or after "Valid until") or sold out. For a signed-in member it also learns how often their organisation membership redeemed the offer, across all frontends and also before the membership was theirs, and whether the redemption limit is reached. It never learns how many codes are left.

End an offer when the deal is over. Once every offer of a partner has ended, you can archive the partner.