Revenue
Commerce Sales Dashboard
A commerce starter kit for revenue, conversion, AOV, and stock risk.
Recipe Workspace
Preview the layout, understand the KPIs, copy the starter
Review the dashboard at a practical desktop ratio first, then use the KPI rationale, code starter, and AI IDE prompt below.
Live Recipe Preview
Commerce Sales Dashboard
A commerce starter kit for revenue, conversion, AOV, and stock risk.
Live Recipe
Commerce Sales Dashboard
A commerce starter kit for revenue, conversion, AOV, and stock risk.
Conversion
AOV
Stock risk
Revenue trend
ApexChartsProduct Command
RechartsRevenue
Sample data
Conversion
Sample data
AOV
Sample data
Watch List
Detail Table
Revenue
Sample data
18,420
상태Conversion
Sample data
34.8%
상태AOV
Sample data
$84.2K
상태Top
Four KPI cards
Middle
Primary trend and segment view
Bottom
Priority table and alerts
KPI Ingredients
Revenue
Revenue belongs in the primary row when an owner can act on it this week.
Alternative KPI: Revenue segment
Conversion
Conversion belongs in the primary row when an owner can act on it this week.
Alternative KPI: Conversion segment
AOV
AOV belongs in the primary row when an owner can act on it this week.
Alternative KPI: AOV segment
Stock risk
Stock risk belongs in the primary row when an owner can act on it this week.
Alternative KPI: Stock risk segment
Code Starter
Copy component starter
const metrics = [
{ label: "Revenue", value: "18,420", change: "+8.2%" },
{ label: "Conversion", value: "34.8%", change: "+2.1%p" },
{ label: "AOV", value: "$84.2K", change: "+12.4%" }
];
export function CommerceSalesDashboardPreviewCards() {
return <section className="grid gap-3 md:grid-cols-3">{metrics.map((metric) => <article key={metric.label} className="rounded-xl border border-zinc-200 bg-white p-4"><p className="text-xs font-bold text-zinc-500">{metric.label}</p><strong className="mt-1 block text-2xl font-black">{metric.value}</strong><span className="text-xs font-black text-emerald-600">{metric.change}</span></article>)}</section>;
}AI IDE Prompt
Paste into your AI IDE
Create a Commerce Sales Dashboard. Put KPI cards for Revenue, Conversion, AOV, Stock risk, trend and segment charts, a priority table, and empty/loading/error states.
Bundle Preview
3 screens included
Preview the overview, detail, and settings screens as SVG before downloading the ZIP source.
Decision System
Why this dashboard should exist before it is designed
AdSense-quality pages need original explanation, not only screenshots. This section documents the decision, data model, failure patterns, and implementation alternatives.
Operating decision
Commerce Sales Dashboard answers this operating question: Is sales movement caused by traffic, conversion, AOV, or stock?. The primary row is not a vanity summary; it decides what an owner should do this week.
The recipe is designed for Commerce PM, Early product builders who need to choose data definitions, chart priority, and bottom-row actions quickly.
Data sources and event definitions
- Orders, checkout events, catalog, inventory table
Before implementation, define event names, owner, refresh cadence, and missing-data behavior for each source.
Required KPIs and removal rules
Revenue
Revenue belongs in the primary row when an owner can act on it this week.
Alternative or removal signal: Revenue segment
Conversion
Conversion belongs in the primary row when an owner can act on it this week.
Alternative or removal signal: Conversion segment
AOV
AOV belongs in the primary row when an owner can act on it this week.
Alternative or removal signal: AOV segment
Stock risk
Stock risk belongs in the primary row when an owner can act on it this week.
Alternative or removal signal: Stock risk segment
Common failure patterns
Treat isolated movement in Revenue as a signal to inspect data definitions or operating bottlenecks.
Treat isolated movement in Conversion as a signal to inspect data definitions or operating bottlenecks.
Treat isolated movement in AOV as a signal to inspect data definitions or operating bottlenecks.
Treat isolated movement in Stock risk as a signal to inspect data definitions or operating bottlenecks.
Alternative layout
For an MVP, keep Four KPI cards. As data matures, expand Primary trend and segment view into segment comparison or cohort analysis.
Implementation Blueprint
KPI audit protocol before implementation
Use this table before designing the UI. Without a formula, review cadence, and action trigger, a dashboard can look polished but still fail to support an operating meeting.
Revenue
Revenue = source event aggregate / comparison baseline. Start segmentation by Revenue segment.
Daily morning
If Revenue moves more than 10% week over week, inspect the causal segment and action table together.
Conversion
Conversion = source event aggregate / comparison baseline. Start segmentation by Conversion segment.
Weekly review
If Conversion moves more than 10% week over week, inspect the causal segment and action table together.
AOV
AOV = source event aggregate / comparison baseline. Start segmentation by AOV segment.
After campaign end
If AOV moves more than 10% week over week, inspect the causal segment and action table together.
Stock risk
Stock risk = source event aggregate / comparison baseline. Start segmentation by Stock risk segment.
Monthly report
If Stock risk moves more than 10% week over week, inspect the causal segment and action table together.
Event and table starter
When starting from an AI IDE, lock event and table names first. It makes generated components and queries much more consistent.
commerce_sales.viewed
Source event for Revenue. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.
commerce_sales.converted
Source event for Conversion. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.
commerce_sales.risk_flagged
Source event for AOV. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.
commerce_sales.resolved
Source event for Stock risk. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.
Weekly review sequence
- 1Separate whether the Revenue movement is a real operating issue or short-term noise.
- 2Read it with Conversion to narrow the cause to acquisition, conversion, quality, or throughput.
- 3Use the bottom table to choose one owner, one segment, and one action for this week.
- 4At the next review, adjust the layout based on recovery after the action, not on the same chart alone.
Frequently asked questions
Which KPIs should Commerce Sales Dashboard prioritize?
Commerce Sales Dashboard should prioritize Revenue, Conversion, AOV, Stock risk. Keep Revenue in the primary row only when an owner can act on it this week.
What data sources are required?
Orders, checkout events, catalog, inventory table are the baseline sources. Define event names, refresh cadence, owner, and missing-data behavior before implementation.
Can this layout be used for an MVP?
For an MVP, start with Four KPI cards and Primary trend and segment view. Add bottom tables and alerts when operating actions become clear.
Which metrics should be removed?
Remove metrics that cannot trigger an action within one weekly review cycle, have unstable definitions, or behave like vanity metrics without adjacent context.
How should the AI IDE prompt be used?
Use the prompt as a starting point, then add real field names, table names, state UI requirements, and accessibility requirements for your project.
Market Pattern
Marketplace-proven dashboard pattern, rewritten for Dashcipe
This section documents the public preview pattern behind the layout and how Dashcipe changes it into original KPI guidance.
Observed pattern
Commerce templates group sales cards, product rankings, order status, and inventory warnings into one command view.
Dashcipe adaptation
Dashcipe turns product/order patterns into revenue cause analysis and action tables.
Originality guard
No product imagery or template-specific layout is reused.
Free Resources
What you can use for free
Use the KPI logic, layout, code starter, prompt, Figma SVG, schema, and tokens directly.
Starter Kit Files
What's inside this bundle
- overview.html
- detail.html
- settings.html
- src/page.tsx
- src/components
- src/data/sample-data.ts
- data/schema.json
- tokens.json
Compatibility
Built for fast implementation
- Next.js App Router
- Tailwind CSS
- Static HTML preview
- Figma SVG import
Implementation time: 35 min
Quality Checklist
Market-ready signals
- 3 production-style screens
- Reusable TSX components
- Empty/loading/error states
- Light/dark tokens
- Schema-backed sample data
Use this recipe when
- The vertical metrics are already roughly known
- You need to prioritize charts and tables quickly
Skip this recipe when
- No events or data definitions exist yet
- You only need a marketing landing page
Expert Notes
How a real operator should read these KPIs
These notes turn each metric into an operating decision, data source, and removal rule.
Commerce PM
- Why it matters
- Revenue is not a vanity number; it decides the next operating action.
- Failure signal
- Treat isolated movement in Revenue as a signal to inspect data definitions or operating bottlenecks.
- Data source
- Orders, checkout events, catalog, inventory table
- When to remove
- Remove it from the primary row if no owner can act within one weekly review cycle.
Commerce PM
- Why it matters
- Conversion is not a vanity number; it decides the next operating action.
- Failure signal
- Treat isolated movement in Conversion as a signal to inspect data definitions or operating bottlenecks.
- Data source
- Orders, checkout events, catalog, inventory table
- When to remove
- Remove it from the primary row if no owner can act within one weekly review cycle.
Commerce PM
- Why it matters
- AOV is not a vanity number; it decides the next operating action.
- Failure signal
- Treat isolated movement in AOV as a signal to inspect data definitions or operating bottlenecks.
- Data source
- Orders, checkout events, catalog, inventory table
- When to remove
- Remove it from the primary row if no owner can act within one weekly review cycle.
Commerce PM
- Why it matters
- Stock risk is not a vanity number; it decides the next operating action.
- Failure signal
- Treat isolated movement in Stock risk as a signal to inspect data definitions or operating bottlenecks.
- Data source
- Orders, checkout events, catalog, inventory table
- When to remove
- Remove it from the primary row if no owner can act within one weekly review cycle.
Recipe Flow
Move through recipes without returning to the list
Related Recipes
Similar dashboard recipes
Recipes from the same category or stack.
AdMob Revenue Dashboard
Is a revenue drop caused by traffic, pricing, or placement?
GA4 App Analytics Dashboard
Where do users come from, convert, or drop off?
Play Console Operations Dashboard
Where does store quality change appear first?