Returns customers actually finish.
Self-service portal that prints its own label. A rules engine that prefers exchanges and store credit when the customer would. RMA tied back to the original order, the SKU's return rate, and the COGS that walks back into stock.
The shape of returns in CCEN.
Returns is the reverse-logistics app. Customers initiate from the portal, the rules engine routes the RMA, the warehouse receives and inspects, the policy resolves to refund, exchange, or store credit, and the inventory and finance loops close automatically. Every step writes to the order's audit trail.
Customers initiate, without calling.
The portal lives on your domain, branded in your style. Customers authenticate by order number and email, see their eligible items, pick a reason from a configurable list, and get back a label or a drop-off code. The whole flow takes under a minute.
The rules engine sits between the customer's selection and the outcome. Exchange before refund when the customer flagged 'wrong size'. Store credit for repeat customers who already have a return in progress. Restock fee thresholds for high-return-rate categories. Region-specific windows for EU and CA. Amazon's 30-day window applied to Amazon orders only. Shopify flexible windows applied to Shopify.
When a return needs human review, it routes to a queue with full context: the order, the customer's history, the SKU's return-rate trend, and the photos the customer uploaded. CS resolves in seconds, not minutes.
Inspect, restock, and reconcile.
When the package arrives, the warehouse scans the RMA. The mobile UI shows the expected items, the inspection checklist, and the resolution path. Receivable items go back to a configured bin (often a forward-pick or a clearance shelf). Damaged items split off to write-off with a typed reason.
Inventory updates on scan, not on close-of-day. Available count rises within seconds. The RMA closes with a typed outcome and a link back to the inspection record.
If the resolution is exchange, the new fulfillment kicks off automatically with the original shipping address. If the resolution is refund, the payment refund goes to the original method. If store credit, the customer's profile balance updates and they get an email.
Per-SKU return rates, live.
Every RMA carries a structured reason. Wrong size, color not as expected, damaged in transit, didn't match listing photo. Reasons roll up by SKU, by listing, by channel, by carrier. The merchandising team sees the listing photo that's lying. The buying team sees the SKU that should not be reordered.
Restocked inventory updates COGS automatically at the original layer's cost. Damaged units charge to a write-off ledger. Finance sees a clean accrual. The CFO does not have to ask what 'returns variance' means in your monthly close.
Returns velocity feeds the Replenishment agent. A SKU returning at 18 percent gets fewer units on the next PO than a SKU returning at 4 percent. The buying decision is informed, not abstract.
Three returns moves Loop and Returnly do not make.
Inventory closes the loop on scan
Restocked units re-enter inventory at the original landed cost the second the warehouse scans them. Available rises in seconds, not at close-of-day.
Per-SKU return rates feed buying
Reasons roll up by SKU, listing, channel, carrier. The next PO weights returns into MOQ math. Buying decisions get smarter every quarter.
Per-channel return windows
Amazon's 30-day rule, Shopify's flexible window, EU's 14-day right of withdrawal, all enforced at the rule layer. One portal, every policy.
Returns built like the rest of ops.
Self-service portal
On your domain. Branded. Auth by order number and email. Label or drop-off code in under a minute.
Rules engine
Exchange before refund, store credit for repeat returns, restock fees by category, region-specific windows.
Exchanges native
New fulfillment kicks off on resolution. Same address. Same SLA. No copy-paste between tools.
Refunds and store credit
Refund to original method, or post to customer profile balance. Customer-facing email on resolution.
Warehouse inspection
Mobile scan-in. Expected items, checklist, photo upload, typed outcome. Bin routing per outcome.
Restock or write-off
Restock to forward-pick or clearance shelf. Damaged splits off to write-off ledger with typed reason.
Per-SKU return rates
Reasons roll up by SKU, listing, channel, carrier. Find the listing photo that lies.
Closed-loop COGS
Restocked units re-enter at original landed cost. Write-offs charge a separate ledger. Clean accrual.
Buying signal
Returns velocity feeds the Replenishment agent. High-return SKUs get fewer units on the next PO.
Where returns actually come from.
Across a quarter of returns at a mid-size apparel brand on CCEN, the reasons cluster. Each reason gets a typed code on the RMA, so the merchandising team and the buying team can act on the same data. The chart is live, queryable, and exportable to your auditor.
Mia Belle Baby found one listing returning at 32 percent because the size chart was wrong. Fixed the chart, returns dropped 60 percent on that SKU in two weeks.
Carriers, accounting, and the helpdesk handing off context.
Returns reads from the carriers, writes to your accounting tool, and hands off to your helpdesk when a return needs human review.
“We thought we had an 8 percent return rate. After CCEN's per-SKU report, we found one listing returning at 32 percent because the size chart was wrong. Fixed the chart, returns dropped 60 percent on that SKU in two weeks.”
Returns that close the loop.
See the customer portal, the rules engine, the warehouse inspection flow, and the financial resolution running on real returns.