Create a Return Merchandise Authorization (RMA) record in an OMS or ERP and communicate it to the customer and warehouse
domain: shopify.dev · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Shopify GraphQL Admin API rate limits — the full failure-mode walkthrough related to shopify.dev, checked against official docs, with linked verified routes.
Steps
Validate the return eligibility against the order's return window, item condition policy, and carrier return program rules before creating the RMA
POST a Return resource via the Shopify REST or GraphQL Admin API referencing the original order ID and line items being returned with their quantities and reason codes
Capture the RMA number from the API response and communicate it to the customer via email with return instructions and the authorized item list
Notify the warehouse management system of the pending return with the RMA number, expected item list, and preferred disposition (restock, quarantine, destroy)
Set a return expiry date on the RMA and implement a job to close expired RMAs that were never received
Known gotchas
An RMA does not automatically generate a return shipping label; label creation is a separate API call or carrier integration step
Disposition must be specified before the warehouse receives the goods; an RMA without a disposition instruction causes receiving backlogs
Return reason codes should align with your refund policy rules; mismatched reason codes can trigger incorrect refund amounts or auto-approval of ineligible returns
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?