Upcharges/Deals; Ability To Define Upcharge Defaults At Class And Subclass
(Doc ID 2802401.1)
Last updated on MAY 26, 2023
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version NA and laterInformation in this document applies to any platform.
Goal
Enhancement Request;
When there are product assortments which will have widely varying costs and volumetric factors across related subclasses.
Currently there is no ability to define upcharge defaults at class and subclass levels.
Having the ability to implement upcharge default at class or subclass would provide more accurate cost factors, while still avoiding the burden of item-level maintenance.
In addition, data entry errors have been seen where upcharges are inconsistent across sibling products (different flavors of a beverage for instance).
The ability to establish at subclass level would reduce the risk of these errors.
Another version of this enhancement might be to set up upcharges at item parent level.
This will allow for more accurate and consistent item-level upcharges,
without requiring individual item-level upcharge configuration.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |