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 (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 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 (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.

Status Submitted
Created by Guest
Created on Mar 27, 2026

Enable OMS to Support Multiple SIP Endpoints for Multi‑Organization / Multi‑Market Deployments

IBM Sterling OMS natively supports multiple organizations, enterprises, and markets within a single OMS instance. This is a core capability that allows businesses to run multiple brands or geographies from a unified OMS platform.

However, OMS currently supports configuring only one global SIP endpoint, which creates a significant limitation:

  • Organizations that require multiple SIP environments (e.g., one per brand, per geography, or per inventory organization) cannot route traffic differently for each organization.

  • This restriction forces all OMS organizations—regardless of business differences—into one shared SIP instance or have separate OMS instances.

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

We propose enabling OMS to:

  1. Configure multiple SIP endpoints, each mapped to specific OMS organizations, enterprises, or geographies

  2. Allow routing of inventory‑related APIs from OMS to SIP based on:

    • Organization / Enterprise

    • Catalog / Node

    • Market / Region

  3. Provide tenant‑specific configuration for SIP integration within OMS, without requiring one global endpoint

  4. Maintain backward compatibility for customers who prefer a single global SIP endpoint

This would restore the full value of OMS’s multi‑organization architecture and align integration flexibility with real‑world enterprise structures.