Skip to main content

Eventual Consistency

Some APIs across Commerce are eventually consistent. This means that after a write request (e.g., create, update or delete), there may be a brief delay before the latest value is reflected in all reads across the platform. Once no further updates occur, all endpoints will eventually return the latest value.

Catalog Publication

Allow time for updates to propagate after adding or updating products before publishing a catalog. Changes are typically reflected almost immediately but can take up to 1 minute during high-traffic periods.

Pagination and Filtering

During high-traffic periods, updates to resources may take a few seconds to be visible in requests that involve Filtering or Pagination specifically when the page[offset] parameter is used.

Other Cases of Eventual Consistency

Eventual consistency may also be observed in the following cases:

  1. Updates to a user's personal data may take a few moments to appear in the Personal Data API
  2. Changes in the User Authentication Info API may take time to be reflected in the Account Member API.