In this article
- What a CEO Odoo dashboard should show
- The African multi-entity reporting problem
- How to build the CEO KPI pack in Odoo
- 1. Confirm the Odoo version and data scope
- 2. Audit the source data before designing charts
- 3. Build the underlying views in Odoo Spreadsheet
- 4. Add global filters that match executive decisions
- 5. Set access and record rules before publishing
- 6. Use a snapshot for the external board pack
- Two practical examples
- Dashboard controls that boards should require
- When a dashboard is worth the investment
- Frequently Asked Questions
- Is an Odoo dashboard a separate business intelligence warehouse?
- Can a CEO view several companies in one Odoo dashboard?
- Does a shared Odoo dashboard update after it is sent to the board?
- Which KPIs should be on the first CEO dashboard?
serpa.africa · keyword: Odoo dashboard
Meta description: Build an Odoo dashboard for real-time CEO visibility across finance, sales, inventory and operations, with controls for multi-entity African reporting.
A CEO opens the monthly board pack and sees a healthy revenue figure. The finance lead then points out that a major customer is 90 days overdue, a branch has stock it cannot sell, and a supplier commitment has not yet reached the cash forecast.
An Odoo dashboard can put those connected facts in one executive view, provided the underlying Odoo ERP data is complete, posted correctly and localised for each entity. For African groups, the issue is rarely a shortage of reports. It is the time spent reconciling different entities, currencies, tax treatments and operating teams before the board can act.
At Serpa, we design CEO KPI packs to answer the questions that affect cash, margin, delivery and control. Odoo Dashboards in version 19.0 provides interactive views built on Odoo Spreadsheet. It is not a separate business intelligence data warehouse. The dashboard displays data from the Odoo applications your teams already use, and that data refreshes when the dashboard is opened or refreshed.
What a CEO Odoo dashboard should show
The right pack is deliberately small. A CEO needs an exception-led view that can be filtered by company, branch, period, sales team, product or channel, then investigated by the responsible executive.
We normally begin with the following measures.
| Executive area | Core KPI | What it helps the CEO decide | | Revenue and pipeline | Revenue, sales pipeline and conversion position | Whether demand supports the operating plan and where sales action is required | | Profitability | Gross margin and profit and loss | Whether growth is producing acceptable profit after direct costs | | Cash control | Cash flow, aged receivables and aged payables | Whether collections, supplier commitments and available cash are aligned | | Inventory | Inventory value and stock availability | Whether capital is tied up in stock or service levels are at risk | | Delivery | Order fulfilment and project delivery | Whether customer promises are being met and where work is delayed | | Procurement | Purchase commitments | Whether approved purchasing will create a future cash requirement | | People | Workforce metrics | Whether staffing levels match the revenue and delivery workload | Odoo standard accounting reports include Profit and Loss, Executive Summary, Aged Receivable, Aged Payable and Cash Flow Statement. We use these recognised accounting views as the starting point because finance teams can audit the figures back to posted transactions.
A dashboard should not show every available metric. If an executive cannot explain what action follows when a KPI moves, remove it. Visibility without a decision owner becomes another report that is reviewed too late.
The African multi-entity reporting problem
There is no Africa-wide statutory KPI threshold, reporting form, regulator, filing deadline or penalty for an Odoo dashboard. Reporting obligations remain country-specific as of September 2026. This matters when a group has entities in different African jurisdictions.
A group CEO may want consolidated revenue and cash visibility, but a Kenyan entity, a Zambian entity and a South African entity cannot simply be treated as interchangeable reporting units. Each entity may require its own tax localisation, chart of accounts, currency configuration and statutory-reporting treatment. A single group dashboard can compare performance, but it should not flatten those local controls.
Three practical rules follow:
1. Filter by legal entity before comparing performance. A company filter lets the CEO move from group position to an individual entity. This matters because a strong group number can conceal a branch-level collections or fulfilment problem.
2. Keep country-specific accounting and tax configuration intact. Do not use one tax treatment or chart of accounts across African entities merely to make a dashboard look uniform. The reporting layer should consolidate management views without replacing local compliance configuration.
3. Define the group currency method before publishing board figures. A comparison is only useful when the board knows whether values are shown in entity currency or translated for group management reporting. Finance must approve the method and the period applied.
Tax localisation is part of the Odoo ERP implementation, not a dashboard formatting task. A dashboard can expose figures quickly, but it cannot correct an invoice posted to the wrong tax position or an unapproved journal entry.
How to build the CEO KPI pack in Odoo
1. Confirm the Odoo version and data scope
Odoo 19.0 documentation describes Dashboards as a dedicated application built on Odoo Spreadsheet, with interactive data, global filters, user-group access and snapshot sharing. Confirm the customer’s Odoo version before specifying these features, because feature availability depends on the deployed version.
Then agree the reporting scope in writing: legal entities, branches, reporting currency, financial period, exclusions and the source application for each KPI. This is the step teams often skip. Without it, sales may use order dates while finance uses invoice dates, producing two defensible but conflicting revenue figures.
2. Audit the source data before designing charts
Start with a posting and master-data review across Accounting, Sales, Inventory, Purchase, Projects and Employees. Check who can post invoices, validate stock movements, approve purchase orders and close project stages.
Do not call a dashboard a single source of truth when master data, integrations or posting discipline are weak. It is only a view of the records beneath it. If receivable ageing excludes invoices held in draft, the dashboard may be technically correct while cash exposure is understated.
3. Build the underlying views in Odoo Spreadsheet
Odoo Spreadsheet can insert list, pivot and graph views from Odoo applications. Teams can calculate custom metrics, present them in tables or charts, then use File and Add to dashboard to convert the spreadsheet into a dashboard.
Use standard reports where a finance control already exists. For example, build the cash section around the Cash Flow Statement and aged reports, then add management calculations only where the business definition has been approved. A custom metric should have an owner, a formula and a stated source model.
4. Add global filters that match executive decisions
Apply global filters for company, country, branch, period, sales team, product or channel. Odoo can place lists, pivots and charts from different applications and models in the same spreadsheet dashboard.
A useful CEO view might filter a group dashboard to one branch, then show the branch’s order fulfilment, available stock, aged receivables and purchase commitments together. That is more useful than asking operations, finance and sales to send separate extracts after a board meeting.
5. Set access and record rules before publishing
Dashboard access can be assigned by user group and, in multi-company databases, by company. However, dashboard visibility does not override permissions on the underlying records.
This is a control point, not a technical footnote. A CEO may have access to the dashboard but lack access to the records behind part of a consolidated number. The result can be incomplete group reporting that looks credible on screen. During an Odoo ERP implementation, we map executive reporting access alongside accounting, sales and inventory record rules.
6. Use a snapshot for the external board pack
Odoo supports sharing a frozen dashboard snapshot with internal or external recipients. Use that option when issuing a board pack externally.
A shared snapshot is not a live dashboard. Label the reporting date and time, retain the approved pack, and make clear that later operational postings will not alter what directors received. This creates an auditable reporting point.
Two practical examples
Take a distributor with four entities, central procurement and branch-level sales teams. The CEO sees group revenue rising but cannot explain why cash is tightening. The team builds a filtered Odoo dashboard that places aged receivables, purchase commitments, inventory value and cash flow beside revenue and gross margin. The review identifies that two branches are holding slow-moving stock while a large customer balance is overdue. The business would have benefited from agreeing a common receivables escalation rule before building charts, because the dashboard revealed the issue but did not create the collection process.
Consider a retailer with twelve staff and a US$40,000 monthly payroll. This is an illustrative case, not a Serpa client example. The owner wants a daily dashboard but the accounting team posts supplier invoices only at month-end, while stock adjustments are approved irregularly. A daily cash and margin view would therefore give false precision. We would first improve posting cut-offs and stock approval discipline, then use the Odoo dashboard for weekly operating review and monthly board reporting. The key judgement is simple: do not invest in a live executive pack until the underlying transactions are current enough to support the decisions being made.
Dashboard controls that boards should require
A CEO dashboard should be auditable, not merely attractive. We recommend documenting the following controls before launch.
| Control | Practical requirement | Why it matters | | KPI definitions | Define each measure, source application, calculation and accountable owner | The board can challenge a figure without debating what it means | | Data cut-off | State the period and posting cut-off for each board pack | Late postings can materially change cash, margin and working-capital views | | Entity treatment | Document companies included and the reporting-currency approach | Group comparisons need consistent boundaries | | Access matrix | Test user groups, company access and underlying record rules | A dashboard can otherwise be incomplete for the person relying on it | | Change control | Duplicate standard dashboards before customising them | Odoo notes that standard dashboards can be reinstalled on version upgrade | | Snapshot archive | Retain the approved frozen board snapshot | Directors need a stable record of the figures considered | The most common mistake is editing a standard dashboard directly. Duplicate it first, then customise the copy. A version upgrade can reinstall standard dashboards, which can remove changes made directly to the original.
When a dashboard is worth the investment
If the CEO runs one small entity with a dependable monthly close and only a few decision-makers, begin with standard accounting reports and a disciplined monthly review. Do not build a broad custom Odoo business intelligence layer simply because dashboards are available.
A dedicated CEO KPI pack becomes worthwhile when the business has multiple entities, branches, material inventory, project delivery exposure or reporting delays caused by spreadsheet consolidation. The ROI comes from reducing manual reconciliation and making exceptions visible while management can still act. It does not come from adding more charts.
For larger groups, an ERP readiness audit should test integration quality, master-data ownership, multi-company configuration, tax localisation, approval workflows and the ability to trace a dashboard number to a posted record. Unified systems for enhanced productivity require shared operating definitions as much as they require software.
Frequently Asked Questions
Is an Odoo dashboard a separate business intelligence warehouse?
No. In Odoo 19.0, Dashboards centralises data from Odoo sources into interactive KPI views built on Odoo Spreadsheet. It should be positioned as an executive reporting layer within Odoo ERP, not as a separate data warehouse.
Can a CEO view several companies in one Odoo dashboard?
Yes, provided the database is configured for multi-company reporting and the user has the necessary company and underlying record access. Use company-level filters and test what the CEO can actually open before relying on consolidated figures.
Does a shared Odoo dashboard update after it is sent to the board?
A dashboard refreshes when opened or refreshed. A shared snapshot is frozen, so it should be used for an external board pack where directors need a fixed reporting record.
Which KPIs should be on the first CEO dashboard?
Start with revenue and pipeline, gross margin and profit and loss, cash flow, aged receivables, aged payables, inventory value and availability, order fulfilment, purchase commitments, project delivery and workforce metrics. Add a metric only when its owner and required action are clear.
Request a Consultation to assess whether your Odoo ERP data, access controls and localised multi-entity configuration are ready for an executive KPI pack.