Pricing
Managing product pricing can be complex, especially when context is involved.
For example, different customers or customer groups might have different prices, discounts or even surcharges on the products they buy, depending on the channel and other parametrization which might be involved.
Amarant offers different ways on how a merchant can affect product pricing.
Pricing rules
These rules support two subject types and two target types.
Subject types:
- product
- cart
Target types:
- base
- sale
Info
When referring to base price and sale price, a base price is the regular product price while the sale price might be a discounted price, or "special" price. At the end, product is always sold under the sale price, which has the same value as the base price, unless calculated to a different amount.
Product subject
When using the "product" subject type and depending on the target type, a particular product's base price or sale price can be affected.
The resulting prices of pricing rules become the affected product's prices and are visible in the frontend store, wherever the product is shown.
Cart subject
This works similarly as the "product" type, but it's contextual, it depends on the products in the customer's cart.
It can affect a particular product's base price or sale price in a cart item. The starting point amount for calculation of these prices are based on the already established base price and sale price of a product.
This means other pricing rules of type "product" could have already affected the base price and sale price. That's why priority is important. Each pricing rule has a priority value and rules are applied in descending order.
A rule may be configured to stop processing further rules if that particular rule was applied.
Additionally, actions are able to modify the starting point amount for base price and sale price, but that depends on their implementation.
Create a rule
Active
If a rule is not set to active, it will be skipped while rules are processed.
Featured
Determines if a rule should be shown in the frontend store, for example letting customers know that there's a discount available.
Description
This description is meant to be shown when the rule is set as "Featured".
Channels
The channels in which the rule should be processed.
Validity period
Set the datetime range when the rule should be considered applicable. If not applicable, it will be skipped while rules are processed.
Important
When using the "product" subject type, the changes in the frontend store may not be instantly visible at the moment the rule starts / stops being valid. This is because the frontend store data storage is read-only and may need time to refresh.
The rule itself will be correctly applied or discarded at any point in time, though.
Priority
As mentioned before, rules are processed in descending order by priority. This means the one with the higher priority runs first.
Conditions
Conditions are used to match items. Depending on the subject type, the matching items would be products in the catalog or in the cart.
First, add a condition group and select what the result of the group should be: any, all or none.
Next, add the conditions along with their operators and values. Some conditions allow more than one operator to be used and offer more than one value to be selected or require user input to be entered as a value.
Note
Depending on the subject type, different conditions might be available for selection.
Important
Conditions within a group are queried as "AND", meaning all conditions within a group must match.
On the other hand, groups are queried as "OR", meaning any group can match.
Contextual conditions
These conditions match a customer, customer group or customer organization.
Experimental
This feature is not documented yet.
Actions
Actions are executed if the rule's conditions have matched.
There can be multiple actions, and they are executed in the order they were added in.
Actions can modify the starting point amount for base and sale price or add positive or negative amounts which get added to the resulting price.
They might even set shipping discount to enable free delivery.
Click on "Save rule" to complete the process.
Tier rules
Tier rules are one of the "price modifiers".
They allow a discount or surcharge in percentage or fixed amount to be applied on a product's base or sale price considering the purchased quantity.
Tier rules are assigned to individual products using the "Tier Rule ID" product attribute.
Add items and assign type, quantity and amount to each one.
Note
Price modifiers are executed last, after customer pricing / organizational pricing and pricing rules.
Click on "Save rule" to complete the process.
Customer and organizational pricing
Experimental
This feature is not documented yet.