We are aware that Order forecast for WM Weeks 40-52 for FYE 27 and WM Weeks FYE 28 is incomplete or missing. Our Data teams are working to resolve on priority and we will share more information shortly..
Due to an ongoing issue, the availability of data assets is currently delayed. Our team is actively working to resolve the issue and restore access as quickly as possible. We appreciate your patience and understanding.
On September 18, users may experience delays in receiving Store Inventory (catman) data, potentially resulting in an SLA miss. We are aware of the delay and our team is working to resolve it. We apologize for the inconvenience.
Hierarchy changes are now reflected across the Data Access and Collaboration portfolio. If you have any pre-built reports utilizing hierarchy filters, you may need to clear these filters and recreate them with the new hierarchies.
Please submit requests via a support ticket to get historical UPC Sales to reflect hierarchy changes in Shopper Behavior. You can submit a ticket for these August changes beginning on Monday, August 24.
Hierarchy changes are now reflected across the Data Access and Collaboration portfolio. If you have any pre-built reports utilizing hierarchy filters, you may need to clear these filters and recreate them with the new hierarchies.
Please submit requests via a support ticket to get historical UPC Sales to reflect hierarchy changes in Shopper Behavior. You can submit a ticket for these August changes beginning on Monday, August 24.
Hierarchy changes are now reflected across the Data Access and Collaboration portfolio.
Please submit requests via a support ticket to get the updated item hierarchy. You can submit a ticket for these August changes on or after Tuesday, August 11.
We will restate corrected Markup Markdown Board data this weekend. The restated records will flow through incremental updates to both Data Feeds and Cloud Feeds, which may update values previously received. Please ensure downstream processes are prepared to consume these incrementals. We will update this notice when the restatement is complete.
We are aware of a data issue with RFID Tag Part table. We are working to fix the issue.
Service Advisory: Cloud Feeds, Data feeds Pipeline Delay We are currently experiencing an infrastructure issue impacting Cloud Feeds and Data feeds data pipelines due to a constraint within our platform. As a result, there may be delays in data availability and refreshes. We are actively engaging and working toward resolution. We will provide updates as additional information becomes available.
We have become aware that there is missing store sales data for May 26, 2026. This missing data is impacting Scintilla suppliers and the category advisor persona who rely on headless access (Cloud Feeds, Data Feeds API and Scintilla Media Data Feed). Our team investigated the issue and resolved it as of 11:30 am CT this morning. Report Builder is unaffected and has all sales data for May 26, 2026. Please see the next steps below on how to restore missing sales data. Data Feeds API: The historical file for the affected May 26 store sales data will be made available, and suppliers will need to manually consume it to recover the missing records.
We have become aware that there is missing store sales data for May 26, 2026. This missing data is impacting Scintilla suppliers and the category advisor persona who rely on headless access (Cloud Feeds, Data Feeds API and Scintilla Media Data Feed). Our team investigated the issue and resolved it as of 11:30 am CT this morning. Report Builder is unaffected and has all sales data for May 26, 2026. Please see the next steps below on how to restore missing sales data. Cloud Feeds: The data will be restated and published as an on-demand update in the status table. Suppliers can manually use the status timestamp to read the restated store sales data using CDF. If they do not take manual action today, then it will process automatically tomorrow via the normal CDF process.
The Store Inbound Inventory API endpoint provides information about inventory that is in transit from a Walmart Distribution Center (DC) to a Walmart Store. It shows when an item is requested, allocated, picked, or in-transit, by store number, gtin, and estimated Date of arrival.
Endpoints
GET
/store/{storeNbr}/gtin/{gtin}/storeInbound
Note: In this endpoint, {storeNbr} and {gtin} are the request parameters.
Optional Headers
The following optional header keys are available:
Name
Description
Required
Data Type
wm_context_identifier
A Walmart Supplier's unique identifier.
Mandatory for Preferred Service Providers (PSPs) only.
String
Request Details
Parameter
Description
Data Type
storeNbr
The valid store number associated with the requested details.
Integer
gtin
The 14-digit Global Trade Item Number that uniquely identifies the items.
String
Response Details
Parameter
Description
Data Type
storeNbr
The store number(s) associated with the requested details.
Integer
gtin
The 14-digit Global Trade Item Number that uniquely identifies the items.
String
storeInboundInventoryByEad
Contains inventory in transit, by estimated arrival Date.
Array
quantity
The number of items that are inbound for each state.
Double
locationArea
Destination where item is bound for. For example: STORE, MFC (Market Fulfillment Center).
String
ead
The Estimated Arrival Date of the inventory.
Date
inventoryByState
The array containing the quantity of items grouped by the state i.e. INTRANSIT, PICKED, REQUESTED, ALLOCATED.
Array
state
The state of items in transit. For example: INTRANSIT, PICKED, REQUESTED, ALLOCATED.
