¶ Price list rules - prices by customer, group and view
Price list rules in Hummerce set the "customer price" - the starting point for further promotions - depending on the store view, the customer, their group or company, and item criteria. Thanks to them, a single product catalog can show different prices to different customers and groups, without creating separate items.
As of Hummerce 2.22-2.35, updated 2026-09-29.
¶ Benefits and use cases
- A price that depends on the store view - e.g. a different price in the wholesale view than in the retail one, on one product catalog.
- A discount calculated automatically from a property assigned to the item, category, producer, item group, the logged-in customer, their customer group or their company - without creating separate price lists for every combination.
- One rule handles many customers and items at once thanks to criteria (e.g. "all customers in the VIP group", "all items from producer X").
- Copying an existing rule with one button when setting up a similar rule for another group or customer.
- The result is visible to the AI assistant - MCP tools show which rule and which calculator set a given customer's price.
- A price list rule sets the customer price (customerPrice) - the starting price for product and cart promotions.
- Rules are checked in the order of the list in the panel (the order can be changed); only active rules are taken into account.
- A rule consists of: a general criterion (e.g. the store view), a customer criterion (logged-in or guest, with the option to narrow it down to e.g. a customer group), an item criterion (e.g. producer, category, item group, a specific item), and a price calculator.
- If the rule's criteria are met, the store applies the price from its calculator. If a rule doesn't return a price, the next rule on the list is checked.
- Base price (taken from the item) - the behavior from before price list rules were introduced, the price straight from the item.
- Price from selected price list - the price from a named price list, including customer and company price lists.
- Price from selected property - the price taken from any item property (e.g. a separately entered wholesale price).
- Fixed price - a fixed price entered directly in the rule.
- Discount - the item's base price reduced by a discount entered in the rule.
- Discount from selected property - a discount whose size comes from a property assigned to: the item, the article (variant), the item's main category, the producer, the item group, the logged-in customer, their customer group or their company. This means, for example, that a whole customer group's discount is a single number in the group's property, not a separate rule for every group. Full description of the use case: Customer and group discounts.
¶ Rule order and iterative pricing
- Rules that return a specific, independent price (base price, price list price, fixed price, price from a property) can be set in any order.
- Discount rules (Discount, Discount from property) calculate the discount from the price set earlier - so a rule with a discount shouldn't be first on the list, and the first price list rule should be one that returns a specific price.
- To have the discount added to the price from the previous rule, instead of stopping the calculation at the first match, you need to enable the Continue iteratively counting prices in price list rules setting (off by default).
- The rule parameter Use the next rules if the calculated price is null lets the store move on to product promotion rules when no price list rule matches a price.
- Since version 2.32, any rule (price list, product promotion and cart promotion) can be copied with one button. The copy lands below the last active rule on the list, inactive, with a symbol built from the source rule - useful when setting up a similar rule for another group or customer.
- Every additional active rule adds to the store's load - a large number of rules may require more computing power.
- Rules and calculated prices that match the criteria are stored in a cache - see Cache.
- Since version 2.22 - price list rules.
- Since version 2.30 - discount-from-property calculators (item, article, category, producer, item group, logged-in customer, their customer group) and the Continue iteratively counting prices in price list rules setting.
- Since version 2.32 - copying a rule with one button.
- The discount-from-property calculator for a company (the logged-in customer's company) - available together with the Company accounts module.
- Price lists and individual prices - required for the "Price from selected price list" calculator.
- Customer groups, item groups, categories and producers - if they're meant to be a rule criterion or the source of a discount property.
- Company accounts - for the company property discount calculator.
- Views - for rules that depend on the store view.
- The result of the rules feeds into product and cart promotions.
- Price list rules aren't part of the standard store configuration - they're enabled as part of implementation. Scope:
- checking the standard rules (base price, general item price list, customer prices) and their order,
- setting up rules for chosen groups, customers, companies or views and the properties that are the source of a discount,
- enabling iterative pricing, if the discount needs to be added to a price list price,
- clearing the price cache, testing on the test environment and the production rollout.
- Minimum estimated time: a new rule with a ready-made calculator, with no template changes - from 2 h.
- What the time depends on: the number of rules and the complexity of the criteria, the number of groups/customers/companies with a separate discount, whether the discount needs to combine with a price list price (iterative pricing), integration with an ERP that sends prices (quoted separately), the store's version - an older one needs an update first (quoted separately).
- A discount and a price list price combine only with the correct rule order and iterative pricing enabled - the wrong configuration gives unpredictable prices.
- Returned prices can duplicate if a product promotion uses the same discount source as a price list rule.
- A rule with no calculator selected doesn't calculate anything - in the standard panel and through the AI assistant, a calculator is required when creating a rule.
- A large number of active rules increases the store's load.
- No operations on price list rules in the REST API - configuration only in the panel or through the AI assistant (requires admin permissions).
- We do not verify the configuration for legal compliance - how prices are set for individual customers and markets is decided by the store.
- Price list rule operations in the REST API.
- A panel view showing which rule and which calculator currently set the price of a given item for a chosen customer.
- More ready-made rule templates to choose from when setting up a new rule.
Can different customer groups have a different percentage discount?
Yes. The "Discount from selected customer group property" calculator applies a discount based on the value saved in that group's property.
Can the price depend on the store view?
Yes, a rule's criterion can restrict it to chosen views - e.g. a different price in the wholesale view.
Can a discount and a price list price combine in one rule?
Yes, provided the rule with the discount isn't first on the list and the Continue iteratively counting prices in price list rules setting is enabled.
Can an existing rule be copied instead of building a new one from scratch?
Yes, since version 2.32 any rule can be copied with one button.
Will the AI assistant create a new price list rule?
Yes, but it requires a calculator - a rule without one is saved as inactive.
How long does setting up a price list rule take?
A new rule with a ready-made calculator - from 2 h. The time grows with the number of rules and the complexity of the criteria.
Want to see how price list rules could work in your store? Contact the Hummerce team (in Polish).
- Rule list: Assortment -> Price list rules - the Symbol and Item criteria columns, activation, edit, delete and history operations, Set order, copying a rule (since 2.32).
- A rule: Symbol, Price policy (calculator), Active, For all views or a list of Views, For logged-in customers / For guest customers, Criteria for logged-in customers, Item criteria, Order, Use the next rules if the calculated price is null.
- Global setting: Configuration -> Settings - Continue iteratively counting prices in price list rules (off by default).
- Groups and criteria: Customer groups, Item groups, categories, producers - usable as a rule criterion or a carrier of a discount property.
- Clearing the rule and price cache: Cache.
¶ REST API and MCP
- REST API: no operations on price list rules - configuration only in the panel or through MCP.
- MCP (AI assistant - MCP server):
ec2_price_calculators_list - calculators available for price list rules (rule_type=customer_price) and their parameters,ec2_price_rules_list, ec2_price_rule_details - the list of rules and the full details of one, with unset parameters,ec2_price_rule_create, ec2_price_rule_update - creating and changing a rule (a calculator is required when creating one),ec2_price_rule_set_parameter, ec2_price_rule_delete_parameter - setting or clearing a calculator parameter,ec2_price_rule_reorder - setting the order of all price list rules at once (a partial list is rejected),ec2_price_for_customer, ec2_diagnose_price - the price calculated for a customer and the rule responsible for it (see Price lists and individual prices).- Reading and writing price list rules requires admin permissions.