Smart Cart Loading Issues

Update timeline

1. investigating Apr 22, 2026, 04:53 PM UTC

   We have received multiple reports of Smart Cart loading inconsistently on some merchant storefronts.We have received multiple reports of Smart Cart loading inconsistently on some merchant storefronts. Our team is actively investigating and will provide updates as we learn more.

2. investigating Apr 22, 2026, 05:02 PM UTC

   Our team continues to investigate. Current findings suggest the impact may vary by region.

3. monitoring Apr 22, 2026, 05:06 PM UTC

   A change has been deployed and merchants who reported issues are seeing improved results. We are continuing to investigate the root cause and will share more details as they become available.

4. resolved Apr 22, 2026, 05:18 PM UTC

   This issue has been resolved. Our team is completing a full root cause analysis, which will be posted to the status page once available. Thank you for your patience.

5. postmortem Apr 22, 2026, 07:19 PM UTC

   **What happened:** On April 22, 2026, between approximately 11:45 AM and 1:02 PM ET, a subset of shoppers on Rebuy-powered storefronts experienced an inability to load SmartCart V2. Merchants and shoppers who encountered the issue during this window would have seen the cart fail to initialize. All other Rebuy functionality remained operational throughout the incident. ‌ **Duration:** Approximately 1 hour and 17 minutes. ‌ **Impact:** A subset of shoppers on affected storefronts were unable to load SmartCart V2 during the incident window. No data was lost or compromised. ‌ **What caused it:** A software release introduced changes that shifted internal script references in a way that caused the cart to fail for shoppers loading a fresh version of the storefront script during the deployment window. Shoppers with a cached version of the script were unaffected. ‌ **What we did:** Our team identified the issue within minutes of the first report, rolled back to the previous stable release, and confirmed full restoration of SmartCart V2 by 1:02 PM ET — approximately 16 minutes from first report to resolution. ‌ **What we are doing to prevent recurrence:** We have identified the root cause and are implementing structural improvements to our deployment pipeline, including additional validation steps to catch this class of issue before it reaches production.