> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/merchandising-experiences/offer-modifications/offers-library/the-volume-discount-duel.md).

# The Volume Discount Duel

[Experiences](https://github.com/intelligems-io/docs/tree/main/public-docs/getting-started/common-use-cases/offer-test-common-use-cases/broken-reference/README.md) allow you to serve specific discounts and offers to your site visitors. One of these types of Offers is a Volume Discount. While you can have such an Experience on all the time, Intelligems can also help you test which thresholds and discounts drive the most value.

You can do this by setting up an [Merchandising Experience](/merchandising-experiences/offer-modifications.md).

*What this test design might look like:*

<table data-header-hidden><thead><tr><th width="203"></th><th></th><th width="215"></th><th></th></tr></thead><tbody><tr><td></td><td><strong>Control Discount</strong></td><td><strong>Higher Discount</strong></td><td><strong>Lower Discount</strong></td></tr><tr><td><strong>Product A</strong></td><td><p>15% off $100 or more</p><p>20% off $150 or more</p><p>25% off $200 or more</p></td><td><p>20% off $100 or more</p><p>25% off $150 or more</p><p>30% off $200 or more</p></td><td><p>10% off $100 or more</p><p>15% off $150 or more</p><p>20% off $200 or more</p></td></tr></tbody></table>

{% hint style="info" %}
We recommend taking a look at a histogram of your order values for the last month (or more) when deciding what Volume Discounts to test, especially if Volume Discounts will be a new addition to the site. For example, if a majority of your orders come in around $100, you may not want to provide a discount for orders over $100, but rather start around $150.
{% 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://docs.intelligems.io/merchandising-experiences/offer-modifications/offers-library/the-volume-discount-duel.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.