Sales set-up · step 3 of 3
Pricing Rule
A pricing rule is a named set of conditions on item, party, territory, quantity or date that changes the price or discount of every sale or purchase line that meets the conditions.
Why it exists: Because the price on each line should come from a stated rule that anyone can read, not from whoever typed the discount last.
Where it sits
Pricing RuleThis document
Sales set-up: Territory → Sales Partner (ERPNext DocType) → Pricing Rule
How a pricing rule moves through its life
Four states. Pick one to see what a pricing rule is, and what it can still become.
Valid-from date is in the future. The rule does not match yet.
Then: Active
Valid-from date is in the future. The rule does not match yet.
Then: Active
Not disabled, and the transaction date falls between the valid-from and valid-upto dates.
Then: Expired
Not disabled, and the transaction date falls between the valid-from and valid-upto dates.
Then: Expired
The valid-upto date has passed. The rule no longer matches.
Then: Disabled
The valid-upto date has passed. The rule no longer matches.
Then: Disabled
The disable box is ticked. The rule never matches, whatever its dates.
Ends here
The disable box is ticked. The rule never matches, whatever its dates.
Ends here
Rules that must hold, and what breaks them
Rules
- When more than one rule matches and they do not stack, the highest priority number wins. If the top priority is still shared, ERPNext stops with a conflict error.
- A price rule sets a rate or a discount. It cannot be saved with neither.
- A rule's minimum quantity cannot exceed its maximum quantity, and its minimum amount cannot exceed its maximum amount.
Does this happen in your business?
Tick what you recognise. Each tick shows what it costs.
Tick any that happen here.
In ERPNext, and in your system
How ERPNext models it
| DocType | What it does here |
|---|---|
| Pricing Rule | priority (1 to 20; a higher number wins) and has_priority (for zero). apply_multiple_pricing_rules lets rules stack. |
| Pricing Rule | applicable_for: Customer, Customer Group, Territory, Sales Partner, Campaign, Supplier or Supplier Group. |
| Pricing Rule Item Code | Child table for Item Code. Item Group and Brand have their own child tables. |
| Pricing Rule | rate_or_discount: Rate, Discount Percentage or Discount Amount. Required for a price rule. |
What other systems call it
| System | Name | Note |
|---|---|---|
| ERPNext | Pricing Rule | DocType Pricing Rule. Docs updated 2026-07-24; source pricing_rule.json and utils.py at v16.50.0. |
| Tally | Price List | Tally's own site (published 2019-11-11, updated 2025-08-28). Price lists per stock item or group, with rates for distributors, dealers and retailers. A price level attaches a tier to a party. The page does not say how overlapping prices combine. |
| Zoho Books | Price List | Zoho Books help (undated). Attached to a contact and applied to new transactions automatically; a line-item list can be chosen too. The page does not describe how two lists combine. |
| SAP Business One | Price List | SAP Learning: price lists, period and volume discounts, discount groups, special prices for Business Partners and blanket agreements. Which one wins is from a third-party summary, not confirmed by SAP. |
| Odoo | Pricelist | Rules apply to a product, a category or all products. A product's own rule overrides its category's (Odoo 18.0 docs). The docs do not give the tie-break for equal rules. |
From each maker's own documentation, checked 13 October 2026. A dash: not confirmed.
Where a pricing rule connects
More terms it connects to
Each one opens that term.
Questions about pricing rules
The one most people ask is answered first. Type to find the rest.
What does a pricing rule mean for the business?
- A rule with a condition expression that errors is skipped silently when a document is priced. A broken condition therefore looks like a rule that never matches.
- When more than one rule remains, rules in the document's currency are kept first.
- Between two percentage discounts with the same priority, the rule for the price list in use is preferred.
- A rule with a threshold returns a suggestion to order more, rather than a price. A coupon-based rule checks the coupon's validity and use count first.
- A rule with no end date keeps matching until someone disables it. The default valid-upto is far in the future.
Reviewed 14 October 2026. All 40 documents: the ERP glossary.