> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/rewards-redemption/rewards/reward-list/creating-reward.md).
# Creating Reward
This section will explain you how to add reward in the Admin Panel
## 🛠️ Creating Rewards
You can create rewards in Open Loyalty directly from the **All rewards** list by clicking **➕ Add reward**.\
This opens a step-by-step wizard:
1. **Reward type** – type, value and wallet
2. **Basic settings** – details, dates and targeting
3. **Limits** – per member and reward limits
4. **Coupon configuration** – generating and managing codes *(coupon rewards only)*
5. **Additional info** – instructions, brand and images
6. **Summary** – review the configuration
A material reward has no **Coupon configuration** step, so its wizard has five steps. Editing a reward opens the same wizard.
You can also **Import rewards** from a previously exported `.JSON` configuration file (e.g., from another tenant or environment).
{% hint style="info" %}
The **Active reward** toggle in the upper right corner of the wizard sets the reward's status:
* **Active** – available for members to redeem immediately.
* **Inactive** – saved as draft, not visible until activated.
{% endhint %}
***
### 1. Reward type
First, select the reward type:
* 📦 **Material reward** – a physical item (e.g., T-shirt, mug).
* 🎟️ **Coupon** – a digital reward such as a discount or voucher (e.g., $10 off, 10% off, or a set value).
If you choose **Coupon**, you also select the coupon type here (see [Reward Types](/rewards-redemption/rewards/reward-list/reward-types.md)), and the wizard gets the **Coupon configuration** step.
On the same step, you set:
* 💳 **Wallet** – the wallet the units are taken from, with the price in currency and the reward price in units.
* 🗂️ **Category** – assign to a reward category (if previously created).
***
### 2. Basic settings
In this step, you define the main details of the reward:
* 🏷️ **Name** (with translations if needed).
* 📝 **Description** (rich text editor).
* 📆 **Reward availability** – the period during which members can redeem the reward using units.
* Always available.
* Available only in a specific period of time.
* 👁️ **Reward visibility in catalog** – the period during which the reward is displayed in the catalog for the targeted members.
* Always visible.
* Visible only in a specific period of time.
* 🎯 **Reward targeting**
* Available for everyone.
* Available for a specific segment.
* Available for a specific tier.
***
### 3. Limits
Set how many times rewards can be redeemed:
* **Reward availability limit** – maximum redemptions across all members.
{% hint style="warning" %}
For **uploaded coupon codes**, this option does not appear - availability is limited by the number of uploaded codes. Only the member redemption limit applies.
{% endhint %}
* **Member redemption limit** – maximum redemptions per member.
You can set limits across different time periods:
* **In total** – fixed number of redemptions until exhausted.
* **Hourly** – resets every hour.
* **Daily** – resets every day.
* **Weekly** – resets every week.
* **Monthly** – resets every month.
* **Yearly** – resets every year.
* **Unlimited** – no restriction.
***
### 4. Coupon configuration *(only for coupon rewards)*
If the reward is a **coupon**, choose the **Source of coupons**:
* ⚙️ **Autogenerated coupons** – codes generated by Open Loyalty.
* Options: **length**, **charset** (Alpha / Numeric / Alphanumeric), and optional **prefix**.
* 📂 **Coupons uploaded from an external source** – coupon codes uploaded in bulk. Importing codes is only possible after the reward has been created.
In the same step, under **Coupon pending and expiration settings**, define the coupon lifecycle:
* **Pending stage** – number of days before the coupon becomes active.
* **Expiration** – either after a set number of days or on a fixed date.
***
### 5. Additional info
Optional content that provides more context:
* 📖 **Usage instructions** – how to use the reward.
* 📜 **Conditions description** – terms and conditions.
* 🏷️ **Brand name**
* 📝 **Brand description**
#### Custom attributes
* Add extra fields to store additional details (e.g., SKU, partner ID, internal codes).
#### Reward images
* Upload images in `.jpg` or `.png` format (max 3 MB).
* These images are displayed in the reward catalog.
***
### 6. Summary
Review the configuration before saving the reward.
***
## Rewards export/import
In the Rewarda section, you can export and import rewards. These actions require a file in a `.json` format.
### Exporting rewards
{% hint style="success" %}
**Exporting rewards how-to**
To export a single reward or several rewards:
1. Go to **Rewards** -> **All rewards**
2. Click **SELECT TO EXPORT**
After clicking this button you will see the checkboxes next to the reward name
3. Select the rewards you want to export to the JSON file
4. Click **EXPORT TO .JSON FILE (X)** to download the file
{% endhint %}
### Importing rewards
{% hint style="success" %}
**Importing rewards how-to**
To import a single reward or several rewards:
1. Go to **Rewards** -> **All rewards**
2. Click **ADD REWARD** -> **Import rewards**
After clicking this button you will see the pop-up window to upload the JSON file
3. Follow the instructions from the popup window.
4. Click **IMPORT** to upload the rewards file
5. After importing the rewards you will see the list of all successful and/or rewards that require the action.
{% endhint %}
### Duplicating reward configurations to a different tenant
{% hint style="success" %}
**Exporting rewards to a different tenant how-to:**
To export a single reward or several rewards to different tenants:
1. Go to **Rewards** -> **All rewards**
2. Click **SELECT TO EXPORT**
After clicking this button you will see the checkboxes next to the reward name
3. Select the rewards you want to export to a different tenant
4. Click **Export rewards to 'Different tenant' ->** Select the targeted tenant
5. To complete the action click **Copy \`Rewards and view the target tenant.**
6. After importing the rewards you will see the list of all successful and/or rewards that require the action to edit.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.openloyalty.io/rewards-redemption/rewards/reward-list/creating-reward.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
