7 mistakes store owners make with their numbers (and how to avoid them)

The most common mistakes store owners make with their numbers are comparing an unfinished period with a finished one, comparing seasonal months instead of the same period last year, mixing net, gross and total sales, forgetting how refunds are dated, trusting incomplete data, reading big percentages on small numbers, and treating revenue as profit.

None of these needs a spreadsheet to fix. Each section below shows the mistake with a small example, how to spot it in WooCommerce, and the fix. They apply whether you read the reports yourself or ask an AI, because an AI answers the question you give it, framing and all.

1. Comparing a partial period with a full one

The mistake: on the 10th, you look at "this month" against "last month" and see sales down 65%.

Say you sold $9,000 last month. Ten days into this month you're at $3,150. That looks like a collapse, but you're on pace for roughly $9,450 over the month, slightly ahead.

The fix: compare the same number of days. In the date picker, set the 1st to the 10th of this month and compare with the 1st to the 10th of last month. For weekly reviews, only compare complete Monday-to-Sunday weeks. The guide on comparing two date ranges shows how.

2. Comparing seasonal months with each other

The mistake: "December was up 40% on November, great month." Almost every store's December beats its November. And January will look like a disaster against December.

The fix: compare with the same period last year (Compare to › Previous year). That shows real growth, with the seasonal swing taken out. If your store is too young for that, compare with a stable baseline such as a four-week average, and expect the seasons to move it.

3. Mixing net, gross and total sales

The mistake: comparing this month's "sales" from one place with last month's "sales" from another, where one is net and the other is total.

WooCommerce uses three figures:

A store that switched to free shipping will see total sales drop even if net sales held steady. A store running heavier coupons will see gross sales rise while net sales doesn't.

The fix: pick net sales for tracking and use it everywhere. More in net sales vs gross sales vs total sales.

4. Forgetting that refunds are dated on the refund date

The mistake: a strong October turns weaker when you look again in November, or November looks soft for no reason.

WooCommerce Analytics records a refund as a "Return" on the date the refund was made, not the order date. So a big October sale followed by refunds in early November lowers November's net sales. Your Orders list, which shows orders by the date they were placed, tells a different story.

The fix: when a month looks oddly weak, check the Returns column in Analytics › Revenue first. After a sale, wait a few weeks before judging it, so most refunds have landed. See returns for how Analytics counts them.

5. Trusting data that isn't complete

The mistake: reading a report that's missing orders.

Three things cause it:

• Excluded statuses. Analytics leaves out orders whose statuses are listed under Analytics › Settings. If you use a custom status, its orders may not be counted.
• Analytics hasn't caught up. New orders reach Analytics in the background, so the last little while can be missing.
• Historical data never imported. Stores that added Analytics later may be missing older orders until someone runs Import historical data.

Attribution has its own version: orders placed before order attribution was turned on, or where tracking was blocked, show as Unknown. A rising "Unknown" share isn't a new channel.

The fix: before any review, compare last week's order count in Analytics › Revenue with the Orders list. If they're far apart, find out why first. The guide on why WooCommerce Analytics numbers don't match your orders lists the causes.

6. Reading big percentages on small numbers

The mistake: "Instagram orders up 200%." From 2 orders to 6.

Small counts swing wildly from week to week on chance alone. A product that sold 3 units last week and 9 this week may not be trending at all.

The fix: always read the count next to the percentage. Wait for several weeks in the same direction before acting on small numbers, or group them into a longer period (a month instead of a week). An AI that gives you "up 200%" without the counts is hiding the most important part, so ask for both.

7. Treating revenue as profit

The mistake: "Net sales up 25%, so we made 25% more." If the increase came from a 30%-off sale, heavier ad spend, or free shipping you paid for, profit may have gone down.

Say you sold $10,000 of products at a 50% gross margin: $5,000 left after product costs. A month later you sell $12,500, but with a 20% discount on most of it and $1,000 more in ads. Your margin is now much thinner and the extra ad spend comes off the top, so you may have kept less than before.

The fix: track profit separately, at least monthly. That needs a cost for each product, shipping costs, payment fees and ad spend. WooCommerce has a Cost of Goods Sold feature you can turn on under WooCommerce › Settings › Advanced › Features, and the WooCommerce profit reporting guide explains the rest.

How Askshelf helps (and where it doesn't)

Askshelf reads through WooCommerce Analytics, so it uses net sales, counts the same order statuses, takes refunds out and uses your store's time zone. Each answer lists the lookups it ran, with their date ranges, so you can see whether it compared like with like.

It can help with mistake 7 up to a point. With Cost of Goods Sold on and a cost on each product, its profit lookup returns gross profit and margin for a date range, compared with an earlier one, so you can see whether a bigger month earned more or just sold more. It doesn't know shipping costs, payment fees or ad spend, so it stops at gross profit. And it can only answer the comparison you ask for, so mistakes 1 and 2 are still yours to avoid in how you phrase the question.

To check any AI's figures against your reports, read how to check an AI's answers about your store. For a routine that avoids most of these traps by design, see the weekly WooCommerce reporting checklist, and for the wider picture, using AI to analyze your WooCommerce store. The sales reporting use case shows what Askshelf answers about sales.