Our upstream team is transitioning RFID SKU data to a new source. During this period, there may be times when no new data is available. We’ll notify you once the new source is live.
Merchandising will be making additional hierarchy changes for Departments 5, 7, and 87 between Monday, February 23 and Friday, February 27. Additional hierarchy changes for fashion departments will begin on Monday, March 2 and last for up to 8 weeks. The above hierarchy changes will be reflected in Channel Performance on a daily basis, pulling in changes each morning from the day before. If you have any pre-built reports utilizing hierarchy filters, you may need to clear these filters and recreate them with the new hierarchies. Shopper Behavior, Customer Perception, Digital Landscapes, and Insights Activation will reflect all Departments 5, 7, and 87 hierarchy changes on Monday, March 9. Fashion hierarchy changes for Shopper Behavior, Customer Perception, Digital Landscapes, and Insights Activation will also begin to be reflected on Monday, March 9 and will continue to update on a weekly cadence each Monday.
Upcoming restatement to correct overinflated backroom inventory data Walmart Data Ventures was recently informed up our upstream partners that, due to faulty Logic, Backroom Adjustment Retail Amount metrics (backroom_adj_cst_amt and backroom_adj_retail_amt) are overinflated within Backroom Adjustment Inventory at the store level. To correct this data, Walmart Data Ventures worked with upstream partners to restate the data beginning Friday, March 6, and will finalize this work on Monday, March 9. For Data Feeds and Cloud Feeds clients, we will send the updated data in the form of insert and updates, Please plan accordingly.
Transaction History Endpoint Update: The following optional header keys are now available for the Transaction History endpoint:
Name
Description
Required
Sample Value
continuationpagetoken
Transaction History responses can contain a maximum of 60 records. When the response has more than 60 records, the response header will contain a Continuation Token. This Continuation Token needs to be sent back in the request header to get any additional records.
