Returns Are Rising. Which Products Need Attention First?
Compare products fairly, separate volume from return rates and give the operations team a focused investigation with evidence attached.
Returns are up. Which products should the operations team investigate first?
The product with the most returns may also be the biggest seller. A higher return rate may matter more, but a sharp percentage change based on a handful of deliveries can give a misleading impression. The review needs to show where the change is substantial and what evidence would help explain it.
Consider a Canadian distributor reviewing two product lines: storage bins and travel mugs. Delivery records, returned quantities, receipt dates and reason codes are available for analysis. The manager wants to choose a focused investigation for the next operations meeting.
Give every delivery the same observation window
The manager compares products delivered in June and July 2026. These delivery groups are often called cohorts. Records are complete through September 7 and reviewed on September 8, so every delivery has had time to complete the agreed observation window.
For this review, a return unit is an original delivered unit received back within the first 30 days after delivery. The return rate is those units divided by the original units delivered in that month. Both months use exactly the same window. Later returns remain outside this comparison, even though the June deliveries have had more time to generate them.
The analysis counts each original unit once, includes partial returns at their actual quantity and converts cases and individual items to consistent units. Cancelled orders and free replacement deliveries are excluded from both sides of the comparison. Return requests awaiting receipt are tracked separately.
A delivery can have several return records, and a return shipment can contain several units. Record counts, returned units and affected orders describe different things. Check the links to original deliveries and identify unmatched records before accepting the totals. If recent records are incomplete, move the comparison back to groups with complete observation windows.
Explore: separate sales growth from a changing return rate
Using these records, the manager can ask AIREA:
Compare June and July delivery groups by product using the agreed return window of 30 days. Show delivered units, returned units, return rate and the change in percentage points. Identify unmatched return records separately.
AIREA can generate tables and charts that the manager can inspect and question further.
In this example, storage bin deliveries rise from 1,000 to 1,500 units. Returns rise from 40 to 60, while the rate stays at 4%. Travel mug deliveries stay at 1,000 units, but returns rise from 20 to 60. Their rate moves from 2% to 6%, an increase of four percentage points.
Across both products, returned units double from 60 to 120. Deliveries increase from 2,000 to 2,500 units, and the combined return rate rises from 3% to 4.8%.
Both products now have 60 returned units. The bins' increase is consistent with higher volume at an unchanged rate. The mugs account for 40 additional returns at the same delivery volume, making them the stronger starting point for investigating deterioration.
The manager can also ask:
Apply each product's June return rate to its July delivered quantity. Compare that reference number with actual July returns.
That calculation gives 60 bin returns and 20 mug returns, or 80 altogether. Actual returns are 40 units above this reference, all from mugs. Using product rates accounts for the changed product mix; applying the overall June rate to every July unit would obscure that distinction. This comparison helps set priorities without establishing a cause.
Keep credits and financial impact separate
The operations review counts physical units. Finance may also need the value of credits, but credits can be posted later, cover price adjustments or relate to earlier deliveries.
Where reliable links exist, examine credits associated with the selected returns separately, stating the posting cutoff and currency. In this example, financial amounts would be reported in CAD, excluding sales tax. Do not treat credits posted during July as the monetary equivalent of July's returned units.
Freight, inspection, repair and disposal costs need their own records. Credit value alone does not establish the full cost of a return or the savings from preventing one.
Follow the reason code into the evidence
A reason code gives the investigation a direction. “Leaking” describes a reported problem; it does not establish whether the cause is a defective seal, assembly, handling or use.
The manager follows up:
For travel mugs, compare return reasons across both delivery groups. Show units returned for each reason and the rate per delivered unit. Show missing reasons separately, then compare product versions and delivery channels where records support it.
Compare similar groups before assigning blame. A product's overall rate can change because more deliveries went through a channel with a different return pattern. Check sample sizes and compare the same channel or version across periods before treating a segment difference as an explanation.
Here, July's 60 returned mugs include 42 coded “leaking”. Of those 42, 30 are linked to one production batch. That concentration warrants inspection, but the batch's share of delivered units also matters. A batch supplying most deliveries could naturally account for many returns.
The next step is to establish delivered quantities by batch and inspect the relevant returned units. If batch links are incomplete, record that gap and ask the warehouse lead to verify the records before ranking batches by return rate.
Analyze: make the investigation choice reviewable
The manager opens the useful generated outputs and uses Lineage View to review the process steps in plain English. They check the delivery groups, observation window, units, exclusions and calculations against the intended question and source records.
The product comparison and reason breakdown become Pinned Evidence. Key Context records the data cutoff, counting rules, known changes and unresolved batch links. AIREA can then generate an Analysis Result from that evidence and context.
The proposed action is specific: the quality lead will review the mug returns coded “leaking”, inspect available units and verify batch delivery quantities before the next operations meeting. The stable bin rate remains part of the workload review. The evidence supports an investigation priority; the team still needs to establish the cause and choose any corrective action.
Share the question the team needs to resolve
After reviewing the current Analysis Result, the manager can use Share to send it with Pinned Evidence and Key Context attached. If either changes, the result must be generated again before sharing.
The receiving team can see why mugs need attention, which records support that choice and what remains uncertain. People responsible for quality, service and commercial decisions decide what to change and whether customer contact is needed.
Bring a returns question from your next operations review to an AIREA pilot conversation. Start with comparable delivery groups and a clear decision about what to investigate first.
Bring your next business question.
Explore how AIREA could fit the way your team works.
Join the pilot