Events

You can subscribe to events and view the events that are published to IBM® Cloud Object Storage (COS) endpoints or webhook endpoints. These endpoints are flexible, cost-effective, and scalable for your unstructured data.

Important: IBM Sterling Inventory Visibility is not meant for running push mechanisms in real time. It can be used for occasional pushes to marketplaces that do not call Sterling Inventory Visibility APIs directly. It can also be used for accounting and auditing purposes.

Event characteristics

Characteristics IBM Cloud Object Storage Webhook
Description Events are pushed to COS and clients need to download from COS to process the data. Events are pushed to a client's REST webhook.
Hosting Hosted on the cloud. Hosted by client.
Configuration Configure an account on the COS cloud service. Configure a webhook to support oauth2 authentication.
Scalability Ability to scale up with different tiers. Webhook needs to scale up as needed.
Potential issues Need to implement a PULL process to get failed events. Need to implement a PULL process to get failed events.
Data loss Data loss if PULL process is not implemented. Data loss if PULL process is not implemented.
The following table lists a rough estimate of the number of events raised for the transactions requested. The actual number of events is influenced by other factors such as the number of concurrent transactions for similar items.
Table 1. Estimation of events expected to be published.
Transaction Notes Minimum events raised Maximum events raised Additional information
Create reservation Open order reservation in Sterling Inventory Visibility. 2 (PICK-1 & SHIP-1) 2 (PICK-1 & SHIP-1)  
Create order and reservationId Reservation is consumed rsvr_demand is created in Sterling Inventory Visibility. 2 (PICK-1 & SHIP-1) 2 (PICK-1 & SHIP-1)  
Schedule order rsvr_demand is converted to scheduled demand. 0 4 (PICK-2 & SHIP-2) Depending on work load pattern at that point in time, changes can either get aggregated or not get aggregated.
Release order Temporary reservation created (of type for_demand). Scheduled demand is converted to allocated demand. 0 4 (PICK-2 & SHIP-2) Depending on work load pattern at that point in time, changes can either get aggregated or not get aggregated.
Confirm shipment Supply is reduced. Demand is reduced. 0 4 (PICK-2 & SHIP-2) Depending on work load pattern at that point in time, changes can either get aggregated or not get aggregated.
  • All item-related changes lead to computing availability and trigger an event message. Examples of item-related changes are configuration changes (such as updates to safety stock, fulfillment options, changes in parent-child relationship), transaction-related changes, or bulk actions like DG sync.
  • For Sync Supply and Sync Demand PUT API requests, Sterling Inventory Visibility relies on the most recent sourceTs value for the record to know whether data is up to date and an event needs to be triggered. If sourceTs is not specified, then the timestamp of the API call is used. If an API request includes a sourceTs that is earlier than the last time that the sync occurred, then the sync is ignored and an event is not triggered.
  • Event messages are sent at least one time from Sterling Inventory Visibility to the customer endpoint. In some cases, messages are sent more than one time. Therefore, you might notice duplicate event messages from time to time for various reasons. When processing data, ensure that you remove all duplicate event messages.