> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/rules-and-customizations/rules-overview/pricing-by-segment-and-partner.md).

# Pricing by Segment and Partner

Not every customer should pay the same price. **Pricing rules** let you charge by *who's buying* — enterprise, resellers, nonprofits — with discounts, markups, and overrides resolved at checkout, in priority order.

{% embed url="<https://youtu.be/S-sB5p7UAxw>" %}

**Where to find it**

Go to **Rules & Automation → Pricing Rules**. Rules are evaluated from **low priority to high**, and the first rule that matches sets the price.

**Build a segment or partner rule**

1. Select **New Pricing Rule** and give it a clear name.
2. Choose the **Rule Type** — **Segment Pricing** for a customer segment, or **Partner Pricing** for the accounts you sell through.
3. Set the **Adjustment** — a percentage discount, a percentage markup, a fixed override, or a tiered price table — and its value (for example, 25% off).
4. Under **Conditions**, define *who* it applies to: match on a customer attribute such as **segment** equals *Partner*, or *Enterprise*.
5. Set the **Priority** (lower number wins, so specific rules beat broad ones) and **Save**.

**How resolution works**

* Rules are checked in priority order; the **first match wins**, so put the most specific rules at a lower number.
* Scope a rule to specific **products**, **categories**, or **journeys**, or leave it to apply everywhere.
* Adjustments are applied at checkout, so the right customer always sees the right price — no manual price lists.

> **Tip:** Combine rule types freely — a volume discount for large teams, segment pricing for enterprise, and partner pricing for resellers all live in one resolution order. Priority decides which one applies when a customer qualifies for several.

**Learn more:** [Rules Overview](/product/rules-and-customizations/rules-overview.md) · [Targeting with Audiences](/product/rules-and-customizations/rules-overview/targeting-with-audiences.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 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.peakcommerce.com/product/rules-and-customizations/rules-overview/pricing-by-segment-and-partner.md?ask=<question>&goal=<endgoal>
```

`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.