> For the complete documentation index, see [llms.txt](https://docs.prestashop-project.org/v.8-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prestashop-project.org/v.8-documentation/user-guide/selling/managing-catalog/managing-discounts.md).

# Managing Discounts

![](https://3898701297-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fenglish-documentation-for-prestashop-1-7%2F-MD-vfnaVcWH12Xtc2rz%2F-MD-vwawVlJLvyFatwHO%2F51839844.png?generation=1595596083276418\&alt=media)

Discounts and vouchers play an important role in your daily relationships with your customers. Typically, customers like two things when shopping:

* Feeling special, unique.
* Getting good prices.

Both can be achieved with customized discounts, and this is precisely where vouchers come into play – or more precisely, price rules.

"Price rules" can take two forms:

* **Cart rules**. It enables you to create per-customer voucher codes, but also much more.
* **Catalog price rules**. Enables you to assign price reductions by category, brand, supplier, attribute or feature.\
  \
  For instance, you can set a rule that would say that Spanish customers belonging to the "Good clients" group would get 10% off on your electronics category and all Sony products for the first week of July.

This chapter contains the following sections:

* [Cart Rules](/v.8-documentation/user-guide/selling/managing-catalog/managing-discounts/cart-rules.md)
* [Catalog Price Rules](/v.8-documentation/user-guide/selling/managing-catalog/managing-discounts/catalog-price-rules.md)


---

# 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://docs.prestashop-project.org/v.8-documentation/user-guide/selling/managing-catalog/managing-discounts.md?ask=<question>&goal=<user_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.