Loop Returns

Loop sits on top of Shopify and runs the return itself — the portal the shopper uses, the label, the exchange, the refund. Because it is Shopify-native, every record it holds already carries the Shopify order and line item ID. There is nothing to match. It connects and the detail is simply there.

What you get. The reason the shopper actually chose, at line level. Whether the return became a refund, an exchange or store credit. What the item was exchanged for. The condition it came back in and what was done with it. Loop's reason list runs to parent and child pairs — far more specific than the ten values Shopify records on its own.

Why that matters. "Size" is not an insight. "Ran small, exchanged for the next size up" is. The first tells you a product has a returns problem. The second tells you to grade the pattern up half a size, and it tells you before you commit the next production run.

Questions it answers. What is the real reason behind our worst returning style. How many of our returns are exchanges rather than lost sales. Which products are being exchanged into, and are we stocked for that. Is the fit problem one direction or both.

What it needs from you. A Loop API key, which you generate in your own Loop account. Read access is enough.

One honest note. Loop only sees the returns that went through Loop. If some of your returns are handled outside it — a marketplace return, or one processed by hand — those still appear in Reportly from their own source, but without Loop's extra detail. Reportly shows you which is which rather than blending them into one number.

‍