The short answer
Ask each retailer for a simple, recurring report of units sold and on-hand by SKU—or use a shared sheet, portal export, or POS partner report when they have one. EDI 852 Product Activity Data is the formal version of that report for big-box and chain accounts. Most independent stockists never send it. For indie doors, relationship-based reports and reorder patterns are how small brands see what moved until a connected sales source exists.
Selling wholesale to independent stores? Set up your brand on Ordrly. Core is $0/month.
Why small brands can't see sell-through the way big CPG does
After you ship an opening order, the next useful question is not "did they pay?" It is "what actually sold at the register?" That gap—units that left your warehouse versus units that left the shelf—is the difference between sell-in and sell-through. As ENDVR puts it, sell-in is the wholesale transaction; sell-through is the retailer's sale to the shopper, and sell-through is the truer demand signal.
Large suppliers get that signal as a structured feed. SPS Commerce describes EDI 852 Product Activity Data as the document buyers use to share inventory and sales by location with sellers. The same X12 purpose appears in mapping guides such as EDI Academy's 852 notes: a retailer or distributor advises a trading partner of inventory, sales, and other product activity so the partner can plan shipments or propose replenishment.
Most how-to pages assume that world. Inventory Insights and Hairball walk through weekly 852s from chains like Walmart, Target, Ulta, and CVS. Scout centers on portals such as Retail Link and KeHE Connect, plus syndicated panels from SPINS, NielsenIQ, and Circana. Independent boutiques and specialty shops usually have none of that—one POS, no supplier portal, no 852. Search results still answer as if you were onboarding a national chain. That is the open lane this guide fills.
What "sell-through data" actually means
Sell-through data is evidence of what shoppers bought (and, ideally, what is still on hand) for your SKUs at that retailer. It is not the same as:
Sell-in / wholesale orders. What the retailer bought from you. Useful, but it can sit in the back room for months.
Distributor ship-in. What a distributor shipped to a store. Opener's CPG sales-data guide stresses that ship-in is not true register sell-through; confusing the two leads to over-ordering and phantom velocity.
Syndicated market panels. Category and share views across many retailers. Helpful for pitching, expensive and laggy for day-to-day stockist ops.
At a high level, sell-through rate for a period is units sold divided by units available to sell (often units received or beginning inventory plus receipts), expressed as a percentage. Leave deep benchmarks and category tables for a dedicated sell-through-rate guide. For weekly ops, the fields that matter most are units sold, on-hand, and the period covered—not a perfect industry average.
Practical ways to get stockist sales data without EDI 852
You do not need a VAN, an AS2 mailbox, or a NetSuite connector to start. You need a repeatable ask and a place to store the answers.
1. Ask for a weekly or monthly units-sold report
Email or chat the buyer (or the owner-operator) with a short, specific request: SKU or UPC, units sold in the period, units on hand at period end, and the dates covered. Weekly is ideal for fast movers; monthly is fine for slower specialty goods. Put the cadence on a calendar so it does not depend on you "remembering to check in."
2. Get portal or POS partner access when it exists
Some independents use a POS or wholesale partner that can export sales by vendor. Ask whether they can grant a vendor login, a scheduled CSV, or a broker/rep export. Treat portal access like any other credential: one named person on your side, no shared passwords emailed around the team.
3. Share a simple sheet per account
A one-tab Google Sheet or Excel file—one row per SKU per week—beats a vague "how's it selling?" call. The retailer pastes numbers; you own the roll-up. You need a shared schedule and clear fields, not enterprise EDI.
4. Use inventory check-ins and photos as a bridge
When a store will not run reports, a monthly shelf count (or a clear photo of the facing plus backstock) is still data. It will not give you true register velocity, but it tells you whether the opening order is gone, stuck, or half-sold before you push another PO.
5. Treat reorder patterns as a proxy—carefully
If an account reorders the same SKUs every six weeks, that pattern is a signal—not true sell-through. They may be overstocking, understocking, or ordering from habit. Use reorder timing to start a conversation, then confirm with units sold or on-hand. For quiet first-order accounts, the missed reorders calculator and our missed wholesale reorders guide help quantify and win them back.
Compare the methods
Method | Effort for the brand | Accuracy for true sell-through | Burden on the retailer | Best when |
|---|---|---|---|---|
Weekly/monthly emailed report | Low setup; steady follow-up | High if fields are clear | Low–medium | Trusted indie accounts with a willing buyer |
Shared sheet | Medium (you design the sheet) | High if updated on schedule | Medium | 5–30 doors and no portal |
POS / portal export | Medium (access + mapping) | Highest among non-EDI options | Low after setup | The store's POS can export by vendor |
Shelf photos / count check-ins | Medium travel or chase time | Low–medium (on-hand, not scans) | Low | Very small accounts or early tests |
Reorder-pattern proxy | Low if you already track orders | Low as sell-through; useful as a flag | None | You need a triage list before asking for data |
EDI 852 / chain portals | High (EDI, mapping, compliance) | High at covered doors | Built into the retailer's program | You are already a mandated chain vendor |
Syndicated POS panels | High cost and contracts | Market-level, not every indie door | None to the store | Category pitches and national CPG work |
What to ask retailers for (minimum useful fields)
Ask for the smallest report that supports the decision—usually "which SKUs need a reorder, and how many?" Practical store-level guides such as Opener's make the same point. Minimum fields:
Identity: your SKU or consumer UPC, and the store or banner name
Period: start date, end date, and whether the week ends Saturday, Sunday, or another convention
Sales: net units sold in the period (confirm whether returns are netted out)
On-hand: units available to sell at period end, if they will share it
Gaps: a note when a row is missing, estimated, or covers a partial week
Optional later: retail price, promo flags, and in-stock coverage. Skip shopper names and other retailers' category files—you only need your own items' movement. Keep one working table (retailer, SKU, period, units sold, on-hand, source, next action) and preserve the raw export before you clean it.
How to use the data without overordering
Sell-through visibility only helps if it changes the next PO.
Separate sold-out from slow. Strong units sold and zero on-hand is a reorder candidate. Weak sales and high on-hand is merchandising or assortment—not a production signal.
Think in weeks of supply. Ten units a month with eight on hand is not a panic order; ten a week with eight on hand is.
Size to lead time, not ego. Cover transit plus pick or production time, add a small buffer, and do not refill to the original opening order by default.
Confirm before you push. A shared number plus a short note beats a surprise shipment. See how to get retailers to reorder and the wholesale reorder email template.
Watch the sell-in vs sell-through gap. Rising sell-in with flat sell-through means inventory is building at retail.
Where Ordrly fits today (honest)
Ordrly is built for the indie wholesale loop: catalog, connections, orders, chat, and getting the next PO started without PDF ping-pong. Per Ordrly's features page, here is what is live for this topic—and what is not.
Live today:
Brand analytics with sell-through and cohort views for accounts you sell to on Ordrly (order activity in the network—not a scrape of every indie register).
Reorder recommendations and retailer low-stock alerts so connected stores get nudged when your products run low.
Shopify catalog sync for brand inventory, public brand pages, locations and stock, and Reorder Radar for spotting reorder opportunities in Shopify data and inviting those retailers onto Ordrly.
Not live yet (roadmap / next on For Brands and Wholesale):
True observed retailer register or POS sales automatically feeding the next PO.
Vendor-managed inventory from that signal—roadmap only; see our VMI guide.
Demand forecasting as a marketed live capability—treat fuller forecast-driven planning as a future feature.
Ordrly can show sell-through-style analytics from in-network orders and make reordering easier. It cannot yet replace a boutique POS export or an EDI 852. Until observed sales sources connect, the practical methods above are how you see indie-door sell-through.
Ready to put reorders on rails while you collect better stockist data? Create your brand account. Core is $0/month; you pay a 1.5% Network Fee only when an order runs through Ordrly. Retailers stay free at retailer registration.
FAQ
How can a small brand see what its products sold at each retailer?
Ask each account for a recurring units-sold (and ideally on-hand) report by SKU, use a shared sheet or POS export when available, and track reorder patterns as a secondary signal. EDI 852 and chain portals cover big retail; independents usually need a direct ask.
What is EDI 852?
EDI 852 is the X12 Product Activity Data transaction. Retailers and distributors use it to tell suppliers what sold, what is on hand, and related activity by location so the supplier can plan replenishment. It is common in large retail programs and rare among independent stockists.
Is distributor "sales" the same as sell-through?
Usually no. Distributor reports often measure ship-in to the store or DC, not what scanned at the register. Use them as a demand signal, then confirm with retailer POS or a direct units-sold report when the decision is production or a big reorder.
Do I need syndicated data from NielsenIQ, Circana, or SPINS?
Only if you need category and competitive context across many doors. For day-to-day stockist replenishment, your own SKUs' units sold and on-hand at each account matter more—and cost far less than a syndicated subscription.
Can Ordrly pull my retailers' POS sell-through today?
Not as an observed register feed into the next PO. Ordrly today provides brand analytics from on-platform order activity, reorder recommendations, low-stock alerts to connected retailers, Shopify sync for brand inventory, and related wholesale tools. Connecting true indie POS/Shopify sales sources into the next PO is the next step on the public roadmap—not something to claim as live.
What does Ordrly cost?
Core is $0/month with a 1.5% Network Fee. Basic is $99.99/month (1.25%), Growth $449.99/month (0.75%), Scale $999.99/month (0.35%), and Enterprise is custom. Plans are monthly only; paid plans include a 15-day trial. If Ordrly introduces a retailer, a 15% acquisition fee replaces the Network Fee on that first order only (for example, $75 on a $500 order). Card and ACH processing are billed at cost. Retailers use Ordrly free.
Start with the ask, then automate the reorder
Big-box sell-through assumes EDI 852, vendor portals, and analysts to clean the feeds. Small brands selling to independents win with a clear field list, a standing cadence, and the discipline to turn units sold into a right-sized next PO.
Use Ordrly for what is live now—wholesale ordering, in-network analytics, low-stock alerts, and reorder recommendations—while you collect stockist sales data the practical way. Fuller POS visibility and VMI remain on the roadmap.
Brands: Join Ordrly as a brand. Core is $0/month, with the same software on every plan.
Retailers: Create your free retailer account to order and reorder from the brands you carry in one place.