# Creating Reward

## 🛠️ Creating Rewards

You can create rewards in Open Loyalty directly from the **Rewards list** by clicking **➕ Add reward**.\
This opens a step-by-step form where you define the reward type, general settings, limits, and (if applicable) coupon configuration.

You can also **Import rewards** from a previously exported `.JSON` configuration file (e.g., from another tenant or environment).

***

### 1. Type of reward

First, select the reward type:

* 📦 **Material reward** – a physical gift (e.g., headphones, coffee machine).
* 🎟️ **Coupon** – a digital coupon that can represent discounts, free shipping, or converted points.

If you choose **Coupon**, you’ll later see additional sections for coupon type, configuration, and expiration settings.

***

### 2. Basic settings

In this section, 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.
* 🗂️ **Category** – assign to a reward category (if previously created).

***

### 3. Redemption 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.
{% endhint %}

* **Member redemption limit** – maximum redemptions per member.

<figure><img src="/files/60dF8oqTUfljO9l9Og5l" alt=""><figcaption></figcaption></figure>

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. Additional settings

Optional descriptive fields to provide more context:

* 📖 **Usage instructions** – how to use the reward.
* 📜 **Conditions description** – terms and conditions.
* 🏷️ **Brand name**
* 📝 **Brand description**

<figure><img src="/files/4URxQIPQPvuQkuNikMdw" alt=""><figcaption></figcaption></figure>

***

### 5. Custom attributes

* Add extra fields to store additional details (e.g., SKU, partner ID, internal codes).

<figure><img src="/files/TZkK8Fa8uAe1QRaE2Kax" alt=""><figcaption></figcaption></figure>

***

### 6. Reward images

* Upload images in `.jpg` or `.png` format (max 3 MB).
* These images are displayed in the reward catalog.

***

### 7. Coupon configuration *(only for coupon rewards)*

If the reward is a **coupon**, configure how the coupons will be provided:

* ⚙️ **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.

<figure><img src="/files/K5UXFLzrzJ4tZ0PT4oTn" alt=""><figcaption></figcaption></figure>

***

### 8. Coupon pending & expiration settings *(only for coupon rewards)*

Define 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.

***

### 9. Reward status

Finally, decide whether the reward should be:

* **Active** – available for members to redeem immediately.
* **Inactive** – saved as draft, not visible until activated.

###

## 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** -> **List of 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&#x20;
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** -> **List of 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** -> **List of 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: 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://help.openloyalty.io/main-features/rewards/reward-list/creating-reward.md?ask=<question>
```

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.
