AI dashboard

AI dashboard · e-commerce

Net Sales Review, Built by AI on Your Data Model

Net sales, profit, channels, customers, products and conversion for an online store. Claude built it through OWOX MCP, and every number comes from a governed Data Mart, not from the AI's guess.

9 Data MartsBuilt by Claude via OWOX MCPRefreshed every Report runE-commerce data model

The dashboard

What each view answers

Eight questions, one Data Model

Every view answers one question a sales, marketing or operations lead actually asks. All of them read the same twelve Data Marts of the e-commerce Data Model below, 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
E-commerce data model · 12 Data Marts · 15 relationships · open it →

Summary

How is the year going?

Net sales, profit, orders, sessions and conversion against the same dates last year, with each month's net sales next to its gross booked value, so cancelled and returned orders stay visible instead of quietly inflating the total.

PurchasesOrdersSessionsConversion rateSessions

Forecast

Where will the year land?

Cumulative net sales day by day against last year, and where the year closes at this pace. The demo store has no plan in its Data Model, so the page compares with last year and says so rather than inventing a target.

PurchasesOrders

Top 5

What moved net sales most?

The five biggest moves across channel, customer segment, category and country. Each cut splits the same revenue, so the moves overlap; the page tells you that instead of letting them look additive.

Traffic SourcesCustomersProduct CategoryCountries

Acquisition

Do the ad platforms tell the truth?

Net sales by channel, then each platform's spend against the revenue the store itself recorded, next to what the platform claims. Facebook claims 1,091 conversions; the store recorded 720 orders from it.

Unified Ad SpendSessionsTraffic SourcesROASFacebook ROASConversion value

Customers

Who buys, and where?

Net sales by customer segment and by market. Segment and geography are each defined once in the Data Model, so every view cuts revenue the same way.

CustomersCountriesOrders

Products

Which categories earn their keep?

Margin by category against the target margin each one is managed to, and the products that carry the year. Cost of goods sits in the Data Model, so profit is a field, not an estimate.

ProductsProduct CategoryPurchases

Conversion

Why did net sales move?

A bridge that splits the change into more sessions, a lower conversion rate and order value, then conversion by traffic type and device.

SessionsOrdersConversion rateAverage order value

Data

Can I trust these numbers?

The Data Model behind the page, how its Data Marts join, when the source tables last changed, and the checks that reconcile: segment revenue adds up to the total, and orders agree across Data Marts.

PurchasesOrdersSessions

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 salesNet profitConversion rateAverage order valueSessionsReturn on ad spendFacebook ROASConversion value

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 revenue means, every time

Each export is its own version of the truth, so two dashboards give two numbers. The file goes to whoever has it, and it is out of date the moment it is saved.

Two exported files showing 29 and 32 orders for the same days

Which one goes to the board?

On your Data Model

Net sales is one field, defined once by your analyst

Every view reads the same Data Marts, so the numbers agree across tabs and tools. Data Marts and Contexts decide who sees what, and the dashboard is a Report, refreshed every time it runs.

Purchases in the e-commerce Data Model, joined through Orders to Sessions and Customers

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. 01Your warehouseBigQuerySnowflakeDatabricksRedshiftAthenaYour data stays where it is. OWOX runs on it and keeps no copy.
  2. 02Data ModelData MartsjoinsmetricsYour analyst defines once what net sales, an order and a channel mean.
  3. 03OWOX MCP and APIgovernedpermissionsThe only door the AI gets: the Data Marts it may read, nothing raw.
  4. 04Claude or ChatGPTyour own AIAsk for the dashboard in plain words. It builds it on the Data Model.
  5. 05AI dashboardReportevery runKept 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.