For the complete documentation index, see llms.txt. This page is also available as Markdown.

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:

Get started

Tip: Rule order matters — within Business Rules the first matching rule wins, so set Priority deliberately when rules could overlap.

Last updated

Was this helpful?