Skip to Main Content
IBM Sterling

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 (

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Jul 28, 2020

Better integration between manageOrganizationHierarchy and Calendars

The API for managing organizations allows the caller to specify the receiving, shipping and business calendars, but only by specifying the calendar key.

The key is typically a system generated value which is unique to the environment and therefore not useful in an interface.

Please allow for the API to specify instead the calendar id for these three calendars.

Better yet, allow the API to specify the Calendar details directly by adding an optional Calendar node to the API.

What is your industry? Retail
How will this idea be used?

Legacy systems that feed OMS retail store location info typically also maintain store hours / calendar info. Consistency between these APIs greatly simplifies the integration points to maintain store hours and locations.

Consistency in the API (by allowing a foreign key to be specified by id, rather than by key) allows much easier integration to source or legacy systems. Keys cannot typically be used by interfaces as they can change between environments. Ids can be used as they can be specified externally when the calendar is created.