Decomm of legacy data tables re-scheduled to December 12 With the recent transition to our new Omni Item Dimensions table, previous pre-release notes communicated that any legacy data tables would be decommissioned on October 28. This decommissioning activity is now scheduled for December 12, 2026.
Action Required: eCommerce Dataset Update (October 28, 2026). The eComm Inventory, eComm Instock Percentage, and FC eComm Instock Percentage datasets are transitioning to Walmart Item Number (WIN). Cloud Feeds users must update their table schemas and reload the full history. Do not process the history load as incremental (CDF) data. Resume incremental processing after the next regular refresh.
SBU & Department 46 Hierarchy Changes:
Fashion → Style;
Home → Style;
ETS + Hardlines → ETS/Hardlines;
Department 46 (Beauty) → Style.
Important Dates:
Operational hierarchy updates: October 20; Shopper Behavior updates: December 7. Please login to
Scintilla.com for a more detailed banner
Share your experience in our short survey! Click here
We are aware of incorrect data for the street_dt field in Product Dimensions. Our data teams are prioritizing identifying a resolution. We anticipate that the corrected data will be available in the September 25, 2026 refresh. We apologize for the inconvenience.
We are aware of incorrect data for the street_dt field in Product Dimensions. Our data teams are prioritizing identifying a resolution. We anticipate that the corrected data will be available in the September 25, 2026 refresh. We apologize for the inconvenience.
As of today, September 23, Scintilla’s Store Inventory metrics have transitioned from a legacy data source to the new Enterprise Inventory (EI) data source, meaning that any data for September 23 and onwards will sourced from EI. This aligns Scintilla with the enterprise-standard inventory system, eliminates inconsistent logic within the legacy data source, and improves replenishment metric accuracy. Merchandising already completed this transition for Merch One on Tuesday, June 23. Historical data (June 1, 2025 – September 22, 2026) will go through a restatement process. Restatement work will begin on September 24, 2026 and will not be completed until October 8, 2026. Approximately 60 days' worth of data will be restated daily (with no restatement work performed on Fridays and Saturdays). In completing the historical restatement on October 8, we will be eliminating the temporary variance that existed between Scintilla and Merch One from June 23–September 22, 2026. During restatement period, clients should expect fluctuations to the relevant metrics that will be resolved once we finalize on October 8. They should also expect fluctuations due to changes to logic / formulas for the following fields: Instock % - TY/LY, Traited & Valid Store Count, Traited Item count and related velocity metrics. The following columns will be removed in the UI and null in BI Link from the date of release: Carry opt Cd, Carry Opt Status.
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.
Scintilla Media Data Feed updates released during October 2026.
Action Required
🔴 Action Required
eComm Inventory now uses Walmart Item Number grain
The eComm Inventory table has transitioned from Catalog Item ID (catlg_item_id) grain to Walmart Item Number (wm_item_nbr) grain. This provides a consistent Walmart Item Number grain for joining eCommerce inventory data with other Walmart Item Number–based datasets.
What changed
wm_item_nbr now replaces catlg_item_id as the item-level grain.
The external schema and composite primary key have been updated accordingly.
A history file for eComm Inventory was provided through the history endpoint on October 27, 2026.
WPID has been removed from eComm Inventory, with no replacement field.
What you need to do: Adopt the new table structure so your data tables continue to work. Use the history file provided on October 27, 2026, and begin consuming the incremental data with the new schema on October 28, 2026.
Decommission Notice
🔴 Decommission Notice
Catalog Item ID–grain eComm Inventory
The previous Catalog Item ID–grain version of eComm Inventory is no longer accessible as of October 28, 2026, 12:00PM CST.
Customers should now read the new Walmart Item Number–grain structure referenced above.
Documentation Updates
🟡 Documentation Update
Omni Item Dimensions is now the data source for Data Access & Collaboration tools
Operational data for Data Access and Collaboration tools has transitioned to a next-gen data source, Omni Item Dimensions, keeping the data aligned with Merch One.
What changed
Improved operational data refresh time (from D-2 to D-1).
Reduced data discrepancies between systems.
All 1P items now have a Walmart Item Number.
Improved metadata for certain items, including Brand Name, Product Descriptions, and Sell Unit of Measure.
Note: This is separate from the decommission of the legacy item attributes, which remains planned and is tracked on the Coming Soon page.
🟡 Documentation Update
Store Inventory restatement behavior clarified
Following the Enterprise Inventory (EI) transition, clarifying guidance has been added to the Store Inventory reference page explaining the current data refresh and restatement cadence:
Monday–Friday: D-1 incremental data and D-2 restatements are delivered together.
Saturday: D-1 incremental data and PSI automation data are delivered.
Sunday: D-1 incremental data plus a weekly restatement covering the prior 30 days are delivered.
As a result, data initially delivered for a business date may be updated in the following day's refresh as additional inventory data is finalized. This can affect metrics such as on-hand quantity, replenishable in-stock numerator, and related in-stock calculations.
This is expected behavior, not a data accuracy issue. Treat the most recently delivered business day (D-1) as preliminary.
Learning Resources
🔵 Learning Resource
Omni Item Dimensions FAQ now available
A new FAQ page, FAQs - Omni Item Dimensions is now available here.
It covers:
What Omni Item Dimensions is and why it matters
Identifier relationships between WM_ITEM_NBR and CATLG_ITEM_ID
Grain and primary key guidance
Loading and ingestion guidance
Join guidance for both Supplier and Category Advisor personas
Guidance on preventing duplicated or lost records when joining
This FAQ explains how customers can continue deriving Catalog Item ID in limited scenarios for the eComm Inventory table above.
