This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
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.
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.
Hi Paul, thank you for submitting your idea. This would require changes to the backend pricing engine and rule configuration. We will consider it for a future update to the product.