How to audit a messy WooCommerce backend.
A working checklist. The order matters — start at the database and work outward, because most of what looks like a plugin problem is actually a data problem with plugin symptoms.
Step 1 — Inventory the plugins
List every active plugin. For each, answer three questions: what does it do, when was it last updated, and is anything actually wired to it. Most stores have at least two plugins doing the same job and one that nothing depends on. Deactivate the orphans before doing anything else.
Step 2 — Check the cron
WooCommerce relies on WP-Cron for almost everything that happens off-the-click — emails, recurring tasks, stock updates. On a low-traffic store, WP-Cron can simply stop firing reliably. Move it to a real system cron and verify the last successful run for every recurring job.
Step 3 — Trace the integrations
Open every external integration and confirm: API key still valid, last successful sync, error log clean. Half of all “the data feels off” complaints trace back to an integration that has been quietly failing for weeks.
Step 4 — Audit the order statuses
WooCommerce status flows are easy to customize and easier to break. Pull the last 90 days of orders by status and look for outliers — orders stuck on processing, refunds that never moved past pending, on-hold orders nobody noticed. The pattern of stuck orders is usually a map of broken automations.
Step 5 — Inspect the email layer
Transactional and marketing email drift on different schedules. Confirm SPF/DKIM/DMARC, send a test through every transactional template, and verify Klaviyo or Mailchimp triggers fire on the right WooCommerce events — not on “custom event sent two product launches ago.”
A messy backend is rarely a single broken thing. It’s twenty things that were once working, accumulated.