Help & Guide/Connected store
Checkout check (Woo vs Magento)
Open in appCatch a broken cart on the same ~5-minute loop as uptime, with separate recipes per platform.
- 1Open Settings → Checkout.
- 2Leave origin pulse on so each plugin sync (~5 min) reports checkout health without marking the homepage down.
- 3Turn on the browser happy path if you need Magento’s JS checkout (email field) or a custom Woo theme.
- 4Set shop/cart/checkout paths and selectors for each connected store. Magento cart is /checkout/cart, not /cart.
- 5Save. The next plugin sync and the next scheduled browser run use the new recipe.
WooCommerce checkout is a PHP form. The plugin adds a simple in-stock product to cart on the server (then empties it) and uses wc_get_checkout_url. The browser flow is shop → product → cart → billing field.
Magento / Adobe checkout is a Knockout SPA. The origin pulse only proves Magento’s checkout URL is not 5xx. Add-to-cart, minicart, and the guest email field need the browser flow. OneStepCheckout and Hyvä stores override checkout path and the email selector.
A Cloudflare challenge on the browser flow is inconclusive — it is not a checkout outage. Home shows that limitation with a link to Settings → Checkout. Shopify and BigCommerce have no origin pulse.
Related
- Transaction MonitoringPlaywright checkout (and similar) flows on a schedule.
- Create a checkout testAdd a Playwright flow so a broken cart is caught before shoppers.
- How origin health works by platformWhat CPU, RAM, disk, and load mean — and which stores can send them.
- SettingsAlerts, origin health, checkout, planned work, team, and advanced detectors.
Still stuck? Open a support ticket.