In 2023 at Nordstrom, I helped expand a retail ticketing compliance program that removed a major bottleneck in our distribution centers. We projected $22M in annual savings from reduced DC touches and supplier chargebacks; we finished the year at $24M net savings (about 10% above forecast) while improving supplier compliance.
At Nordstrom, I also built KPI dashboards for 1,500+ suppliers. At Electric Mirror, I tracked cost-per-mile and SLA performance for 500+ monthly shipments through Power BI. At Starbucks, I build global customs analytics dashboards using both Power BI and Tableau, and automated reporting workflows that cut manual effort by 30%.
Three companies. Three different scales. Three different tool stacks. And the same pattern every time: the dashboards that get adopted are the ones built around decisions leadership is already making. The ones that try to show everything get ignored.
This is what I have learned about which supply chain metrics actually drive action, why most dashboards fail within months of deployment, and how to build ones that leadership opens without being asked.
Loveleen Kakra
Program Manager — Supply Chain & Logistics
Loveleen Kakra is a supply chain and logistics leader with 15+ years of experience spanning imports, global forwarding, retail operations, e-commerce, and enterprise customs analytics. He has held program management and analytics roles at Starbucks, Amazon, Nordstrom, Electric Mirror, Panalpina, and C.H. Robinson. At Nordstrom, he built KPI dashboards for 1,500+ suppliers and reengineered supplier compliance using Lean Six Sigma, eliminating 50 million manual handling actions annually. At Starbucks, he builds global customs analytics dashboards using Power BI and Tableau and automated reporting workflows that reduced manual effort by 30%. He holds a CSCP certification from ASCM and a Master's in Technology Management — Supply Chain Logistics from the University of Bridgeport.
What is a supply chain dashboard?
A supply chain dashboard is a visual reporting tool that consolidates key performance indicators — on-time delivery, cost-per-unit, supplier compliance, inventory accuracy, and SLA adherence — from ERP, TMS, and procurement systems into a single view. Effective dashboards answer specific operational or strategic questions and are designed around the decisions leadership needs to make, not the data that is available.
What metrics should a supply chain dashboard track?
The metrics that consistently drive action across manufacturing, retail, and enterprise environments are: on-time delivery rate (the metric leadership always reviews first), cost-per-mile or cost-per-unit for freight spend visibility, supplier performance scores tied to SLA compliance, order fill rate and inventory accuracy, and cycle time from order to delivery. Avoid tracking more than 8-12 KPIs per dashboard — too many metrics creates noise that hides the signal.
What tools are best for supply chain dashboards?
Power BI and Tableau are the two dominant tools for supply chain analytics. Power BI integrates natively with Microsoft ecosystems (Azure, Excel, SharePoint) and costs less per user. Tableau excels at complex, multi-source visualizations and ad-hoc data exploration. The deciding factor is not which tool is better — it is where the data lives and who needs to use the dashboard. If the organization runs on Microsoft, Power BI wins. If analysts need deep exploration, Tableau wins.
Why do most supply chain dashboards fail?
Most supply chain dashboards fail because they are built for the builder, not the decision-maker. Common failures include tracking too many metrics (signal-to-noise ratio collapses), not connecting to live ERP data (manual updates make dashboards stale within weeks), no stakeholder requirements gathering (the dashboard answers questions nobody is asking), and no feedback loop after deployment (build, deploy, forget).
Every supply chain leader I have worked with has the same problem: the data exists, but nobody can find it fast enough to make a decision. Cost data sits in the ERP. Shipment data lives in the TMS. Supplier performance is buried in spreadsheets. Carrier SLAs are tracked in email threads.
A supply chain dashboard is supposed to solve that problem. And most of them don't.
- Supply Chain Dashboard
A supply chain dashboard is a real-time or near-real-time visual reporting tool that consolidates key performance indicators from ERP, TMS, WMS, and procurement systems into a unified view designed to support operational and strategic decision-making. Effective supply chain dashboards are built around specific decisions — not around available data — and track 8 to 12 KPIs that directly tie to cost, service level, and compliance outcomes.
A good dashboard is not a summary of your data. It is an answer to a question. "What is our on-time delivery rate this week?" is a question. "What is our cost-per-mile trending across the Southeast?" is a question. "Here is everything we know about our supply chain" is not a question — it is a data dump with charts on it.
At Starbucks, my dashboards answer three to five questions per view. That focus is what drives adoption.
A supply chain dashboard is not a data summary with charts. It is a tool designed around specific decisions leadership needs to make. The dashboards that survive are the ones that answer 3 to 5 questions per view — not the ones that visualize every metric the ERP can produce.
Across every supply chain role I have held — from freight data analysis at a mid-size manufacturer to global customs analytics at Starbucks — the same handful of metrics survive every dashboard redesign. The rest get added in the first version and removed by the third.
The Metrics That Always Survive
| Metric | Why It Survives | Who Reviews It | Where I Tracked It |
|---|---|---|---|
| On-time delivery rate | Directly impacts customer satisfaction and contract compliance | VP/Director of Supply Chain, Operations leadership | Panalpina (60% → 90%), Nordstrom |
| Cost-per-mile / cost-per-unit | Exposes freight cost trends and carrier performance | Finance, Supply Chain leadership | Electric Mirror (500+ shipments/mo) |
| Supplier performance score | Drives contract renewal and vendor management decisions | Procurement, Supplier Operations | Nordstrom (1,500+ suppliers) |
| SLA adherence | Shows carrier and supplier compliance against contractual commitments | Operations, Procurement | Electric Mirror, Nordstrom |
| Customs compliance metrics | Tracks tariff classification accuracy and filing compliance across countries | Trade Compliance, Global Trade leadership | Starbucks |
The Metrics That Always Get Cut
Vanity metrics die fast. Dashboard views, total shipment counts without context, raw inventory levels without accuracy percentages. Anything that shows activity without insight gets challenged in the second leadership review and removed by the fourth.
The filter I use now: if a metric drops by 10%, would someone in leadership change their behavior? If the answer is no, it doesn't belong on the dashboard.
The supply chain metrics that survive every dashboard redesign are the ones that trigger action: on-time delivery rate, cost-per-mile, supplier compliance scores, and SLA adherence. If a 10% drop in a metric wouldn't change leadership's behavior, it does not belong on the dashboard.
The Nordstrom supplier operations program was one of the largest dashboard projects I have worked on: 1,500+ suppliers and stakeholders across sourcing, finance, logistics, and DC operations.
The Requirements Problem
The biggest issue we had in 2023 was retail ticketing violations. For many items, goods arrived at our DCs with missing tickets or wrong prices. That created manual rework at the DCs, slowed outbound flow to stores, and increased labor cost.
I started by gathering requirements with my team and coordinating with engineering to map data sources and system dependencies. We then aligned on the exact operational questions the dashboard needed to answer:
- Which suppliers were driving most ticketing violations?
- Which DCs saw the highest repeat ticketing failures?
- How much labor cost and delay did those violations create?
- What chargeback model would be fair and effective?
When stakeholders ask for everything on one dashboard, your job is to bring the conversation back to decisions. Which suppliers need intervention? Which DCs are overloaded by rework? What is the cost if we do nothing?
The Analysis That Shaped the Program
I pulled two quarters of inbound shipment and audit data from our DC network, then analyzed:
- percentage of units with retail ticketing violations
- top suppliers driving those violations
- DC-level concentration of ticketing issues
- labor spend required to fix violations before goods could flow to stores
To validate the findings, I reconciled results with the supplier compliance dashboard I had previously built. Then I created a Tableau report with focused worksheets showing the top non-compliant suppliers, the DCs with the highest ticketing failure rates, and the estimated dollars Nordstrom was spending on correction work.
That analysis informed strategy conversations around reduced touches at DCs and chargebacks for non-compliant vendors. The projected annual savings from this program was over $22M.
Implementation and Supplier Rollout
We launched the expanded retail ticketing compliance program in February 2023 and communicated changes to suppliers months in advance through portal updates and newsletters. That lead time mattered — it gave suppliers space to adjust before chargebacks began.
In year one, the program generated $24M net savings (about 10% above projection) through reduced labor cost and chargebacks, while improving flow efficiency across DC operations.
How We Increased Supplier Buy-In (Not Just Enforcement)
One risk I flagged early: suppliers might interpret this as a penalty program instead of a supply chain efficiency initiative.
To reduce that risk, I introduced a biweekly supplier compliance reporting loop for top violators. Using our Tableau supplier scorecard, I generated supplier-specific extracts and a pivot summary showing:
- two-week shipment volume by DC
- audit failures
- failures tied specifically to missing/wrong retail ticketing
- trend movement over time
Program managers used these reports in direct supplier conversations to explain the "what, why, and impact" and align on joint corrective actions. That reporting cadence improved cooperation and accountability instead of creating defensive pushback.
The most effective dashboards are not reports — they are feedback loops. The dashboard surfaces the problem, the process defines the response, and recurring supplier-level reporting keeps everyone accountable to progress.
At Nordstrom, I used dashboard-driven analysis to expand a retail ticketing compliance program across 1,500+ suppliers: identified top violators and DC hotspots, launched in February 2023, paired chargebacks with biweekly supplier coaching reports, and delivered $24M net savings in 2023 (10% above projection) while reducing operational friction in DCs.
While supporting daily leadership reporting at Nordstrom, I inherited a manual process that required pulling data from three separate Tableau dashboards and then copying the data into PowerPoint.
The Bottleneck
The original workflow took 1 to 1.5 hours each day because:
- each source dashboard had large historical data and slow refresh behavior
- users had to re-apply filters for date range and DC scope every time
- final slides required manual copy-paste, increasing risk of reporting errors
The Fix
After aligning with my manager and getting source access, I rebuilt the workflow in one dedicated Tableau dashboard:
- customized SQL query scopes in source tabs to include only relevant timeline and fields
- worksheet 1: PO violation submissions and completions by DC
- worksheet 2: pending violations split by within SLA (48 hours) vs outside SLA
- worksheet 3: histogram for DC performance by pending POV count
- scheduled daily refresh and validated outputs against legacy dashboards
I then updated layout and formatting so users could export directly to PPT format, reducing manual editing and preserving consistency.
Outcome
The process dropped from 60-90 minutes to about 15 minutes per day (roughly 70%+ faster), while improving reporting consistency and reducing copy-paste error risk.
Consolidating three slow dashboards into one purpose-built Tableau report, with targeted SQL scopes and PPT-ready output, turned a 1-1.5 hour daily PO violation reporting process into a 15-minute workflow with better consistency and lower error risk.
Electric Mirror is a mid-size manufacturer of lighted mirrors and TV mirrors for hospitality and healthcare, running on Epicor ERP, processing 500+ shipments per month.
Building the Data Pipeline
I integrated outbound freight and order data with Epicor ERP to create a unified view. Then I built Power BI dashboards that tracked cost-per-mile by lane and SLA performance against carrier commitments. Alongside this, I developed Excel-based freight quoting models for pricing accuracy.
The challenge at a mid-size manufacturer is that data often lives in disconnected systems — ERP for orders, carrier systems for shipment tracking, spreadsheets for freight quotes. The dashboard work at Electric Mirror was as much about building the data pipeline as it was about the visualization layer.
The Scale Difference
At Electric Mirror, one Power BI workbook could cover the entire freight analytics operation. The audience was a small leadership team, the data came from one ERP, and the metrics were consistent week to week. This simplicity is actually an advantage for mid-size companies — the dashboard can be built and iterated faster because there are fewer stakeholders and fewer data sources to reconcile.
At a mid-size manufacturer like Electric Mirror, the dashboard challenge is building the data pipeline — connecting ERP, carrier systems, and spreadsheets into a unified view. The visualization itself is simpler because the audience is smaller and the metrics are consistent. Power BI dashboards tracking cost-per-mile and SLA performance gave leadership freight cost visibility they hadn't had before.
At Starbucks, I work on global customs and trade analytics — a scale change from anything I had done before.
Customs compliance spans multiple countries, each with different regulatory frameworks, tariff schedules, and reporting requirements. The dashboard challenges at this scale are fundamentally different from a single-ERP manufacturer.
Automating What Used to Be Manual
I lead data extraction, cleansing, and transformation for global customs analytics using SQL, Alteryx, and Excel. I build Power BI and Tableau dashboards for customs performance visibility and automated customs reporting workflows — reducing manual effort by 30%.
That 30% reduction matters beyond just time savings. In global trade compliance, manual reporting processes introduce human error that can trigger compliance violations. Automating the data pipeline eliminates those error categories.
What Changes at Enterprise Scale
Three things are fundamentally different about building supply chain dashboards at enterprise scale:
At enterprise scale, supply chain dashboards require automated data pipelines (not manual Excel assembly), strict data governance (every metric must have one definition), and audience segmentation (the same data presented differently for regional vs global teams). I reduced manual customs reporting by 30% at Starbucks by building Alteryx-powered pipelines feeding Power BI and Tableau dashboards.
At Starbucks, I use both Power BI and Tableau for different dashboard needs. The debate about which tool is "better" misses the point. They solve different problems for different audiences.
| Factor | Power BI | Tableau |
|---|---|---|
| Best for | Operational dashboards with defined metrics and regular refresh schedules | Analytical dashboards where users need to explore data and ask ad-hoc questions |
| Data integration | Native Microsoft ecosystem — Azure, Excel, SharePoint, SQL Server | Strong cross-database joins — connects to nearly any source without middleware |
| Cost | Lower per-user cost, included in many Microsoft 365 enterprise agreements | Higher per-user licensing, separate procurement |
| Learning curve | Faster for users already in Microsoft ecosystem | Steeper initial learning, but more powerful for complex visualizations |
| Real-time refresh | Strong with DirectQuery and Azure streaming datasets | Requires Tableau Server or Tableau Cloud with extract scheduling |
| Ad-hoc exploration | Limited — designed for structured report consumption | Excellent — drag-and-drop exploration is Tableau's core strength |
When I Choose Power BI
When the data already lives in Microsoft systems — SQL Server, Azure, SharePoint — and the dashboard audience is operational (they need to see the same metrics every week), Power BI wins. The integration is seamless, the cost is lower, and the refresh pipeline is simpler.
At Electric Mirror, Power BI was the obvious choice. The data came from Epicor and Excel, the audience was a small leadership team, and the dashboards needed to show the same cost-per-mile and SLA metrics every week.
When I Choose Tableau
When analysts need to explore the data — filter, drill down, compare periods, ask questions the dashboard designer didn't anticipate — Tableau wins. Its visual exploration capabilities are genuinely better for ad-hoc analysis.
At Starbucks, Tableau serves the use cases where teams need to investigate and explore data beyond predefined reports — where the questions aren't fully known in advance and the analyst needs flexibility to drill into the data.
The tool question is never "which one is better?" It is "where does the data live and who needs to use this?" If the answer is Microsoft data and operational users, choose Power BI. If the answer is multi-source data and analytical users who need to explore, choose Tableau. At Starbucks, we use both — for different dashboards, serving different audiences.
Power BI wins for operational dashboards in Microsoft-native environments with lower cost per user. Tableau wins for analytical dashboards where users need ad-hoc exploration across multiple data sources. The deciding factor is not the tool — it is where the data lives and whether the audience consumes structured reports or investigates data.
After building dashboards across multiple companies and industries, the failure patterns are predictable.
- Building for the builder: Analysts build dashboards that answer their own questions, not the questions leadership asks. The dashboard becomes a technical showcase instead of a decision tool.
- Too many metrics: Signal-to-noise ratio collapses when a dashboard tracks 20+ KPIs. Leadership opens it, can't find what matters, and goes back to asking questions over email.
- No data governance: "On-time delivery" means something different to logistics (shipped on time), sales (received on time), and finance (invoiced on time). Without a single definition per metric, the dashboard creates arguments instead of alignment.
- Disconnected from live ERP data: Dashboards built on manual data exports become stale within days. If someone has to pull, clean, and upload data to refresh the dashboard, it will stop being refreshed within a month.
- No feedback loop: The dashboard is built, deployed, and forgotten. Nobody asks users if the metrics are useful. Nobody tracks which views get opened and which get ignored. The dashboard slowly becomes irrelevant as business questions evolve.
The Adoption Test
The simplest test for whether a dashboard is working: does leadership open it without being asked? If someone has to remind people to look at the dashboard, the design failed.
Supply chain dashboards fail when they are built for the builder instead of the decision-maker, track too many metrics, lack data governance, depend on manual data uploads, or have no feedback loop after deployment. The test is simple: does leadership open the dashboard without being asked? If not, the design failed.
- 01A supply chain dashboard is a decision tool, not a data summary — effective dashboards answer 3 to 5 specific questions leadership asks weekly, tracking 8 to 12 KPIs that directly tie to cost, service level, and compliance outcomes
- 02The metrics that survive every redesign are: on-time delivery rate, cost-per-mile or cost-per-unit, supplier compliance scores, and SLA adherence — anything that wouldn't change leadership behavior if it dropped 10% does not belong on the dashboard
- 03At Nordstrom, retail ticketing compliance analytics identified top violating suppliers and DC hotspots, informed chargeback strategy, and supported a February 2023 launch that delivered $24M net annual savings (10% above projection)
- 04Biweekly supplier-specific compliance reporting improved supplier cooperation by turning enforcement into shared progress tracking, contributing to lower operational friction and reduced touches across DCs
- 05A separate daily PO violation reporting optimization reduced reporting cycle time from 1-1.5 hours to 15 minutes by consolidating three dashboards into one PPT-ready Tableau workflow
- 06Power BI wins for operational dashboards in Microsoft-native environments, Tableau wins for analytical dashboards requiring ad-hoc exploration — the deciding factor is where the data lives and who uses the dashboard
- 07At Starbucks, automating customs reporting workflows with Alteryx, SQL, Power BI, and Tableau reduced manual effort by 30% and eliminated categories of human error in global trade compliance
- 08Common dashboard killers: building for the builder instead of the decision-maker, too many metrics, no data governance, disconnected from live ERP data, and no post-deployment feedback loop
What is a supply chain dashboard?
A supply chain dashboard is a visual reporting tool that consolidates key performance indicators from ERP, TMS, WMS, and procurement systems into a unified view for operational and strategic decision-making. Effective dashboards track 8 to 12 KPIs — including on-time delivery, cost-per-unit, supplier compliance, and order fill rate — and are designed around specific decisions rather than available data.
What KPIs should a supply chain dashboard track?
The most impactful KPIs are on-time delivery rate, cost-per-mile or cost-per-unit, supplier performance scores tied to SLA compliance, and SLA adherence. Limit to 8-12 KPIs total. The filter for inclusion: if the metric drops 10%, would leadership change their behavior? If not, it does not belong on the dashboard.
Should I use Power BI or Tableau for supply chain analytics?
Power BI is the better choice for operational dashboards in Microsoft-native environments — it integrates natively with Azure, SQL Server, Excel, and SharePoint, and costs less per user. Tableau is the better choice for analytical dashboards where users need ad-hoc data exploration and complex multi-source visualizations. The deciding factor is where the data lives and whether the audience consumes structured reports (Power BI) or investigates data (Tableau). Many enterprise organizations use both for different use cases.
How many metrics should a supply chain dashboard have?
Limit to 8 to 12 KPIs across the entire dashboard, with 3 to 5 shown on the landing page. Tracking more than 12 metrics causes signal-to-noise ratio collapse — leadership cannot find what matters and stops using the dashboard. Design the landing page for executives (one-glance summary) and add drill-down pages for analysts who need deeper exploration.
Why do supply chain dashboards fail?
The five most common failures are: building the dashboard for the analyst instead of the decision-maker, tracking too many metrics, having no agreed-upon data governance (different definitions for the same metric across departments), relying on manual data exports instead of live ERP connections, and deploying without a feedback loop to evolve the dashboard as business questions change. The simplest adoption test: does leadership open the dashboard without being reminded?
What tools are used to build supply chain dashboards?
Power BI and Tableau are the two dominant visualization tools for supply chain analytics. Alteryx and SQL handle data extraction, cleansing, and transformation upstream of the dashboards. ERP systems (SAP, Epicor, Oracle) serve as primary data sources. Excel remains essential for ad-hoc freight quoting models and data validation. The full pipeline is: ERP/TMS data source → SQL/Alteryx for extraction and transformation → Power BI or Tableau for visualization.
How do you gather requirements for a supply chain dashboard?
Start with stakeholder interviews to identify the 3 to 5 decisions each audience makes weekly. Then map those decisions to specific metrics and data sources before designing visuals. In my Nordstrom retail ticketing work, requirements aligned around four decisions: top violating suppliers, DC-level concentration of issues, labor cost impact, and chargeback strategy. Once those were clear, dashboard scope became straightforward.
How do you get suppliers to cooperate with a compliance program?
Communication and visibility need to happen before and after launch. At Nordstrom, suppliers were informed in advance through portal updates and newsletters, but I also added biweekly supplier-specific compliance reports for top violators. Those reports showed each supplier's shipment volume, failed audits, and ticketing-specific failures by DC over a two-week window. Program managers used them to run joint corrective action plans. This shifted the narrative from 'penalty' to 'measurable improvement,' which increased supplier cooperation and helped sustain results.
- 01Supply Chain Operations Reference (SCOR) Model — Digital Standard — Association for Supply Chain Management (ASCM)
- 02CSCMP Supply Chain Management: Terms and Glossary — Council of Supply Chain Management Professionals (CSCMP)
- 03Gartner Supply Chain Top 25 — Methodology and Rankings — Gartner (2025)