Synchronizing inventory data from Global Inventory Visibility to Sterling Intelligent Promising Inventory Visibility (phase 1)

To integrate with IBM® Sterling™ Intelligent Promising Inventory Visibility, sync your demand and supply data to IBM Sterling Intelligent Promising Inventory Visibility.

The supply and demand data exists in both Sterling Order Management System and IBM Sterling Intelligent Promising Inventory Visibility, but Global Inventory Visibility continues to be the inventory management system for Sterling Order Management System.

For more information, see the Sterling Intelligent Promising Inventory Visibility IBM Documentation.

Benefits

Sterling Order Management System publishes inventory (push model) to external systems such as e-commerce or third-party marketplace so that the external systems can locally store the availability information. Whenever the availability information changes, Sterling Order Management System publishes the new picture, and the other systems need to update their local copy accordingly. The Push model is primarily used to cater the scalability requirements rising from the browse volumes such as fetching the availability information in the product list page, product details page, and so on.

The Sterling Order Management System stores inventory locally and makes it available to the selling channels when needed. This results in creation of a duplicate and outdated inventory picture that causes either overselling or under selling of products.

Sterling Intelligent Promising Inventory Visibility handles inventory lookup calls for all the browsing volumes from any channel, cart functions, and checkout volumes. Sterling Intelligent Promising Inventory Visibility is built on the distributed computing architecture that involves memory-grid, NoSQL, and CloudStack that cater to ultra high volume requirements.

The benefits of integrating Sterling Order Management System with Sterling Intelligent Promising Inventory Visibility are:
  • Eliminates multiple copies and caches of inventory.
  • Resilient® and Responsive to use in a pull model, where any on-premise or cloud service invokes a REST API for availability check, reservations, or inventory changes.
  • Deployed and load balanced across multiple data centers.
  • Assured SLAs and response times.
  • Call the appropriate APIs from the selling channels or source of inventory changes.
  • Real time update of supply from any source such as POS, SIM, vendor, and so on.
  • Eliminates the need to have hardware provisioned for a peak demand throughout the year.