Case study 03 · Retail & data

Retail Insights

A retailer ran on spreadsheets and overnight exports, and the numbers always arrived late. We turned them into four live dashboards the whole team opens every morning.

Client
Multi-region retailer
Industry
Retail, in-store and online
What we did
Data pipeline, data warehouse, Power BI dashboards
Used by
Operations, finance, store managers
Retail Insights · SalesUpdated today, 06:00
Revenue$2.45M▲ 18.6% vs last month
Orders48.7K▲ 15.8%
Avg basket$54.30▲ 2.4%
Profit$312K▲ 22.1%
Revenue per day
22 Apr · $98.5K
$129K$63.0K
Revenue by channel
In-store$1.43M
Online$670K
Marketplace$210K
Mobile app$140K

Try it: switch dashboards, pick a region, hover the chart. Sample data, not the client's.

4

dashboards: sales, deliveries, returns, and which customers make money.

06:00

every morning the numbers are fresh, before the first store opens.

Days

to plan a season or a promotion. It used to take weeks.

0

manual exports. Nobody copies data into a spreadsheet any more.

01The problem

By the time the report arrived,the week was already over.

Stores in several regions, an online shop and a warehouse, each keeping its own numbers. Someone had to export them, clean them up and paste them together before anyone could see how the business was doing. So every decision was made on last week's picture.

Before
  1. MonExports pulled from each system
  2. TueAn analyst cleans and merges spreadsheets
  3. WedReport emailed, already questioned
  4. ThuMeeting argues about whose number is right
  5. FriDecision, one week late
With Retail Insights
  1. 02:00Data collected and checked, automatically
  2. 06:00Dashboards refreshed
  3. 08:30Everyone opens the same numbers and acts the same day
02How it works

Every night,nobody touches it.

Tap any step to see what happens there. The whole run finishes while the stores are closed, and a bad batch of data is stopped before it reaches a dashboard.

Step 2

Check. Duplicates are removed, store and product names are matched up, and anything that looks wrong is held back and flagged instead of quietly ending up in a report.

03Four dashboards, four questions

Each screen answersone question.

We did not start from charts. We asked each team what they check first thing in the morning, and built one screen per answer.

Sales

Are we selling?

Revenue, orders and basket size by day, store, region and channel. Store managers see their own store first.

Checked by Store managers
Deliveries

Is it arriving on time?

On-time rate, late orders, and which warehouse or carrier is causing them, before customers start calling.

Checked by Operations
Returns

What comes back, and why?

Return rate and reasons by product, so a sizing problem or a damaged batch shows up in days, not at stock-take.

Checked by Buyers
Customers

Who actually makes us money?

Profit per customer after returns, delivery and discounts. The one nobody had before.

Checked by Finance
04The number nobody had

The biggest customerwas not the best one.

Sales reports rank customers by how much they buy. But some of the biggest buyers also send the most back, need the most deliveries and only buy on discount.

Once returns, delivery and discounts sit in the same place as sales, profit per customer can be worked out for the first time. Flip the switch to see what changes.

Rank customers by
#CustomerSpendReturns, delivery, discountsProfit
1Northgate Outfitters$84.2K−$44.3K−$12.3K
2Harbor Home Goods$61.5K−$11.2K$12.2K
3Pine St. Boutique$52.8K−$34.7K−$14.6K
4Bluebird Kids$39.9K−$5.7K$9.5K
5Metro Office Supply$33.4K−$4.5K$8.2K
6Kline & Daughters$27.1K−$2.7K$7.6K

The usual report. Northgate looks like the best customer in the business.

05Built to keep answering

New question?No new project.

Most dashboard projects stop at the dashboards, and the next question means starting again. Here the real work sits underneath: one organised home for all the data, refreshed every night.

So when finance asks about margins by supplier, or a buyer wants returns by colour, the answer is a new view on data that is already there, not another round of exports.

Step 1

Map the data

Every system that holds a number, who owns it, and which reports people actually rely on.

Step 2

The nightly pipeline

Automatic collection and quality checks, with alerts when a source is late or looks wrong.

Step 3

One data home

A central database where sales, deliveries, returns and customers link up by order.

Step 4

Dashboards and training

Four dashboards built with each team, then a handover so they can filter and explore on their own.

For the technical reader.

Apache Airflow

Runs and schedules the nightly pipeline, retries failed steps and sends alerts.

PostgreSQL

The central data warehouse, modelled as a star schema around orders.

Data marts

Pre-built tables for sales, products, customers and stores, so dashboards stay fast.

Power BI on Azure

The four dashboards, hosted on Azure, filterable by region, store and week.

Common questions

What did SeedInov build for the retailer?

A nightly data pipeline, a central data warehouse and four Power BI dashboards for sales, deliveries, returns and customer profit.

Which technology does it use?

Apache Airflow, PostgreSQL with a star schema, data marts, and Power BI on Azure.

How fresh are the numbers?

Data is collected and checked overnight, and the dashboards are refreshed by 06:00 every day.

Is the data on this page real?

No. The interactive dashboard uses sample data, not the client's.

More case studies

All case studies →