SellerLegend

Appearance

Sales Statistics -- Combined Product × Period Grouping ​

April 21, 2026

Overview ​

The Sales Statistics Dashboard now supports combined product × period grouping — one row per product dimension per period bucket. This makes month-over-month and year-over-year analysis per SKU, ASIN, brand, or product group far easier: pick your two axes and the dashboard returns a single grid you can sort, filter, and export.

What's Changed ​

New inline grouping dropdowns ​

The dashboard title bar has been rebuilt with three inline dropdowns replacing the old pop-up selector:

  • By <Product dimension> — None, Product, SKU, ASIN, Parent ASIN, Brand, Product Group.
  • By <Period> — None, Day, Week, Month, Quarter, Semester, Year.
  • Table / Chart — switch between tabular report and the daily chart.

Picking both a product dimension and a period produces the new combined view.

Combined view ​

  • One row per (product-dimension, period) pair — e.g. one row per ASIN per Month.
  • All the usual metrics are present: revenue, units, profit, ROI, margin, ACOS, TACOS, PPC spend, sessions, conversion rate, etc.
  • Works with any product dimension and any period bucket.

API & MCP support ​

Both surfaces accept a new optional period_by parameter alongside view_by=product:

  • API GET /sales/statistics-dashboard — see the updated Sales endpoints.
  • MCP get-sales-statistics tool — pass period_by alongside view_by="product".

Scheduled / saved reports now persist the period axis too, so you can set up a recurring "ASIN × Month" CSV export.

What Is Not Available in Combined View ​

The following columns and behaviors only make sense in single-axis reports and are not populated in the combined view:

  • Velocity, out-of-stock days.
  • Inventory snapshots (in-stock, inbound, reserved, local inventory, warehouse).
  • Buybox price, sales rank.
  • Row-over-row trend indicators (Green/Red up/down arrows).

Why This Matters ​

Previously, producing a "revenue per ASIN per month" export meant setting up 12 separate monthly date ranges and stitching the results together. The combined view does it in a single request.

Backward Compatibility ​

Fully backward compatible:

  • Every existing URL (view_by=product&group_by=SKU, view_by=date&group_by=Month, view_by=chart&group_by=Day) continues to work verbatim.
  • Every existing API and MCP request is accepted unchanged.
  • Every pre-saved / scheduled report continues to replay identically.

The combined view is strictly opt-in via the new dropdowns or the new period_by parameter.

Impact ​

No action required. If you've been building MoM / YoY pivots manually, the combined view should save you significant time. API and MCP callers can start passing period_by immediately; older clients continue to work without changes.