Fashion & Apparel × Loop Returns

Returns Are the Single Biggest Margin Killer in Fashion. Loop Tells You the Rate. Agentis Puts It in Every Order's Margin.

In fashion and apparel DTC, returns are not a customer-service function: they are the P&L. A brand shipping 30% return rates at $14.50 round-trip cost per return is burning $4.35 per order on returns alone, before any other cost. For a $75 AOV brand doing 120,000 orders a year, that is $522,000 annually in pure returns logistics, and it does not count the restocking, inspection, re-tagging, steaming, or write-off cost on items that come back damaged. Loop Returns has the best dataset in the industry on return rate per SKU, exchange-vs-refund ratio, and return reason, but that data sits in a Loop dashboard, disconnected from the orders that are generating the next round of returns. This is the integration that matters most for fashion: taking Loop's SKU-level return history and making it an input to the profit floor that Agentis checks on every Shopify Plus order before it ships, so an order built around a dress with a known 42% return rate is judged fundamentally differently than one with a T-shirt that returns at 6%.

Why This Matters

The headline return rate on a fashion DTC brand is typically 25–35%, but that single number hides a bimodal distribution that is the actual story. T-shirts, sweatshirts, accessories, and bottoms in stable sizing tend to return at 5–12%. Dresses, structured blazers, denim, shoes, and anything size-sensitive return at 35–55%. When you apply the same 'free returns, free shipping over $75' policy across both categories, you are subsidizing the high-return SKUs with margin from the low-return SKUs, and because customers are not idiots, they load their carts disproportionately with the high-return items. The economics are brutal: on a $128 dress with a 42% return rate, you need to reserve 42% × (shipping cost + return shipping + restocking + 22% damage write-off) = 42% × ($9.80 + $11.40 + $4.50 + $28.16) = $22.64 per order in expected return cost. If your gross margin on the dress is 58% ($74.24), your return-adjusted margin is $51.60, or 40.3%. Still fine. But apply a 20% winback discount and free returns: $128 × 0.8 = $102.40 revenue, minus $22.64 return reserve, minus $53.76 COGS, minus $2.97 Stripe, minus $9.80 outbound shipping, minus $3 in Klaviyo touches = $10.23, or 10%, against a 25% floor. This is a $5M–$30M brand's entire margin problem in one SKU category, and it is a very common leak in DTC fashion.

How Margin Leaks At This Intersection

Three specific leaks live at the fashion × Loop Returns intersection. First, the 'bracketing' customer: someone who orders the same dress in sizes 4, 6, and 8 intending to return two. Loop sees this pattern; Shopify does not. The 'order' looks like $384 AOV, but the realized revenue is $128 and you have eaten three round-trip shipping costs. Without Loop data flowing into Agentis, bracketing orders with stacked discounts ship without a second look because the AOV looks great. Second, the 'repeat returner': Loop tracks that roughly 8% of fashion customers account for 35% of return volume, and those customers have predictable return rates on every order. That insight should affect how their next discounted order is judged, but it never does, because the Loop signal is siloed. Third, the SKU-level return cliff: Loop data shows that after 90 days in catalog, return rates on fit-sensitive items jump 6–12 points as the reviews surface fit complaints. Nothing in the order flow knows the same dress is now generating materially different return economics than it did at launch. Agentis bridges all three by consuming Loop's rolling 90-day return rate per SKU, per customer, per category, and using it in each order's profit-floor evaluation as a first-class cost.

Recommended Setup

  1. 1Connect Loop Returns to Agentis via API key and enable the return.created + return.completed webhooks so rates stay current
  2. 2Load Loop's rolling 90-day return rate per SKU into Agentis and configure a 30-day rebuild window so new catalog items adopt category-level rates until they have data
  3. 3Configure per-category return cost models (e.g., dresses $22/return, outerwear $28/return, accessories $6/return) including restocking labor and damage reserve
  4. 4Enable customer-level return rates: orders from customers with a rolling return rate >35% are checked against a stricter floor
  5. 5Turn on bracketing detection: Agentis flags orders containing 2+ sizes of the same style and can hold them before fulfillment for review
  6. 6Configure exchange-vs-refund weighting: exchanges are treated at 30% the cost of refunds since revenue is retained, tightening floors only where refund ratio is high
  7. 7Review the weekly 'return tax' report with merchandising to identify SKUs where the true return-adjusted margin is below floor and pull them from promotional calendars

How Agentis Closes The Gap

Agentis subscribes to Loop's return.created and return.completed webhooks and polls the /returns endpoint nightly to maintain a SKU-level return-rate table, a customer-level return-rate table, and a category-level return-rate table. When an order is placed, Agentis applies the deeper of the three rates to the order's projected margin: if the customer has a 38% personal return rate and the SKU has a 42% return rate, Agentis uses 42%. It multiplies that rate by the full per-return cost (outbound shipping that will be re-eaten, return shipping, restocking labor, and a category-specific damage reserve from Loop's return-reason data) and treats the result as a line-item cost. If the return-adjusted contribution margin falls below the fashion floor, Agentis flags the order within 60 seconds with the reason (for example, 'bracketing: 3 sizes of one style') or holds it before fulfillment under rules you approve, and logs it in the Evidence Ledger. On the back end, Agentis builds a 'return tax' report that shows which SKUs, which customer segments, and which promotions are driving unprofitable return volume, so merchandising and lifecycle teams can adjust pricing and promo targeting at the source.

Frequently Asked Questions

How quickly does Loop data flow into Agentis's margin calculations?

Return rates are updated nightly via the /returns endpoint poll, and webhooks fire on individual return events. Because return-rate math is inherently a trailing 90-day calculation, nightly is sufficient, as the rate for a SKU does not move meaningfully hour-to-hour. Customer-level rates update within about 15 minutes of a return being initiated in Loop.

What about brand-new styles with no Loop history?

New SKUs inherit the category-level return rate from Loop for the first 30 days in catalog, weighted toward the higher end of the range because launch reviews have not yet surfaced fit complaints. After 30 days, Agentis transitions to the SKU-specific rate. You can also manually override the rate at launch if you expect a particular style to return heavily (e.g., a new denim fit).

Does this hurt conversion by changing free returns on risky orders?

No. Agentis does not change your return policy or anything the shopper sees at checkout. It acts after the order is placed: it flags the order, or holds it before fulfillment under your rules, so your team can review it. The conversion question only comes up later, if you decide to change promo targeting or free-returns rules based on what the return-tax report shows.

How do exchanges factor in? We push exchanges aggressively and Loop handles them well.

Exchanges are weighted at ~30% the cost of refunds in the Agentis model, because the revenue is retained and only the logistics cost is lost. If your Loop data shows a SKU has a 35% return rate but a 70% exchange ratio, the effective refund rate is 10.5% and the return-adjusted margin barely moves. This is exactly the kind of nuance that single-number return rates hide.

Related Integration Playbooks

Playbook

Klaviyo Flows Are Running Your Beauty P&L. Make Sure They Are Running It Profitably.

Klaviyo flows drive a large share of beauty revenue, but GWP, samples, and discount stacking can make them margin-negative. How Agentis shows true contribution margin per flow and per order.

Playbook

Home Goods Is the Vertical Where Shipping Cost Eats Margin Alive. ShipStation Has the Data. Agentis Checks Every Order Before It Ships.

Home goods brands lose contribution margin on under-priced heavy-freight and oversize-parcel orders. How Agentis + ShipStation put real shipping cost into every order's margin check before it ships.

← Back to Fashion & Apparel overview

Free Audit, No Commitment

Protect Every Order's Profit Margin

See exactly how much margin Agentis can recover for your store in 7 days, no commitment required.