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 Market Fulfillment Center (MFC) API provides suppliers with visibility into which products (by GTIN or wm_item_nbr) are being added and removed from a Market Fulfillment Center assortment. Data is updated weekly.
Please note that this endpoint will be unavailable during the hours of 12AM and 2AM CST.
Endpoints
POST
/inventory/items-assortment
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 Body Details
Parameter
Mandatory
Description
Data Type
store_number
Yes
This is an identifying number of a store within a country. It is the most used store identifier and is an essential store attribute for reporting.
Integer
zone_type
Yes
Zone in which the inventory is located. The only valid input is MFC.
Array
Response Body Details
Parameter
Description
Data Type
supplier
The name of the supplier.
String
store_nbr
The store number associated with the requested details.
Integer
gtin
The 14-digit Global Trade Item Number that uniquely identifies the items.
String
wm_item_nbr
The Walmart Item Number that uniquely identifies the items.
String
status
Status of the item in the assortment for a specific store. Valid Values: - Keep: Product continues to be available in the MFC Assortment - Add: Product will be added to the MFC Assortment for this store - Delete: Product will no longer be in the MFC assortment for this store
String
effective_date
The Date in which the status of the item goes into effect. In YYYY-MM-DD format.
