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 Jul 23, 2026

Support custom destination zones (geography groups) as a condition in SIP sourcing rules

IBM Sterling Intelligent Promising (SIP) sourcing rules currently allow conditions to be defined on standard destination attributes such as country, state, city, and postal code, along with other order attributes. However, there is no way to define a custom zone — a named grouping of geographic areas (e.g., a set of postal code ranges, ZIP prefixes, or states) — and use that zone as a condition (LHS) in a sourcing rule.

We request that SIP support the ability to:

  1. Define reusable custom zones as named entities, where a zone is a collection of geographies (postal code ranges, ZIP3 prefixes, states, or a combination).

  2. Reference these custom zones directly as a condition in sourcing rules (e.g., "IF destination is in Zone_Southeast THEN source from Node Group X").

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

In order to support business requirements, we need to model sourcing rules based on custom attributes