> 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.md). # Rules Overview PeakCommerce applies business logic automatically through its **Rules & Automation** engines — **Business Rules**, **Plan Dependencies**, **Pricing Rules**, **Territory Rules**, and the **Policy Engine**. Together they decide what's offered, enforce pricing and dependency limits, route ownership, and set the guardrails every channel operates within — so journeys, storefronts, CSR flows, and AI agents all behave consistently without custom code. The engines work as a stack: pricing and plan dependencies shape *what* a customer can buy, business rules adjust *how* a change behaves (such as when an upgrade takes effect), territory rules route ownership, and the Policy Engine sets the hard ceilings — for example a maximum discount — that no channel can exceed. Watch a pricing rule being built — a regional markup applied by a customer-attribute condition: {% embed url="" %} **Get started** * [Creating and Managing Rule Sets](/product/rules-and-customizations/rules-overview/creating-and-managing-rule-sets.md) — build and scope Business Rules, set change-plan timing, and apply policy locks. * [Protecting Margin with Policies](/product/rules-and-customizations/rules-overview/protecting-margin-with-policies.md) — set discount caps and downgrade protection in the Policy Engine, with block/warn/approval enforcement. * [Keeping Add-ons in Sync with Plan Dependencies](/product/rules-and-customizations/rules-overview/keeping-add-ons-in-sync.md) — link an add-on's quantity to your seats so it scales automatically and never under-bills. * [Targeting with Audiences](/product/rules-and-customizations/rules-overview/targeting-with-audiences.md) — define a reusable segment with the condition builder, then target offers, rules, and journeys with it. * [Reason-Based Retention Routing](/product/rules-and-customizations/rules-overview/reason-based-retention-routing.md) — send each cancellation reason to the step most likely to save that customer. * [Pricing by Segment and Partner](/product/rules-and-customizations/rules-overview/pricing-by-segment-and-partner.md) — charge by who's buying, resolved at checkout by priority. * [Governing the Change Lifecycle](/product/rules-and-customizations/rules-overview/governing-the-change-lifecycle.md) — control when and how each plan change takes effect, with per-direction timing and proration. * [Running a Promo That Converts](/product/rules-and-customizations/rules-overview/running-a-promo-that-converts.md) — build an offer that's targeted, capped, and resolved by priority, with a live preview of its billing impact. * [Rules & Automation](/product/using-peakcommerce/workflows-and-actions/workflows.md) — the full set of engines and how they fit together. > **Tip:** Rule order matters — within Business Rules the first matching rule wins, so set **Priority** deliberately when rules could overlap. --- # 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.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.