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.
Our APIs are deployed in isolated Sandbox and Production environments. Charter Supplier onboarding onto these environments requires authentication with the Walmart API Proxy/Gateway before initiating an API call. The first step to authenticating your access is generating access keys.
Before you begin:
🚧
If you have already onboarded to Data Feeds APIs, you do not need to generate keys again. Please also make sure your business partners have already connected with a Walmart Data Ventures Account Manager.
Before you begin generating your API access keys, you need to have access to a command line terminal. For Windows systems, ensure that either Git Bash or OpenSSL for Windows has been installed. PuttyGen tool is not recommended as the default format is not PKCS8.
Generating API Keys - Windows-based Systems
Watch the video or continue reading below to generate your keys.
Create a desktop folder, titled "RSA Keys" (optional)
Right-click the folder and select "Show more options" to open the Git Bash or OpenSSL terminal (optional)
From the terminal command line, you will generate an RSA key-pair:
Paste the following command into the terminal and hit enter.
Using -des3 ensures that the pem file generated in the above step will be passphrase protected. You will be prompted for the passphrase. The passphrase will be located directly above the prompt in the terminal. In the example below, 65537 is the passphrase: Example:
e is 65537 (0x010001)
Enter pass phrase for my_rsa_key_pair:
Note: Please note this passphrase in a safe location. You will use it again.
Type the passphrase into the terminal where prompted (note that while entering the passphrase, it will not look like you are actually typing) and hit enter.
You may be prompted to enter the passphrase twice.
Next, you will export the private key in the private_key.pem file:
Paste the following command into the terminal and hit enter.
Type the same passphrase into the terminal where prompted (note that while entering the passphrase, it will not look like you are actually typing) and hit enter.
Finally, you will export the public key in the public_key.pem file:
Paste the following command into the terminal and hit enter.
Type the same passphrase into the terminal where prompted (note that while entering the passphrase, it will not look like you are actually typing) and hit enter.
What Happens Next
You should now have three files in the folder you created (or your chosen location): my_rsa_key_pair, public_key.pem, and private_key.pem.
If you are requesting access to multiple environments, remember to repeat the above steps for each environment you are requesting. It is helpful to sufficiently label your RSA folders for easier reference when generating Authentication Signatures.
🚧
Keep your private key(s) safe.
This will be used to generate the Authentication Signature before making any API call. Your private key should be protected just as you would a password. Walmart is not responsible for your private key. Please keep your private key in a secure location.
Now that you have your keys, you will be able to move on to Step 2.