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 Future consideration
Created by Guest
Created on May 17, 2026

Add delta/incremental snapshot support to productAvailabilitySnapshot.v2 — return only SKUs changed since a specified time

Currently, the productAvailabilitySnapshot.v2 event publishes a full snapshot
of all SKUs every time it runs, regardless of whether those SKUs have had any
changes since the last snapshot. This means consumers must download, parse,
and process the entire dataset on every run — even when only a small subset
of SKUs have actually changed.

Requested change: introduce an optional delta/incremental snapshot mode that
accepts a "since" timestamp parameter and returns only the SKUs whose
availability data has changed since that point in time.

Example request behavior:

  • Full snapshot (current behavior): no timestamp provided → all SKUs returned

  • Delta snapshot (requested): since=<ISO timestamp> → only changed SKUs returned

This would allow consumers to:

  1. Process a dramatically smaller set of files and records on routine runs.

  2. Reduce COS storage read costs by skipping unchanged SKU records.

  3. Complete downstream processing faster, improving overall pipeline performance.

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

Our team triggers productAvailabilitySnapshot.v2 regularly to keep our
downstream inventory availability data in sync. The majority of SKUs do
not change between runs, but we are forced to process all of them every
time to find the ones that did.

This would reduce the number of COS files we need to read, the volume of
records we need to parse, and the total time our pipeline takes to complete
a sync cycle — directly addressing the performance concerns raised on our
support call.

  • Admin
    Sampson Wong
    May 27, 2026

    Thanks for the recommendation. We have accepted this as an enhancement request. The roadmap and timeline will be shared once it has been finalized.