How to process refund and return requests on Starch

Refund and return requests are one of those workflows that looks simple until it isn't. A customer wants their money back. You verify the purchase, check your policy, issue the refund or reject it, update your records, and communicate the outcome. That's the theory. In practice, the request comes in through email, or a support ticket, or a DM, and the relevant order data lives in Stripe or Shopify or your payment processor, and whoever needs to approve it is already in three other tabs. What this looks like in your business depends on your stack, your volume, and how your team is structured — a solo founder running an e-commerce brand handles this differently than an ops team processing B2B service credits. But the core problem is the same: refund requests arrive through one channel, the data you need to resolve them lives somewhere else, and the outcome needs to get recorded in yet another place. On Starch, you describe what that resolution flow looks like for your business — which systems to pull from, what the approval logic is, how you want to communicate back to the customer — and the platform assembles the connections and surfaces to make it work. Starch connects to Stripe, Shopify, Gmail, Intercom, Zendesk, and 3,000+ other apps through its integration catalog, plus any website through browser automation. You can start from a pre-built template or describe exactly what you need from scratch.