Anders Rylander

There is a need for smart rounding functionality when adjusting prices through 'Margin Component Price Adjustment' for at least 2 reasons:

• The "Get active price" data entity holds both ordinary prices and alternative prices, where 'alternative price' is populated by the result of the 'Margin Component Price Adjustment' functionality. If ordinary prices (i.e. trade agreements) are rounded off, alternative prices should also be rounded off.
• 'Margin Component Price Adjustment' can only be applied with 'Percentage' calculations. Calculating an adjusted price with a percentage will always create decimals. External sales prices with random decimals is not something retailers (or any business) can work with. Calculationg with 'Amount' is a work around on individual prices. But when calculating price adjustments on multiple (hundreds or thousands) of SKU's, this option is not feasible in the same way.

For retailers to work with 'Margin Component Price Adjustment' as a tool for campaigns, smart rounding is essential.