Tracking Return Reasons to Reduce Future Returns

Zainab runs an online fashion business in Abuja. She sells clothing and accessories through Instagram and her website, fulfilling orders from her studio apartment turned mini-warehouse and delivering across Abuja through a network of dispatch riders. The business has grown steadily over two years, and her return rate of roughly fourteen percent of delivered orders is within the range she has been told is normal for online fashion retail.

What Zainab has not done is look carefully at why those returns are happening. She receives returned items, processes the exchange or credit, and moves on. She has a vague impression that size is the most common issue and that some products seem to come back more than others, but these impressions are formed from the physical experience of handling returns rather than from any systematic record.

If she were to track return reasons over a two-month period, she would discover something that would change her approach to both her product selection and her product presentation. She would find that forty percent of her returns cite sizing inconsistency as the reason: the item fits differently from the size chart on the product page. She would find that twenty percent cite colour discrepancy: the colour received does not match the colour shown in the product image, particularly for items photographed in direct sunlight that appears lighter than the actual fabric. She would find that fifteen percent cite quality below expectation: the fabric weight or finish is finer than the product description and images suggest.

Each of these return reasons points to a specific, correctable problem. The sizing inconsistency returns point to a size guide that is either inaccurate or presented unclearly. The colour discrepancy returns point to a photography approach that should use more accurate colour rendering. The quality expectation returns point to product descriptions that create expectations the actual product cannot always meet. Fixing these specific problems would reduce Zainab's return rate, not through better returns handling but through eliminating the causes of returns before orders are placed.

This article is about the return reason data that makes this kind of root-cause reduction possible: what data to capture, how to analyse it for actionable patterns, what the most common return reasons in Nigerian retail reveal about the underlying problems they point to, and how Odoo's returns management capabilities capture and analyse this data as a natural part of the returns processing workflow.

Why Most Nigerian Retailers Do Not Track Return Reasons

The Operational Focus Problem

When a customer returns a product, the operational priority is completing the return transaction efficiently and moving on to the next customer. This operational focus is entirely appropriate in the moment and is the right orientation for the staff member processing the return. Its consequence, however, is that the return reason information, which the customer has either stated explicitly or implied through their description of the problem, is not captured in a form that accumulates into analysable data.

A staff member who processes twenty returns in a week and accurately completes each transaction but records no return reason data has contributed nothing to the business's understanding of why products are coming back. The return reason the customer provided, which was the most valuable information in that interaction, has been registered mentally by the staff member and then lost when the next customer arrived.

The cultural norm in Nigerian retail of not asking probing questions about returns, out of concern that the customer will feel interrogated, sometimes extends to not recording the reason they volunteered. This is a missed data opportunity that compounds over every return handled without a reason code. The cost of capturing the reason is seconds. The value of the pattern it reveals, accumulated across hundreds of returns, can be measured in reduced return rates and improved product decisions worth significant annual financial impact.

The Missing Connection Between Returns and Buying Decisions

Even in businesses where some return reason tracking exists, the information is rarely connected to the buying and product selection decisions that could address the underlying causes. The buyer who selected the product, the merchandiser who wrote the product description, and the photographer who shot the product images are typically not reading the returns data that tells them what customers are finding wrong with the product when they receive it.

This disconnection between returns intelligence and buying intelligence means that the same problems recur season after season. Products from suppliers whose size consistency is poor are reordered because they sell well, without accounting for the return rate that is reducing the effective revenue generated by each unit sold. Products whose descriptions consistently create expectations that the actual product fails to meet are re-listed with the same descriptions because no one has connected the return reason data to the description review process.

Building the connection between return reason data and buying decisions is the organisational change that converts return reason tracking from a quality management activity into a commercial profitability improvement. When the buyer reviews return rates by product and return reasons by product as part of their reorder decision process, they have a complete picture of product commercial performance that unit sales data alone cannot provide.

The Most Common Return Reasons and What They Indicate

Sizing and Fit Issues

Sizing and fit is the most common return reason in clothing and footwear retail globally, and it is equally dominant in Nigerian fashion retail. A return attributed to sizing or fit can indicate one of three underlying problems, each of which requires a different corrective response.

The first is an inaccurate size guide. If the measurements listed on the product page for a specific size do not accurately represent the garment's actual measurements, customers who follow the guide will receive garments that do not fit as expected. The correction is to re-measure the garments and update the size guide to reflect accurate dimensions.

The second is a product with unusual sizing relative to the standard for its category. Some garments from specific suppliers or regions run consistently smaller or larger than the nominal size label suggests. A product description that notes runs small relative to standard sizing and recommends sizing up sets the right expectation for the customer before they order, reducing the rate of sizing-related returns without changing the product itself.

The third is a customer who ordered online without being able to try the garment and simply guessed wrong. This return reason is less correctable through product description improvement and is better addressed through a generous exchange policy that makes the size correction easy, converting a potential customer loss into a loyalty-building service interaction.

Distinguishing between these three causes requires more than counting sizing returns. It requires noting whether the sizing complaint relates to a specific product, a specific supplier's range, or the customer's general expectations, which is the level of detail that a well-designed return reason coding system captures.

Product Description Discrepancy

Returns attributed to the product being different from its description or images represent a specific opportunity for improvement because the product itself has not changed. What needs to change is the accuracy of the information provided about the product before purchase. These returns are entirely preventable without supplier changes, product reformulations, or logistics improvements. They require only better product information.

The specific discrepancies most commonly cited in Nigerian online retail returns include colour rendering that does not accurately represent the actual fabric colour, fabric weight or texture that is different from what the product image and description imply, product dimensions that are listed incorrectly or in an ambiguous format, and construction quality that the product images do not clearly convey because the photography angle or lighting obscures relevant details.

Each of these discrepancies points to a specific element of the product listing that should be improved. Colour discrepancies suggest that photography guidelines should specify colour-accurate lighting conditions. Weight and texture discrepancies suggest that product descriptions should explicitly state the fabric weight in grams per square metre for clothing items where this is relevant. Dimension discrepancies suggest that the measurement process and listing format should be reviewed. Construction quality discrepancies suggest that close-up detail photography should be standard for products where construction matters to the customer's purchasing decision.

Quality Below Expectation

Returns citing quality below expectation indicate a mismatch between the quality level the customer expected based on the product presentation, pricing, and description, and the quality level they actually received. This mismatch can exist at the product level, where a specific product's quality is inconsistent or lower than acceptable, or at the category or brand level, where the customer's overall quality expectation for products at a certain price point is not being met.

Product-level quality returns point toward supplier quality management: the need for incoming quality inspection that catches quality below standard before products are listed or dispatched. Category-level quality expectation returns point toward pricing and positioning alignment: ensuring that products are priced and presented in a way that sets appropriate quality expectations rather than implying a quality level the product cannot consistently deliver.

For Nigerian retailers sourcing from domestic manufacturers or small-scale producers, incoming quality inspection before products are accepted into stock is particularly important because quality consistency may be lower than for internationally standardised products. A simple incoming inspection protocol that checks the critical quality attributes for each product category, before the product is listed for sale or dispatched to a customer, catches quality issues that would otherwise generate returns after the customer receives the product.

Wrong Product Received

Returns citing the wrong product being received are order accuracy failures rather than product quality or description issues. As discussed in the order accuracy article earlier in this series, these returns represent a fulfilment process problem rather than a buying or merchandising problem. They are addressed through the operational process improvements described in that article: better order capture, structured picking processes, and verification steps at key handoff points.

The commercial value of distinguishing wrong product returns from quality or description returns in the return reason coding is that it correctly attributes the problem to the fulfilment process rather than the product, which directs the corrective effort to the right function. A retailer who conflates wrong product returns with description discrepancy returns in an undifferentiated quality code will investigate the product description when the actual problem is in the picking process.

Building a Return Reason Tracking System

The Return Reason Code Structure

A return reason code structure should be specific enough to direct corrective action but not so granular that it creates data entry complexity that staff will work around with generic codes. For most Nigerian retailers, a structure of six to ten primary reason codes, with optional secondary codes for the most common primary reasons, strikes the right balance.

A practical set of primary reason codes for a Nigerian retail business covers sizing or fit, colour discrepancy, quality below expectation, product different from description, wrong product received, changed mind or no longer needed, product fault or defect, and delivery damage. Each of these codes points toward a different corrective action domain: sizing toward size guide accuracy, colour discrepancy toward photography, quality toward supplier management, wrong product toward fulfilment accuracy, and product fault toward returns tracking for supplier warranty claims.

The secondary code structure allows more specific attribution within the most common primary categories. Within the sizing category, the secondary code distinguishes between too large, too small, and unusual proportions. Within the quality category, it distinguishes between fabric quality, construction quality, and finish quality. This level of specificity is most valuable for the categories where return rates are highest, because it provides the granularity needed to identify whether the problem is consistent across all products in the category or concentrated in specific products or suppliers.

Connecting Return Reasons to Product Records

The return reason data becomes its most commercially valuable when it is connected to the specific product being returned rather than aggregated across all returns in a period. A return reason code recorded against the specific product SKU allows the return rate and return reason profile for each product to be calculated from the accumulated records.

A product with a return rate of twenty percent where sixty percent of the returns cite sizing as the reason is a specific, actionable data point. It tells the buyer that this product has a sizing issue that is generating returns at a rate that may be reducing its net profitability below what the gross sales figures suggest. The decision about whether to continue stocking this product, request revised size guides from the supplier, or update the product listing with clearer sizing guidance is much better supported by this specific data than by the general observation that returns seem high on this product.

In Odoo's returns processing workflow, the return reason is captured at the time of processing and associated with both the customer's return record and the product record. The product-level return reason analysis is then available as a standard report that the buying team can review as part of their product performance assessment, alongside the sales velocity and margin data that the same system provides.

Using Return Reason Data to Reduce Future Returns

The Product Listing Review Process

Return reason data should trigger a periodic product listing review process that uses the data to identify which specific product descriptions, images, or size guides need improvement. A quarterly review that identifies the ten products with the highest return rates and the most common return reason for each produces a manageable improvement list that the merchandising or content team can work through systematically.

Each improvement should be documented with the before and after state of the product listing and the expected impact on return rate. After the improvement is implemented, the return rate for the affected products should be monitored in the following period to assess whether the change produced the expected reduction. This measurement closes the improvement loop and builds the analytical capability to predict which types of listing changes are most effective at reducing returns.

For Nigerian retailers managing a large product range, the product listing review process benefits from prioritisation. Not every product with an above-average return rate warrants equal attention. Products that generate high return volumes in absolute terms, products with very high return rates that may be undermining their net profitability, and products in categories where a systemic issue (such as sizing inconsistency across a supplier's range) suggests that a single improvement would benefit multiple products simultaneously deserve the highest priority.

Supplier Quality Conversations Grounded in Data

When return reason data identifies a pattern of quality or sizing issues concentrated in a specific supplier's products, the data provides the specific, quantified evidence needed for a productive supplier quality conversation. A conversation that presents a supplier with the information that your products in size medium are generating a twenty-two percent return rate where the primary reason is too small compared to a five percent return rate for medium sizes from other suppliers in the same category is a conversation grounded in specific evidence that the supplier can investigate and respond to.

This data-based approach to supplier quality conversations is more productive than general expressions of concern about quality or sizing, because it gives the supplier a specific problem to investigate rather than a general criticism to defend against. Suppliers who receive specific return reason data and who can trace the pattern to an identifiable production variable, a new fabric source, a change in the cutting template, or a quality control gap at a specific stage, are suppliers who can make targeted improvements that reduce the return rate in subsequent seasons.

Category-Level Return Rate Benchmarks

Over time, the accumulated return reason data allows Nigerian retailers to establish category-level return rate benchmarks: the expected return rate for each product category given its specific characteristics and customer base. These benchmarks provide the context for evaluating individual products' return rates as above or below normal for their category, rather than comparing all products against a single universal benchmark that does not account for category-specific factors.

A twelve percent return rate for an online fashion retailer is normal. A twelve percent return rate for a pharmacy selling consumer health products would be unusually high. A five percent return rate for a high-end jewellery retailer might be high relative to their category benchmark. Category-specific benchmarks, built from the retailer's own historical data, are more useful as performance evaluation tools than generic figures drawn from international retail research that does not account for the specific characteristics of Nigerian retail markets and consumer behaviour.

How Odoo Captures and Analyses Return Reason Data

Return Reason Capture in the Returns Workflow

Odoo's returns management workflow includes a return reason field that is captured at the time of processing. The reason codes are configurable to match the specific code structure the retailer has defined, ensuring that the data captured reflects the categories most useful for the business's specific analysis needs rather than a generic universal set.

The return reason is associated with the specific product being returned, the specific customer, and the specific original sale. This multi-dimensional association means that the return data can be analysed by product, by customer segment, by product category, by supplier, or by time period, allowing the most relevant analytical view to be generated for each specific management question.

Return Analytics and Product Performance Reporting

Odoo's reporting capabilities allow return rates to be calculated by product, by category, and by supplier from the accumulated return records. The buying team can view a product performance report that shows each product's sales volume, revenue, gross margin, and return rate in a single view, providing the complete commercial picture needed to assess whether a product's sales performance justifies its continued stocking when return-adjusted net revenue is lower than gross sales suggest.

The return reason breakdown by product, also available from Odoo's returns reporting, shows not just how much a product is being returned but why, which is the information needed to distinguish products with correctable description issues from products with genuine quality problems from products where the return rate reflects appropriate customer behaviour rather than any specific problem with the product or its presentation.

Data2Bots: Returns Data Strategy for Nigerian Retailers

Configuring Odoo's return reason tracking for maximum commercial value requires decisions about the code structure, the reporting views, and the connections between returns data and other business data that reflect each retailer's specific analysis priorities. Data2Bots works with Nigerian retail clients to define the return reason code structure that will be most useful for their specific product categories, configure the reporting views that make the returns analysis accessible to the buying and merchandising teams who need to act on it, and build the data connections between returns performance and product, supplier, and customer management that convert the returns data from an operational record into a commercial intelligence resource.

Their training for returns data analysis covers the review process for identifying which products warrant listing improvements, the supplier quality conversation skills needed to use return reason data effectively in vendor management, and the benchmarking methodology for evaluating return rates within the context of category-specific expectations. To schedule your free thirty-minute discovery consultation, visit data2bots.com/odoo-erp-nigeria.

Conclusion

Zainab's fourteen percent return rate is within normal bounds for online fashion. What it is not is irreducible. The sizing inconsistency returns, the colour discrepancy returns, and the quality expectation returns are each the product of a specific, correctable problem that systematic tracking would reveal and analytical discipline would address. The returns that remain after those corrections are the genuinely unavoidable ones: customers who simply change their mind or who could not have been given better information in advance.

The difference between a fourteen percent return rate and a nine percent return rate, applied to a business processing hundreds of orders per month, is a material reduction in the cost of processing returns, the postage and logistics cost of return shipping, the staff time consumed by returns handling, and the occasional customer relationship loss that a difficult returns experience produces. Achieving that reduction costs nothing in product investment or marketing spend. It costs the analytical discipline to capture return reasons systematically and the organisational commitment to review the patterns they reveal and act on them.

Odoo provides the return reason capture and the analytics. Data2Bots implements them with the Nigerian retail expertise to make the data useful from day one. The returns reduction that follows is the compound return on a one-time investment in getting the data right.