---
title: "Product Performance Dashboard: Margin by Category | OWOX"
canonical: "https://www.owox.com/dashboards/product-list-efficiency"
updated: "2026-11-16"
---

AI dashboard · products

# Product performance dashboard, built by AI on your Data Model

Net sales, profit and margin by category, product and price tier for an online store, against each category's target margin and the sales plan. Claude built it through OWOX MCP, and every number comes from a governed Data Mart, not from the AI's guess.

6 Data Marts · Built by Claude via OWOX MCP · Refreshed every Report run · [E-commerce data model](/data-models/e-commerce)

[Get Started Free](https://www.owox.com/app-signup) · or [book a call](https://calendly.com/owox/book-a-call)

## The dashboard

## What each view answers

## Six questions, one [Data Model](/data-models/e-commerce)

Every view answers one question an owner asks about what the store sells, starting with the plainest: are we selling more, at the margin we planned? Between them they read six Data Marts of the e-commerce Data Model, and each view names the ones it uses, so you can open the definition behind any number.

![The E-commerce data model: 12 Data Marts and how they join](https://cdn.owox.com/www/portfolio-management-data-model/e-commerce/diagram/10.svg/w=1600,fit=scale-down,format=auto)

[E-commerce data model · 12 Data Marts · 15 relationships · open it →](/data-models/e-commerce)

Summary

### Are we selling more, at the margin we planned?

Opens with what the numbers mean: how sales and margin moved, how much of what customers ordered never settled, how the categories sit against their targets and how each price tier's share of the catalog compares with its share of sales. Then net sales, net profit, net margin, units and booked sales against the same dates last year, month by month.

[Purchases](/data-models/e-commerce#mart-purchases)

[Orders](/data-models/e-commerce#mart-orders)

[Item revenue](/metrics/item-revenue)

Categories

### Which categories beat their target margin?

Each category's net sales, change on last year and net margin against the target margin on its own record, with the person accountable for it and the share of its booked sales that was cancelled or returned. Then the four categories month by month.

[Purchases](/data-models/e-commerce#mart-purchases)

[Products](/data-models/e-commerce#mart-products)

[Product Category](/data-models/e-commerce#mart-product-category)

[Orders](/data-models/e-commerce#mart-orders)

Products

### Which products make the profit?

The fifteen most profitable products, ranked by net profit rather than net sales, with their category and price tier. Then net sales by margin band, from thin to premium.

[Purchases](/data-models/e-commerce#mart-purchases)

[Products](/data-models/e-commerce#mart-products)

[Product Category](/data-models/e-commerce#mart-product-category)

[Average revenue per unit](/metrics/average-revenue-per-unit)

Price tiers

### What does each price tier bring in?

Each price tier's share of the catalog, of product page views and of net sales, side by side, with its margin and units. A tier the catalog is full of can bring in little, and the reverse.

[Purchases](/data-models/e-commerce#mart-purchases)

[Products](/data-models/e-commerce#mart-products)

[Pageviews](/data-models/e-commerce#mart-pageviews)

[Pages](/data-models/e-commerce#mart-pages)

Views

### Which products are viewed and never sold?

How many catalog products sold this year, how many were viewed and never sold, and how many product page views led nowhere, with the products viewed most for the fewest sales.

[Pageviews](/data-models/e-commerce#mart-pageviews)

[Pages](/data-models/e-commerce#mart-pages)

[Products](/data-models/e-commerce#mart-products)

[Purchases](/data-models/e-commerce#mart-purchases)

[E-commerce conversion rate](/metrics/ecommerce-conversion-rate)

Plan

### Are we on plan?

Net sales, orders and net sales per order against the sales plan, month by month, over the same days on both sides.

[Purchases](/data-models/e-commerce#mart-purchases)

[Orders](/data-models/e-commerce#mart-orders)

[Average order value](/metrics/average-order-value)

## Metrics

## The metrics on this dashboard

Each one is defined once in the Data Model and read the same way in every view. Follow a chip for what the metric means and how to calculate it.

Net sales · Net profit · Net margin · [Item revenue](/metrics/item-revenue)[Average revenue per unit](/metrics/average-revenue-per-unit)[Average order value](/metrics/average-order-value) · Target margin · [E-commerce conversion rate](/metrics/ecommerce-conversion-rate)

## Connected, not a snapshot

## An AI dashboard is only as true as what it reads

Most AI dashboards start from an exported file. That works until the second export.

On a CSV

### The AI guesses what counts as a sale, every time

One export sums every order line, the next keeps only completed orders, and the same months show $3.16M in one deck and $2.66M in another. The file goes to whoever has it, and it is out of date the moment it is saved.

![Two exports of the same orders giving sales of $3.16M and $2.66M](https://cdn.owox.com/www/content-marketing-dashboard/product-list-efficiency/body-vector/1-h7w54o.svg/public)

Which one goes to the board?

On your Data Model

### Net sales and margin are defined once, on the order line

Purchases counts revenue only for completed orders and carries cost and profit on the same line, and the target margin sits on each category's record, so every view judges a category against what it was meant to deliver.

![Purchases in the e-commerce Data Model, joined to Products, Product Category and Orders](https://cdn.owox.com/www/portfolio-management-data-model/e-commerce/diagram/10.svg/w=1600,fit=scale-down,format=auto#mart-purchases)

One definition, every view.

**Connecting the AI straight to the warehouse is not enough either.** A warehouse rarely holds the business context, so the AI still guesses what the numbers mean. The Data Model is where that context lives.

## How it is built

## From your warehouse to a dashboard in five steps

Your analyst does step two once. After that, anyone with access asks their AI for the dashboard they need.

1.  01 · Your warehouse · BigQuery · Snowflake · Databricks · Redshift · Athena · Your data stays where it is. OWOX runs on it and keeps no copy.
2.  02 · Data Model · Data Marts · joins · metrics · Your analyst defines once what net sales, a margin and a category mean.
3.  03 · OWOX MCP and API · governed · permissions · The only door the AI gets: the Data Marts it may read, nothing raw.
4.  04 · Claude or ChatGPT · your own AI · Ask for the dashboard in plain words. It builds it on the Data Model.
5.  05 · AI dashboard · Report · every run · Kept as a Report, refreshed every time it runs, like Sheets or Excel.

## Build yours

## Build this on your own data

Connect your warehouse, describe your business once, and let your AI build the dashboards your team asks for.

[Get Started Free](https://www.owox.com/app-signup) · or [book a call](https://calendly.com/owox/book-a-call)

## Links

Pages this page links to, on this site and on docs.owox.com. Where the page has a Markdown twin, its address follows the link.

- [E-commerce data model](https://www.owox.com/data-models/e-commerce) — /data-models/e-commerce.md
- [Get Started Free](https://www.owox.com/app-signup)
- [Item revenue](https://www.owox.com/metrics/item-revenue) — /metrics/item-revenue.md
- [Average revenue per unit](https://www.owox.com/metrics/average-revenue-per-unit) — /metrics/average-revenue-per-unit.md
- [E-commerce conversion rate](https://www.owox.com/metrics/ecommerce-conversion-rate) — /metrics/ecommerce-conversion-rate.md
- [Average order value](https://www.owox.com/metrics/average-order-value) — /metrics/average-order-value.md
