Morning returns queue
Priya Sharma, customer experience lead at Northwind, asked which returns were waiting to be processed. Memtro listed the open returns with their outcomes and label status. Her team worked through them in order.
Loop Returns + Memtro
Which returns are waiting to be processed?
Loop Returns connects Memtro to your Shopify store's returns. It reads returns by state and date with their items, reasons, outcomes and label status, and one return with its notes. It also reads the advanced shipping notice of returns in transit and which items of an order can be returned. When asked and granted, it can note, flag, process, close or cancel a return, remove items from it, and create a return link. Loop can also tell Memtro as returns are submitted, change or close, and a job can start on it. Each event type is added in Loop Admin.
In Memtro
What you can do with Loop Returns in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Loop Returns tool, reads what it needs, and answers with the source cited.
What it does
- 01Returns created or updated in a window, with state, outcome, order, item count, return method and label status.
- 02One return by id or order name, with every item, reason and outcome, and its internal notes.
- 03The advanced shipping notice of returned items in transit, and an order's per-item return eligibility.
- 04When asked and granted, adds an internal note, flags a return for review, or closes, cancels or removes items from a return. The customer is not told of a flag.
- 05When asked and granted, processes a return, issuing its refund, exchange or credit, which moves money, or creates a return link for an order.
- 06With events on, a return submitted, a return closed or a return label created in Loop can start a job.
Acts when asked
When you ask it to
These tools change something in Loop Returns. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
- 01Add an internal note to a return
- 02Flag a return for review
- 03Process a return, issuing its refund, exchange or credit
- 04Close a return without fulfilling it
- 05Cancel a return
- 06Remove items from an open return
- 07Create a return link for an order
Events
When it happens
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Loop Returns, choosing the same kinds; the tab shows Loop Returns's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Loop Returns signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooks- 01A return was submitted
- 02A return changed (including closed, cancelled or expired)
- 03A return was closed
- 04Queued processing of a return failed
- 05A return shipping label was created
- 06A return label's status changed
- 07Returned items were restocked in Shopify
- 08A gift card was requested for an exchange
- 09A Happy Returns shipment was processed
- 10Loop needs a label for a return
- 11A label request was cancelled
In practice
Ask it like you would a colleague
Once Loop Returns is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Loop Returns + MemtroWhich returns are waiting to be processed?
Show the return for order #1001 with its reasons.
Which returned items are in transit this week?
Can the customer on order #1042 still return the jacket?
Flag the return on order #1001 for review.
New return starts a job
When a customer submitted a return at Acme Ltd, Loop told Memtro and a job started. It read the return with its items and reasons and summarised it for Dan Fletcher, the returns manager. Nothing was processed until he asked.
Teams
Where it fits
The teams that lean on Loop Returns most, a question each of them asks, and what they connect beside it.
- OperationsMonitors and digests that run themselvesOperations lead, Analyst, Team manager, Administrator“List my jobs”Used alongside Help Scout, Stripe, Xero, Postgres, ShipEngine and 8 more.
- SupportAnswer tickets with the whole company behind youAgent, Team lead, Escalation owner, Head of support“Which VIP conversations have been waiting more than a day?”Used alongside Help Scout, HubSpot, Postgres, Xero, Stripe and 8 more.
- FinanceAsk the ledger questions in plain EnglishFinance lead, Credit control, Management accountant, Founder or CFO“Which invoices over £5k are more than 30 days overdue?”Used alongside Xero, Stripe, Postgres, HubSpot, QuickBooks Online and 10 more.
Better together
Works with
A record in Loop Returns is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
- Finance and commerceLoop Returns with XeroInvoices, bills, contacts and reports, answered in plain English with figures cited to Xero.
- Finance and commerceLoop Returns with StripeCustomers, charges, invoices and subscriptions through a restricted key.
- Finance and commerceLoop Returns with FellohBookings, payments, refunds, chargebacks, supplier payments and payouts from the travel payments platform.
- SupportLoop Returns with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportLoop Returns with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportLoop Returns with IntercomCustomer conversations and the people behind them, in your company memory.
- Email, calendar and chatLoop Returns with GmailSearch and read mail so the last thread with a customer is one question away, and send the reply when you ask.
- Email, calendar and chatLoop Returns with SlackSearch messages, read channel history and threads, post when you ask, and answer when mentioned.
- Email, calendar and chatLoop Returns with Google CalendarMeetings in a window, event details, and the next two weeks synced into memory, and events it can create, change or cancel when you ask.
Also in Shipping and delivery
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Setup
How to connect
Connect withAPI key
- 1
In Loop Admin, open Returns Management → Tools & integrations → Developer Tools and generate an API key with the Returns and Orders scopes. Leave Carts unticked.
- 2
In Memtro, open Connections → Loop Returns and paste the API key.
- 3
An administrator grants the actions by name, such as Process a return, to the teams that may use them. Events are turned on from the connection's Events tab, and the address is then added as a webhook for each topic in Loop's Developer Tools.
- 4
Ask "Which returns are waiting to be processed?"
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Loop Returns tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in Loop Returns?+
Only when you ask, and only what it has been granted: add an internal note to a return; flag a return for review; process a return, issuing its refund, exchange or credit; close a return without fulfilling it; cancel a return; remove items from an open return; create a return link for an order. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
Who can use a Loop Returns connection?+
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my Loop Returns data?+
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
How do I connect Loop Returns?+
API key. In Loop Admin, open Returns Management → Tools & integrations → Developer Tools and generate an API key with the Returns and Orders scopes. Leave Carts unticked.
Can Loop Returns start a job?+
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Loop Returns, choosing the same kinds; the tab shows Loop Returns's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Connect Loop Returns in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.