Returns stop being an inbox thread. They become a queue with evidence, a recommendation, and a decision.
A shopper files a return with photos. The recipe pulls the real order from Shopify, and AI weighs the request against your return window and policy, then stops and hands it to a person. Nothing is auto-decided. Your reviewer sees the request, the photos, and the AI recommendation in one place, makes the call, and the customer is emailed the outcome either way. Approved refunds can be issued straight through Stripe.
Free · no credit card · you connect your own apps
Installing provisions each one, wired together and ready to run.
Customer-facing intake: order, reason, photo evidence. Publishing it auto-creates the Return Requests response sheet, the single system of record.
A reusable template for telling the customer the outcome, sent once the reviewer approves (and any automatic refund has gone through) or rejects.
Verifies the order in Shopify, runs the AI eligibility check, logs the request, routes it to a human reviewer, issues approved refunds via Stripe when a charge is on file, and emails the customer the outcome.
You connect your own accounts. Swap any app that offers an alternative at install.
Looks up the order to pull its total, date, and line items for the eligibility check.
Emails the reviewer a secure link to review the request when it's ready for human sign-off.
Emails the customer their return outcome. Swap for Brevo.
Issues the approved refund against the original charge, when a charge ID is on file for the request.
The shopper fills the Return & Refund Request Form: order number, reason, and photos of the item. Worth flagging before you publish it: the order field expects Shopify's internal numeric order ID, not the #1001-style number printed on the shopper's receipt. Publishing the form auto-creates the Return Requests sheet, which becomes the record for every request that follows.
The workflow looks the order up in Shopify and pulls its total, date, and line items, so the review is against what was actually bought, not what the customer remembers buying. The AI Eligibility Check then weighs the request against your return window and any policy notes you set at install, and recommends approve, reject, or needs-review.
Your reviewer gets an email with a secure link. Opening it shows the request, the photos, and the AI recommendation together, the person makes the call, always. If they want the refund issued automatically, they paste the Stripe charge ID into the charge_id column on the request's row before approving.
On approval, if a charge ID is on file, a refund is created in Stripe against the original charge and the amount is written back to the sheet. If there isn't one, the request is still marked approved and you issue the refund yourself. Either way (approved or rejected) the customer gets an email. No request ever goes quiet.
Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.