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.
The Scintilla In-Store Locations API retrieves a list of store locations and associated information, including store address, hours, hierarchy (region, market, etc), and calendar events.
Endpoints
GET
/admin/v1/locations
Request Parameters
Parameter
Description
Data Type
sort
The way data being returned is sorted.
String
LocationNumber
Returns information about a specific location.
String
UpdatedDate
Returns information based on the UpdatedDate parameter.
String($Date-time)
Limit
Limits the number of locations that are returned. Used with Offset to retrieve in batches.
Integer($int32)
Offset
If not specified it will grab the first “limited amount”. If you want to get the next batch you will need to offset by that value.
Integer($int32)
Response Details
Parameter
Description
totalCount
Returns the total number of events in the response for this employee.
results
An Array containing details of the events returned in the response.
id
An ID associated with the event. This is automatically created by the system and can be used if you want to get details of a specific event (optional).
employeeNumber
The employee number of the employee associated with the event.
number
The store number associated with the event.
retailer
The name of the retailer associated with the event.
lat
The latitude coordinate of the event location (optional).
Long
The latitude coordinate of the event location (optional).
invoiced
Denotes whether or not the event is invoiced (true/false).
metersFromLocation
Provides the distance from the store where the user checked in or out on the app.
utilizedBadge
Indicates whether or not the employee checked in/out with their badge.
manuallyAlteredTime
Indicates if the event time has been manually altered (true/false).
reportedTime
The event time reported, in UTC Date/time format.
systemTime
The event time recorded by the system, in UTC Date/time format.
offset
Can be used to retrieve events in batches. If not specified it will grab the first “limited amount”. If you want to get the next batch you will need to offset by that value.
limit
Limits the number of events that are returned. Used with Offset to retrieve in batches.
sortBy
Returns the column name data is being sorted by, based on sort requested.
sortAscending
Indicate if the returned events are sorted ascending (true/false). Prefix with a minus in the sort parameter for descending.
For any technical or support questions, please contact us.
Please note: Provider organizations are responsible for providing support for their employees. Walmart Scintilla In-Store only provides support to Provider Administrators and the Field Group’s technical team, enabling each company to properly support the field reps.
Disclaimer
Your use of the API documentation is at your own discretion and risk. To the maximum extent permitted by law, the APIs, documentation and all related software, components, and support are provided by Walmart on an "as-is" and "as available" basis without any warranties of any kind, and Walmart expressly disclaims any and all express and implied warranties, including, but not limited to, warranties of merchantability, fitness for a particular purpose, title, noninfringement, non-interference, and warranties arising from a course of dealing. You acknowledge that Walmart does not warrant that the APIs will be uninterrupted, timely, secure, or error-free. Walmart may modify and delete API documentation in its sole discretion and without notice.
In no event shall Walmart be liable to you or any third parties for any damages whatsoever, including, without limitation, those resulting from loss of use, damage to your computer system, loss of data or profits, or any liability arising out of or in connection with the use of the APIs, documentation, software, components, or support.
