> 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/using-peakcommerce/workflows-and-actions/workflows.md).

# Rules & Automation

PeakCommerce's **Rules & Automation** engines apply business logic automatically across commerce — so journeys, pricing, and access behave consistently without custom code. You manage them under **Rules & Automation** in the admin navigation.

## The engines

| Engine                | What it does                                                                                                                           |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Business Rules**    | Trigger actions and enforce conditions in commerce flows — for example requiring or hiding steps, or reacting to a customer's choices. |
| **Plan Dependencies** | Define how plans and add-ons relate — what can be bought together, what requires what, and what conflicts.                             |
| **Pricing Rules**     | Apply pricing logic such as discounts, tiers, and promotions within guardrails.                                                        |
| **Territory Rules**   | Route customers and assign ownership by region or segment.                                                                             |
| **Policy Engine**     | Enforce guardrails — the hard limits (for example a maximum discount) that no channel, including AI agents, can exceed.                |

## How it fits together

Rules evaluate as customers move through [journeys](https://gitlab.com/peak-hercules/peak-help-docs/-/blob/main/product/using-peakcommerce/journeys-and-pages/journey-basics/journeys-overview.md): pricing and plan dependencies shape what's offered, business rules adjust the flow, territory rules route ownership, and the policy engine sets the ceilings everything else operates within. Because the policy engine binds these limits centrally, the same guardrails apply whether a person, a CSR, a partner, or an AI agent is transacting.

> For multi-system automation (for example post-cancellation billing tasks), PeakCommerce generally recommends building workflows in your system of record — Zuora or Salesforce — when it has a workflow module, for the most flexibility and extensibility.


---

# 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/using-peakcommerce/workflows-and-actions/workflows.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.