Major incident

Salsify: Walmart 1P Connector Publication Failures

Affected: Enhanced Content, Walmart

Current status of Salsify: Minor issues — live Salsify status

Timeline

1. Apr 16, 2026, 09:22 UTC
   investigating
   We have identified an issue causing all publications via the Walmart 1P (Vendor) connector to fail due to an error retrieving credentials from Walmart's API. This appears to be related to an outage on Walmart's side. Walmart 3P (Marketplace) services appear to be unaffected at this time. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
2. Apr 16, 2026, 13:55 UTC
   investigating
   We are currently investigating an issue causing publications via the Walmart 1P (Vendor) connector to fail due to an error retrieving credentials from Walmart's API. This issue also impacts Enhanced Content publishes for customers utilizing OAuth authentication with Walmart’s API Gateway.Walmart 3P (Marketplace) services using legacy authentication appear to be unaffected at this time. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.
3. Apr 16, 2026, 23:23 UTC
   monitoring
   Walmart has reported progress in resolving the internal errors that have been broadly impacting supplier API submissions. As of 6:40 PM WET (1:40 PM EDT), our engineering team has observed the first successful publications through the Walmart 1P (Vendor) and Enhanced Content (OAuth) connectors. While this indicates that the service is recovering, we are continuing to monitor the success rate to ensure stability across all accounts. Action Required for Failed Submissions: Please note that any publications that failed prior to this recovery window will not automatically reprocess. Please republish the affected products to transmit them to Walmart. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for assistance or questions.
4. Apr 17, 2026, 09:22 UTC
   resolved
   This incident has been resolved.

Updates as published by Salsify (original).