The same return arrives twice
How you'll know: Stock goes up by two for one returned item, or the ERP shows a duplicate credit.
Fix: Loop delivers at least once and retries failures up to five times. Record what you've handled and ignore repeats.
Before anyone writes code against Loop, check its integrations list. Your helpdesk, email tool or 3PL may already be on it. Whatever isn't, usually the WMS, the ERP or something homegrown, goes through Loop's API and webhooks. That route runs in two directions, and most stores have only built the first.
If returns sit in the warehouse waiting for someone to log into Loop, it's the two-way half you're missing.
Keys go in the X-Authorization header. Scopes include returns, orders and destinations; grading needs the returns scope. Loop's grading guide says API access has to be enabled for your store, through your Merchant Success Manager or Loop support.
Watch for: the Label API, the Webhooks API and the Ship by Loop API. They need OAuth 2.0, not a key.
Grading and disposition work on line_item_id. The Return webhook carries it, and so does the return details endpoint.
Grade Items records condition, from grade_a to grade_d, or incorrect_item, missing or junk. Assess Dispositions records what happens next: back_to_stock, resale_hold, recycle, donate or missing. Each call takes up to 20 items.
Watch for: assuming one call covers both. It doesn't, and a return graded but never dispositioned leaves the restock decision open.
Send a process event when the goods check out, or a flag when they don't, and add a return note saying why so the support team can see it.
Watch for: a 200 with the body true. It means Loop queued the work, not that it's finished. A 200 with an errors body is a refusal, and no webhook will follow.
return.closed tells you processing finished. return.processing.failed tells you it failed in the background. Update the warehouse record only on the first.
How you'll know: Stock goes up by two for one returned item, or the ERP shows a duplicate credit.
Fix: Loop delivers at least once and retries failures up to five times. Record what you've handled and ignore repeats.
How you'll know: Retries pile up after a busy weekend of returns.
Fix: Loop counts anything slower than ten seconds as a failure. Accept the event, queue it, and do the posting afterwards.
How you'll know: Counts drift between the store and the warehouse after returns close.
Fix: Pick one system to own inventory and drive it from the Restock topic. The Loop Returns page goes through that and the store credit booking that trips up the books.
Yes. It has REST endpoints for returns, orders, labels, grading and disposition, plus webhooks. Most calls use an API key made in Loop's Developer Tools; the Label, Webhooks and Ship by Loop APIs use OAuth 2.0.
One-way means your systems receive Loop's data and react to it. Two-way means your warehouse also writes back: grading items, recording dispositions and processing or flagging returns through the API, so Loop finishes the return without anyone opening its admin.
Yes. Topics include Return, Return processing, Label, Label requests, Restock and Gift card, and return events fire when a return is created, updated and closed. Loop retries failed deliveries and may send one more than once.
Loop runs as a Shopify app and doesn't document how the app itself is built. What you can rely on is that the public API and webhooks work alongside it, so a store can keep the app and build whatever its settings don't cover against those endpoints.
Its integrations page lists Gorgias, Klaviyo, Attentive and Rise for customer experience, ShipBob, ShipHero and Ryder for logistics, and EasyPost for labels. Check that page for the full current list before planning custom work.
Whoever has the time: your developers, or n-frames. We set up the keys and OAuth, the webhook listener, the grading and processing calls from your WMS, and the ERP postings, and test each against a real return.