Syndicated vs. panel data: what each measures

Syndicated vs. panel data: the two-sentence version

Here is the whole syndicated vs panel data distinction in two sentences. Syndicated data measures retail sales, what was sold through which stores. Panel data measures consumer behavior, who bought what, and whether they came back. Both run off samples, both get extrapolated up to total-channel estimates, and they answer genuinely different questions.

The category analyst pulling SPINS or Circana every week is working in syndicated data. The consumer-insights team digging into repeat-purchase behavior on a new launch is working in panel data.

Syndicated POS scan data: what it measures

Syndicated retail data tracks transactions at the point of sale, and it arrives from one of two places. The first is retailer scan data, the actual POS transactions from chains that license their data to a syndicator like SPINS, Circana, or NielsenIQ. The second is distributor flow data, what got shipped from distributors, KeHE and UNFI for natural, others for conventional, to the retailers in their networks.

Both streams get reconciled and projected up to a total-channel estimate. What comes out the other end is a sales number per SKU, per retailer, per week.

It is good at a particular set of things. Which SKUs sell at which retailers. Distribution metrics, your ACV, TDP, store count. Velocity, meaning sales per store per week. Promotional lift, regional performance, share trends.

It is also blind to a particular set of things. It cannot tell you whether the same household bought your product twice. It cannot tell you whether a SKU you just launched is going to your existing customers or to net-new buyers. It has nothing on the demographics or lifestyle of the actual person buying. And it cannot see what else went into the basket.

Panel data: what it measures

Consumer panel data tracks what individual households buy over time. The major panels, NielsenIQ Homescan, Circana's panel, Numerator, recruit a representative sample of households who self-report or scan their purchases continuously.

NielsenIQ Homescan, one of the two largest US household panels, tracks roughly 100,000 households, a sample that projects to total US household purchase behavior by demographic cut. Circana's panel is comparable in scope. Both report with a lag of several weeks and publish at a coarser frequency than syndicated scan data does.

What comes out is a longitudinal record of every measured household's purchase history, projectable to the total US population, or to a demographic slice of it, by household demographics.

It is good at the things syndicated data is blind to. Repeat purchase rate after trial. Buyer demographics, income, age, household composition, region. The cross-category basket, what else your buyer grabs on the same trip. Penetration, the share of households buying your brand at least once. And source of volume, the question of whether your growth is stealing from competitors, growing the category, or some of both.

It has its own blind spots. It is poor at real-time weekly sales movement, because the cadence is slower and the per-cell samples are smaller. It cannot say much about performance at a specific retailer below the major-chain level. And it struggles with small or new SKUs, where the per-SKU sample is just too thin for a reliable read on a long-tail item.

Where they overlap and disagree

Both syndicated and panel data report some version of "category dollars," and the two numbers usually disagree. Sometimes by 5%, sometimes by 30%. A few reasons why.

Universe differences are the big one. Syndicated data measures stores that license their POS. Panel data extrapolates from household purchases no matter where the purchase happened. Channels one covers and the other does not, DTC, Amazon, regional chains, Costco, convenience, account for a lot of the gap on their own. Whole Foods is its own special case here. It does not report scanner data to SPINS, Circana carries it inside conventional grocery, and NielsenIQ projects its sales through panel data, so "Whole Foods sales" is a number that changes depending on who you ask. On top of that, every syndicator and every panel runs a different projection model. And the definitions diverge: a "category" built from SPINS attributes is not the same object as a "category" built from the NielsenIQ hierarchy, so cross-source category numbers are rarely apples-to-apples until someone normalizes them.

So when the numbers disagree, the useful reaction is almost never "which one is right." It is "what is the actual question, and whose universe matches it better."

A worked example: a new flavor launch

A wellness snack brand launches a new flavor of its bestselling bar in Q1. By Q2, the question on the table is the one every launch raises: is the new flavor growing the brand, or just cannibalizing the original?

Syndicated data, SPINS in this case, gives you this much. The new flavor's ACV after 12 weeks is 38% in Natural Channel. Its velocity is $29 per store per week at carrying stores. And the original flavor's velocity is down 4% at stores carrying both, flat at stores carrying only the original. That read points at mild cannibalization in the dual-SKU stores, the original is a little soft exactly where the new one showed up. But is that cannibalization for sure, or just noise? The syndicated data shrugs.

Panel data does not shrug. It says 62% of the new flavor's buyers in the first 8 weeks were new to the brand entirely, no SKU bought in the prior 52 weeks. Another 21% were existing buyers who traded up to the new flavor and bought the original less often as a result. The last 17% were existing buyers who added the new flavor without cutting back on the original at all.

That cuts the question clean. 62% net-new buyers means the new flavor is genuinely growing the brand, not just shuffling existing buyers around. The 4% velocity dip on the original at dual-SKU stores is real cannibalization, but only the 21% slice of it, and against 62% new buyers the launch comes out net-positive.

You cannot get to that conclusion without panel data. Syndicated data alone will never tell you whether the $29 per store per week on the new SKU came from new buyers or from existing ones who simply switched.

A practical decision rule

Most weekly category and sales reporting runs on syndicated data. Most strategic and innovation work pulls panel data in alongside it.

When the numbers disagree significantly

Here is a scenario that comes up all the time. The brand's SPINS natural-channel sales are up 12% year-over-year. The panel says brand penetration is down 3%. So which one is wrong?

Neither. They can both be true at the same time, because they are measuring different things. SPINS up 12% means the brand's dollar sales through measured natural retailers are growing, and that could be velocity gains, distribution expansion, price increases, or all of the above. Panel penetration down 3% means fewer households bought the brand at all over the trailing year, which could happen because the brand converted fewer new buyers even as the buyers it kept bought more, bigger baskets or more frequent trips per household.

Put those together and the real story emerges: the brand is extracting more dollars per buyer while losing ground at the top of the funnel. That is a different strategic problem from "we are growing on both dimensions" and a different one from "we are shrinking on both." Look at only one source and you would set the wrong strategy with full confidence.

The cost asymmetry between syndicated and panel data

Brands adding panel data to their syndicated read for the first time usually get surprised by the same thing: panel data costs a lot more per actual cell of insight than the POS contract led them to expect.

Rough US-market pricing as of 2026. Syndicated POS, SPINS, Circana, NielsenIQ, runs $30,000–$150,000 a year for a brand-level contract with multi-retailer coverage, scaling with retailer count, category depth, and add-on banners like Kroger total. Household panel data, NielsenIQ Homescan, Circana Panel, Numerator, runs $40,000–$120,000 a year for full demographic and category access at the brand level. Numerator's receipt panel sits at the low end of that band, the legacy Nielsen and Circana panels at the high end, especially once buyer-level retailer attribution is in the deal.

The asymmetry is not in the absolute dollars, the two ranges overlap. It is in what each dollar buys. A syndicated contract gives you weekly SKU-level sales across hundreds of retailers and thousands of stores. A panel contract gives you demographic-cut household behavior on a small sample, projectable but inherently noisier the further down into a sub-category you push.

So the practical budget order is almost always the same. Brands pay for syndicated first, because it is the operating-system data for weekly sales tracking, and they add panel later, when a specific strategic question, repeat rate, source of volume, demographic profile, is clearly worth the marginal $50,000-plus a year. Panel is the analytical splurge. Syndicated is the utility bill.

Smaller brands tend to put panel data off until a Series B raise or until they clear $10M in revenue. Before that, the decisions panel data would inform are not load-bearing enough to justify what it costs. Once a brand is placing national distribution bets, fighting for shelf in a category where source of volume actually moves a retailer buyer, or running a new-item launch program it needs to defend, panel data starts earning its keep, and the cost per decision drops fast, because the same dataset ends up informing five or six strategic calls in a year rather than one.

Doing this in Scout

Scout's primary surface is syndicated retail data, the SPINS extracts your team uploads weekly, presented as shared dashboards that sales, category, and commercial leadership all read off the same page. Panel data is not integrated into Scout today. The panel use cases, repeat rate, source of volume, demographic profile, generally live in a separate workflow on the panel vendor's own platform. The split most teams settle into: Scout for the weekly syndicated cadence, panel data for the quarterly strategic reads and innovation decisions.

Summary + further reading

The core of it: syndicated data measures store-level retail sales, panel data measures household-level consumer behavior. They disagree on category numbers because they cover different universes with different projection rules, and neither is wrong for disagreeing. Most weekly category reporting is syndicated, while panel data is the right tool for repeat rate, buyer demographics, and source-of-volume questions. And when the two disagree, diagnose the cause instead of crowning a winner. More often than not they are both telling a true story, just about different things.

Related: What is SPINS data? · Reading SPINS panel coverage