Picqer Power BI dashboard
We bring orders, pick lists, stock and returns from the Picqer API into a single Power BI model. For Fokker Services Group, we brought stock and market data together.
Prices, stock and logistics data in one view gave Fokker Services Group time back
Fokker Services Group employees manually gathered prices, stock levels and market data from different sources. We developed a central dashboard that connects the ERP system to several external marketplaces, built with Python, SQL and Dash.
How long does an order stay with us before it ships?
Picqer knows when an order was created, when the pick list was closed and what was returned. To see this by week, warehouse or online shop, you need to export lists. A Power BI model puts the data side by side.
A Picqer dashboard tracks orders from creation to pick list closure
From order to dispatch
The time between creating an order and closing its pick list, by warehouse, day and hour. This shows you where orders stand.
Stock by location
Physical and available stock by warehouse and location, alongside quantities sold and purchase orders still in transit.
Returns by reason
Every returned product has a return reason in Picqer. You can see what comes back and what can be sold again, by product, supplier and reason.
Stock alongside other sources
Picqer alongside your webshop, accounting system or marketplaces, as we did when we brought stock and market data together in one dashboard for Fokker Services Group.
We define when an order counts as shipped before loading the data
-
Flows and definitions
Which online shops, warehouses and fulfilment clients are involved, and what counts as received, picked and shipped.
-
API key and initial model
Use your own API key, then build a single overview and check it against the figures in Picqer.
-
Expand and manage
Returns, purchasing and other sources follow the same model. Data refreshes and access permissions each have a designated owner.
Is the overview in Picqer enough, or do we also want the figures in Power BI?
A good fit if
You want to see Picqer figures over a longer period or compare them with revenue and margin figures from your webshop and accounting system. Or you handle fulfilment for multiple clients and want to report on each one.
Not a good fit if
You mainly check what’s outstanding today, and the overviews in Picqer already show you that. In that case, a second layer would take more work to maintain than it’s worth.
What determines the scope
How many warehouses, webshops and fulfilment clients are included, how much historical data you want to load, which sources you add alongside Picqer, and who manages the model.
Will this put a strain on our Picqer environment?
Picqer sets a per-minute limit for each API key. We use a dedicated key for loading data, retrieve only new data and wait when Picqer indicates that it’s too busy.
Retrieve Picqer data on a schedule, via webhooks or in a data warehouse?
On a schedule via the API
Choose this if a few updates a day are enough. Our advice for most online shops: retrieve only new orders and closed pick lists each time.
With webhooks
Choose this if you want to record an event immediately, such as a closed pick list or a change in available stock. Picqer then sends a message automatically.
A data warehouse
Choose this if Picqer is one of several data sources or if you want to store historical data outside Picqer. See how to get a data warehouse built.
Bringing stock and orders from separate systems into one view is something we do often
Data Science Lab has worked with data and AI since 2016 and is a Microsoft Partner for Fabric. For Fokker Services Group, we brought ERP and market data together in one dashboard; for Vivara, we built a data platform using Magento, among other sources.

Your order flows and warehouses are the focus of our first conversation
Stef Stoelwinder
Business DevelopmentStef is your first point of contact. In our first conversation, we’ll discuss your online shops, warehouses and the reports you currently export from Picqer.
E-mail info@datasciencelab.nl
Phone +31 (0)20 3636 724
Orders, inventory or returns: which Picqer metrics do you want to see every week?
Tell us how many online shops and warehouses you have in Picqer and which reports you’re missing. We’ll reply by email or suggest an initial conversation.
Message sent
Thanks for your message. We’ll be in touch as soon as possible.
Frequently asked questions
Through Picqer’s API: a REST API using JSON, hosted on your Picqer account’s own subdomain. According to Picqer, you can read all data in Picqer through the API, which is included in every subscription at no extra cost. We set up a data loading step and build the model on top of it.
To see how a dashboard starts with the decision it needs to support, read about Power BI dashboards.
An administrator creates an API key under Settings in Picqer. The key is sent as the username via HTTP Basic Auth. Picqer recommends a separate key for each application so you can revoke it independently.
Picqer sets a per-minute limit for each key and returns an error code if you exceed it. Lists are paginated; the loading step works through the pages and retrieves only new data on each run.
A pick list in Picqer has a creation time and a closing time. For each product, it records the quantity needed and the quantity picked. We call the time between order creation and pick list closure the lead time.
We show that time by warehouse, by day and by the hour the order was created, so you can see where orders are being held up.
Yes. Picqer shows physical stock, reserved stock and available stock for each product and warehouse, as well as the stock at each location. An order can be fulfilled from multiple warehouses.
If you load stock data every day, you build up a history that you can compare with quantities sold and purchase orders.
Yes. Picqer knows what has been picked and dispatched; the webshop knows what was sold and at what price. A single model lets you see both side by side. You can read how we make Lightspeed eCom data accessible in Lightspeed eCom Power BI dashboard.
It works the same way for other webshops or marketplaces: only the loading step differs.
Typically, they report on orders and pick lists by day and warehouse, the time from order to dispatch, stock alongside sales, backorders, returns by reason and product, and, for fulfilment, everything by client.
For revenue, margin and cash flow at management level, see the financial dashboard in Power BI.
In Power BI, row-level security limits what each person can see. For example, a fulfilment client might see only their own orders, or a team leader only their own warehouse.
For how we set up workspaces, apps and refreshes, see Power BI consultant.
If you mainly want to know what’s currently open, Picqer has its own reports for that, and its API has a stats section covering open orders and open pick lists, among other things. Or if product and location data in Picqer needs sorting out: in that case, start with data quality.
If one export a week is enough, we’ll tell you that too.
How do orders and stock from Picqer fit in with the rest of your figures?
- Power BI dashboardsHow we build a dashboard around the decision it needs to support.
- Lightspeed eCom in Power BIRevenue, margin, products and customers from your Lightspeed online shops in a single model.
- Financial dashboardRevenue, margin, cash flow and budget versus actuals in a single model, using data from Picqer and other sources.