Odoo POS · intermediate · 8 min read
POS Reporting and KPIs
Measure Odoo POS performance: session reports, sales by store, basket metrics, payment mix, shrink indicators, identified customer rate, and dashboards for retail leadership.
Last reviewed 2026-07-30 · Estimated effort: 2–6 weeks typical implementation slice
Table of contents
POS reporting in Odoo draws from POS orders, sessions, and payments — giving store and HQ visibility into revenue, refunds, payment mix, and cashier activity when sessions close cleanly.
Useful KPIs include sales per store, average basket, units per transaction, identified customer rate, refund ratio, session close timeliness, and cash variance — aligned to roles from cashier to CFO.
Garbage in, garbage out: inconsistent configs, unclosed sessions, and offline sync delays distort metrics. Project planning should define reporting requirements before go-live.
Leadership buys POS expecting Monday-morning dashboards. Without agreed KPIs and close discipline, reports show gaps that finance manually fixes in spreadsheets.
This article defines practical POS metrics and data hygiene. Pair with loyalty for customer identification KPIs and project planning for reporting acceptance criteria.
POS orders capture lines, taxes, discounts, payments, and linked partners. Sessions bound orders in time and tie to cash control. Accounting entries flow from configured journals.
Reporting granularity depends on consistent store configs — mixed tax or payment setups across sites complicate consolidated views.
- ▸POS order: lines, refunds, partner link
- ▸Session: open/close, cash variance, responsible user
- ▸Payment method breakdown per session
- ▸Product and category sales via standard reporting
Daily sales versus target, transactions per hour, average basket, and refund count help managers coach staff without waiting for month-end.
Session close compliance — all registers closed same day — prevents orphaned orders from skewing trends.
Chain-wide sales by store, payment mix trends, margin by category when cost data exists, and shrink proxies from refund and void patterns.
Compare POS to ecommerce in Retail dashboards when omnichannel leadership needs one revenue picture.
Odoo native reports suit operational review. BI tools export via SQL or API for executive dashboards — define refresh cadence especially when offline sync batches orders.
Document metric definitions so store comparisons use the same filters and date boundaries.
- ✓Define KPI dictionary before go-live — names, formulas, owners.
- ✓Require same-day session close as store operating standard.
- ✓Review cash variance threshold alerts weekly during rollout.
- ✓Track identified customer rate if loyalty is strategic.
- ✓Reconcile POS sales to accounting weekly in hypercare.
- ✓Cross-link Retail when reporting spans store and web channels.
- !Reporting on open sessions that still accept orders.
- !Mixing test POS configs in production dashboards.
- !Ignoring offline sync delay when judging daily ecommerce ATP.
- !Different fiscal date cutoffs per store without documentation.
- !Building executive dashboards before pilot validates data quality.
- !Void-heavy stores without investigating training or fraud.
POS KPIs are only as trustworthy as session close discipline and config consistency across the chain.
Next, publish a KPI dictionary and validate pilot store numbers against manual counts before executive rollout.
On-time fulfillment
on track> 95%
Inventory accuracy
watch> 98%
Order cycle time
on track↓ trend
Exception rate
critical< 3%
Open store
Hardware and cash float.
Trade
Sales and exceptions.
Replenish
Backroom to floor.
Close
Counts and reports.
Frequently asked questions
Can Odoo report sales by cashier?
Session and order records tie to users. Reports can slice by responsible cashier when session discipline is enforced.
How do refunds appear in KPIs?
Refund orders reduce net sales in period reports. Define whether gross versus net is your standard executive metric.
Can we compare stores with different opening hours?
Use comparable time windows or sales per open hour. Document normalization rules in the KPI dictionary.
Does offline mode delay reporting?
Orders sync on reconnect — intraday dashboards may lag until backlog clears. Monitor sync after incidents.
Related articles
Loyalty Programs and Customer Experience
Design Odoo POS customer experience: partner linking at register, loyalty points, promotions, returns with history, and consistent profiles across store and ecommerce channels.
View →Planning an Odoo POS Project
Structure an Odoo POS implementation: stakeholders, phases, requirements, pilot criteria, UAT, training, hypercare, cutover, and success metrics for retail go-live.
View →Integrating POS with Inventory
Connect Odoo POS to inventory truth: stock locations, real-time deduction, picking policies, replenishment, omnichannel ATP, and avoiding oversell across stores and ecommerce.
View →Common Odoo POS Implementation Mistakes
Avoid frequent Odoo POS failure patterns: inventory disconnect, fiscal late scoping, hardware untested, config drift, weak training, offline surprises, and reporting gaps.
View →Defining POS dashboards for your retail leadership?
Share your reporting audiences and KPI priorities — we will outline Odoo reporting scope.
