Integrations and data sources
What Scout connects to
Back office and point of sale, distributors, retailer portals, syndicated panels, and the spreadsheets nobody has gotten around to automating. New integrations land continuously, so a source that is not named below is an onboarding conversation rather than a dead end.
Below the list: every portal ships its own reports, its own column names, and its own definition of a week. Our guides go report by report and column by column: what each field means in the portal's own words, what the report can answer, and what it cannot.
The most expensive mistake in this whole category is reading distributor data as consumer demand. A distributor knows what it shipped to a store; it cannot see the register. Where that distinction matters, these guides say so explicitly. For the analysis methods that sit on top of this data, see /learn; for the vocabulary, the CPG glossary.
Systems we read
Back office and point of sale
PDI Technologies · Petrosoft Retail360 · CStoreOffice
The systems a store already runs on. Scout reads the item file, the invoice history and the register export, then works across every site at once, which is the view a single-store back office was never built to give. Where you would rather not run one at all, Scout can hold the item file itself. More on these sources.
Distributors and wholesalers
KeHE · UNFI · C&S
Order books, cost catalogs and shipment history, pulled on a schedule rather than downloaded by hand. Cost changes and pack-size changes land as events you can see, instead of as a surprise on an invoice.
Retailer portals
Walmart · Kroger 84.51 · Whole Foods · Target · Publix · Costco · Sprouts · Wegmans
Each portal ships its own reports, its own column names and its own definition of a week. Scout harmonizes them so a number means the same thing across all of them.
Syndicated panels
SPINS · NielsenIQ · Circana
Panel data alongside first-party numbers rather than instead of them, so a category read and your own sell-through sit in the same view. More on these sources.
Whatever you already have
Spreadsheets · CSV and Excel exports · ERP and accounting
The exports nobody has gotten around to automating yet. A spreadsheet is a first-class source in Scout, which matters because it is usually the only place some of the data exists.
Not seeing yours? The list keeps growing, and it is not a menu you are limited to. If your data comes out of a system that is not named here, that is a normal onboarding conversation rather than a blocker.
Report-by-report portal guides
Written one portal at a time, so this is a much shorter list than the one above and is meant to be. Each guide is the deep read on a portal we already connect to.
For brand teams
Distributor and retailer portals that report how your products moved: shipments, fill rate, voids, and the reports that look like sales but are not.
KeHE CONNECT Supplier: reports and columns
What every report in the KeHE CONNECT Supplier portal contains, what each column means, and the one question none of them can answer.
KeHE CONNECT Supplier · 9 report groups
Kroger 84.51 OnDemand: reports and columns
What lives in the Kroger 84.51 OnDemand portal, which report answers which question, and what every export column actually means.
Kroger 84.51 OnDemand · 5 report groups
UNFI Insights: reports and columns
What every report in UNFI Insights contains, what each column means in the portal's own words, and why nine of the twelve cannot be backfilled.
UNFI Insights · 7 report groups
For retail buyers
Buyer-side portals for order books, cost catalogs, and the authorization lists that decide what a store can actually order.
No guides published yet.
For store operators
Point-of-sale reporting: what the register recorded, at what price, and how the exports map to categories and departments.
No guides published yet.