HubSpot tracks sell-in and sell-through for consumer brands by bringing sell-in from the ERP sync and sell-through data from retailer files into the same account view. Sell-in is what the brand ships to retailers, and sell-through is what consumers actually buy off the shelf. Match the two by retailer, store, and product, then report both by account, product, and region.
Leadership often combines these numbers by hand, since shipments sit in the ERP and sell-through arrives in retailer reports and spreadsheets. On one HubSpot account page, the gap between them shows which retailers need a reorder, which products are slowing down, and where a rep or trade marketer should spend the week. This guide covers the matching key, how each number reaches HubSpot, where the numbers live, the metrics that show the gap, and the alerts and dashboards that act on it. The ERP, the retailer files, and any data warehouse keep the detail.
HubSpot tracks both numbers by pulling sell-in from the ERP sync, loading sell-through from retailer files through data studio or imports, and matching them on the same retailer account, store, and SKU. Dashboards then show both side by side by account, product, and region.
The flow has four parts:
Sell-in tells you what the brand shipped to a retailer, and sell-through tells you what consumers bought at that retailer. Each number alone misleads, since strong shipments can hide slow shelves and strong shelf sales can hide an approaching stockout.
| Term | Plain definition |
|---|---|
| Sell-in | Units or dollars the brand ships and invoices to a retailer or distributor |
| Sell-through | Units or dollars consumers buy from that retailer's shelves or site |
| Sell-through rate | Units sold to consumers divided by units shipped, over the same period |
| Weeks of supply | Units on hand at the retailer divided by average weekly units sold |
| Reorder cycle | The time between a retailer's purchase orders for a SKU |
Sell-in alone can look healthy right up until a retailer stops ordering, because the product sat in the back room. Sell-through alone can look healthy while the shelf empties, because nobody planned the next shipment. Side by side, they show the reorder that's coming and the product that's stuck.
Sell-in lives in the ERP as shipments and invoices by account and SKU. Sell-through lives in retailer portals, reports, and files that arrive in different shapes from each retailer, and some retailers now sell that access as a data product.
Retail data access keeps changing. Modern Retail reported in August 2026 that Walmart is extending its Scintilla data platform to Sam's Club, and Kroger's 84.51° has announced self-service data ordering for suppliers in 2026. Each retailer's format is its own.
| Number | System of record | How it reaches HubSpot | Refresh | Grain |
|---|---|---|---|---|
| Sell-in shipments and invoices | ERP | ERP data sync, marketplace app, middleware, or custom API connection | Daily or as the sync runs | Order and line item, or rolled up by account, SKU, and week |
| Retailer sell-through | Retailer portal, report, or file | Data studio from Sheets, Excel, or a warehouse, or a scheduled import | Weekly or monthly, as the retailer provides | Store, item, and week |
| Retailer on-hand inventory | Retailer portal, report, or file | Same as retailer sell-through | Weekly | Store and item |
| Distributor depletions | Distributor reports | Data studio or scheduled import | Monthly | Account, SKU, and month |
| DTC orders | Commerce platform | Commerce data sync | As orders arrive | Order and line item |
HubSpot works best as the relationship hub while the ERP stays the source of truth for orders and inventory, a split our guide on when HubSpot should be your system of record covers in depth.
Want a second look at your sell-in and sell-through data flow? The Architecture Blueprint maps your current HubSpot setup against where it needs to be, including the accounts, products, and syncs behind a combined view.
Build one key for each retailer, store, and SKU, so a row from the ERP and a row from a retailer file land on the same record. Without matching keys, the two numbers never meet.
Model each retail chain as a parent company and each store or distribution center as a child company. HubSpot's guide to adding a parent or child company notes that a parent can have many child companies, each child has one parent, and you can associate them in bulk through import. Store each retailer's store number on the child company.
Keep your SKUs in the product library with the SKU, UPC, product line, and category. HubSpot's guide to creating and managing products covers SKUs, custom product properties, and bulk import.
Retailers often report their own item numbers. Keep a mapping table, illustrative below, that converts each retailer's code to your SKU before the data loads.
| Retailer | Retailer item code | UPC | Your SKU |
|---|---|---|---|
| Retailer A | 004471223 | 012345678905 | SUN-SPF30-200 |
| Retailer B | RB-88213 | 012345678905 | SUN-SPF30-200 |
| Distributor C | DC-5531 | 012345678912 | SUN-SPF50-100 |
Send rows that don't match to an exceptions sheet with a named owner, and review it before each weekly load. Give the mapping one owner and a change process, following our approach to property governance with data contracts.
Data source: your retailer master list, product master, and each retailer's item list.
Sign it's working: nearly every row in each retailer file matches a store and a SKU on the first load.
Sync shipments and invoices from the ERP at the grain your reports need, either every order and line item or a rollup by account, SKU, and week. The ERP stays the source, and HubSpot shows sell-in beside the relationship.
| Route | Example | Label |
|---|---|---|
| HubSpot-built data sync | NetSuite | Native integration |
| Third-party app | Apps listed on the HubSpot App Marketplace for your ERP | Marketplace app |
| Middleware | Integration platforms that connect several ERPs | Middleware |
| Custom build | Code that reads ERP APIs and writes to HubSpot | Custom API connection |
HubSpot's guide to using its integration with NetSuite lists the objects that sync, including companies, contacts, deals to opportunities, invoices, orders to sales orders, and products from several NetSuite item types, with one-way or two-way sync. Our NetSuite and HubSpot integration, powered by Commercient middleware, offers another route.
| Grain | Best for | Trade-off |
|---|---|---|
| Every order and line item | Reorder timing, order history on the account, line-level reports | More records to sync and maintain |
| Rolled-up summary by account, SKU, and week | Sell-in totals beside sell-through | Less detail for order-level questions |
Brands with a few hundred retail accounts often sync orders and line items. Brands with thousands of store-level rows often roll up sell-in to match the grain of their sell-through files.
Data source: your ERP.
Sign it's working: sell-in totals in HubSpot match the ERP's shipment report for the same period.
Load retailer files into data studio or through scheduled imports, map them to your stores and SKUs, and refresh them on each retailer's cadence. Each retailer sends a different shape, so the mapping step does most of the work.
HubSpot's data studio page describes connections to Google Sheets, Excel files, and cloud data warehouses such as Snowflake, with curated datasets flowing into segments, reports, and workflows. Data studio is part of Data Hub Professional and Enterprise, and HubSpot Credits apply when data syncs out of data studio.
| Loading option | How it works | Best for |
|---|---|---|
| Data studio from a spreadsheet | Retailer files land in a shared Google Sheet or Excel file that data studio reads | A few retailers sending weekly files |
| Data studio from a warehouse | Retailer data lands in a warehouse such as Snowflake, and data studio reads it | Many retailers or large store-level files |
| Scheduled import | A standardized file updates summary properties on each retailer | Accounts without Data Hub Professional |
Load each retailer on its own schedule, weekly for retailers with weekly portals and monthly for distributors with monthly depletion reports. Store a Last sell-through file date property on each retailer, so everyone knows how fresh the number is.
Data source: retailer portals, reports, and files.
Sign it's working: every active retailer shows a Last sell-through file date within its expected cadence.
Hold the numbers as summary properties on each retailer by default, use datasets for blended reporting, and add a custom object snapshot on Enterprise when you need history by retailer, SKU, and period.
| Option | What it handles | Limits | Tier |
|---|---|---|---|
| Datasets in data studio | Blending ERP and retailer data, then feeding reports, segments, and workflows | Credits apply when data syncs out of data studio | Data Hub Professional or Enterprise |
| Summary properties on the retailer company | Last four weeks of sell-through, sell-through rate, weeks of supply, last file date | One current value per property, so history lives elsewhere | Any, filled by import, sync, or data studio |
| Custom object snapshots | One record per retailer, SKU, and period, with units shipped, units sold, and on hand | More records to maintain | Enterprise |
HubSpot's guide to creating custom objects notes they need an Enterprise subscription and can carry their own properties and associations.
Start with summary properties on each retailer. Reps see the numbers on the account page, and workflows can act on them. Add datasets when leadership wants blended reporting across channels, and add custom object snapshots when trend reports by SKU and period need to live in HubSpot. Our technology consulting team can help you choose.
Data source: the ERP sync and retailer files from Steps 2 and 3.
Sign it's working: a rep opens a retailer record and sees both numbers for the same period without a spreadsheet.
Five metrics show the gap between sell-in and sell-through: sell-through rate, weeks of supply, the sell-in versus sell-through gap, reorder timing, and slow-moving SKUs. Calculate them on the same period and grain.
| Metric | Formula (plain text) | What it signals |
|---|---|---|
| Sell-through rate | Units sold to consumers divided by units shipped, for the period | How fast the shelf accepts what you ship |
| Weeks of supply | Units on hand at the retailer divided by average weekly units sold | When the retailer will need a reorder |
| Sell-in versus sell-through gap | Units shipped minus units sold, for the period | Inventory building up or running down |
| Reorder timing | Days since the last purchase order compared with the usual reorder cycle | A reorder that's late |
| Slow-moving SKUs | SKUs with a sell-through rate below your threshold for several periods | Products that need promotion or a range review |
A sunscreen SKU ships 1,200 units to Retailer A in four weeks, and consumers buy 840. The sell-through rate is 840 divided by 1,200, or 70%. With 600 units on hand and 210 units sold per week, weeks of supply is 600 divided by 210, or about 2.9 weeks. All numbers here are illustrative.
Data source: sell-in, sell-through, and on-hand values from Steps 2 to 4.
Sign it's working: the account owner can explain each metric for their top retailers in one sentence.
Use workflows to alert the account owner when sell-through slows or weeks of supply run low, create reorder reminders, and group retailers by performance. Per HubSpot's guide to creating workflows, workflows need a Professional or Enterprise subscription.
| Trigger | Action | Owner |
|---|---|---|
| Weeks of supply drops below your threshold | Task to confirm the next purchase order | Account owner |
| Sell-through rate falls for two straight periods | Task to review shelf placement or promotion | Account owner and trade marketing |
| Days since last purchase order passes the usual reorder cycle | Reorder reminder | Account owner |
| No sell-through file within the expected cadence | Task to request the latest file | Sales operations |
Build segments of retailers by performance, such as accelerating, steady, slowing, and at risk, so trade marketing can plan programs for each group.
Data source: the metrics from Step 5.
Sign it's working: reorder tasks arrive before stockouts, and slowing accounts get a review within the week.
Build one dashboard for reps by account, one for trade marketing by product, and one for leaders by channel and region. Each shows sell-in against sell-through for the same period.
| Dashboard | Views | Audience |
|---|---|---|
| Account view | Sell-in, sell-through, weeks of supply, and open tasks by retailer and store | Reps and key account managers |
| Product view | Sell-through rate and slow-moving SKUs by product line | Trade marketing and product teams |
| Partner scorecard | Sell-through rate, reorder timing, and growth by retailer | Sales leadership |
| Executive view | Sell-in against sell-through by channel, region, and month | CEOs and general managers |
Reports that combine companies, products, and custom objects use HubSpot's custom report builder, available on Professional and Enterprise subscriptions. When your team wants help keeping these dashboards current, ongoing HubSpot support covers report fixes and new views.
Data source: summary properties, datasets, and custom objects from Step 4.
Sign it's working: leadership reviews sell-in and sell-through from the HubSpot dashboard, with no separate spreadsheet.
Retailer-provided data carries sharing terms, so limit it to the people your agreements permit and confirm those terms before you load anything. HubSpot's permissions help you match access to the agreement.
Per HubSpot's guide to assigning access to records, Professional and Enterprise accounts can limit users to records owned by their team. HubSpot's guide to managing view and edit access for properties covers restricting individual properties on Enterprise subscriptions, such as a retailer's store-level sell-through. Review each retailer agreement with your legal team, and record the permitted uses on the retailer's company record.
Many brands use both: a data warehouse or BI tool holds item-level history by store and week, and HubSpot holds the summary and the relationship. HubSpot puts the number in front of the person who can act on it, and the BI tool answers deep analytical questions.
| Question | Where it's answered |
|---|---|
| Which retailers need a reorder this week? | HubSpot |
| Which account owner should call which buyer? | HubSpot |
| How did a promotion affect sell-through by store over two years? | Data warehouse or BI tool |
| What's the price elasticity of a SKU across regions? | Data warehouse or BI tool |
Brands without a warehouse can start in HubSpot with summary properties and datasets, and add a warehouse when store-level history grows. Our HubSpot integration library lists connections we've built, and HubSpot integration development covers systems without a listed app.
Datasets, summary properties, and standard integrations cover sell-in and sell-through for most brands. When files from many retailers need normalization, matching retailer item codes to SKUs needs custom logic, or retailers need a portal with its own interface and permissions, Brainstem Ventures by Campaign Creators adds custom capabilities that connect to your existing systems. It's a specialized software engineering capability within Campaign Creators, built to keep the systems that work and engineer what's missing.
Brands selling direct as well can bring DTC orders into the same view through their ecommerce marketing stack.
Consumer brands track sell-in and sell-through in HubSpot by syncing shipments from the ERP, loading retailer files through data studio or imports, and matching both on the same retailer, store, and SKU. Summary properties put both numbers on the account page, datasets and custom object snapshots add blended reporting and history, and workflows turn the gap into reorder tasks and reviews. The ERP, retailer files, and any warehouse keep the detail, and HubSpot shows the people who manage each account what to do next.
Campaign Creators designs HubSpot around trade accounts, orders, and products for brands that sell through retailers and distributors. As a HubSpot Elite Solutions Partner, we apply CRM architecture expertise to how consumer brands see what ships and what sells.
We map your retailers and SKUs, connect your ERP and retailer files, implement the account and product model in HubSpot, and build the dashboards your sales and trade marketing teams review each week.
Ready to see sell-in and sell-through in one view? Book a consultation with our team.