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.

The engines in the app

Each engine has its own workspace under Rules & Automation, with summary counts, search, and a "Create with Mango" shortcut.

Pricing Rules — discounts, tiers, and overrides resolved by priority across plans, segments, and journeys.

Territory Rules — route accounts to the right profile by condition and locale; the highest-priority match wins.

Plan Dependencies — keep linked quantities in sync so targets follow a source charge automatically.

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.