Updated: February 3, 2022 7:36am

Accumulated Discounts

The Accumulated Discounts feature enables retailers to layer multiple discounts at either the item level or transaction level. This is different than the default behavior in which entering a new discount overwrites any existing discount. When the "Accumulate Manual Discounts" preference is selected (Node Preferences > Transactions > Discounts), a new discount entered by the Associate is applied to the already discounted price. For example, say a $10 item has a 10% discount, taking the Price to $9. An associate then applies another 10% discount. If the "Accumulate Manual Discounts" preference is selected, this takes the item Price from $9 down to $8.10. If the preference is not selected (default behavior), the second 10% discount simply replaces the first 10% discount and the item Price remains $9.
You can see the details of all discounts applied to an item via the Show Discounts button in Item Details > Discounts or Transaction Details > Discounts. In the example below, a series of 1.00 discounts was applied to an item, with each discount accumulated on top of the other.
Item discount details

Accumulate Spread Discounts
Transaction level discounts can be spread. Spreading a transaction discount distributes the discount amount among the items on the transaction. If the "Accumulate Spread Discounts" preference is selected, then additional discounts can be applied on top of a spread discount amount. For example, a transaction has two $10 items for a subtotal of $20. An associate applies a 20 percent transaction discount (2.00 discount amount) and then spreads the discount. Each item's price is reduced to $9. If the "Accumulate Spread Discounts" preference is selected, an Associate can enter a new transaction discount, spread that discount, and the spread discount will be applied to the already discounted Price.

Multiple Discounts and Reasons (Accumulated Discounts)
Users assign a Discount Reason to each individual discount. The same reason can be used for multiple reasons.
When multiple discounts are applied, when viewing the consolidated discount info for the transaction, "Multi" will be displayed as the Discount Reason.
multi discount reason

Node Preferences > Transaction - Discounts
This area has preferences related discount rounding, accumulated discounts, and other discounting options.

Preference Description
Accumulate Manual Discounts When enabled, manual discounts are accumulated. When disabled, entering a manual discount replaces the existing manual discount. Note: Price Level and Customer discounts always accumulate, regardless of this preference.
Accumulate spread discounts When enabled, spread discounts are accumulated. When disabled, spreading a discount more than once replaces the existing spread discount.
This preference will replace existing spread discount. For example, if you have already spread one discount and then want to spread a discount again, if the preference is disabled it will replace the previous spread discount. If the preference is enabled, Prism will accumulate it. This preference has no effect on line item discounts


Accumulated Discounts and Comparison Pricing are mutually exclusive features
When the "Use Accumulated Discounts" preference is set (Node Preferences > Transactions > Discounts), the discount(s) are applied to the Active Price Level in Inventory. The Accumulated Discounting feature enables multiple discounts to be layered on each other. For example, a 10 percent discount followed by a five percent discount. When the Use Accumulated Discount preference is selected, the discounts are always applied the Active Price Level (regardless of what price level may be selected in the "Bring Original Price from Price Level" preference).
Comparison Pricing uses the "Bring original Price from Price Level" preference (Node Preferences > Transactions > General). This preference sets the price level to use as the "original price" when making comparisons between the base price and comparison price. When this preference is selected, if there is a difference between the price on the document for the item and the price for the price level selected in preferences, the difference is displayed as the discount amount and discount percent for the item. Comparison Pricing is set at the Store level. At the Corporate or Subsidiary level, the "Bring Original Price from Price Level" preference is set to "Active Price Level" and cannot be changed. If using Comparison Pricing, other settings, like Use Accumulated Discounting are ignored. Similarly, if you have enabled a preference like "Use accumulated discounting," then the "Bring Original Price from Price Level" setting is ignored.

Populate Max Discount From preference
When a user lists an item on a transaction and tries to apply a discount to that item, Prism checks to make sure the value does not exceed the Maximum Discount Percentage entered in the item's Inventory record.
Sample Prism Inventory record showing Max Discount % set to 100 percent:
Prism Inventory record showing Max Discount Percentage 
Users need to be aware that RIL (or Retail Pro 9) has TWO max discount fields: Max Discount % and Max Accumulated Discount %.
Sample legacy Retail Pro Inventory record showing Max Discount % and Max Accumulated Discount % fields:
RIL Inventory record showing Max Discount percentage 
For backward compatibility, there is a "Populate Max Discount From" preference in Admin Console > Node Preferences - Merchandise - Inventory - General. The preference has two possible values:

  • RIL Max Discount %: Each item's RIL Max Discount % field value will be copied to the Prism Max Discount % field.
  • RIL Max Accumulated Discount: Each item's RIL Max Accumulated Discount % field value will be copied to the Prism Max Discount % field.

Sample Admin Console - Node Preferences - Merchandise - Inventory - General: Populate Max Discount From:
Populate Max Discount From preference

 

In Prism 2.0 and later, there is no dependency to RIL (or Retail Pro 9). For previous Retail Pro 9 users that need the preference, configure the preference in 1.14.7 or earlier to the desired setting. For new Prism users, changing this setting from the default risks losing what they have set up, causing a lot of rework if the user doesn't realize the field used to populate Max Discount Percentage was switched and then the user adds new  inventory.