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.
API call attempts have the potential to return a variety of errors. Find common error codes, reasons, and resolution details below.
Refer to the applicable endpoint reference page for specific endpoint error information, this page is for quick reference of common errors. Expand each to view details.
400 (BAD REQUEST)
Error Message
Reason
Resolution
Invalid parameter.
An invalid parameter may have been provided in the request.
Please check and provide a valid parameter in the request header. See the individual endpoint reference page for specific parameter information.
401 (UNAUTHORIZED)
Error Message
Reason
Resolution
Could not authenticate inrequest, auth signature: Signature verification failed.
This is possibly because of: 1. using an incorrect private key for generating the signature. 2. a malfunctioning Authentication signature.
Make sure you are using the correct private key and other parameters. Please try generating a new Authentication Signature.
The Tmestamp 1639999142531 passed for the signature has expired .
The Tmestamp for the signature has expired.
Please generate a new signature and try again. Signatures expire every 3 minutes.
403 (FORBIDDEN)
Error Message
Reason
Resolution
The Consumer ID is not subscribed to the service name.
When the "wm_consumer.id" Header is not present or not correct.
Please use the provided Consumer ID in the request header.
Request is missing required security headers, please read documentation for security headers.
This is because any one of the mandatory request headers are missing.
Request headers should have all four attributes: wm_consumer.id, wm_sec.auth_signature, wm_consumer.intimesta mp, and wm_sec.key_version.
404 (NOT FOUND)
Error Message
Reason
Resolution
Not found.
The provided URL is incorrect.
Please use the correct endpoints. Refer to individual endpoint reference pages.
A requested GTIN is not mapped to the Supplier.
- A provided GTIN doesn’t belong to the supplier. - A provided GTIN is not mapped to the supplier for a few stores.
Please use the appropriate GTIN belonging to the supplier.
Data not found for the given request parameters.
There is no data for a requested GTIN and storeNbr.
Provide the valid GTIN for the particular storeNbr.
405 (METHOD NOT ALLOWED)
Error Message
Reason
Resolution
Method not allowed.
An incorrect HTTP verb has been used.
Use the correct request method. Refer to the endpoint reference pages or endpoint quick view page for relevant methods.
429 (TOO MANY REQUESTS)
Error Message
Reason
Resolution
Too many requests, please retry after some time.
This is possibly due to a number of requests exceeding the given quota. The peak rate limit for Near Real Time API is generally 600 transactions per minute (TPM). Please refer the Throttling section in the endpoint reference pages for specific endpoint information.
Since the requests are getting throttled, it is suggested to try again after some time.
500 (INTERNAL SERVER ERROR)
Error Message
Reason
Resolution
Internal server error.
One or more services are unavailable. Please contact support.
