Merchlint
Available now
Next, in this order
  • EspañolES
  • FrançaisFR
  • ItalianoIT
  • PortuguêsPT
  • NederlandsNL
  • SvenskaSV
  • TürkçeTR

A language shows up here once its pages are actually written. Nothing on this site is machine-translated, except a few German and Spanish pages that no native speaker has reviewed yet.

Install free Install
← All checks

It sold all year, and now nobody can buy it

Products that sold over the past twelve months and are out of stock today, listed with what each one earned, so the list starts where the money is.

Group
Money
Confidence
F — fact read directly from your store
Name on the plugin screen
They were selling, now nobody can buy them
Included in
the free plugin
Updated
Code
A1

The symptom

There is no symptom. That is the whole problem.

A product that sold steadily for a year goes out of stock, and nothing anywhere tells you. No error, no notice, no email. Orders for it just stop, and a store that gets orders every day does not notice that one product has dropped out of them.

You find out months later, usually because a customer asks.

What it costs

This is the check the whole plugin exists for, and the reason is arithmetic: you already know what the product is worth. It earned a specific amount over the past twelve months. Today it earns nothing. The difference is not a projection. It is the product’s own track record.

It stays hidden because WooCommerce keeps the two halves of the answer on separate screens:

  • Analytics → Stock lists everything that is out of stock, including every product that never sold a single unit. On a large catalog that is thousands of rows, and nobody reads it twice.
  • Analytics → Products lists what sold. With stock management on, it also shows each product’s stock status, but you can’t sort or filter by it, so the out-of-stock bestsellers are scattered through a long table.

What you want is the overlap: products that sold and can’t be bought now. No WooCommerce screen gives you that list, no plugin in the WordPress.org directory showed it when this one was written, and it is the one list a store owner actually acts on.

How to check it yourself

Two steps. First, what earned money in the last twelve months. WooCommerce keeps an analytics table for exactly this, and it is far faster to query than the orders themselves:

wp db query "SELECT product_id, SUM(product_net_revenue) AS revenue, SUM(product_qty) AS qty
  FROM wp_wc_order_product_lookup
  WHERE date_created > DATE_SUB(NOW(), INTERVAL 12 MONTH)
  GROUP BY product_id
  ORDER BY revenue DESC"

Then check the top of that list as it stands today. Ask WooCommerce rather than the database: a variable product can be marked out of stock while some of its variations still sell, and a query does not see that.

wp eval '
foreach ( [123, 456, 789] as $id ) {          // IDs from the query above
    $p = wc_get_product( $id );
    if ( ! $p ) { echo "$id: deleted\n"; continue; }
    if ( "publish" !== $p->get_status() || $p->is_in_stock() ) { continue; }
    if ( $p->is_type( "variable" ) && $p->child_is_in_stock() ) {
        echo "$id: marked out of stock, but a variation is in stock\n";
        continue;
    }
    printf( "%d\t%s\n", $id, $p->get_name() );
}'

The second message is a different problem with its own check: Sold out, but its variations are in stock.

How to fix it

  1. Work from the top of the money column and stop early. Three products restocked is a result you can measure this week. Two hundred products reviewed is a week with nothing to show.
  2. Decide; don’t restock on reflex. Each product has three honest answers: bring it back, replace it with its successor and redirect the old address, or take it out of the catalog so it stops soaking up traffic. See Selling, but hidden from the catalog for when hiding a product is the right call.
  3. Check whether anyone decided at all. A product that went out of stock on the day of an import is a different story from one that sold out.
  4. Then look at what it points to. A supplier who stopped delivering, a variation that was deleted, a stock sync that hasn’t run since spring: the finding is often a symptom of something bigger.

When it’s a false alarm

  • Lines you discontinued on purpose. Keeping them in the catalog for order history is correct. Hide the finding and it stays hidden across scans and updates.
  • Seasonal goods in the off-season.
  • One-off or limited items: vintage, handmade, one-of-a-kind stock. They sold once and were never meant to come back.
  • Products replaced by a successor SKU. The revenue moved to the new product, and the old one is rightly gone. It needs a redirect, not a restock.
  • Products sold only for free, or with every sale refunded. From version 0.3.5 Merchlint skips them. A gift added to orders at a price of 0 is the usual case, and nothing was at stake anyway.
  • A product marked out of stock whose variations can still be bought. From version 0.3.5 it goes to Sold out, but its variations are in stock instead. It can be bought, so it does not belong on this list.

How Merchlint finds it

Two stages, and the split matters more than it looks.

First, the analytics table supplies the candidates. wc_order_product_lookup has one row per product per order, with the net revenue already worked out. Adding up twelve months of sales by going through orders one by one, on a store with twenty thousand orders, is not something you do while somebody waits.

Then WooCommerce confirms each candidate before anything is reported. Merchlint loads the product with wc_get_product() and reports it only if WooCommerce itself says it is out of stock. The tables only pick the candidates. Since version 0.3.5 the variations count too: a variable product counts as unavailable only when none of its variations can be added to the cart. A product on backorder still takes orders, so it is not on this list. Products whose sales earned nothing in the period (sold only at a price of 0, or every sale refunded) are skipped.

This check is about stock. A product that is in stock but can’t be bought because it has no price is Product with no price or a zero price.

The consequence is worth stating plainly, because it is a deliberate design choice: if the underlying schema changes, this check can miss a finding, but it can never invent one. Silence under-reports; it does not lie. On a store where the analytics table is empty or turned off, the check says it could not run rather than reporting zero problems.

Confidence: F—fact from the database, confirmed a second time through WooCommerce’s own API.

Revenue is never added up across currencies. A store selling in euros and dollars gets a separate figure for each, with the currency shown. Adding them without an exchange rate would mean inventing a number, and one invented number costs the whole report its credibility.

Run this check on your store

Doesn't match what you see in your store? Email us—we read every message. contact@merchlint.com