What is the difference between the legacy Price fields and these new Price attributes?
We have released a new feature in RetailOps Version 1.6.36, Price attributes. In previous versions, RO stored prices under three different fields: Offer Price, MSRP, and MAP. While these fields are useful, they are not flexible enough to support the wide range of use cases for which users would need different prices.
Converting these fields into attributes allows you to create as many different price attributes as needed. These can then be used on various sales channels by configuring them into the channels’ feeds. Storing prices as attributes also allows you to add dependencies and meta fields and to configure associations as needed (for more details on attributes, read this help article here).
However, the most useful aspect of Price attributes is support for tiered pricing.
What is tiered pricing?
Tiered pricing allows you to set different prices on an item depending on how many units are ordered. This is typically used to encourage customers to purchase larger quantities to take advantage of discounts.
For example, say you’re selling vitamin supplements. You can sell each bottle of vitamins for $9.99. However, you can offer a lower price of $7.99 per bottle if customers purchase 5 or more.
How does tiered pricing work?
Tiered pricing can be configured in the PIM. You must set at least two different prices and the quantity levels for which the prices apply.
Note that the quantity entered will be used as the minimum quantity needed to use the corresponding price tier. In the example below, $9.99 will be applied to orders for 1-4 units; $7.99 will be used for 5-9 units; $5.99 will be used for 10 or more units.
I’ve already created an attribute for pricing. How do I convert this into a Price attribute?
If you have previously created an attribute for pricing purposes and would like to convert it into a Price attribute, please contact RetailOps Support. We will modify the attribute on the back-end.