A single secondary sales transaction takes less than four minutes to complete. The order booker walks in, checks the shelf, takes the order, logs it, and moves to the next shop. By the time he is out the door the system has already captured enough data to diagnose everything that is working and everything that is broken in that territory. Nobody reads it that way.
The receipt gets filed. The order gets processed. The data sits in a system that was built to track transactions, not to ask questions about them.
Every secondary sales visit is a diagnostic event disguised as a transaction.
What A Single Visit Actually Captures
Most companies think of an order as a line item. Product, quantity, value. That is what gets reported. That is what gets reviewed.
But the visit that produced that order generated far more than a line item. The system captured the booker who made the visit, the time he arrived, how long he spent at the outlet, which SKUs he sold, how many lines were on the bill, the total drop size, and the GPS coordinates that confirm he was actually there.
That is not a transaction log. That is a snapshot of operational health at a specific outlet on a specific day by a specific person.
When the booker arrived tells you whether the outlet was visited during its peak decision making window or during the dead hours when the owner is distracted, the counter is busy, and the order gets rushed. A booker consistently visiting a high value outlet at 3pm when the owner makes purchasing decisions at 10am is not underperforming. He is arriving after the game is already over.
How long the booker spent tells you whether the visit was a real engagement or a check in. A 2 minute visit at an outlet that carries 40 SKUs is not a sales call. It is a presence log. The booker walked in, asked if they need anything, wrote down what the retailer already knew he needed, and left. No range selling. No shelf check. No new SKU introduction. The duration reveals whether selling actually happened or whether the visit was administrative.
This is the number that hides the most revenue. If an outlet carries 8 of your SKUs but the average bill only includes 3, the booker is taking orders, not selling. He is recording what the retailer volunteers instead of walking the range and identifying what is missing from the shelf. The difference between 3 SKUs per bill and 5 SKUs per bill across 200 bookers across 22 working days is not a marginal improvement. It is a structural shift in revenue that was available every single day and nobody asked for it.
The total value of the order tells you whether the outlet is being served at its potential or at its habit. A retailer who orders the same amount every week regardless of season, promotion, or shelf depletion is ordering on autopilot. The booker is letting him. Drop size trends over time reveal whether the relationship is growing, flat, or quietly declining. A flat drop size at an outlet where foot traffic is increasing is a missed opportunity that compounds every single week.
The GPS stamp confirms the booker was physically at the outlet. But it also tells you something else. When you map the timestamps and coordinates across a full day, you see the route. You see the travel time between stops. You see whether the booker is working the territory in the sequence that maximizes selling time or in the sequence that minimizes driving effort. Two bookers covering the same territory can have a 90 minute difference in productive selling time based purely on route sequence. The GPS data already knows this. Nobody is reading it.
The One SKU Question
Here is the simplest version of what this data makes possible.
Take an operation with 200 order bookers. Each booker visits an average of 25 outlets per day. The current average is 3.4 SKUs per bill.
What happens if that average moves to 4.4 SKUs per bill. One additional SKU per transaction.
The math is not complicated. 200 bookers multiplied by 25 outlets multiplied by 22 working days multiplied by 1 additional SKU. That is 110,000 additional line items per month. Multiply by average SKU value and the revenue impact is not incremental. It is a category level shift.
One more SKU per bill is not a stretch target. It is the difference between a booker who takes an order and a booker who sells.
And the data to identify where those missing SKUs are is already in the system. Every bill that went out with 3 SKUs from an outlet that carries 8 is a receipt that already contains the diagnosis. The outlet has the range. The booker did not walk it.
Why Nobody Reads The Receipt
The reason this data goes unread is not because companies do not collect it. Most SFA systems capture all of this automatically. The booker does not even have to think about it. The app logs the time, the duration, the location, the SKUs, the value.
The problem is what happens after the data is collected.
It gets aggregated. The individual visit disappears into a daily summary. The daily summary disappears into a weekly report. The weekly report becomes a monthly number. By the time anyone in leadership sees it, the receipt is gone. All that remains is a revenue figure per territory that tells you what happened but nothing about why.
The data enters the system as a diagnostic. It exits the system as a scoreboard.
This is the cost of aggregation without interrogation. The system is designed to roll up, not to drill down. And the questions that would reveal the most about operational health are all drill down questions. Which booker is consistently under 3 SKUs per bill. Which outlets have declining drop sizes. Which routes have the longest travel gaps between visits. Which time slots produce the highest conversion.
These are not complex analytics. They are simple filters applied to data that already exists. The system has the answers. Nobody is asking the questions.
The Compounding Effect
What makes this especially frustrating is that the impact of small improvements at the transaction level compounds in ways that the monthly revenue review never reveals.
One more SKU per bill is not one improvement. It is an improvement multiplied by every outlet, every day, every booker, every month. It compounds across the entire operation simultaneously.
The same is true in reverse. A booker who spends 90 seconds less per visit than he should is not losing 90 seconds. He is losing the SKU conversation that would have happened in that time, at every outlet, every day. Over a month that is hundreds of missed selling moments from a single booker. Across a team of 200 it is tens of thousands.
Small inefficiencies at the transaction level do not add up. They multiply. And they multiply silently because nobody is looking at the level where they originate.
The Diagnostic That Already Exists
Every company running secondary sales already has a diagnostic system. They just do not know it.
The SFA is not a transaction log. It is a diagnostic engine that nobody has turned on. Every field it captures is an answer to a question that would change how the operation is managed. But the questions are never asked because the system was set up to track, not to diagnose.
| What The System Captures | What It Actually Reveals |
|---|---|
| Time of visit | Whether the booker is arriving during the outlet decision window or outside it |
| Visit duration | Whether selling happened or just order taking |
| SKUs per bill | Whether the booker is walking the range or recording what the retailer volunteers |
| Drop size trend | Whether the outlet relationship is growing, flat, or quietly declining |
| GPS route | Whether the day is optimized for selling time or for driving convenience |
The table is not theoretical. Every row represents a field that is already being captured in most SFA systems. The right column represents a question that almost nobody is asking.
The most expensive data in FMCG is not the data you do not have. It is the data you collect every single day, store in a system you trust, and never once ask a useful question about.