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).
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
prioritize items with same GTIN during fulfillment
We have an requirement from client on GTIN concept.
A watch can be from different factories, like The China factory SKU would be AU1234, whereas the India factory SKU would be AU1234I or AU1234IE. And below are the requirements Consolidated ...
Different safety factor % of onhand buffer to be set for each Node Type
Bussiness needs to mask an article with item node combination as there might be different scenario's where the store decides not to sell an item even if there is an inventory in the store. So we are looking if there is any other configuration whic...
DeliveryLeadTimeUE should include order and order line reference in the input
Our current client implementation relies on product delivery on a specific date such as birthday. The product can only be delivered on that specific day, not a day before and not a day after. In order to achieve that OMS is relying on an external ...
Application should allow log tracing at app server level
In Production, there are cases where Support engineers need to debug an issue enabling verbose trace for an application server. However , the logging on a specific application server is not supported by IBM Sterling product.
Provide for consideration of in-store take-sales (non-order) / cash-and-carry when calculating node sell-thru - without impacting transaction quota
Today, Sterling provides for calculation of store node sell-through velocity based on the order fulfillment that OMS has visibility to by virtue of orchestrating orders. However, in practice, a given store node derives a large portion of its sell-...
Ability to convert JSON payload to XML sent to asynchronous defined in OMS
OMS currently supports conversion of JSON payloads to XML if passed to REST endpoints defined from OMS. However, if there are asynchronous services defined in OMS using JMS/ MQ, it mandates that the inputs passed is always XML for consumption by O...
When any alert is raised for Agent Exception for an order , all the alerts are consolidated under AGENTEXCEPTION exception type and not per order number. if alerts are available for each order number , it will be easier for IT support team to look...
To introduce OOTB flag for backordering of remaining qty on change release
Currently in Sterling Order Management V9.5 On TO release, a shipment request is sent to WH. Two flags "ShipShipment" and "ShortShipment" will be sent in ShipConfirm message by WH. If ShipShipment is Y, OMS can expect more shipments and if ShortSh...
To enhance the WebStore application to support the pagination strategy -"GENERIC"
PaginationStrategies are set to perform ServerSidePagination or MixedPagination. It helps to fetch the records in batches. Store supports NEXTPAGE Strategy. But not all the OOTB List APIs support NEXTPAGE Strategy. By default, only 'Generic' strat...
Returns processing on over shipped catch weight quantities
When a refund is initiated on an overage product (Meat/Deli), IBM matches Refund quantity with ORDERED qty, NOT with SHIPPED quantity. This causes discrepancy during settlement, and needs to be manually adjusted.
Do not place IBM confidential, company confidential, or personal information into any field.