WooCommerce test
A hosted test store. Everything happens there — this page is the map.
- Every link below goes through the WordPress login first. Sign in once in a tab and the rest open straight through.
- Webhooks are queued, not sent inline. WP-Cron only runs when the site gets a request, so on a quiet test store a delivery can wait until someone loads a page.
- API secrets belong in a server or a password manager. Nothing on this page stores or asks for one.
Everything WooCommerce and its extensions write. Webhook deliveries log under the webhooks-delivery source, with the response each endpoint returned.
WooCommerce → Status → LogsCreate and edit webhooks, and see each one's status. WooCommerce disables a webhook after repeated failed deliveries, so check here first when one goes quiet.
WooCommerce → Settings → Advanced → WebhooksConsumer key and secret pairs. The secret is shown once, at creation — copy it then or make a new key.
WooCommerce → Settings → Advanced → REST APIThe queue webhooks are delivered from. A delivery that never arrived is usually still pending here rather than failed.
WooCommerce → Status → Scheduled ActionsPlacing or editing an order is the quickest way to fire order.created and order.updated webhooks.
WooCommerce → OrdersVersions, PHP limits and WP-Cron state — the first thing to attach to a bug report.
WooCommerce → Statushttps://woo-test.aivo.one/wp-json/wc/v3/.