Sales Nowcast

How to build a pre-earnings channel check for a retail chain

Black-and-white photo of an empty parking lot bordered by a row of trees.

A channel check is still the backbone of pre-print work on a retail name, but the term covers a sprawling set of methods, from a few phone calls with a regional manager to a formal survey across franchise locations. Before you can build one, it helps to separate what holds up at scale from what is really just anecdote dressed up as data.

What a classic channel check covers

Most initiation reports and PMs ask for roughly the same mix: calls with vendors and former employees, a handful of store visits in your coverage markets, maybe a read from a card-panel provider, and whatever the sell-side consumer team is hearing from franchisees. Add in app-based footfall data if your desk pays for it. Each piece tells you something, and each also has a blind spot.

A regional manager call is one person's read on one region. A card panel captures spend, not units or traffic, and it lags. An app panel only sees the slice of the population that opted into location sharing on that particular app, which skews younger and urban and rarely covers the full store base.

None of that makes these checks worthless. It means they're built on samples, and a sample can be wrong in either direction without you knowing it.

Where the gaps actually show up

The gap matters most on names with a long tail of smaller-format or rural locations, where app panel penetration is thin, and on multi-banner retailers where management guides to a blended comp that hides divergence between banners. If your store visits happen to land in a market running hot or cold relative to the chain, you anchor the model on that visit without realizing it's an outlier. Most of this legwork also happens in the final two or three weeks before the print, right as the quiet period kicks in, so there's no clean way to go back and check whether week six of the quarter looked different from week eleven.

What's missing from most checklists is a layer that's objective, covers every location in the chain rather than a sample of it, and updates often enough to show a trend building or breaking before management gets on the call.

Adding a traffic layer to the checklist

The calls and store visits still matter. A traffic layer gives you something to check them against: if a vendor contact says traffic felt soft in week nine, you can look at the actual count for that week instead of taking the call at face value. Because a daily vehicle count pulled from satellite imagery covers every lot in the footprint, it reaches the rural stores and small-format banners the app panels miss, and it runs for the full quarter, so you can tell whether a slowdown is a one-week blip or a six-week pattern. Sales Nowcast builds exactly that: a daily, seasonally adjusted vehicle-count index per chain, delivered as a time series, so the traffic read already exists before you're on the call asking management to explain it.

A workable pre-print checklist, roughly in order, looks like this:

  • Pull consensus and the prior guide for the comp range you're underwriting
  • Line up your usual vendor and franchisee calls for the back half of the quarter
  • Run whatever card-panel or app-panel data your desk already pays for
  • Schedule store visits in two or three markets, ideally ones where you don't already have a strong view
  • Layer in a chain-wide traffic count that covers every location, not just the ones you can drive to
  • Mark the inflection weeks on a calendar and check your other sources against them

At least one piece of this check needs to be a full count of the chain, running daily. Three store visits and a vendor call are a sample, and a thesis built on a sample alone is a guess with good production values.

If you want to see what that daily traffic read looks like for a name on your coverage list, that's the whole reason Sales Nowcast exists.

Get started

← Back to the blog