Help CenterAnalytics / Sales analysis / Business analytics

In the store SKU and product SKU tabs, why do the rows' total orders add up to more than the total?

Page Analytics / Sales analysis / Business analyticsUpdated 2026-10-23
Short answer

When an order has two products, each row counts it once, so the rows add up to more than the total; the total row is the real number of distinct orders, the same as the trend cards. Cancellations and refunds are also counted per row: an order counts for a row only if that row's product was cancelled or refunded.

In short

Each row's "Total orders" = orders containing that product; an order with two products counts once on each row

The total row = the real number of distinct orders, the same as the trend cards

Example

An order buys A and B: row A counts 1 order and row B counts 1 order, so the rows add up to 2, while the total row counts 1.

Which row do cancellations and refunds go to?

  • An order counts as cancelled for a row only if that row's product was cancelled (the whole order or just that product); refunds work the same way.
  • The total row counts whole orders, like the trend cards: an order with only some products cancelled is not counted as cancelled there.

What about grouping by SPU?

Several SKUs of the same SPU in one order count as one order. Product SPU groups by the warehouse product's current SPU code, or its SKU code when it has none.

What is "Unmatched products"?

In the product SKU tab, order lines not yet matched to a warehouse product get their own row, so the rows still add up to the other tabs. Once matched, new orders go to that product.

"Valid units sold" vs "Units sold"

The default valid units sold excludes cancelled units; "Units sold", which includes them, can be added in column settings.