Skip to content

Retail and consumer goodsBI, AI and ML for the business

Every store's sales on one page

Till sales, orders and store master data sit in different systems, and the picture of the network arrives after month end. In Muvia revenue, growth, units and customers for every store sit in one dashboard, week by week, from the grand total down to a single department.

Illustrative scenario: it describes a typical case, not a customer project.

A store network cannot be read one spreadsheet tab per region.

Every week someone pulls sales from the tills, puts them next to the orders in the ERP and sends management a file with one tab per region. When a group of stores starts to slip, it shows up in the monthly total, weeks later.

The problem is not the amount of data. It is that nobody sees it all together, at the same grain and with the same filters. A drop in a handful of stores disappears into the network average.

Who it's for
General and sales management, network and regional managers, category managers.
Till sales by store and category, customer orders from the ERP on SQL Server and the store master in Excel flow into Muvia; out come a network dashboard, the same page on the meeting-room screen, a PDF report every Monday and Athena's answers.

In Muvia, step by step

Real product screens, recorded on a project with sample data.

1 of 5

The video · Till sales, orders and store master data sit in different systems, and the picture of the network arrives after month end. In Muvia revenue, growth, units and customers for every store sit in one dashboard, week by week, from the grand total down to a single department.

What you get

One reading of the network
Management and regional managers look at the same figures with the same definitions, instead of a different file for every region.
Local drops show up
The store-by-week heatmap brings out the group of stores that is slipping while the network total holds.
From the total to the department
Whoever opens the dashboard drills from category to department in two clicks, without asking for a new extract.
Current on the wall too
The meeting-room screen and the Monday report read the latest copy of the data, with no copy and paste.

For the technical team

How it is built in Muvia

  1. 1

    Load sales and master data

    Add the till files as a source: each new file is appended to the same table, with no schema to design. The ERP on SQL Server is copied every night, incrementally, and the store master comes from Excel.

  2. 2

    Write the measures once

    In the SQL editor, define revenue, growth on last year, units and active customers by store and by week. Each query becomes a dataset with stable fields that the dashboard, the report and Athena all read the same way.

  3. 3

    Build the dashboard

    Key figures at the top, a store-by-week heatmap, a sunburst that goes from category down to department. The dashboard's parameters filter by region or channel without touching the queries.

  4. 4

    Put it on the wall and in the inbox

    The same page runs in kiosk mode on the meeting-room screen, always on the latest copy of the data. A notebook of text and charts becomes a PDF every Monday for the regional managers.

The data it needs
  • Daily sales by store and category, from the till files
  • Orders from retail chains and wholesale customers, from the ERP on SQL Server
  • Store master with region and channel, from an Excel file
  • Categories and departments of the range
Parts of Muvia used

Bring us a question you can't answer today.

We start from a real question your business has and walk the path from source to dashboard with your systems, not a demo dataset.