> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/samita-wholesale-b2b/overview/wholesale-pricing-vs-volume-pricing.md).

# Wholesale pricing vs Volume pricing

Understand when to use Wholesale Pricing versus Volume Pricing, since the two features solve different problems.

Both features give discounts, but they trigger on different conditions. This page helps you pick the right one — or use both together.

## What is wholesale pricing?

You can offer a wholesale price to specific customers or customer groups. You choose which products, collections, or your entire catalog it applies to, and set the discount as a percentage or a fixed amount. Showing customers their wholesale price builds trust and encourages repeat bulk buying, while your retail shoppers keep seeing regular pricing.

<figure><img src="https://1875078098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcI28ZFsoFjOa0T0AsCVi%2Fuploads%2Fgit-blob-a64838690bc9f59ae6d5d043fe274c940eba7148%2Fimage%20(326).png?alt=media" alt=""><figcaption></figcaption></figure>

***

## What is volume pricing?

Volume pricing (also called quantity-break pricing) discounts a product more as customers buy more of it. It's a win-win: you move more inventory, and the customer saves money by ordering in bulk. For example:

* 10–19 units = 10% off
* 20–29 units = 20% off
* 30–39 units = 30% off
* 40–49 units = 40% off
* 50+ units = 50% off

<figure><img src="https://1875078098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcI28ZFsoFjOa0T0AsCVi%2Fuploads%2Fgit-blob-6e58d703410a4eb6cf29dfeb0f66d32308f5acae%2Fimage%20(327).png?alt=media" alt=""><figcaption></figcaption></figure>

***

## What's the difference?

{% columns %}
{% column %}
**Wholesale pricing**

One discount value applied to selected products or customers, regardless of quantity.

Example: Buy product A, get 10% off.
{% endcolumn %}

{% column %}
**Volume pricing**

Discount tiers based on quantity purchased (quantity breaks), and can display a pricing table on your storefront.

Example: Buy 10, get 10% off. Buy 20, get 15% off.
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
You can run both features at the same time. If a product and customer match rules from both features, contact **<support@samita.io>** to confirm how the app resolves the conflict for your setup.
{% endhint %}

> ### **Need support?**
>
> If you do encounter any difficulty while proceeding these steps, don’t show any hesitation to contact us promptly via the email address [support@samita.io](https://help.samita.io/support@samita.io)


---

# 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.samita.io/samita-wholesale-b2b/overview/wholesale-pricing-vs-volume-pricing.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.
