PepsiCo Hotshot Dashboard
Transforming warehouse replenishment planning from a reactive spreadsheet workflow into a centralized decision-support platform that minimizes stockouts.
Project Overview
Unlike traditional inventory dashboards that only report static stock levels, the PepsiCo Hotshot Dashboard actively guides warehouse planners toward actionable replenishment decisions.
Prior to this project, PepsiCo warehouse planners reconciled inventory data across multiple spreadsheets and disjointed ERP systems, leading to delayed ordering decisions and increased risk of out-of-stock events. The Hotshot Dashboard was designed to centralize inventory visibility and streamline the path from monitoring to replenishment execution.
"The product unifies executive-level visibility, detailed SKU diagnostics, and recommended hotshot ordering actions into a single operational workspace."
The Operational Replenishment Workflow
The platform supports the complete operational decision cycle by guiding users through six structured stages:
By aligning the interface with the way supply chain professionals naturally solve problems, we transformed inventory management from a reactive process into a proactive decision-making workflow.
Business Problem
Warehouse teams spent significant time manually consolidating data. Without a centralized tool:
Delayed Stock Detection
Stock shortages were often detected too late to prevent out-of-stock events on critical consumer brands.
Inconsistent Ordering
Ordering decisions varied widely between planners due to manual calculation methods and fragmented data sources.
The Product Vision
Our primary goal was to design an interface that reduces the time between identifying a stock shortage and initiating replenishment. Rather than merely presenting data, the platform consolidates all replenishment activities into a single operational workspace that planners can use with confidence.
Interactive Dashboard Mockup
Explore the live interactive recreation of the two dashboard screens. Swap modules using the navigation buttons inside the simulator frame.
Hotshot Replenishment Dashboard
Product Designer Contributions
As the Product Designer, my end-to-end deliverables included:
Information Architecture
Wireframes
Design System
Developer Handoff
Primary Users
Warehouse Managers
Need a quick operational snapshot of daily inventory health to manage onsite teams.
Replenishment Planners
Require SKU-level calculation transparency to make accurate daily ordering decisions.
Supply Chain Managers
Monitor pipeline arrivals and historical fill rate impacts across multiple locations.
Designing for Fast-Paced Daily Workflows
Supply chain planners interact with inventory dashboards multiple times throughout the day. These interactions are typically fast-paced, repetitive, time-sensitive, and data-intensive. The interface was intentionally designed to minimize unnecessary clicks while ensuring that the most important operational signals remain immediately visible.
Information Architecture
The product adopts a simple, task-oriented information architecture that minimizes navigation complexity:
Landing Screen Hub
Instead of overwhelming users with data tables immediately, the Landing screen serves as an operational gateway. It introduces the three core functional modules so users can navigate based on their current task rather than searching through multiple reports.
Executive Summary
The Executive Summary acts as the command center for daily inventory monitoring. Its purpose is to answer a single operational question: "How healthy is today's inventory?" before asking users to investigate further.
Need Sheet Workspace
While the Executive Summary identifies operational risks, the Need Sheet explains the underlying inventory mechanics. For every product, planners can evaluate: Beginning Inventory, Source Net Inventory, DSD Orders, Fill Risk, DSD Net Inventory, Total Net Inventory, and Required Hotshot Quantity.
Hotshot Recommendations
Instead of showing every SKU, the Recommendations module filters the broader inventory dataset to surface only those SKUs that satisfy replenishment criteria. Planners receive required date, brand, material, and recommended quantity, culminating in a clear primary action: Submit Hotshot Orders.
Visual Hierarchy & Scanning
To help planners understand inventory health within seconds, information is organized into three distinct visual layers:
1. Primary Layer
Business-critical metrics (Total cases, SKUs in shortage) occupy the top section of the page.
2. Secondary Layer
Inventory position metrics (Net inventory, Reserve stock) provide context behind the primary KPIs.
3. Tertiary Layer
The Fill Rate Impact chart compares conditions before and after Hotshot replenishment.
Data Visualization Strategy
Instead of overwhelming users with numerous charts, the dashboard employs focused visualizations:
- KPI Cards: Large numerical cards provide immediate visibility into critical metrics.
- Distribution Charts: A proportional donut chart summarizes inventory balance at a glance.
- Inventory Tables: Aligned numerical columns and row spacing support rapid scanning across large tables.
Interaction Design
Each interaction directly supports the replenishment workflow:
Persistent Filters
Filters (Date, SKU, Location) remain consistent across modules to preserve analytical context.
Export Functionality
Support for spreadsheet exports ensures seamless communication across logistics teams.
Primary Call to Action
The Submit button reinforces a clear Analyze → Validate → Execute progression.
Color Strategy
Color is used intentionally to reinforce operational meaning:
- Red highlights shortages, inventory risks, and urgent replenishment needs.
- Blue represents healthy inventory, navigation states, and stable operational states.
- Green communicates positive outcomes and successful replenishment impact.
Usability Considerations
To reduce cognitive load during extended workdays, the interface incorporates high-contrast values, clear labeling of inventory metrics, large interactive controls, and simplified workflows.
Key Learnings & Reflections
This project reinforced the importance of designing dashboards as operational products rather than collections of visualizations. Planners rarely seek more data—they seek clarity on what action should be taken next.