Skip to content

Lightspeed Retail Power BI dashboard

We bring till sales, stock by store and purchasing data from Lightspeed Retail into one Power BI model. For Athlon, we brought parts inventory from separate systems together.

Athlon brings procurement, workshop and logistics data together in one central data platform

At Athlon, parts for maintenance and repairs were tracked in separate systems and spreadsheets, so no one had a complete, up-to-date picture. Together, we built a central data platform, with a data pipeline on Azure that automatically synchronises the sources.

Read the case study

Which shop and which salesperson performed well, and why do we only find out after the month-end close?

The Lightspeed back office shows sales and stock for each shop. To compare branches, staff and purchasing, you have to export lists and combine them in Excel. A Power BI model reads data directly from the tills and shows all the shops side by side.

Schedule a conversation

Sales, stock and purchasing by store in one Lightspeed POS dashboard

Discuss your stores

Sales by store and employee

In R-Series, every sale is linked to a store, till and employee. You can see revenue and receipts by branch and salesperson.

Stock by branch

Lightspeed tracks stock levels and reorder points for each product and store. The model shows what has fallen below its reorder point, by branch or across all branches.

Purchasing from suppliers

Purchase orders by supplier and store, with order and receipt dates, sit alongside sales. You can see whether deliveries are keeping up with demand.

POS data alongside other sources

POS data alongside webshop, accounting or warehouse data in one model, as we did for Athlon by bringing together purchasing, workshop and logistics data.

We define stores, product groups and what counts as a sale before loading data

  1. Stores and definitions

    Which branches to include, what counts as revenue, and how you handle returns, discounts and cancelled receipts.

  2. Access and initial model

    A dedicated OAuth connection to your Lightspeed account, followed by one overview per store, checked against the back office.

  3. Adding stock and purchasing

    Stock, purchasing and customer data are added to the same model. A designated owner takes responsibility for data refreshes and access rights.

Is the Lightspeed back office enough for multiple stores, or is your own model worth it?

Talk it through with us

A good fit if

You have multiple stores and want to compare sales by employee and stock by branch, or you want to look at your till data alongside your online shop and accounting data.

Not a good fit if

You have one store and the reports in Lightspeed already answer your questions. In that case, maintaining your own model takes more work than it’s worth.

What determines the scope

How many stores and tills are included, whether you use R-Series or X-Series, how much historical data you want to load, whether Lightspeed eCom or accounting software is involved, and who manages the model.

Will loading the data affect our tills?

Lightspeed sets a separate request limit for each integration per account. We retrieve only changed data and load it outside opening hours where possible.

Lightspeed exports, your POS version’s API or a data warehouse behind it?

Back-office exports

Choose this if you have one or two stores and a monthly report is enough. It takes little development work, but you’ll need to do manual work every month and won’t have item-level history.

Your POS version’s API

Choose this if you have multiple stores and want to make decisions daily. Our advice: add a loading step that retrieves and stores only changed sales and stock data for each store.

A data warehouse

Choose this if your POS system is one of several data sources, alongside your online store, accounting system and warehouse. See building a data warehouse.

We've brought together point-of-sale, stock and purchasing data from separate systems before

Data Science Lab has worked with data and AI since 2016 and is a Microsoft Partner for Fabric. For Athlon, we built a central data platform for its parts inventory; for Ammega, we built Power BI dashboards and a Power BI app.

Book an introductory meeting

Your stores, your POS version and the lists you make by hand: that’s where our first conversation starts

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your first point of contact. In our first conversation, we’ll discuss your stores, your Lightspeed version and the reports you’re missing.

How many Lightspeed stores would you like to see in a single Power BI overview?

Tell us how many stores and tills you have, and which version of Lightspeed you use. We’ll reply by email or suggest an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

Through the API for your point-of-sale system. Lightspeed has two retail POS products, the R-Series and the X-Series, each with its own API and documentation. Both use OAuth for access. We load the data and build the Power BI model on top of it.

For why we start with the decisions you need to make rather than the charts, see Power BI dashboards.

Lightspeed has renamed its products. The former Lightspeed Retail is now Lightspeed Retail POS (R-Series), and Vend is now Lightspeed Retail POS (X-Series). According to Lightspeed, the L-Series is its restaurant POS system: Lightspeed Restaurant POS (L-Series).

This page covers the two retail POS systems. If you’re not sure which one you have, we’ll work it out together in our first conversation.

The R-Series API includes sales with line items and payments, products, stores, employees, customers, suppliers and purchase orders. Each sale includes the store, register, employee and customer, along with a timestamp for its most recent change.

The loading step uses that timestamp to load only what has changed since the previous run.

In the R-Series, stock is held in a separate table by product and store. It includes the quantity on hand, the reorder point and the target stock level. A row with store number 0 contains the total across all stores; we leave it out of the model to avoid double-counting.

This lets you see which products are at or below the reorder point in each store, and where else they are still in stock.

The X-Series has its own API covering sales, products, outlets, stock, customers, users, consignments and purchase orders. Each request requires a specific permission, such as read-only access to sales.

The model stays the same: sales by outlet and employee, and stock by outlet. Only the loading step differs between versions.

Lightspeed eCom is the online store; Retail is the in-store POS system. When they’re connected, Lightspeed identifies the POS system as the source for products. In-store sales and stock then come from Retail, while online orders come from eCom.

For how we bring online store data into Power BI, see the Lightspeed eCom Power BI dashboard.

We keep the credentials for loading data outside the report, with only the permissions needed. In Power BI, row-level security limits what each person can see. For example, a store manager can see only their own store. Sales by employee should preferably be shown only to the people who manage those employees.

For how we set up workspaces and refreshes, see Power BI consultant.

Typically, they report on revenue and margin by store, product category and employee; the number of receipts and average transaction value; stock by store compared with sales; and purchase orders that are still open.

For cash flow and budget versus actuals, see the financial dashboard in Power BI. If you have one store and the back office meets your needs, we’ll tell you.