In Made in America, Sam Walton describes a leadership culture that no other large retailer had. Kmart reviewed regions. Sears reviewed regions. Penney's reviewed regions. David Glass believed Walmart could do something more powerful. They reviewed individual stores. If the conversation was about the Walmart in Dothan, Alabama, or Harrisburg, Illinois, everybody in that room was expected to know whether a twenty percent increase was good or bad, what payroll was running, who the competitors were, and how the store was performing. Glass, who would become Walmart's CEO, put it plainly: "We keep the company's orientation small by zeroing in on the smallest operating unit we have. No other company does that."
That was not a slogan. It was an operating discipline. While competitors were content with regional averages, Glass and Walmart's leadership dug into individual stores every single week. They believed that regional summaries hid as much as they revealed. A region could look healthy while a handful of stores were quietly falling apart. The only way to know was to look at the level where customers actually walked through the door.
He asked whether the Dothan store's twenty percent increase was good or bad, what payroll was running, and who the competitors were. That was more powerful than anything a regional average could tell him.
The system Glass helped build
That same operating philosophy led to one of the most consequential decisions in modern retail: the creation of Retail Link. David Glass played a pivotal role in developing Walmart's automated distribution network and the Retail Link program, which gave suppliers direct access to store-level sales and inventory data. The idea was radical at the time. Let suppliers see what is happening at the store and SKU level, and give them the tools to help manage their own categories more effectively.
Retail Link was not just a data portal. It was an expression of Glass's belief that performance had to be measured, understood, and acted on at the most granular level possible. The same discipline that led Walmart's leadership to review individual stores in Saturday morning meetings was now being extended to the supplier community. If Walmart's own executives were expected to know individual store performance, why shouldn't the suppliers who stocked those shelves have the same visibility?
The system changed names. The friction stayed.
Retail Link eventually evolved. Walmart replaced it with Luminate, and the core data access layer became Scintilla. The interface changed. The terminology changed. The level of granularity shifted in some areas. But one thing did not change: the operational friction that suppliers face every week trying to actually use the data.
Scintilla still starts with downloads. Thousands of Walmart supplier teams repeat the same painful ritual every single week. Download the files. Clean the columns. Fix the date ranges. Merge one export with another. Rebuild the pivots. Only then does analysis begin. By the time the data is ready to inform a decision, the best window for action has already started to close.
It is a striking irony. The system that David Glass helped build so suppliers could see store-level detail has, through decades of evolution, become the system that makes store-level detail hardest to reach on a weekly basis.
What gets lost in the weekly grind
The most damaging consequence of this friction is not the hours it consumes. It is the level of detail it forces teams to abandon. When an analyst spends most of the morning preparing data, they do not have the bandwidth to examine performance at the store and SKU level. They aggregate up. They look at regions. They look at totals. They look at whatever level of summary lets them produce something before the next meeting.
| The weekly grind | What happens |
|---|---|
| Download. Clean. Repeat. | Teams spend hours pulling files from Walmart portals, pivoting tables, and merging spreadsheets before analysis even starts. |
| The window closes fast. | By the time the data is ready, the best time to act has already shrunk. Insights arrive after the pressure does. |
| Surprises are expensive. | Phantom stock, missed instocks, and replenishment failures surface in buyer meetings instead of morning dashboards. |
That is exactly the opposite of what David Glass built the system to do. He wanted suppliers to understand performance at the individual store level. The data to do that still exists inside Scintilla. But the workflow between the download and the decision has become so heavy that most teams never get there with enough time to act.
Operating versus observing
There is an important distinction between seeing data and acting on data. If you cannot diagnose performance at the store and SKU level inside Walmart, you are not operating. You are observing. Observation does not fix revenue leakage. Operators do.
Most supplier analytics programs are built around observation. They help teams see dashboards, review trends, and track high-level KPIs. That is a starting point, not a finish line. Operating means knowing why a specific store's in-stock dropped, whether the issue is phantom inventory or a replenishment gap, and what to do about it before the next buyer conversation.
That level of diagnostic speed requires a workflow that does not begin with an hour of file preparation. It requires the kind of granular, immediate clarity that Glass demanded from his own Saturday morning meetings, now extended to every supplier team that manages a Walmart account.
The workflow to get there before it matters is what breaks down.
The smallest operating unit is where margin is won or lost
David Glass understood something that still applies thirty-five years later: scale is not about seeing more data. It is about seeing clearly at the level where decisions actually happen. Regions do not sell products. Stores do. And within those stores, individual SKUs either perform or they do not.
Walmart built an entire data infrastructure around that principle. The supplier teams that win are the ones who can actually use it at that level. Not once a quarter in a deep dive. Every week in a morning review. That is where phantom inventory gets caught before a buyer notices. That is where replenishment failures get escalated before they cost the next forecast cycle. That is where the margin lives.
Scale is not about seeing more. It is about seeing clearly.
The question for every Walmart supplier team is whether their current analytics workflow lets them reach that level of detail on a weekly cadence. If the answer is no, the issue is not a lack of data. It is a workflow that was never designed to get there fast enough.
A different starting point
At Zoom Retail Analytics, the approach starts from the same principle Glass operated by. Focus on the smallest operating unit. Make store and SKU level performance the default view, not an aspirational drill-down that only happens when someone has a free afternoon. Build the workflow so analysts start with exceptions and anomalies instead of spending the first hours of the day preparing files.
That means the same raw exports suppliers already download from Scintilla can become the starting point for organized, filtered, prioritized analysis without the spreadsheet gauntlet in between. The data Glass made available to suppliers decades ago finally gets used the way he intended: at the level where it actually changes outcomes.
FAQ
Why does store-level analytics matter more than regional reporting for Walmart suppliers?
Because regions average out performance. A region can look healthy while individual stores have phantom stock, replenishment gaps, or declining trends that only surface when the data is examined at the store and SKU level.
What is the connection between David Glass and Retail Link?
David Glass played a pivotal role in developing Walmart's automated distribution network and the Retail Link program, which gave suppliers direct access to store-level sales and inventory data. That system evolved into what suppliers now know as Scintilla.
Why do supplier teams struggle to reach store-level detail every week?
Because the workflow between downloading Scintilla data and producing an actionable view is still manual and time-consuming. By the time files are cleaned, merged, and formatted, analysts have already lost the time they needed for granular diagnosis.
Get to store-level clarity every week
If your team is still spending Monday morning on file prep instead of store-level diagnosis, the workflow is the bottleneck. See how Zoom Retail Analytics helps supplier teams start with exceptions instead of spreadsheets.