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.
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.
Here you can find answers to common Cloud Feeds questions. Can't find the answer to your question? Please contact us.
Data Feed API FAQs
Frequently asked Data Feed API questions.
What is the expiration timeline for digital signatures and timestamps?
The digital signatures and timestamps expire every 3 minutes; we recommend users regenerate the signature for every call.
Does everyone at the company need an API Consumer ID?
No, API Consumer IDs are shared at a company level. The same Consumer ID will be applicable for everyone in the company.
Does the RSA key have an expiration date?
No, the RSA key does not have an expiration date.
Can I request a different Consumer ID for production if I lose my keys?
Yes, we can regenerate the Consumer ID for production. Regeneration of Consumer IDs can take 3-5 business days.
Do I need to generate different RSA keys for Sandbox, Production, and Category Advisor APIs?
Yes. You will need to use a unique RSA key for each environment. Please refer to the table below for more details on RSA keys requested.
Scenario
Description
Keys Needed
1
Sandbox only
1 RSA needed
2
Production only
2 RSAs needed: 1 for Production and 1 for Category Advisor API
3
Both Production and Sandbox
3 RSAs needed: 1 for Sandbox, 1 for Production, and 1 for Category Advisor API
Is there a limit to the number of API calls that can be called?
Data Feed APIs have a uniform rate limit of 25 transactions per minute (TPM) across all of the API endpoints (Snapshot, Status, History, and Incremental) that are provided to the Clients. For more info, please refer to our API Documentation.
Is there a TTL (Time to Live) for Signed URLs?
All signed URLs are activated with a TTL of 10 mins. Once this TTL expires, new sessions are not allowed, but an existing session will not be stopped while downloading files.
When will the Data Feed API data be refreshed?
SLAs will vary by feed and are listed in our API documentation.
How often is data refreshed for API consumption?
Data refresh will occur as often as the underlying data asset allows. For example, Store Sales and Store Inventory will differ in refresh rate due to the number of records being restated and the processing time of the underlying source. Our recommendation is to set up an automated process to call our "Get Status" APIs at least every 15 minutes so you will capture the latest status as soon as the data is updated.
Why am I seeing 'no data available' when I call an API?
For incremental data feeds, there may be days without new data, such as during holiday periods for some feeds or when there are no modular changes. These are valid scenarios where the API call can show a 204 Response Code where the API Call is successful, but there is no data available to be generated or where feed will not appear as "Available" in the Get Status call.
Please ensure that you have received an "Available" response from our "Get Status" API for the data feed in question. Additionally, if more than 45 days have passed since onboarding and historic data has not been ingested, you must submit a request to regenerate the historic data.
In the Order Forecast Feed, what does the value 0 in the dc nbr field denote?
The value "0" will show for Vendor to Store or Vendor to DC orders.
Please note:
The store_nbr field represents the destination to where the item needs to be shipped. In the case of Vendor to DC and DC to DC orders, this field will contain the Distribution Center Number instead of the Store number.
The dc_nbr field represents the source from where the item will be shipped. For Vendor to Store and Vendor to DC orders this field will be null.
In Order Forecast Feed, some store nbr values will contain the Distribution Center Number, while dc nbr is 0, what does this signify?
This will happen when it is a Vendor to DC order.
Please note:
The store_nbr field represents the destination to where the item needs to be shipped. In the case of Vendor to DC and DC to DC orders this field will contain the Distribution Center Number instead of the Store number.
The dc_nbr field represents the source from where the item will be shipped. For Vendor to Store and Vendor to DC orders this field will be null.
Why are some Forecast Sequence Number fcst seq nbr values other than especially when dc nbr is 0, what does it mean?
fcst_seq_nbr are unique numbers generated by the forecasting system for a given store/item combination on a given date. Please see our Business Glossary for more information on Forecast Sequence Number.
Availability Ship Date avlbl ship dt just shows one value throughout (i.e., 1970-01-01). Is this a real value?
When requesting forecasting values, you will want to use Scheduled Ship Date (sched_ship_dt) because that is used to tell when an item is scheduled to be shipped.
