> 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/implementation-guide/rewards-redemption/rewards/reward-list/reward-flow.md).
# Reward Flow
This section will describe the basic flow of rewards redemption depending on the business scenario (Reward Catalog or receiving Reward in the Campaign).
In the Admin Panel, you can use rewards as an effect in the Campaign or as a Reward Catalog and use it on your app so your customers can purchase them.
***
## Rewards as the Effect Campaign
The rewards can be used as one of the effects of the campaign. Besides adding/deducting units, you can grant the member with a specific reward.
The diagram below presents the simple flow of receiving the reward from the campaign:
***
## Reward Catalog
You can use rewards as a reward catalog so your members can purchase them in your app. The diagram below will present the basic flow of issuing rewards when you use it as a catalog.
The diagram below presents the simple flow of buying the reward from the reward catalog:
### Manually assigning reward
Admin panel allows for manually assigning rewards. To do so, click three dots next to the reward and select 'Claim for' from the menu.
The diagram below presents the simple flow of assigning the reward manually (or buying a reward by a member) with deducing points from the member's wallet (Price in Points set in the reward configuration):
---
# 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 dynamically 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/implementation-guide/rewards-redemption/rewards/reward-list/reward-flow.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 `build a script that syncs our docs to a CMS` 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.
.png)
