A dashboard with the numbers you actually check
Odoo's reporting tools (pivot tables, generic dashboards, spreadsheet exports) can answer almost any question, which is exactly why they're not built to answer one question fast. A focused dashboard skips the navigation and filters and shows the handful of numbers a specific manager actually looks at every day.
Management dashboard
This week
$18,420
Sales (7d)
34%
Margin
1,248
In stock
6
Open POs
Sales by day
Interactive demo: a sample weekly management view.
How it pulls data from Odoo
A dashboard like this reads from the same models Odoo's own reporting uses: sales analysis (sale.report), on-hand stock (stock.quant), open purchase orders (purchase.order), invoiced revenue (account.move), using Odoo's search and aggregation methods (search_read, read_group) rather than duplicating that data anywhere.
The aggregation and layout (this week's sales next to margin next to open POs) happens in the dashboard itself, so the numbers can be arranged exactly the way a specific manager thinks about the business, instead of however Odoo's generic dashboard widgets happen to group them.
What changes for management
Instead of opening three different Odoo apps and applying filters to answer "how's this week going," the answer is one glance. That matters most for numbers checked daily or multiple times a day: the small friction of navigating Odoo's full interface adds up, and often means the check happens less often than it should.
Typical scope and timeline
A first version (four to six KPIs, one refresh cadence, one audience) is what the starting price below reflects. Dashboards with role-based views (a warehouse manager sees different numbers than a sales manager), drill-down into underlying records, or metrics that require custom calculation logic beyond what Odoo already computes are scoped based on which of those apply.
Pricing
From $490
Starting price for a single-screen dashboard covering a handful of metrics from one or two Odoo modules. More metrics, multiple views, or role-based access are scoped separately.
Questions about this use case
Have a workflow like this?
Tell us what's slow or manual today. We'll tell you honestly whether a focused app is the right fix.
