Analytics Core User Guide.

Analytics Core for WooCommerce · User guide

This guide is for shop owners who want a fast sales dashboard, and for developers who want to know what the plugin stores and how to rebuild it. Analytics Core is free, so nothing here depends on a license.

Nothing here assumes you know PHP. The developer section at the end is optional.

What this plugin does

WooCommerce already knows every order. A report that re-scans those orders on every click gets slower as the shop grows.

Analytics Core copies the numbers you care about into daily snapshot tables, then shows them on a clean admin dashboard. Light by default, with a real dark mode.

You keep using WooCommerce as the ledger. If a snapshot looks wrong, you rebuild it. You never edit table rows by hand.

Shoppers never see this plugin. Scripts and styles load only on the Analytics Core admin screen.

Analytics Core Overview: rail, closed month, yesterday, and sales over time
Overview: left rail, closed month through yesterday, written summary, and sales over time.

What is included

Analytics Core is free. There is one package and every report in this guide is in it.

AreaIncluded
TotalsNet sales, gross sales, discounts, refunds, tax, shipping, orders, average order value
OverviewClosed month, yesterday against the day before, written summary, month target and run-rate
SalesNet by day, hour-of-week heatmap, day matrix, recent orders, filters
CustomersNew vs returning, RFM as of yesterday, refunds by customer type, days to a second order, cohorts
ProductsSKUs that make about 80% of net, movers, first product and a later order, margin when cost of goods is on
OrdersTax, shipping, optional gateway fees, order list. Failed and cancelled stay out of net
OffersCoupon and billing-location breakdowns
SeasonsYear against year. Presets follow the store country
ComparePrevious-period comparison on every range
SubscriptionsMRR added, churned, and active when WooCommerce Subscriptions is active
ExportCSV from the selected range
HistoryNot time-boxed. Any period the snapshots cover. Closed through yesterday

There is no license, no trial, and no upgrade inside this plugin. Retention Core and Wholesale Core are separate products.


Requirements

  • WordPress 6.0 or newer
  • PHP 8.2 or newer
  • WooCommerce 8.0 or newer

WooCommerce Subscriptions is optional. When it is active, MRR added, MRR churned, and active-subscription counts use live subscriptions. When it is not, that KPI card is hidden.

The plugin declares compatibility with High-Performance Order Storage (HPOS) and Cart & Checkout Blocks. It reads orders through WooCommerce CRUD, never wp_posts directly.


Part 1Install and import history

  1. Activate WooCommerce.
  2. Upload and activate Analytics Core.
  3. The setup screen opens once. Choose:
    • History to import: 30 days, 90 days, 180 days, 12 months, or a custom start date. The window ends yesterday.
    • Daily job: the time of day, in the site timezone, when the snapshot job runs.
  4. Save and import history splits that window into batches of 14 days and queues them. A 12 month import is 27 batches. Skip for now keeps the defaults (180 days, 2:00 am) and does not import.
Analytics Core setup screen: history to import and daily job time
The setup screen. It opens once after activation.

Progress is the bar on the Analytics Core screen (for example 8 of 27 complete). Each batch is a row under WooCommerce → Status → Scheduled Actions. You can leave the page. The shop keeps taking orders.

Change the same fields later under WooCommerce → Settings → Analytics Core. Rebuild history now queues another import for the saved window.

WooCommerce Settings, Analytics Core tab
WooCommerce → Settings → Analytics Core. The same two fields, plus Rebuild history now.

A brand-new shop shows zeros until orders exist and those dates have been aggregated. Reports use complete days, through yesterday. There is no Today view.


Part 2The dashboard

Open Analytics Core in the wp-admin sidebar. Administrators and Shop Managers can read the desk. Changing settings or pressing Rebuild history needs manage_options (Administrators). WordPress’s own menu is folded on this screen; the left rail is Analytics Core. The date range at the top applies to every page.

Ribbon

  • Title, plus the date window for the selected range, marked closed through yesterday.
  • Updated line: when the snapshot was last written and when the daily job runs next.
  • Range chips: Yesterday · 7 days · 30 days · 90 days · 12 months · Custom.
  • Custom shows start and end date fields. Both are required, and the start must be on or before the end. There is no maximum length.
  • Yesterday is the previous day in the site timezone, not the last 24 hours.
  • Compare previous equal-length window. Export writes a daily snapshot CSV.
  • Rebuild history asks before it queues a rebuild of the saved window. It does not include today. Shown to Administrators. Shop Managers do not see it.
  • Light / Dark is remembered in this browser.

KPI cards

CardWhat it shows
Net salesGross minus discounts minus refunds in the window. The hint shows average order value and refund dollars.
Gross salesOrder subtotals, with the discount total in the hint.
New vs. returningRevenue from first-time customers. The hint is returning revenue.
OrdersOrder count. The hint is the first-time customer count.
MRR / churnOnly when WooCommerce Subscriptions is active. The hint links to Retention Core.
Analytics Core Overview desk with KPI cards and sales over time
Overview desk: rail, sticky range, KPI cards, and sales over time.

Summary

The Summary panel on Overview is written from the snapshot totals. It is plain sentences, not a chatbot: net sales, the change against the previous period, refunds as a share of gross, and where revenue came from.

Each section has a Details button that explains how that number is built. It stays closed until you open it.

Empty and error states

  • First paint shows skeleton cards while the REST call runs.
  • If the API fails (capability, REST blocked, tables missing) you see an alert with the error message. Numbers already on screen stay put during a refresh.

Part 3The report pages

The report is split by the question you are asking. The date range at the top applies to every page. Filters on Sales, Products, Customers, and Orders slice the order fact tables. Unfiltered Overview figures still come from the daily snapshot, so the totals you already trusted do not change meaning.

PageQuestion
OverviewHow did the closed month look? Yesterday against the day before, tax and shipping, concentration, and the written summary. There is still no Today figure.
SalesNet by day, hour of week, the day matrix, and recent orders.
ProductsWhich SKUs make about 80% of net, movers versus the previous window, refund %, first-product repeat, margin when cost of goods is on.
CustomersNew versus returning, RFM as of yesterday, the customer list, refund split, days to second order, cohorts.
OrdersTax, shipping, optional gateway fees when WooCommerce stored them, and the order list.
OffersCoupon discounts and billing location.
SubscriptionsOnly when WooCommerce Subscriptions is active. MRR added, churned, active. Cancel intercept stays in Retention Core.
SeasonsYear against year for named windows. Presets follow the store country.

Sales

Net sales by day, an hour-of-week heatmap in the site timezone, a day matrix of orders and net, and the recent order list. Filters use the order fact table. Failed and cancelled orders are counted and listed; they never enter net sales.

Sales page: net by day and hour-of-week heatmap
Sales: net by day and the hour-of-week heatmap on closed days.

Products

The catalogue for the selected window. Top ~80% is the share of net from the products that make about 80%. Movers compare this window with the previous one. First product and a later order shows, for each product on a customer’s first order, how many of those customers ordered again. Margin is net sales minus the product cost stored on the order line. It only calculates when WooCommerce cost of goods is on.

Products page: Pareto share, movers, and the catalogue
Products: the SKUs that make about 80% of net, movers, and the catalogue.

Customers

New and returning splits revenue and customer count between first orders and customers who had bought before. RFM as of yesterday is a 3×3 grid from closed orders — recency, frequency, and lifetime net. It is not a live “today” score. Refunds by customer type tells you whether refund dollars land on first orders or later ones. Days to the second order buckets the gap from first order to second. Repeat rate by first order is one row per starting month.

Customers page in dark theme: RFM as of yesterday
Customers in dark mode: RFM as of yesterday, plus who came back.

Offers

Coupon codes with the orders they were used on and the discount they gave, and billing countries with order and net totals. Switch between the two with the Coupons / Locations toggle. Both export to CSV.


Part 4How the numbers are calculated

All dates use the site timezone.

MetricRule
Included ordersStatus completed, processing, refunded, or partially-refunded
GrossSum of order subtotals, before discounts
NetGross minus discounts, then minus refunds that occurred on that day
RefundsCounted on the refund’s created date, not the parent order date
Failed / cancelledCounted and listed. Never added to net sales
FiltersSales, Products, Customers, and Orders slice the order fact tables. Unfiltered Overview still uses the daily snapshot
New customerFirst qualifying order for that customer (user ID, else billing email)
Returning revenueNet from customers who already had an earlier qualifying order
Product unitsLine quantities. Refunds decrement units on the refund date
Active subscriptionsCount still active on the last day of the selected range, not a sum
RenewalsWooCommerce Subscriptions renewal orders

Cohort rows (first-order month by months later) are rebuilt whenever a range is aggregated. They feed the repeat-rate table on the Customers page.


Part 5When numbers update

  1. An order changes status, a refund is created, or (with Subscriptions) a subscription status or renewal fires.
  2. That calendar date is marked dirty. This write does not query orders.
  3. Once a day, the scheduled job rebuilds yesterday and the two days before, plus any older dirty day on its own. It does not scan the days in between.
  4. The dashboard reads the snapshot tables. It does not scan orders when you change the date range.

Rebuild history rewrites the saved history window, ending yesterday, in 14-day chunks. The dashboard asks first. It replaces the stored totals for that window and does not include today. Use it after an import, or if you suspect the cache drifted. It is a manual rebuild, not a schedule. Only Administrators see the button. Shop Managers can read the report and cannot queue a rebuild.

Import progress

The progress bar on the Analytics Core screen while a history import is running, for example 8 of 27 complete.

Drop a screenshot here


Part 6Light and dark

Default is light: an off-white canvas, white cards, and blue and purple chart series.

Dark mode is a first-class theme, not inverted CSS. The choice is saved per browser, not as a WordPress setting. A small boot script applies the saved theme before the dashboard paints, so there is no flash of the wrong colours.

Analytics Core Customers page in dark theme, RFM as of yesterday
Customers in dark mode: RFM as of yesterday.

Where everything lives

TaskWhere
DashboardAnalytics Core (top-level admin menu)
History window and daily job timeWooCommerce → Settings → Analytics Core
Rebuild historyDashboard ribbon or WooCommerce → Settings → Analytics Core. Administrators only
Import batchesWooCommerce → Status → Scheduled Actions
ThemeLight / Dark in the dashboard ribbon
CSV exportExport in the ribbon, plus the Offers tables

For developers

Snapshot tables are created with dbDelta and prefixed msdk_analytics_: daily totals, products, cohorts, coupons, categories, locations, repeat timing, first product, order facts, order items, and customer RFM. Deleting the plugin drops those tables and its options.

REST

Read routes need view_woocommerce_reports (Administrators and Shop Managers). POST /backfill needs manage_options. Cookie plus X-WP-Nonce; the dashboard uses apiFetch with the wp_rest nonce.

GET  /wp-json/msdk-analytics/v1/dashboard?range=30d
POST /wp-json/msdk-analytics/v1/backfill
     { "start": "2026-03-27", "end": "2026-09-23", "chunk": 14 }

range accepts yesterday, 7d, 30d, 90d, 12m, or custom.

WP-CLI

wp analytics-core aggregate
wp analytics-core aggregate --start=2026-03-27 --end=2026-09-23

A seed command exists for Local and staging sites. Do not run it on a live catalogue: it creates real completed orders.

ItemValue
Admin screenadmin.php?page=msdk-analytics-core
Daily jobmsdk_ac_daily_reconcile (Action Scheduler)
Dirty dates optionmsdk_ac_dirty_dates
REST namespacemsdk-analytics/v1
Text domainmsdk-analytics-core

WordPress 6.0+, PHP 8.2+, WooCommerce 8.0+.


Need help?

Questions about setup, a number that looks off, or a WooCommerce conflict: contact us. You talk to the people who built Analytics Core.