Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WooCommerce Analytics Not Working: Causes and How to Fix It

WooCommerce Analytics Not Working: Causes and How to Fix It

Short answer

WooCommerce Analytics usually fails because historical orders were never imported, Action Scheduler jobs are stuck, the REST API is blocked or report settings exclude some order statuses. Import historical data from the Analytics settings, clear the pending scheduled actions, fix any REST API error and then clear the analytics cache.

Key takeaways

  • Analytics reads from lookup tables filled by background jobs, not live orders.
  • Import historical data after migrations or restores.
  • Pending wc-admin scheduled actions mean the queue is stuck.
  • A blocked REST API leaves reports blank or loading.
  • Excluded statuses and date type change what the totals show.
  • Clear the analytics cache after each fix.

Why is WooCommerce Analytics not working?

WooCommerce Analytics usually breaks because historical orders were never imported, background jobs are stuck, the REST API is blocked, or the report settings exclude the orders you expect to see.

Analytics does not read your orders table live every time you open a report. WooCommerce copies order data into its own lookup tables in the background, and the reports read from those tables.

So when something interrupts that copy, the reports go blank, show zero sales or stop at a certain date. The orders themselves are safe; only the report data is missing.

The fixes below run from quickest to most involved. Take a full backup before clearing caches, deleting data or running database tools. Our guide on how to back up a WooCommerce store covers that step.

What are the common symptoms and their likely causes?

Most Analytics problems fall into a handful of patterns, and the symptom often points straight at the cause.

SymptomLikely causeFirst thing to try
Reports show zero for old datesHistorical data never importedRun the historical data import
New orders do not appearAction Scheduler jobs stuck or WP-Cron not runningCheck Scheduled Actions for pending jobs
Reports spin forever or show an errorREST API blocked or a JavaScript errorCheck Site Health and the browser console
Totals differ from the Orders screenStatus or date type settingsReview Analytics settings
Analytics menu missingFeature disabled or plugin conflictCheck the Features settings

Work through the matching section first. If that does not help, go through the others in order.

How do you import historical data into Analytics?

Go to Analytics > Settings, find the Import historical data section, choose a date range or all time, and start the import so WooCommerce rebuilds the lookup tables.

This is the fix for stores that had orders before Analytics existed, migrated from another platform, or restored a database from a backup.

The import runs in the background in batches. On a large store it can take a long time, and the progress bar may sit still while batches wait their turn.

If an earlier import got stuck, use the option to delete previously imported data and then start a fresh import. That clears half-finished rows that can confuse the totals.

The official WooCommerce Analytics documentation describes the settings screen and import tool in detail.

How do you check whether background jobs are stuck?

Open WooCommerce > Status > Scheduled Actions (or Tools > Scheduled Actions) and filter by pending and failed actions whose names start with wc-admin.

WooCommerce uses the Action Scheduler library to queue Analytics work. Every new order, refund and status change creates a small job that updates the report tables.

If you see hundreds or thousands of pending wc-admin actions, the queue is not being processed. Failed actions usually include a log note that explains why.

The most common reason is that WP-Cron is not running. Action Scheduler relies on WordPress cron or on its own async requests, and both need visits or a server cron to fire.

Our guide to fixing past-due Action Scheduler actions goes into the queue checks step by step.

If cron is the problem, see how to fix WP-Cron not running.

How do you run stuck actions from the command line?

If you have WP-CLI access, you can process the queue directly with the action-scheduler commands, which avoids timeouts in the browser.

The Action Scheduler WP-CLI page lists the commands and flags. Running the queue in smaller batches is gentler on shared hosting.

After the queue clears, refresh the Analytics reports. Recent orders should now appear.

Is the REST API blocking Analytics?

Yes, it can be; the Analytics screens load their data through the WooCommerce REST API, so anything that blocks REST requests leaves the reports empty or stuck loading.

Check Tools > Site Health first. If it reports a REST API error, Analytics will not work until that is fixed.

Common blockers include:

  • A security plugin that disables the REST API for logged-out or all users.
  • A firewall or CDN rule that challenges requests to /wp-json/.
  • Broken permalinks, which you can usually reset by saving Settings > Permalinks once.
  • Server rules that return errors for JSON requests.

The WordPress REST API handbook explains how routes work. Our guide to fixing the REST API error in Site Health covers the usual causes.

You can also open your browser's developer tools on an Analytics page. Failed network requests to wc-analytics routes and their status codes tell you exactly where the block is.

Do the Analytics settings hide some orders?

Yes; Analytics only counts orders in actionable statuses and skips any statuses you list as excluded, and it can date orders by created, paid or completed date.

Open Analytics > Settings and review these options:

  • Excluded statuses removes orders in those statuses from every report. If Processing or a custom status ended up here, those sales vanish from the totals.
  • Actionable statuses controls which orders appear in the activity panel as needing attention.
  • Date type decides which date WooCommerce uses to place an order on the timeline.

Date type explains many wrong total complaints. If you report by completed date, an order paid on the 30th but completed on the 2nd lands in the next month.

Custom order statuses added by plugins also need care. If a plugin moves paid orders into a status that is excluded, they will not count.

Is caching showing old report data?

Analytics caches report results to stay fast, so after fixing the underlying problem you may need to clear that cache before numbers change.

Look under WooCommerce > Status > Tools for a tool to clear the analytics cache, and run it once. Then reload the report.

Page caching and object caching can also interfere. Make sure your caching plugin or host never caches wp-admin pages or REST responses for logged-in users.

If you use a persistent object cache such as Redis, flushing it after a large import can help the reports pick up fresh data.

Could a plugin or theme conflict be the cause?

It can; a plugin that changes orders, statuses or admin scripts can break Analytics, so a quick conflict test is worth doing when nothing else explains the problem.

The safest way is on a staging copy. Disable all plugins except WooCommerce, switch to a default theme, and check whether Analytics loads and updates.

Then turn plugins back on one at a time until it breaks again. The official how to test for conflicts guide describes the same process, and our guide to setting up a staging site helps if you do not have one yet.

Ad blockers and privacy extensions in the browser can also block admin scripts with analytics in the URL. Try the reports in a private window with extensions off.

Is Analytics switched off?

Sometimes; recent WooCommerce versions let you turn Analytics on or off, and some optimisation plugins or code snippets disable it to save resources.

Check WooCommerce > Settings > Advanced > Features for an Analytics option and make sure it is enabled. Then reload wp-admin.

Developers can disable WooCommerce's admin features with filters. If someone added such a snippet in the past, search your theme's functions file or snippet plugin for code mentioning woocommerce_admin and review it.

Performance plugins that offer to disable WooCommerce bloat sometimes include Analytics in that list. Look through their settings too.

Do server limits stop Analytics from updating?

They can; imports and report queries need enough PHP memory and execution time, so a very small hosting plan can leave imports half-done or reports timing out.

Check WooCommerce > Status for your PHP memory limit and other server values. Our guide to the WooCommerce status report explains what each line means.

If memory is low, raise it as shown in our guide to increasing the PHP memory limit. Large stores also benefit from a real server cron rather than visit-based WP-Cron.

Database health matters too. Our guide to optimising the WooCommerce database covers cleaning old sessions and transients that slow everything down.

What should you do if nothing works?

Collect your system status report, the error notes from failed scheduled actions and any console errors, then ask on the WooCommerce support forum or your host.

The WooCommerce support forum on WordPress.org is free and watched by the WooCommerce team. Clear details get faster answers.

When you post, say which reports are wrong, which dates are affected and what you already tried. Include whether you migrated recently, enabled HPOS or changed hosting.

Once Analytics works again, our guide to setting up WooCommerce Analytics shows how to configure reports so they match the way you run your store.

Frequently asked questions

Why does WooCommerce Analytics show zero sales?

Most often the historical data import was never run, so older orders are not in the report tables. It can also happen when paid orders sit in an excluded status. Run the import from the Analytics settings and review the excluded statuses list.

How long does the historical data import take?

It depends on how many orders you have and how fast your server processes background jobs. Small stores finish in minutes, while stores with many thousands of orders can take hours. A working server cron helps it finish faster.

Does fixing Analytics change my actual orders?

No. Analytics keeps its own copy of order data in separate lookup tables. Importing, deleting imported data or clearing the cache only affects those report tables, not the orders themselves. A backup before any database work is still wise.

Why do Analytics totals differ from the Orders screen?

Analytics may date orders by paid or completed date instead of created date, and it skips excluded statuses. Refunds are also shown separately. Check the date type and excluded statuses settings to make both screens line up.

Can a security plugin break WooCommerce Analytics?

Yes. Analytics loads data through the REST API, so a security plugin or firewall that blocks REST requests can leave reports empty. Allow REST access for logged-in administrators and check Site Health for a REST API warning.

Sources

  1. WooCommerce Analytics WooCommerce
  2. Action Scheduler WP-CLI Action Scheduler
  3. How to Test for Conflicts WooCommerce
  4. REST API Handbook WordPress Developer Resources
  5. Understanding the WooCommerce System Status Report WooCommerce

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.