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.
The Inventory Action Capture (IAC) API provides the capability for Pay-For-Scan (PFS) suppliers to send their Walmart Store inventory actions back to the Walmart Enterprise Inventory.
Endpoints
POST
/store/inventoryActions
Request Body Details
Parameter
Mandatory
Description
Data Type
messageId
Yes
A unique reference identifier for the message that can be any unique value up to 36 characters. The messageId must be unique for every call.
String
eventType
Yes
Event type will be a unique identifier for the type of action that is being taken at the store. Note: Only the four events below will be accepted, and they arecase sensitive (upper case).
ARRIVAL - Used for arrival or restocking of the merchandise. "Arrival" Event Type cannot have a negative quantity value. Please always provide a positive value with this event. Ex: If an item has "quantity" value as "40" with "arrival" event, 40 units will be added to the available inventory.
REMOVAL - Used when merchandise is being removed from the store due to damage, overstock, expiration, etc. Please always provide a positive value with this event. Ex: If an item has "quantity" value as "40" with "removal" event, 40 units will be subtracted from the available inventory.
CORRECTION - Used when inventory needs to be reset to a value that is different from what is available in the Enterprise Inventory. It can also be used if the available quantity is not known.
For correction, a positive quantity must be provided. Negative quantities will be rejected. For example, if the current inventory shows 25 but needs to be corrected to 20, the correction event should be sent as 20.
BOOTSTRAP - Use this event for a new item/GTIN, for a quantity count signifying a starting Available value. For Bootstrap, a representative would need to do a full inventory count of all Supplier merchandise in the store.
String
storeNbr
Yes
The store number where the event is taking place.
Integer
lineInfo
Yes
This array will contain the list of details of the items that are being acted on. Maximum of 10 items are allowed per event.
Array
gtin
Yes
The 14-digit global trade identification number of the item that is being acted on.
String
secondaryItemIdentifier
No
An optional secondary item identifier, such as ITEM NUMBER, UPC, etc.
Record (JSON Object)
type
Yes
The secondary item identifier type. E.g., UPC, ITEM NUMBER etc.
String
value
Yes
The value of the secondary identifier.
String
destinationLocation
Yes
Record of where the item is being dropped in the store.
Record (JSON Object)
locationArea
Yes
Area within the score where the item is being dropped e.g., shelf, salesfloor, backroom, MFC etc.
String
location
No
The aisle location, in sgln format. Example: A-10-100.
String
lpn
No
This is an optional container identifier.
String
quantity
Yes
The quantity of items/merchandise that were added, removed, or corrected (positive or negative) during the action. The value in this field can be negative or positive (ex. - 20, 20).
Float
expiryDate
No
Expiration Date of the item being dropped (gtin level). In YYYY-MM-DD format.
String
documentInfo
No
Optional document-related information, if available, regarding the action being taken.
Array
doctype
No
The type of document being used e.g., INVOICE, PO etc. (optional)
String
docNbr
No
The number/identifier associated with the document. (optional)
String
docDate
No
The Date/time of the the document generation, in epoch format. (optional)
Long
userId
Yes
The user id, or unique identifier, of the person/process triggering the event. This will be sent by the source app.
String
reasonDetails
Yes
Details of the reason why this action is being taken.
Array
reasonCode
No
An optional supplier reason code, Maximum 30 characters.
String
reasonDesc
Yes
A short description of why the action was taken needs to be provided, maximum 30 characters.
String
vendorNbr
No
The vendor number associated with the vendor, if different from the supplier making the delivery (optional), maximum 30 characters.
String
eventCreationTime
Yes
The system time of when the event was created, in epoch format (note: time must be in milliseconds). The event must occur within the last 3 days.
Long
Response Body Details
The response body will contain the message "Events created for the following gtins" for all successful events. Item-related errors will follow in the response. For common item-related errors, please see our Error Codes page.
