Cost per SKU
Cost per SKU is one of the most important metrics in fulfillment because it directly shows how economically viable an individual product variant really is. Many teams know revenue per SKU, but underestimate process-related costs along the entire value chain: from goods receipt through storage and picking to returns handling.
The key point: A SKU with high demand can still be unprofitable if packaging is too complex, picking routes are long, or the return rate is above average. Conversely, slow-moving SKUs can be profitable when they run through stable processes and cause low error costs.
What Cost per SKU Really Means
Cost per SKU refers to the average total cost incurred for a specific item number over a defined period. Depending on the objective, calculations can be performed on three levels:
- Direct process costs per shipment such as pick, pack, label, and postage
- Fully allocated cost per SKU including proportional overhead
- Contribution-margin-oriented SKU costs including returns and service effects
It is important that the data basis remains consistent and that a uniform evaluation period is used.
Typical Cost Blocks per SKU
- Goods receipt and put-away
- Storage space and tied-up capital
- Order picking
- Packaging and materials
- Postage and carrier surcharges
- Returns processing
- Error, rework, and goodwill costs
- IT, admin, and management overhead
Calculation Logic for a Reliable SKU Costing Model
Cost per SKU = (Direct costs + proportional overhead costs + risk costs) / shipped units of the SKU
Four points are mandatory:
- Define cost categories clearly
- Set allocation keys for overhead costs
- Assign return costs according to causation
- Separate one-time special costs from recurring standard costs
Example Cost Structure by Cost Type
Operational Data Collection Without Flying Blind
In practice, costing rarely fails because of math, but because of incomplete data. A robust setup combines warehouse events, shipping data, return reason, and timestamps for process steps.
Recommended Rollout in 30 Days
Checklist for Data Quality
- SKU master data is maintained clearly and without duplicates
- Pick, pack, and shipping times are recorded with timestamps
- Returns are categorized by root-cause clusters
- Carrier costs include surcharges and special services
- Overhead allocation key is documented and approved
- Period and version of the costing model are archived traceably
Derive Management Actions from the Metric
Cost per SKU is only valuable when it leads to concrete decisions.
- Portfolio management: Identify SKUs with permanently negative margin
- Process optimization: Move high runners into faster pick zones
- Packaging design: Reduce material usage and volumetric weight
- Carrier strategy: Optimize rate mix per SKU or product group
- Returns reduction: Improve product data, images, and sizing guidance
Comparison Before and After Optimization
Scale
High margin, low return rate, low picking costs.
Measure: Increase visibility and volume in a targeted way.
Optimize
Stable demand with clear process losses.
Measure: Improve packaging, picking process, and rate mix.
Delist
Weak margin with high return and service burden.
Measure: Review assortment and prioritize alternatives.
Common Errors in SKU Costing
1) Average values without segmentation
If all SKUs are treated the same, averages hide the actual cost drivers.
2) Looking at returns only as an overall rate
Without root-cause clusters such as fit, defect, or expectation mismatch, targeted countermeasures are missing.
3) Allocating overhead arbitrarily
A fixed percentage on revenue seems convenient, but is often not based on actual causation.
4) Mixing special costs into standard metrics
Project costs for relocation, system changes, or campaign peaks should be shown separately.
Practical Example: From Transparency to Decision
A mid-sized shop analyzes 120 SKUs. Result: 18 variants cause disproportionately high costs due to volumetric weight and above-average returns. Instead of immediate delisting, three measures were implemented:
- Packaging redesign for eight affected SKUs
- Revision of product presentation and size guidance
- Carrier switch for two shipping zones
After two cycles, the cost metric for the affected SKUs dropped by an average of 11 percent. At the same time, the return rate in the group decreased by 2.4 percentage points.
Recommendation for Teams
Anyone who wants to use the metric sustainably should establish a recurring review:
- Monthly SKU top list by highest costs
- Clear owner per measure in warehouse, purchasing, shop, and service
- Test windows with measurable target value per lever
- Review after 30 and 90 days
- Document successful standards in packing and process instructions