Ask the management team of most product businesses to name their most profitable products and they will answer immediately — with the products that sell the most. The two are not the same thing, but the conflation is so common that distinguishing them feels pedantic until you run the actual numbers.
When businesses do run the actual numbers — with a full cost allocation against each product line, not just a revenue and direct material view — the results are consistently surprising. High-volume products that anchor the brand narrative turn out to have margins that are below the business average, or sometimes negative once true costs are allocated. Low-volume products that attract little internal attention turn out to be disproportionately profitable. And the decision about where to focus sales effort, marketing spend, and production capacity has been running on the wrong information.
This is not a small problem. It is the most common cause of profitable-looking businesses that chronically underperform on cash flow — because they are successfully selling their way into thin or negative margins on the products they push hardest.
Why the Revenue View Lies
The revenue ranking of products is useful for exactly one purpose: knowing what customers are buying. It tells you almost nothing about which products are creating value for the business. The gap between the two measurements opens as soon as any of the following is true:
- Products have different gross margins — which they almost always do, even within a narrow category
- Products require different levels of customer service, returns handling, or after-sales support
- Products occupy different amounts of warehouse space relative to their revenue contribution
- Products have different order frequency patterns that affect transaction costs
- Products differ in the payment terms they attract, affecting working capital requirements
None of these factors show up in a revenue ranking. All of them affect whether a product is actually worth selling.
The Cost Allocation Problem
The reason most businesses do not have accurate product-level profitability is not lack of interest — it is a data architecture problem. In a typical mid-market business, the information needed to calculate true product profitability is distributed across multiple systems that were never designed to talk to each other.
Sales data lives in the CRM or e-commerce platform. Purchasing costs live in the procurement system or accounts payable. Warehouse costs live in the inventory or WMS system. Labour costs live in HR or payroll. Returns and customer service costs live in the support system. Logistics costs may live in a carrier portal or a spreadsheet maintained by the operations manager.
Calculating true product profitability requires joining all of these data sources against a specific product identifier and allocating shared costs (warehouse overhead, customer service team time, logistics infrastructure) in a principled way across the product range. When this requires manual assembly — exporting from five systems into a spreadsheet and doing the allocation by hand — it happens rarely, if at all. When it does happen, it is already out of date by the time anyone acts on it.
The products a business promotes most aggressively are usually the ones with the best story, the longest history, or the highest revenue numbers. They are rarely the ones chosen through a systematic analysis of which products actually return the most value per unit of business resource consumed.
What Gross Margin Misses
Many businesses do track gross margin by product — revenue minus direct material cost, sometimes including direct labour for manufactured goods. This is better than revenue alone, but it typically misses the majority of the costs that differentiate product profitability at the operational level.
Returns and reverse logistics. In e-commerce and retail, return rates vary enormously by product category. A product with a 30% return rate and a 40% gross margin may have a net contribution close to zero once the cost of return processing, inspection, restocking, and the percentage of returned goods that cannot be resold is factored in. Return rates are rarely tracked against the product P&L — they are managed as an operational cost by the fulfilment team without connecting back to product-level profitability.
Customer service burden. Some products generate support tickets at ten times the rate of others — due to complexity, installation challenges, quality issues, or simply poor documentation. The time your customer service team spends on one product category is time not spent on others. That time has a cost. It is almost never allocated to the product that caused it.
Warehouse footprint. A product that occupies a significant amount of racking space but moves slowly has a carrying cost that extends beyond the inventory financing cost. In a constrained warehouse, choosing to stock that product means not stocking something else. The opportunity cost of that space is real even if it does not appear on the cost of goods sold line.
Working capital consumption. Products with long supplier lead times require earlier purchasing commitments, which ties up working capital longer. Products sold on extended payment terms mean revenue is recognised before cash is received. Neither of these appears in the gross margin calculation, but both affect the real cash economics of a product line.
Contribution Margin Analysis: A More Complete Picture
Contribution margin analysis — which allocates all direct and indirect costs attributable to a product before arriving at its contribution to fixed overhead and profit — gives a more accurate picture of product-level economics than gross margin alone. The practical challenge is doing it rigorously enough to be useful.
The key methodological question in contribution margin analysis is how to allocate shared costs. Some approaches:
- Revenue-proportional allocation is the simplest but often the most misleading — it allocates shared costs in the same ratio as revenue, which is circular (high-revenue products bear more cost simply because they have more revenue)
- Activity-based allocation allocates costs based on actual resource consumption — warehouse space actually used, support tickets actually generated, logistics movements actually required. This is more accurate but requires data that many businesses do not collect at the necessary level of granularity
- Transaction-based allocation applies a cost-per-order or cost-per-unit figure for each operational category, derived from total cost divided by total transactions. Less precise than activity-based but significantly better than revenue-proportional, and achievable with data most businesses already have
The goal is not accounting precision — it is a ranking that is reliable enough to make better decisions about which products to promote, which to defend, and which to quietly retire.
The Portfolio Decisions That Follow
Once a business has a reliable product-level profitability view, several decision categories become significantly clearer.
Where to concentrate sales and marketing effort. If two products have similar revenue but one generates three times the margin, the rational choice is to disproportionately direct sales capacity and marketing spend toward the higher-margin product. Without the profitability view, the instinct is usually to promote the product with the larger absolute revenue number.
Which products to discount — and which never to discount. Discounting a low-margin product to drive volume is one of the most reliable ways to destroy profitability quickly. Knowing which products cannot absorb a discount without going contribution-negative changes how promotions are structured.
Minimum order quantities and pricing floors. For products where a significant portion of cost is order-related rather than unit-related — processing, packing, dispatch, customer service overhead per order — setting minimum order quantities or pricing adjustments for small orders can shift the economics substantially.
Portfolio rationalisation. Every product in a range has an overhead burden — it must be sourced, stocked, described, supported, and maintained in the system. Products that contribute very little margin relative to their overhead burden are candidates for discontinuation, even if their revenue looks acceptable in isolation. The overhead freed by removing them can often generate more value when redirected to higher-performing lines.
The Data Infrastructure Required
Reliable product profitability analysis requires that cost data and sales data share a common product identifier and can be queried together without manual assembly. This is a structural requirement, not a reporting preference.
In practical terms it means that purchase costs, operational costs (warehouse, logistics, customer service), and sales data need to flow through a system where they can be linked at the product level and queried on demand. Businesses running these functions in separate systems — particularly when the systems do not share a common data model — face a reconciliation problem that makes ongoing profitability analysis impractical rather than merely inconvenient.
The businesses that maintain genuine product-level profitability visibility tend to be ones where the operational and financial data live in the same platform, or where integration is deep enough that a single query can join them reliably. This is increasingly the deciding factor in whether product portfolio decisions are made on real economics or on informed intuition.
Product profitability visibility across your entire operation
Response365 Profitability Monitor connects purchasing costs, operational overhead, sales data, and returns in a single view — so you can see true contribution margin by product, category, or customer segment without building a spreadsheet from five exports.