# Static voucher codes Static voucher codes use a fixed code that is the same for every user who redeems the reward. When a user redeems the reward, they are shown this predefined code, which can then be used in-store or online. This method is ideal when you don’t require individual code tracking and want a simple way to distribute a shared discount or offer. #### How it works When a static voucher reward is configured, you enter a predefined code in the reward settings. Each time a user redeems that reward, they receive the same code. This can be shown to a cashier, typed into an online checkout, or validated by your system.
Advantages of static voucher codesDisadvantages of static voucher codes
  • No integration with the Loyalty Engine is required to validate the code.
  • Simple to set up and use—especially for manual or offline validation.
  • Static codes can be shared or leaked, making them unsuitable for automated redemptions in online or self-serve environments.
  • There is no per-user tracking of code usage unless you implement it externally or integrate your system with the Loyalty Engine.
*** ## Static voucher code FAQs #### Can I see the code issued to a user in the Loyalty Console? Yes. While the code is the same for all users, you can view reward activity in the `REDEEMED_VOUCHER` event linked to the reward purchase. #### Can the Loyalty Console generate a static voucher code for me? No. You must manually define the static code during reward setup. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://kbase.whitelabel-loyalty.com/product/loyalty-engine/rewards-and-points/rewards/reward-types/vouchers/static-voucher-codes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.