IBM Sterling Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Provide for native (non-UE) configurability to record discounts/promotions at unit level, to align with most omni-retailers best practices in refunding multi-unit orders

First, please see:

https://www.ibm.com/support/pages/node/269415


In IBMs response, the Sterling team states that it is "as designed" that a customer would receive an entire unit's refund upon the return of the first item of a multi-line order, with no regard for the discount applied at the line! Only upon return of the *last item* is the reduction in refund resulting from the line-level discount applied! They state that the only way around this is to light up UserExits with custom code to manipulate either the order capture or refund outcomes.


Proration of line-level discounts to units upon *order capture* should be a turn-key Sterling function.


Proration of line-level discounts to units upon *refund calculation* should be a turn-key Sterling function.


Vast majority of retailers will expect that best-practice in partial refunding of multi-unit lines is to *by default* pro-rate a line-level discount to the units within that line, such that the *decrease* in refund to the customer resulting from a line-level discount is proportional to the number of units in a given return order. Barring this, retailers are subject to gaming of returns by customers and repeat return abusers. This is especially detrimental for high-ticket item retailers.



  • Guest
  • Jun 29 2022
  • Under review
What is your industry? Retail
How will this idea be used?

We have a recurring bug raised every release for years whereby refund amounts are not as expected, given Sterling's inability to pro-rate line-level charges to units like other Storefronts.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.