Operational Dashboards
Give teams live or near-live visibility into work, stock, availability, queues, ageing, exceptions and service status.
- Role-based operational views
- Current state and ageing
- Exceptions and workload
- Drill-down to records
Vault Commerce OS · Reporting and Analytics
Turn Commerce, Inventory and Operational Activity into Decision-Ready Reporting
Use configurable dashboards, filters, drill-downs, exports and scheduled reporting across inventory, warehousing, rentals, fulfilment, CRM, marketplace activity, returns, exceptions and financial-operational views—without separating the report from the underlying operational record.
Reporting and Analytics is the visibility layer across Commerce OS. It measures operational truth captured by the platform and connected systems; it does not replace the WMS, CRM, Rental Commerce, finance system or external BI environment that owns the underlying business process.
From operational records to governed management visibility
Define + measure + investigate + act
Define + measure + investigate + act
01
Define the Metric
Specify business meaning, source records, filters, time basis, ownership, exclusions and freshness expectations.
Define the Metric
Specify business meaning, source records, filters, time basis, ownership, exclusions and freshness expectations.
→
02
Measure the Operation
Combine the approved operational signals into dashboards, summaries, trends, ageing and capacity views.
Measure the Operation
Combine the approved operational signals into dashboards, summaries, trends, ageing and capacity views.
03
Drill into Evidence
Move from a KPI into the underlying items, transactions, tasks, exceptions or locations that explain the result.
Drill into Evidence
Move from a KPI into the underlying items, transactions, tasks, exceptions or locations that explain the result.
04
Distribute and Govern
Save views, schedule reports, export approved data, control permissions and monitor freshness or reconciliation issues.
Distribute and Govern
Save views, schedule reports, export approved data, control permissions and monitor freshness or reconciliation issues.
A useful KPI should have a clear definition, a known data source and a path back to the records that created it.
Metric clarity + operational evidence
Metric clarity + operational evidence
Choose the reporting depth
Start with Operational Visibility, Add Management Analytics or Feed an Enterprise BI Layer
The right reporting model depends on who needs the information, how frequently decisions are made and whether Commerce OS dashboards are the final analysis surface or a governed source for a separate BI environment.
↔ Swipe through the Reporting and Analytics models
Management Analytics
Combine trends, utilisation, conversion, fulfilment, returns, service levels and financial-operational indicators for management review.
- Trend and period comparison
- Utilisation and throughput
- Conversion and lifecycle metrics
- Saved management views
BI and Data Export Layer
Provide governed exports or supported connections for deeper enterprise analysis in an approved BI or data environment.
- Structured exports
- Scheduled data delivery
- Supported BI connections
- Defined metric and lineage context
Four connected Reporting and Analytics components
Measure Operations, Analyse Performance, Distribute Insight and Govern the Numbers
Reporting should be useful to frontline teams and management while preserving the definitions, permissions and data freshness needed to keep different users looking at the same business reality.
↔ Swipe through the Reporting and Analytics components
Operational Dashboards
Monitor inventory, capacity, work queues, fulfilment, rentals, CRM, returns, exceptions and current service state.
InventoryQueuesAgeingStatus
Performance Analytics
Compare utilisation, conversion, throughput, service levels, returns, exceptions and commercial-operational performance over time.
TrendsUtilisationConversionPerformance
Views, Exports and Delivery
Create saved filters, role-specific views, scheduled reports and approved exports for recurring operational and management use.
FiltersSaved ViewsScheduleExport
Metric Governance and Freshness
Define KPI logic, source records, permissions, freshness, exclusions, reconciliation and change history.
DefinitionsFreshnessPermissionsAudit
See the Reporting and Analytics workflow in action
Follow Operational Data from KPI Definition through Dashboards, Drill-Down, Distribution and Governance
Start with the complete reporting architecture, then move through operational dashboards, inventory and capacity, rentals and fulfilment, CRM and performance analytics, saved views, scheduled reporting, exports, BI access, metric definitions, permissions and freshness.
↔ Swipe through the Reporting and Analytics walkthrough
01
Give operational teams a live view of what needs attention
Give operational teams a live view of what needs attention
Inventory, Capacity, Rentals, Fulfilment, CRM, Returns, Exceptions and Workload
Operational dashboards should answer immediate questions: what is available, what is blocked, what is overdue, what is waiting, who owns it and what needs action next.
Each summary should allow an authorised user to drill into the underlying records instead of forcing teams to trust an unexplained aggregate.
Current-state operational visibility
Ageing, workload and exceptions
Drill-down to underlying records
Ageing, workload and exceptions
Drill-down to underlying records
↔ Swipe through operational reporting controls
Inventory and Capacity Views
See physical stock and space through the dimensions that matter operationally.
- Available, reserved, held or unavailable stock
- Site, zone or location occupancy
- Quantity, unique-item and kit visibility
- Capacity and utilisation where configured
Rental and Fulfilment Views
Monitor active commitments and physical execution.
- Upcoming and active rentals
- Due and overdue returns
- Picking, packed, dispatched and delivery state
- Shortage, failed handover and return exceptions
CRM and Service Workload
Track relationship and task queues alongside operational work.
- Pipeline and stage volumes
- Tasks due and overdue
- Service or case ageing
- Owner, team and escalation workload
Exception and Action Queues
Surface problems that require resolution instead of hiding them inside totals.
- Inventory, fulfilment and return exceptions
- Integration and sync failures
- Data-quality and reconciliation issues
- Owner, severity, ageing and next action
02
Move from today’s workload to trends and operating performance
Move from today’s workload to trends and operating performance
Utilisation, Throughput, Conversion, Service Levels, Returns, Exceptions and Financial-Operational Indicators
Management analytics can compare periods, sites, channels, teams, categories and operating models using clearly defined measures rather than ad hoc spreadsheet formulas.
Financial or settlement reporting should remain scoped to the data Commerce OS actually holds or receives. It should not be presented as audited accounting unless the relevant accounting system and process support that interpretation.
Trend and period comparison
Cross-site, channel and team analysis
Operational-financial views where configured
Cross-site, channel and team analysis
Operational-financial views where configured
↔ Swipe through performance analytics controls
Utilisation and Inventory Performance
Measure whether assets and capacity are being used productively.
- Rental or asset utilisation
- Stock turn or movement frequency where relevant
- Location or capacity utilisation
- Idle, blocked or ageing inventory views
Commerce and Conversion Analytics
Measure demand and conversion across approved client channels.
- Enquiry, shortlist or opportunity progression
- Transaction or rental conversion
- Channel and category comparison
- Repeat activity and lifecycle indicators
Fulfilment and Service Performance
Compare speed, completion quality and exception rates.
- Pick, pack and dispatch turnaround
- On-time delivery or collection where available
- Return turnaround and restoration time
- Shortage, cancellation and exception rate
Financial-Operational and Settlement Views
Bring operational and commercial status together where the platform has the necessary data.
- Gross transaction or rental value where captured
- Adjustments, deductions or refund state
- Settlement or receivable status where connected
- Operational cost or margin inputs only where configured
03
Make recurring reporting easier without duplicating the underlying data
Make recurring reporting easier without duplicating the underlying data
Saved Filters, Role Views, Scheduled Reports, Exports and BI-Ready Data Access
Teams should be able to save the filters they use repeatedly and schedule approved summaries without rebuilding the same report manually every day or week.
Exports and BI feeds should respect the same access model as the source application. A user should not gain access to restricted client, financial or operational data merely because it appears in a report.
Reusable filters and saved views
Scheduled management reporting
Permissioned exports and BI access
Scheduled management reporting
Permissioned exports and BI access
↔ Swipe through report distribution controls
Filters, Segments and Saved Views
Reuse the reporting perspective relevant to each role or operating question.
- Date, site, category, channel and owner filters
- Status, ageing and exception filters
- Personal or shared saved views
- Default role dashboard where configured
Scheduled Reports and Delivery
Deliver recurring summaries to approved recipients.
- Daily, weekly, monthly or configured cadence
- Saved report definition
- Approved recipient or team
- Delivery status and history
Exports and Data Extracts
Provide controlled data for offline review or downstream analysis.
- CSV or approved structured export
- Selected columns and filters
- Exported-by and timestamp history
- Large-export controls where required
BI and Analytics Connections
Feed approved reporting environments where deeper analysis is required.
- Supported scheduled or API-based access
- Governed reporting dataset
- Metric definition and source context
- Freshness and integration-health visibility
04
Make sure different teams interpret the same number the same way
Make sure different teams interpret the same number the same way
Metric Definitions, Time Basis, Permissions, Freshness, Reconciliation and Change History
A KPI should define its source records, calculation, date basis, exclusions and refresh expectations. Without that definition, two dashboards can display different numbers and both appear correct.
Reporting freshness also depends on connected systems. A dashboard should be able to indicate when a source is stale, delayed or awaiting reconciliation rather than presenting an old number as current.
Defined KPI logic and ownership
Freshness and reconciliation visibility
Permission and metric-change governance
Freshness and reconciliation visibility
Permission and metric-change governance
↔ Swipe through reporting governance controls
Metric Definition and Time Basis
Document what the KPI means before relying on it.
- Metric name and business definition
- Source records and calculation logic
- Created, committed, completed or other time basis
- Inclusions, exclusions and denominator
Role and Data Permissions
Keep report access aligned with operational access.
- Role, team, client or site visibility
- Financial or sensitive-field restrictions
- Export and scheduled-report permission
- Shared-dashboard access control
Freshness and Reconciliation
Show whether the report is using current and reconciled inputs.
- Last refreshed timestamp
- Source-system freshness status
- Incomplete or delayed data warning
- Reconciled, provisional or exception state
Metric Change and Audit History
Prevent KPI definitions from changing silently over time.
- Definition and calculation version
- Changed-by and approval history
- Effective date of new logic
- Notes explaining material metric changes
Reporting and Analytics workflow
Define, Build, Validate, Publish, Distribute and Improve
The reporting programme should begin with business questions and metric definitions rather than building charts first.
↔ Swipe through the Reporting and Analytics workflow
Define the Question
Identify the decision, audience, metric, source records, filters, time basis and required freshness.
Build the View
Create the dashboard, table, KPI, trend or drill-down using the approved definitions.
Validate the Numbers
Compare the report with underlying records and reconcile known source-system differences.
Publish with Permissions
Release the report only to the roles, teams, clients or sites authorised to see it.
Save and Distribute
Create approved saved views, schedules, exports or BI feeds for recurring use.
Monitor and Improve
Review freshness, adoption, metric changes, data quality and whether the report still supports the intended decision.
Reporting and Analytics is not the operational source system
Dashboards measure inventory, rental, CRM, fulfilment and other records. Changes to the underlying operation should be made in the module that owns that process, not by editing an aggregate report.
Commerce OS reporting can coexist with external BI
Operational teams can use built-in dashboards while approved data is also supplied to a separate BI environment for deeper enterprise analysis where required.
Reporting responsibility and governance
Keep Metric Ownership, Platform Calculation and Source-System Responsibility Explicit
The implementation should identify who defines the business meaning of a metric, how Commerce OS calculates it and which source system supplies each underlying fact.
Responsibility
Client Business / Management
Commerce OS Reporting Layer
Source or Connected System
KPI definition, business meaning and decision use
Own and approve
Configure approved definition
Supply source facts where connected
Dashboard, filter, drill-down and saved-view configuration
Approve reporting requirements
Configure platform views
Provide source data as applicable
Permissions, exports and scheduled distribution
Approve access policy
Enforce configured access
Subject to external source restrictions
Data freshness and reconciliation
Define acceptable freshness
Expose platform freshness and exceptions
Provide external data according to connection capability
Metric changes and historical interpretation
Approve material changes
Version and record calculation changes
Notify or expose relevant source changes where available
Accounting, statutory or audited financial interpretation
Own with applicable finance process
Report only configured operational-financial data
Accounting system/process remains authoritative where applicable
↔ Swipe through the Reporting and Analytics responsibility views
Client Business / Management
- Business question Own
- KPI definition Approve
- Access policy Approve
- Material metric change Approve
Commerce OS Reporting Layer
- Dashboard and calculation Configure
- Drill-down and filters Configure
- Permissions and distribution Enforce
- Freshness and audit Expose
Source or Connected System
- Source facts Provide where connected
- External freshness Provider-dependent
- Schema and data changes Control externally
- Accounting truth Authoritative where applicable
Common reporting families
Give Each Team the Metrics Relevant to Its Operating Role
Reports can combine dimensions across Commerce OS while still respecting module ownership, client boundaries and access permissions.
↔ Swipe through the Reporting and Analytics use cases
Reporting and Analytics FAQs
Common Questions before Configuring Commerce OS Reporting
The final reporting model depends on the client’s metrics, roles, source systems, refresh expectations, data quality, financial interpretation and whether a separate BI environment is also used.
Can users drill from a KPI into the underlying records?
Where the report is configured for drill-down and the user has permission, a KPI can link to the relevant items, transactions, tasks, locations or exceptions that contribute to the measure.
Can different teams have different dashboards?
Yes. Role, team, client, site and workflow-specific dashboards or saved views can be configured according to the access model.
Can reports be scheduled automatically?
Yes, where configured. Saved reports can be delivered on an approved cadence to authorised recipients, with delivery history retained.
Can users export report data?
Yes, subject to permissions. Exports can use the selected filters and columns and should retain export history appropriate to the implementation.
Can Commerce OS feed Power BI or another analytics environment?
Potentially. BI connectivity depends on the approved data-access method, security requirements, required refresh frequency and implementation scope.
Are dashboards real time?
Not necessarily. Freshness depends on the underlying module and any connected external system. Reports should show the relevant refresh or source freshness state where material.
How do we stop two teams using different definitions for the same KPI?
Key metrics should have an approved definition covering source records, calculation, time basis, inclusions, exclusions and ownership, with material changes versioned.
Can reporting include financial values?
Yes, where Commerce OS holds or receives the relevant data. Such views should be described as operational-financial reporting unless the applicable accounting process supports a stronger accounting interpretation.
Can a user see data in a report that they cannot see elsewhere?
The reporting layer should respect the configured access model. Reports, exports and scheduled deliveries should not become a route around client, role, site or sensitive-field restrictions.
What happens if a connected source is delayed?
The reporting layer should expose stale, delayed, provisional or unreconciled source state where that affects interpretation instead of presenting the data as fully current.
Begin with the decisions, metrics and audiences that matter
Show Us What Your Teams Need to See, Compare and Act On
We will map operational dashboards, KPI definitions, drill-downs, trends, saved views, scheduled reports, exports, permissions, freshness, financial-operational context and any supported BI requirements.