.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiSKU rationalization isn't a glamorous topic, but it's the thing separating brands with healthy margins from brands sitting on warehouses full of inventory nobody wants. If you've typed "what is SKU rationalization in ecommerce" into a search bar at 11pm while staring at a P&L that doesn't add up, you're not alone. Here's the plain-English version, no consultant-speak required.
SKU rationalization is the process of reviewing every SKU in your catalog and deciding, with actual data, whether to keep it, consolidate it, or kill it. That's the whole definition. Nothing mystical about it.
But it's not just "delete the slow sellers and call it a day." Real SKU rationalization also means merging near-duplicate variants that are splitting demand for no reason, and fixing SKUs that are priced wrong or positioned in the wrong category. A product isn't automatically a bad SKU just because it's not selling. Sometimes it's a good product with a bad price tag.
Here's a scenario that plays out constantly in DTC: a brand carries 400 SKUs. Sixty of them generate 80% of revenue. The other 340 sit around as dead weight, tying up cash, taking up 3PL shelf space, and quietly draining ad budget on campaigns that will never scale. That's catalog bloat in a nutshell, and it's exactly why this process exists.
Excess SKUs don't show up as one big obvious cost. They bleed you slowly, in places most dashboards don't surface clearly.
Start with inventory carrying costs. Every SKU you hold, whether it sells or not, costs you storage fees, insurance, and capital tied up in product sitting on a shelf. Add in per-slot warehouse or 3PL fees, and a catalog with too many low-velocity variants starts costing real money just to exist. Low-demand SKUs also tend to carry higher return rates, often because they were never a great fit for the customer base to begin with.
Then there's the ad spend problem. A bloated catalog forces your media budget (and your team's attention) across SKUs that were never going to scale, which drags down your blended ROAS even when your top performers are doing fine on their own. You end up optimizing campaigns for products that don't deserve the spend.
And the cash flow angle is the one that actually keeps operators up at night. Capital stuck in slow-moving inventory is capital that isn't funding a restock of the SKUs actually driving revenue. For operations teams trying to plan inventory and cash runway, that's not a minor inefficiency. It's the difference between restocking on time and scrambling.
Not sure if you're overdue? Look for these:
If two or three of these sound familiar, you're already overdue.
This doesn't need to be complicated. Five steps, repeatable.
Step 1: Pull unified SKU-level data. Sales, margin, return rate, and ad spend, all at the SKU level, not just top-line revenue. This is where most brands get stuck, because that data usually lives in three or four different platforms. A unified view, like what BI reporting is built for, is the difference between a real analysis and a guess.
Step 2: Run an ABC analysis. Bucket SKUs into A (top revenue and margin), B (steady, dependable), and C (long tail, barely moving). This gives you a shape to work with instead of 400 individual decisions.
Step 3: Cross-reference velocity against contribution margin. A SKU that sells a lot but on razor-thin margin isn't automatically a winner. Sometimes your highest-volume SKU is actually a candidate for a price increase, or a cut.
Step 4: Decide, per SKU. Keep as-is, reprice or reposition, bundle with a proven seller, or discontinue. Four buckets, no fifth option where you just "keep thinking about it."
Step 5: Set a cadence. Quarterly is standard for most DTC brands. This isn't a once-a-year spring cleaning. Catalogs shift every season, and a SKU that looked dead in Q1 might be your best seller in Q4.
Most of the damage from SKU rationalization doesn't come from cutting too much. It comes from cutting on the wrong signal.
The most common mistake: cutting purely on revenue. A SKU that sells modestly but at 70% margin can be more valuable than a high-volume SKU at 15% margin. Revenue alone tells you popularity, not profitability.
Second mistake: ignoring seasonality. Discontinuing a winter coat SKU in July because it hasn't sold in 90 days isn't rationalization, it's bad timing. Always check whether a SKU's slow period is permanent or just the calendar.
Third, and this one's almost universal: doing the whole analysis in spreadsheets pulled manually from Shopify, Amazon, and ad platforms. It's stale within two weeks of building it. By the time you act on the data, the data's already wrong.
Fourth: ignoring halo effects. Some low-selling SKUs exist to support a bundle, a subscription tier, or a gift set. Cut the standalone SKU and you might quietly tank your bundle's conversion rate too. A good review accounts for how SKUs function together, not just in isolation.
The baseline is pretty specific: unit sales, revenue, gross margin, ad spend attribution, and return rate, all joined at the SKU level, not the order level or the category level.
Most teams struggle here because the platforms don't make this easy. Shopify reports performance one way, Amazon Seller Central reports it another way, and your ad platforms attribute spend differently from both. None of them sync automatically, and reconciling them by hand is where most SKU reviews quietly die before they even start.
The teams that do this well go a step further and layer forecasting and simulation on top of that joined data. Instead of guessing what happens if you cut a SKU, you can actually model the revenue and cash flow impact before you pull the trigger. That's the difference between a confident decision and a nervous one.
SKU rationalization is only ever as good as the data feeding it. Cut decisions made on fragmented, manually stitched reports tend to be wrong in ways that don't show up until a quarter later, when you realize you killed a SKU that was actually propping up a bundle.
Unified dashboards and forecasting make this a quarterly habit instead of an annual fire drill. If you're still asking what is SKU rationalization in ecommerce and whether it's worth the effort, the honest answer is: it's worth it the moment your data stops living in five different tabs.
Before your next catalog review, it's worth seeing your SKU-level performance in one place. Start here if you want a sense of what that actually looks like.
explore more insights
3 min read
3 min read
3 min read