The planned February Release will include the following:

• Important Updates
  • Volt is now Scintilla In-Store:
    As part of our broader product branding updates, Volt has been renamed to Scintilla In-Store.
    Product functionality, APIs, and data feeds remain unchanged. Documentation has been updated to reflect the new product name across references and descriptions.

The planned July Release includes the following:

New for NRT

• DSC Version 2 Now Available: We’re excited to announce the release of Direct Shipment Capture v2 API, featuring updates that align with current integration and authentication standards:
  • OAuth 2.0 Integration: Implements OAuth for credential management.
  • Standardized Field Naming: Field names have been standardized to support smoother implementation.
• To get started with DSC v2:
  • If you've already onboarded to DSV v1 or any of our other API offerings, please reach out to a Walmart Data Ventures Account Manager or Sales Engineer to request your client Secret so you can begin generating Bearer Tokens for DSC v2 API calls. Note: DSC API v1 will continue to be supported until further notice to ensure a smooth transition for all supplier partners.
  • If you're a new supplier looking to be onboarded to v2, please make sure your business partners have already connected with a Walmart Data Ventures Account Manager or Sales Engineer and have submitted an onboarding request form then visit our Get Started documentation to start setting up your access.

The planned January Release includes the following:

Released for NRT

• Documentation Updates
  • DC Inventory Endpoint Clarification: The DC Inventory Endpoint documentation has been updated for clarity, to include the wmtItemNbr parameter: /dc/inventory/status?itemIdentifier=wmtItemNbr

The planned October Release includes the following:

Released for NRT

• Documentation Updates
  • Transaction History Endpoint Update: New optional header locationArea has been added to Transaction History.
    • locationArea can be used as a filter to display the transaction history of items in specific parts of a store.
    • Accepted locationArea values (case sensitive): STORE, BACKROOM, MFC. If no value is passed for the parameter, it will default to STORE.
  • MFC Endpoint Changes: The Market Fulfillment Center (MFC) Endpoint has the following changes.
    • The endpoint path has been updated to /inventory/items-assortment
    • Request parameter store_nbr has been update to store_number
  • Direct Shipment Capture Endpoint Updates: The Direct Shipment Capture Endpoint has the following changes.
    • asn is longer mandatory: The asn parameter is no longer mandatory in the request.
    • Request destination changed to one: Only 1 destination will be accepted in the request. Requests that contain more than 1, or zero, destinations will result in an error.
    • ETA clarification: A clarification has been added to the documentation to note that ETA parameters should be in UTC format, e.g. 2024-10-17T16:30+0000Z, where "+0000Z" is not changed, i.e. do not provide the timezone offset.

The planned August Release includes the following:

• Released for NRT
  • Endpoint Updates
    • Association Endpoint Update: The Association Endpoint has the following changes.
      • The endpoint name has been updated to Associations (with an 's')
      • Response parameter walmartDataVenturesCompanyId has been update to wm_context_identifier
  • Documentation Updates: Please note the following changes in the documentation.
    • Parameter Definition Change: For clarity, the the definition for parameter wm_context_identifier has been updated to "A Walmart Supplier's unique identifier" throughout the documentation.
    • NRT Throttling Update: The note that there is a uniform rate limit of 600 transactions per minute (TPM) for all NRT API endpoints has been removed from the documentation. The documentation now notes that if the current rate limit is inhibiting your development with our APIs, please contact your Sales Engineering partner to discuss potential solutions.
    • Inventory Action Capture Endpoint Update: An eventCreationTime Bad Request error has been added to the IAC error codes page.

The planned July Release includes the following:

Released for NRT

• Documentation Updates
  • Transaction History Endpoint: Additional Event Type Codes have been added to the Transaction History documentation.
  • Inventory Action Capture Endpoint: A note has been added to clarify that request parameter eventCreationTime must be in milliseconds.

The planned April Release includes the following:

Released for NRT

• Endpoint Updates
  • Inventory Action Capture Endpoint Update: The ICA API will now accept partially correct messages and will respond with the incorrect parts of the request in a separate error.

The planned February Release includes the following:

Released for NRT

• Documentation Updates
  • Inventory Action Capture Endpoint: The eventType CORRECTION has been updated to reflect that only positive quantities are accepted. CORRECTION: Used when inventory needs to be reset to a value that is different from what is available in the Enterprise Inventory. It can also be used if the available quantity is not known. For correction, a positive quantity must be provided. Negative quantities will be rejected. Example: if the current inventory shows 25 but needs to be corrected to 20, the correction event should be sent as 20.

The planned January Release includes the following:

Released for NRT

• Documentation Updates
  • DC Inventory Endpoint: The DC Inventory Endpoint documentation has been updated for clarity, to include the wmtItemNbr parameter: /dc/inventory/status?itemIdentifier=wmtItemNbr

The planned December Release includes the following:

Released for NRT

• Endpoint Updates
  • Multi GTIN Inventory Endpoint Update: The Multi GTIN Inventory (MGI) Endpoint now accepts multiple item identifiers! This endpoint can return inventory information for up to 100 items. Please note:
    • the endpoint name has been updated to Multi Item Inventory
    • a new itemIdentifier parameter has been added, so users can pass either the item's GTIN (as parameter gtin) or Walmart Item Number (as parameter wmItemNbr) in the request. The response will return both the item's GTIN and Walmart Item Number, regardless of the parameter used in the request.
• Documentation Updates
  • Error Code and Sandbox Response: PTo help avoid confusion, the individual endpoint error code and sandbox pages have been consolidated to each endpoint reference page. Please refer to each endpoint reference page for applicable error codes and sandbox responses. For your convenience, a Common Error Codes page has also been added for quick reference to common error code reasons and their common resolutions.