The challenge
Returns are the reverse of a delivery: the goods travel from the customer back to the warehouse, and the courier reports each step. Without a single view it was hard to tell which pickups had been cancelled and why, which were still being organised and which were already on their way.
Problems surfaced late, often only when a customer asked what had happened to their return.
The solution
Courier data is organised into three operational blocks, each with its own table and status counts:
IssuesCancelled or failed pickups, with the reason reported
In managementReturns booked, being collected or awaiting confirmation
In deliveryReturns travelling to the warehouse and their latest event
What the solution includes
Status cardsCount of returns for every status at a glance
Reason notesWhy a pickup was cancelled or failed
Delivery summaryShare of returns by latest courier event
SlicersFilter by date, customer type, order, status and event
Data freshnessLast refresh and download time always visible
Drill-down tablesFrom the totals down to each single return
Results
- Every return visible from pickup request to warehouse arrival
- Cancelled and failed pickups flagged with their reason
- Returns in progress tracked by status instead of by email
- A clear basis for following up with couriers and customers
Stack
Power BI
DAX
Data Modeling
Client names and confidential figures have been omitted. The images on this page contain no client data.