Sell-through rate = (units sold ÷ units received) × 100. Use the same time window for both: units received means beginning on-hand plus everything you received during the period. Pick a reporting rhythm and retail category for benchmark context. All calculations stay in your browser. Free tools hub · Inventory turnover · synthquery.com/tools.
Aligns labels and exports with how you review receipts (formula is the same; consistency matters for storytelling).
Multi-product comparison
SKU name
Units sold
Units received
Empty rows are ignored. At least one row needs both units sold and units received.
Trend periods (optional)
Enter aggregate or representative sold/received per period to plot sell-through over time (e.g. fiscal weeks or months).
Period label
Units sold
Units received
About this tool
Sell-through rate tells you what share of the inventory you put in front of demand actually left the building in a defined window. In the simplest form, you divide units sold by units received—where “received” means everything that became available to sell during the period, typically beginning on-hand inventory plus inbound receipts—and multiply by one hundred for a percentage. That single number is a favorite in retail merchandising because it connects buying decisions to customer pull without getting lost in accounting valuation debates the way some financial ratios can.
Wholesalers and distributors use the same construct when they measure how aggressively channel partners or accounts digest allocations across a season or promo cycle. When sell-through is strong relative to your plan, you are converting receipts into revenue before carrying costs, obsolescence risk, and markdown pressure compound. When it lags, you get early warning that size curves, pricing, or assortment depth may be misaligned—often weeks before the income statement shows the pain. SynthQuery’s calculator keeps every keystroke local: you build a multi-SKU comparison table, optionally layer consecutive periods for a trend view, pick weekly, monthly, or quarterly language that matches your operating cadence, and compare results to illustrative category benchmarks that frame expectations without pretending to be a live peer database.
The introduction you read here anchors the longer sections below: “How to use” walks through data alignment for buyers and analysts; “What this tool does” explains multi-line logic, trend charts, and exports; “Use cases” translates the ratio into retail floors, wholesale reviews, and clearance strategy; “Technical details” differentiates sell-through from inventory turnover in plain language; the comparison table contrasts this free workflow with heavier analytics platforms; and the FAQ tackles definitions, benchmarks, improvement levers, and how this metric interacts with GMROI, DSI, and stock-to-sales thinking you may already track elsewhere.
What this tool does
The comparison grid is the heart of the workflow: each line captures a SKU name, units sold, and units received, with empty rows ignored so you can keep scratch space without breaking validation. The engine computes sell-through as a percentage for every populated row, flags rows where sold units exceed received units (often a data-definition mismatch rather than a miracle sellout), and rolls up a weighted-style blended view by summing sold across SKUs and dividing by the sum of received units—useful when you want one headline number for a class without losing line-level diagnostics.
Trend mode adds parallel period labels with their own sold and received fields, then renders a line chart client-side after you calculate so initial page load stays lighter. Category selectors map to static, documented benchmark bands expressed as percentage thresholds; they exist to orient newcomers, not to replace your historical baselines or syndicated market data. Weekly, monthly, and quarterly selectors primarily drive labeling and how you narrate results to finance versus stores. PDF export uses jsPDF only when you click export; CSV export is a plain-text download. Nothing in this flow uploads unit economics to SynthQuery servers.
Technical details
Let S be units sold in the period and R be units received, defined as beginning available inventory plus all units that became available to sell during that same period, measured in consistent units (eaches, cases, or packs—never mixed). Sell-through rate equals S divided by R, times one hundred, whenever R is positive. If R is zero, the ratio is undefined because there was no replenishment basis to measure against. Values above one hundred percent usually indicate inconsistent definitions—such as counting sales from a wider window than receipts, omitting opening balances, or double-counting transfers—rather than a true operational outcome.
Inventory turnover, often expressed as COGS divided by average inventory value over time, is a different lens: it speaks to how fast capital tied up in stock cycles in dollar terms, while sell-through here is a unit-based measure of how completely a specific receipt cohort clears. The two metrics complement each other during reviews—high turnover with weak sell-through on a subset of SKUs can signal margin mix issues, while strong sell-through with low turnover might reflect premium price points or thin receipts. “Good” sell-through is not universal: grocery consumables in short periods routinely print higher percentages than furniture with long consideration cycles, which is why the tool surfaces category-specific illustrative bands rather than a single global target.
Use cases
Store and district managers review sell-through by SKU weekly to decide on visual merchandising changes, size replenishment, or inter-store transfers before corporate marks down a region. Merchants use the same ratio in monthly hindsight meetings to judge whether the buy depth matched the demand curve—especially for fashion where the cost of missing a trend is smaller than the cost of carrying the wrong color story into clearance.
Wholesale account teams track sell-through at key accounts to prove sell-in was healthy or to justify reorders and co-op displays; when the percentage stalls, the conversation shifts from “ship more” to “fix pricing, training, or placement.” Seasonal businesses run the calculator by period to compare early-season momentum against prior years, which is often more actionable than a single season-end percentage. Product launches benefit from tight windows: comparing the first four weeks of receipts against sellout shows whether sampling, influencers, or search demand converted to movement.
Markdown optimization begins with honest sell-through diagnostics—if velocity is soft while inventory is still fresh, smaller targeted incentives may work; if the ratio collapses late in the lifecycle, deeper cuts may be the only path to cash recovery. SynthQuery’s table layout makes it easy to copy scenarios from your planning system, paste numbers, and share exports with finance without rebuilding a spreadsheet template.
How SynthQuery compares
Many free calculators stop at a single numerator and denominator field, which works until you need to compare a dozen SKUs side by side or show leadership how the ratio moved across fiscal weeks. Enterprise retail analytics suites offer richer forecasting, size-level allocation, and live POS integration—but they also carry implementation time, user seats, and data contracts. SynthQuery targets the middle path: structured inputs, transparent formulas, multi-line comparison, optional trend visualization, and exports you can attach to email without spinning up a BI workspace.
Aspect
SynthQuery
Typical alternatives
Multi-SKU analysis
Table rows with per-SKU sell-through plus blended aggregate.
Single-field calculators that force external spreadsheets for comparisons.
Trend visualization
Optional multi-period rows with lazy-loaded line chart after calculate.
Static numbers only, or charts that require account login.
Category benchmarks
Illustrative retail category bands with clear educational disclaimers.
Opaque “good/bad” labels without definitions, or no context at all.
Privacy
Client-side math and exports; no unit data sent to SynthQuery for this tool.
Hosted FP&A tools that persist scenarios in vendor clouds.
How to use this tool effectively
Start by locking the measurement window. Sell-through is only meaningful when “sold” and “received” describe the same calendar or fiscal slice—otherwise you are mixing an eight-week selling season with four weeks of receipts and the percentage will mislead every stakeholder in the room. Decide whether you are reporting weekly sell-through for floor reviews, monthly for Open-to-Buy meetings, or quarterly for wholesale sell-in retrospectives; the math does not change, but consistent vocabulary prevents apples-to-oranges debates.
Gather units sold from the same source of truth you use for operational reporting: POS net of returns if you are store-based, marketplace fulfilled units if you are omnichannel, or shipment confirmations if you are measuring distributor depletion. For units received, add beginning on-hand units for the SKU (or category aggregate) to everything that arrived during the period, including transfers from DC to store if those units became available to sell. Exclude damaged or quarantined receipts only if your policy consistently excludes them from “available to sell” everywhere else.
Enter each SKU on its own row so you can contrast heroes against dogs inside the same class. Choose the retail category that best matches your assortment for benchmark shading—fashion, electronics, grocery, home, sports, or a general mixed profile—remembering that every banner is unique. Press Calculate to see per-SKU sell-through, a blended aggregate across the table, and optional trend points plotted when your period rows contain valid numbers. Use Export CSV or PDF when you need an immutable attachment; use Reset when you pivot to another door, another season, or another vendor.
Limitations and best practices
Sell-through is sensitive to definitions: consignment inventory, drop-ship sales, BOPIS pickups, and marketplace commissions can all change whether a unit counts as “received” or “sold” in your internal model. Always document the rules you use before comparing results across banners or years. Returns and exchanges should follow the same netting convention your merchant organization already uses in planning meetings. Benchmark bands in the app are static teaching aids, not statistically derived medians from a panel of retailers—substitute your chain’s historical curves when setting targets. This utility is educational and not tax, legal, or investment advice.
Size economic order quantities when replenishment policy meets sell-through reality.
Frequently asked questions
Sell-through rate measures what percentage of the inventory made available during a period actually sold in that same period. The common formula is units sold divided by units received, times one hundred, where units received includes beginning on-hand inventory plus inbound receipts that became available to sell. It is a merchandising and operations metric that helps teams see whether buying depth matched customer demand before markdowns or carryover inventory accumulate.
For this calculator, use the total unit base you were trying to sell through: starting available units for the SKU (or aggregate) at the beginning of the window plus every unit that arrived and was available for sale during the window. Exclude units stuck in QC or damaged hold if your operating definition of “available” excludes them everywhere else. Align transfers, DC allocations, and returns so you do not double-count or omit flows your merchant team already discusses in Open-to-Buy.
There is no universal threshold. Grocery and consumable categories often show very high sell-through in short horizons because purchase frequency is high and pack sizes turn quickly. Fashion and seasonal apparel may target strong in-window sell-through before a planned markdown cadence, while home and big-ticket items naturally move slower. Use the category benchmark bands in the tool as orientation, then anchor targets to your own trailing seasons, competitor shelf checks, and margin requirements rather than an anonymous internet number.
Sell-through, as implemented here, is unit-based and tied to a specific receipt cohort and selling window. Inventory turnover typically divides COGS by average inventory value over time, describing how fast dollars cycle through stock. A business can show decent turnover while certain SKUs underperform on sell-through if mix shifts toward higher-velocity items, so planners often review both: turnover for capital efficiency narratives and sell-through for assortment and depth decisions.
Mathematically the ratio can exceed one hundred percent if units sold are greater than the denominator you labeled as received. That usually signals inconsistent time windows, missing opening inventory, duplicate sales counting, or returns treated differently between numerator and denominator. When the tool flags that pattern, reconcile definitions with your inventory ledger before presenting the figure externally.
Start with demand signals: fix size curves, localize assortments, and align visual merchandising with how customers actually shop the category. Pricing and promotion should be tested with disciplined ladders rather than panicked cuts. For wholesale, improve training, point-of-sale materials, and in-stock persistence at accounts. Operational fixes—faster replenishment, fewer phantom outs, accurate site inventory—often lift sell-through before you touch the buy. Measure each intervention with the same formula so improvements are comparable.
Use the cadence your team already uses to make decisions. Weekly views help stores react to in-season trends; monthly aligns with many financial and OTB cycles; quarterly suits wholesale reviews or long-cycle categories. The percentage math is identical—the period label keeps narratives aligned with the calendar you paste from POS or ERP exports.
No. This calculator runs entirely in your browser like other SynthQuery client-side utilities. PDF generation loads jsPDF locally when you click export. Follow your company policy on how you distribute exported files even though numbers are not transmitted to SynthQuery servers for this feature.
Exports reflect the inputs and outputs visible at export time. If you change a row after exporting, regenerate the file so stakeholders never reference stale scenarios. Accuracy is limited by the integrity of the unit counts you supply; the tool does not audit your ERP.
Keep each row on the same time window and use consistent unit definitions. For dramatically different price points, consider pairing sell-through with margin or cash metrics elsewhere in your stack so a fast-moving low-dollar SKU does not mask a slow high-margin hero. The blended aggregate sums sold and received across rows—useful for class-level headlines while still reading individual lines for action.