> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/bonus-system/admin-dashboard/bonus-products.md).
# Bonus products
Bonus products are rewards: existing products of your catalogue that customers can order with points — either exclusively with points or alternatively with money.
> For rewards to appear in the storefront, **Enable bonus products** must be switched on in the [configuration](/en/plugins/bonus-system/installation.md). There you can also define a minimum cart value, the slider settings and a header image for the rewards list.
## Overview
The list shows the bonus products you created, with the columns **Name**, **Active**, **Valid from** and **Valid until**. The order in the storefront follows the order of this list (default sorting); customers can additionally sort by price or name in the storefront.
## Adding a bonus product
Click **New product** and fill in the fields of the detail page. **Save** applies your settings.
| Field | Type | Description |
| --------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Product | Select | An existing product from your catalogue. |
| Active | Toggle | Only active bonus products appear in the storefront. |
| Valid from / Valid until | Date | Period in which the reward is offered. |
| Costs | Select | *Use redeem point factor from plugin settings* — the point costs are derived from the product price and the conversion factor. Or *Define points* — you set the points directly. Required. |
| Number of points | Number | Point costs when using *Define points*. |
| Only buyable with points | Toggle | The product can only be ordered with points. If off, the customer can choose between money and points. |
| Max. order quantity | Number | Maximum quantity a customer can order of this reward. |
| Restrict for sales channels | Multi select | Sales channels the reward is offered in. Without a selection it applies to all channels. |
> When using *Use redeem point factor from plugin settings*, a redemption conversion factor must be set in the configuration — otherwise the calculation yields no point costs.
## In the storefront
* The rewards list lives at `/bonus-products` and is reachable through the bonus system menu in the customer account. **Hide bonus products menu entry** removes it.
* Optionally, available rewards are shown as a slider in the cart and in the checkout.
* If the balance is not sufficient or the minimum cart value is not reached, the customer gets a corresponding hint.
* Customers who are not logged in are told that they have to log in to buy with points.
## Alternative: every product as a reward
If every product should generally be payable with points, enable **Enable bonus product feature for every product** in the configuration. You then do not need to create individual bonus products; the point costs are derived from the redemption conversion factor.
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.premsoft.de/en/plugins/bonus-system/admin-dashboard/bonus-products.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.