Most CPG reps still build their call schedules on gut feel and geography. That's a problem when your SKU is quietly dying on a shelf in a store you haven't visited in six weeks.
Store-level sales data changes the equation. Instead of covering territory by habit or proximity, you prioritize by velocity — which stores are selling, which are stalling, and where a visit will actually move the needle. Here's how to make that shift practical.
Start With the Data You Actually Have Access To
Before you can prioritize, you need a data source. For alcohol brands in Ontario, the LCBO Sale of Data (SOD) feed is the most direct tool available. It gives you SKU-level sell-through by store, updated weekly. Critically, as of October 2024, the SOD now tracks convenience stores as a separate channel — meaning if you're selling into any of Ontario's 4,600+ licensed c-stores, you can pull that data independently from LCBO retail. That channel split matters enormously for call prioritization: a store that's moving units in the c-store channel may need a completely different conversation than one that's underperforming at a flagship LCBO location.
For cannabis brands, the OCS publishes a live Retail Market Conditions Map that shows average monthly sales per store by region and a Competition Score based on store density versus sales volume. It's publicly available and directly actionable — use it to rank which regions and individual stores warrant more frequent calls based on actual throughput, not assumptions.
If you're in food, beverage, or health and beauty, your primary source is usually retailer scorecards or direct POS exports from banners like Sobeys, Metro, or Loblaw. Even partial data beats none. A Mars United Commerce report from late 2025 noted that only 67% of Canadian retail media networks can connect online and offline sales — which means for most physical-retail CPG brands, your in-store POS data remains the most reliable signal you have. Don't wait for a media attribution model to tell you what your shelf is doing.
Build a Weekly Velocity Ranking by Store
Once you have a data source, the goal is simple: rank every store in your territory by trailing four-week velocity for your key SKUs. Flag the bottom quartile. Those are your priority calls — not because you'll celebrate what's happening there, but because those are the stores where a rep visit is most likely to change outcomes.
A gap in distribution or a facings reduction in a low-velocity store rarely fixes itself. Conversely, a high-velocity store that's consistently out of stock is a different kind of urgent — you're leaving sales on the table and training the retailer that your product is unreliable.
This ranking doesn't need to be complex. A simple spreadsheet scoring each store on velocity, days-out-of-stock (if available), and last visit date is enough to tell you where to go Monday morning. GreenPaths automates this through its daily shelf visibility and gap reporting tools, so reps can walk in each day with a call list ranked by actual need rather than default route order.
Match Data Signals to the Right Conversation
Store-level data isn't just a call prioritization tool — it's prep for the conversation you'll have when you get there. A store manager doesn't care about your national ACV numbers. They care about whether your product is earning its shelf space in their location.
If you're walking into an LCBO with a SKU that's trending below its FY2025-26 annual sales target — the LCBO now assesses all regularly listed products against per-SKU volume thresholds beginning June 2025, calibrated to protect 90–95% of set margin dollars — you need to walk in with a specific ask: better placement, a staff recommendation, a local event tie-in. The data gives you the hook. The rep provides the solution.
If a c-store is outselling a nearby LCBO location for the same SKU, that's a story worth telling the store manager. It reframes your product as a proven mover in the channel, not a commodity asking for shelf space.
Use Route Intelligence to Stop Wasting Calls on the Wrong Stores
Time spent at a store that doesn't need you is time not spent at a store that does. Route intelligence — knowing not just where to go, but when and why — is what separates a rep logging calls from a rep actually influencing outcomes.
GreenPaths' route intelligence layer lets managers set territory call priorities based on gap data and velocity thresholds, so reps aren't defaulting to geographic convenience. Manager dashboards surface which stores have gone unvisited longest against their risk profile, flagging accounts that need attention before they fall off a reset or miss a reorder cycle.
The practical discipline is this: every week, before you set your route, ask which stores in your territory had the lowest velocity in the past 14 days. Go there first. Everything else is maintenance.
Turn Store-Level Data Into a Feedback Loop
Data only compounds in value if you close the loop. After every call, log what you found: was the SKU in-stock, at full facings, properly priced? Did you make a change? What did the manager say?
Over time, this creates a record that connects your activity to outcomes — which stores responded to a visit, which needed a second follow-up, which consistently underperform regardless of rep attention (and may need a different strategy entirely). That record also makes your manager conversations sharper. You're not reporting on how many calls you made. You're reporting on what changed and why.
If your brand is serious about field execution in Canadian retail, GreenPaths is built for exactly this workflow — pulling in sell-through signals, flagging gaps, routing reps to the highest-need stores, and capturing what happens at shelf. The data is already out there. The question is whether your team is using it to drive decisions or just to fill out call reports after the fact.