Returns Are Eating Your Margin. Where AI Helps.

Most stores treat returns as a cost of doing business online. The box comes back, you process the refund, you eat the shipping, and you move on. The numbers have quietly grown large enough that this acceptance is now one of the biggest unmanaged drains on a growing store's margin.

In 2024, U.S. shoppers sent back roughly $890 billion in merchandise, about 16.9% of everything retailers sold. Online, the rate runs close to double the in-store figure, because buying something you can't touch or try on produces more mismatches. For a store doing real volume, the difference between a 15% return rate and a 25% one is often the difference between a profitable year and a painful one.

Here's the part most owners miss: a large share of those returns were avoidable, and AI is genuinely good at preventing the ones that aren't.

The leak is bigger than it looks on the P&L

Returns rarely show up as one line you can stare at. They're scattered across refunds, return shipping, restocking labor, and inventory that comes back in no condition to resell. That spread is exactly why they get ignored.

Processing a single online return costs most retailers somewhere between $15 and $30, before you account for the sale you lost. According to national returns figures from the NRF and Happy Returns, total returns reached around $890 billion in 2024, and the rate has climbed steadily as more buying moved online. Apparel takes the worst of it, with return rates commonly in the 25% to 40% range. Footwear isn't far behind.

None of that is fixed cost. It moves when you change what happens before the order ships.

Most returns are decisions, not accidents

Sort returns by reason and they fall into a few buckets. Damaged goods and honest change-of-mind are real, but they aren't the big one. The largest group, roughly 45%, comes down to fit, size, or color not matching what the shopper pictured.

That's a product-page problem, not a warehouse problem. A customer guesses at a size because the chart is vague, orders two, and sends one back. Multiply that across a catalog and bracketing (ordering several variants intending to keep just one) becomes a planned cost baked into every launch. Nearly two-thirds of shoppers now do it.

The point is that these returns are created upstream, in the listing, by an expectation gap you can close.

Where AI actually moves the number

AI earns its place by closing the fit-and-size gap that drives the most returns, and the evidence is no longer theoretical.

Tools that predict a shopper's correct size from their past orders, measurements, and how similar customers fit have measurably cut size-related returns. One peer-reviewed study across 120,000 shoppers and six European retailers found a 22% average reduction. A fashion brand under the H&M group reported a 32% drop in knitwear returns after pairing AI fit guidance with richer 3D product views, a result documented in Stord's 2026 report on AI in e-commerce.

The same engine that recommends a size also powers better product recommendations, which is the other half of the story. A shopper who lands on the right item in the first place rarely sends it back. We wrote about that side of it in our piece on AI-driven personalization for e-commerce stores.

The basics come first, and most owners skip them

The common advice gets this backwards. Owners hear "AI fit tool" and reach for the expensive, multi-week integration before doing the cheap, obvious work that captures most of the same gain.

Real measurements instead of vague S/M/L. Model height and fit notes on the page. A return policy shown on the product page itself, where most shoppers look for it and where nearly half of stores fail to put it. These cost almost nothing and attack the same expectation gap.

Do those first. Then layer AI fit prediction and 3D views onto the categories where the math justifies it. A store that buys advanced tooling on top of a broken product page is paying for sophistication it can't yet use.

Which stores this pays off for

Not every catalog has a returns problem worth solving with AI. If you sell objective-spec products like electronics or hardware, your return rate is probably already in single digits, and your budget is better spent elsewhere.

If you're in apparel, footwear, furniture, or anything where the buyer is guessing at fit, feel, or scale, this is one of the highest-return investments on the table right now. The more volume you do, the faster it pays back.

The real work is wiring it into your store

The reason these projects stall usually isn't the AI. Running a fit demo on a handful of sample products is easy. Connecting it to your live catalog, real order history, and customer data, safely and without slowing the site, is where the time and budget actually go.

That gap is the difference between a pilot that demos well and something that shows up in your monthly numbers. It's also worth getting right, because a fit tool fed partial or messy data will quietly recommend the wrong size and make your returns worse. Done properly, this is squarely the kind of AI integration work that can earn back its cost inside a season or two.

Measure it like a margin number

If you take one thing from this, make it this: track returns as a margin metric, not an operations afterthought. Look at return-adjusted margin per product, find the handful of items driving most of your returns, and fix those first. The fixes tend to lift conversion while they're at it, since the same clarity that stops a return also helps a hesitant shopper commit to the order.

Working through this?

If returns are eating into your margin and you're weighing whether AI fit or recommendation tools are worth it, this is the sort of problem we help with at Encomage. Our work usually starts by looking at where your returns actually come from, then connecting the right tool to your store's real data so it moves the number instead of just demoing well.

Let's discuss your project

Frequently Asked Questions

Explore more on this topic

Isometric line-art diagram of an e-commerce storefront split into a separate front end and back end joined by an API bridge, with a cost ledger beside the gap

Headless Commerce in 2026: What It Actually Costs

Every guide to headless commerce is written by someone who sells it. Here is the vendor-neutral version: what a headless storefront really costs to build and run, why the field data shows it is not automatically faster, why AI shopping agents do not require it, and the specific cases where it genuinely pays off.

Isometric line illustration of a forking road between two e-commerce platform towers, one marked Open Source and one marked Adobe Commerce, with a small figure deciding at the split

Magento Open Source vs Adobe Commerce in 2026

The two editions share one core but produce very different bills, workloads, and B2B capabilities. A plain-English 2026 guide to choosing between them, including Adobe's new fully managed SaaS edition.

Isometric line-art illustration of an ecommerce conversion funnel connected to gears, a speed gauge, and a rising analytics chart

Ecommerce Conversion Rate Optimization Is an Engineering Problem

The usual CRO advice treats your store as a marketing surface. The biggest conversion leaks are engineering problems: site speed, checkout architecture, and product data. A technical playbook for 2026.

Get Your Products Recommended by ChatGPT & Gemini

Get Your Products Recommended by ChatGPT & Gemini

AI assistants like ChatGPT and Gemini now recommend products by name, pulling from structured data most stores never cleaned up. Why AI shopping traffic converts better than search, and what it takes to get your Magento catalog recommended instead of skipped.

Is Your Store Ready for AI Agents to Buy From It?

Is Your Store Ready for AI Agents to Buy From It?

AI assistants now recommend products from structured data, not marketing copy. Here is what agent-ready means for your store's revenue and where to start.

The Checkout Skimmer Problem on Magento

The Checkout Skimmer Problem on Magento

Checkout skimmers steal card data from Magento stores without breaking anything. What they really cost you, why you won't notice, and how to cut the risk.

Inspired by what you’ve read?

Let’s build something powerful together - with AI and strategy.

messages
mechanizm
folder
gray background