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
Business Rules
Govern how a subscription change behaves — when it takes effect, how it prorates, whether it co-terms to the base subscription, and whether it is blocked outright.
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.
The engines in the app
Each engine has its own workspace under Rules & Automation, with summary counts, search, and a "Create with Mango" shortcut.


Watch a territory rule being built — routing accounts to a service profile by a region condition and priority:

How it fits together
Rules evaluate as customers move through journeys: 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.
Last updated
Was this helpful?
