Build an ERP Dashboard That Actually Drives Decisions (Not Just Charts)

What Is an ERP Dashboard?

An ERP dashboard is a visual, role-based interface within an ERP system that aggregates key data, metrics, and KPIs from integrated business functions — finance, supply chain, inventory, procurement, HR, and order management — into a single consolidated view. It acts as a central control panel, refreshed in real or near-real time, that turns siloed operational and financial data into visual patterns and alerts.

The point is decision support, not decoration. A well-built ERP dashboard tracks performance against goals and surfaces issues early: inventory shortages, cash-flow gaps, and fulfillment delays become visible alerts instead of month-end surprises. As Panorama Consulting notes, role-based customization is a must-have, because a CFO, a warehouse lead, and a production manager need fundamentally different information on the same platform.

It helps to draw one boundary clearly. ERP dashboards focus on internal, back-office operations and resource optimization (financials, supply chain, production, procurement). CRM dashboards focus on external, front-office customer interactions (sales pipeline, leads, opportunities, campaigns, service). The data, the audience, and the decisions are different. If you are mainly tracking the pipeline, see our CRM dashboard guide; this article is about the back office.

ERP Dashboard vs CRM Dashboard: What Actually Changes

Both tools share the same DNA — single-screen, KPI-driven, role-scoped — but the content diverges sharply. Per IBM's ERP-vs-CRM framing, ERP dashboards show finance, inventory, orders and fulfillment, production, procurement, and HR/payroll data, while CRM dashboards show leads, opportunities, contacts, campaigns, support cases, and customer interactions.

The audience flips too. ERP dashboard users are typically finance, operations, supply chain, procurement, and executives. CRM dashboard users are primarily sales, marketing, and customer service teams. A useful SME rule of thumb: if the metric would interest your controller or plant manager, it belongs on the ERP dashboard; if it would interest your head of sales, it belongs on the CRM dashboard.

Some metrics, revenue chief among them, appear on both. That is fine, but the slice differs. ERP shows revenue as recognized, posted, and reconciled finance. CRM shows revenue as forecast, pipeline-weighted, and committed-by-rep. The two should reconcile at quarter-end, and where they do not, that gap is itself a metric worth tracking.

Which KPIs Belong on an ERP Dashboard?

KPI selection is where most ERP dashboard projects go wrong, so it gets its own section. The lists below are representative, drawn from the pre-built Power BI template apps Microsoft ships for Business Central and from Odoo's standard warehouse/operations dashboards. Exact KPIs vary by product, version (cloud vs on-prem), configuration, and industry, so treat these as a starting set, not a universal checklist.

Notice what is missing from these lists: vanity metrics. The 2Wtech analysis of common ERP KPI failures is blunt on this point. Tracking shipments instead of on-time-in-full (OTIF), or raw revenue without margin or cycle-time context, is the classic vanity trap. Every KPI should pass a single test: "What decision will this help someone make?" If the answer is "none, it just looks impressive," drop it before it ever reaches a chart.

• →Finance: revenue, net profit, net profit margin, gross profit margin, EBITDA, current ratio, quick ratio, cash ratio, ROE, ROA, Days Sales Outstanding (DSO), Days Payable Outstanding (DPO), Days Sales of Inventory (DSI), and the Cash Conversion Cycle (CCC), per Business Central's Finance Power BI app.
• →Sales (back-office view): gross profit and gross profit margin, sales by item/customer/salesperson/location, sales vs. budget variances, customer retention, daily sales heatmaps, and period-over-period growth, per Business Central's Sales Power BI app.
• →Inventory and operations: on-hand and total available stock, supply vs. demand, ABC classification by sales amount, projected available balance, planned vs. finished production quantity, capacity utilization, work center load, production scrap, and on-time order completion.
• →Warehouse and logistics (Odoo reference): average delay in days, average lead time, fill rate (% delivered vs ordered), on-time operations %, and reserved stock % by quantity and value.

Design Rules for a Dashboard People Actually Use

Before any platform-specific build, the design principles are the same whether you run Dynamics 365, Odoo, SAP S/4HANA, or Oracle NetSuite. Stephen Few's foundational "Common Pitfalls in Dashboard Design" remains the practitioner reference: avoid inadequate context for data, excessively precise detail, inappropriate display media (think pie charts with too many slices), meaningless visual variety, poor arrangement, and decoration clutter.

1. 01
   Pick 5-7 outcome-linked KPIs per role

   SME best practice is to focus on 5-7 core outcome-linked KPIs per role plus a few leading indicators, prioritizing actionable metrics like OTIF, inventory turns, cash flow, quote-to-order time, and schedule adherence over vanity or lagging-only metrics. Resist KPI overload: when everything is a KPI, nothing is.

2. 02
   Apply the 5-second rule and inverted pyramid

   Big-picture KPIs at the top, details below. A user should grasp the state of the business in five seconds. Use white space, consistent alignment, and minimal semantic color (red = bad, green = good, used sparingly) so the eye lands on the exceptions, not the chrome.

3. 03
   Match the chart to the question

   Line for trends, bar for comparisons, table for precise lookups. Avoid 3D charts, donut charts with more than five slices, and gauges that consume screen real estate for a single number. If a single number matters, a big number tile is more honest than a speedometer.

4. 04
   Pair lagging and leading indicators

   Revenue (lagging) paired with supplier on-time rate or first-pass yield (leading) gives proactive control. A dashboard of only lagging metrics tells you what happened too late to change it.

5. 05
   Review and retire KPIs quarterly

   Dashboards should evolve with shifting business priorities. Stale KPIs erode trust. Schedule a quarterly review and remove anything that no longer maps to a decision someone owns.

How to Build an ERP Dashboard in Dynamics 365 Business Central

Business Central's native path is the Power BI integration via an OData-based connector that exposes BC data through API pages and OData web services. BC online is pre-enabled, and since February 2022 Power BI reports for BC online have been sourced from a secondary, read-only database replica, so reporting load does not impact transactional performance.

Install the pre-built template apps from the Microsoft Marketplace for the functional areas that matter: 'Dynamics 365 Business Central - Finance' (the Financial Overview report, with the full ratio and cash-cycle KPI set above), 'Sales' (gross profit margin, sales by item/customer/salesperson, sales vs. budget, opportunity overview, customer retention, daily sales heatmaps), plus Inventory, Purchasing, Manufacturing, and Projects apps. A Power BI Pro license is required per user who installs, refreshes, or accesses the reports.

Run the 'Connect to Power BI' assisted setup in BC to configure calendar type, UTC offset, the date table range tied to your accounting periods, and report mapping. For Finance, map G/L account categories via Power BI Account Categories so the KPIs compute correctly; unmapped categories are the most common reason a freshly installed Finance app shows blanks.

Embed reports back into BC Role Centers and list pages via the Power BI reports FactBox. The embedded framework exposes AL objects like the 'Power BI Embedded Report Part' (page 6325) for developer customization, including filtering the embedded report to the record a user has selected. Use dimensions on G/L Entries for slicing by department, project, or region. Schedule refreshes in the Power BI service, and install/configure per company for multi-company deployments. For custom work beyond the templates, connect via the BC connector in Power BI Desktop, build your .pbix, and publish to a workspace.

How to Build an ERP Dashboard in Odoo

Odoo's native path is the Dashboards app (built on the spreadsheet_dashboard module), which constructs dashboards from Odoo Spreadsheets populated by live data sources: lists, pivot tables, and charts inserted from Odoo views, with global filters and drill-down to underlying records. Note that the full Dashboards app and Odoo Spreadsheet are Enterprise capabilities; Odoo Community has more limited dashboard options.

The workflow is deliberately modular. First, refine your source views — lists, pivots, graphs — in the relevant Odoo app (Inventory, Sales, Manufacturing, Accounting). Then insert that data into a spreadsheet via Actions > Spreadsheet > Insert list (from list views) or Insert in Spreadsheet (from pivot/graph views). Manipulate with formulas (Odoo-specific plus standard), build tables and charts on the front-end sheet, apply global filters that propagate across the dashboard, and convert the spreadsheet into a dashboard assigned to a section. Once converted, the dashboard is accessible only via the Dashboards app.

Use the pre-built standard dashboards (Sales, Projects, Warehouse, Leads) as starting points, but duplicate before heavy customization since standard dashboards are reinstalled on upgrades. For warehouse and operations, Odoo ships Warehouse Daily Operations (late deliveries, transfers to be assigned, a 7-day activity forecast) and Operation Analysis (average delay in days, average lead time, fill rate %, on-time operations %). The related Warehouse Metrics dashboard adds reserved stock % by quantity and value. Some of these dashboards are restricted to Inventory admin users by default, so plan access via user groups and multi-company scoping, respecting record rules and model permissions.

Complement the Dashboards app with Odoo Studio when you need richer source data. Studio is the low-code customization tool that adds fields, computed fields, models, views (list, form, pivot, graph, kanban), menus, and automations. It feeds the spreadsheets; it is not itself the dashboard builder. For personal collections of kanban/list/graph views (which are not spreadsheet-based), use 'My Dashboard' (the separate board module).

Dynamics 365 or Odoo: How to Choose Without Crowning a Winner

Because Flectic implements both, we do not crown a winner. The right choice depends on your stack, your reporting maturity, and where your users already live. Below is an honest branch, plus a side-by-side.

• →Choose Dynamics 365 Business Central if you are already in the Microsoft ecosystem (M365, Teams, Power Platform), your finance team lives in Excel and Power BI, you need a deep library of pre-built finance/operations KPIs out of the box, and your SME expects to embed analytics inside the ERP Role Center rather than in a separate tool.
• →Choose Odoo if you want dashboards native to a modular open-source suite, you prefer a spreadsheet-first authoring model that finance and operations leads can edit directly, you want one platform covering everything from warehouse and manufacturing to CRM and website, and you value a low-code Studio path to custom source data without a separate BI license. (Note: Odoo's spreadsheet-based Dashboards app is an Enterprise capability; Odoo Community has more limited options.)
• →Either way, the design rules above (5-7 KPIs per role, inverted pyramid, paired lagging/leading indicators, quarterly KPI review) apply identically. The platform changes the mechanics, not the discipline.

The Mistakes That Sink an ERP Dashboard

Most ERP dashboard failures are design and governance failures, not platform failures. The recurring patterns below come from practitioner sources (Panorama Consulting, UXmatters, 2Wtech, Projectline, Meegle) and reflect field experience rather than peer-reviewed research; their concrete claims — KPI names, mistakes, and design rules — are sound, but treat editorial opinion as opinion.

• →KPI overload: cramming dozens of metrics on one view creates noise and analysis paralysis. Teams end up tracking easy-to-measure items rather than the vital few. Cap each role at 5-7 outcome-linked KPIs.
• →Vanity metrics: tracking shipments instead of OTIF, or raw revenue without margin or cycle-time context. Every metric must answer "What decision will this help someone make?"
• →Ignoring data quality: inconsistent metric definitions across departments ("margin" or "inventory" calculated differently), duplicate records, and manual Excel exports produce "dueling spreadsheets" and erode trust. Agree definitions before you build charts.
• →One-size-fits-all design: a dashboard that tries to serve everyone serves no one. Role-based customization is non-negotiable for ERP.
• →Real-time/batch mismatch: real-time is ideal for operational alerting and live inventory but increases cost and system load; batch (common in legacy ERP) is cheaper for financial closes but introduces latency that pushes you into reactive management. Match the refresh cadence to the decision cadence.