Describe what you sell, which purchases qualify for review, and how your team handles returns. Makeform turns the brief into an editable RMA form that collects order and item details, return reasons, condition evidence, and the customer's preferred resolution before a support agent reviews the request.
Route return requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a practical starting point, tailor the policy details, or send the prompt into the Makeform builder. Each structure is an example you can edit, not a promise that a return will be approved.
Audience
Customers requesting a refund or exchange for an online purchase
Format
Guided request with order lookup details and item condition
Prompt size
450 chars
Example form structure
Guided request with order lookup details and item condition
Customer email and order number
Which item and quantity are you returning?
Why are you requesting a return?
Photos of damage or the wrong item
Preferred resolution
Suggested routing tags
Needs review
Replacement requested
Return approved
Ask for one line item per return request. A single order can contain several products, but the condition, reason, serial number, and requested resolution may differ for each item.
Step 1
Request
customer, order, item, reason, and evidence
Step 2
Review
team checks purchase details and return policy
Step 3
Authorize
instructions and reference number sent after approval
Step 4
Resolve
receipt, inspection, and outcome recorded
Why structured intake matters
Customers naturally write “it does not work” and wait for a reply. An RMA form asks for the order, exact item, condition, evidence, and desired resolution in one pass, giving the returns team a consistent record to review.
Required order, invoice, email, SKU, and purchase-date fields give an agent several ways to match the request to a transaction without starting another email thread.
Conditional branches can request damage photos for broken goods, troubleshooting for electronics, or unopened-package details for buyer-remorse returns while keeping other paths short.
Tag requests for damage, wrong item, missing parts, warranty review, or exchange so each submission reaches the support, warehouse, or product team that can make the next decision.
Designed around return cases
Start with the scenario closest to your return workflow. Then replace the sample reasons, products, policy summary, contacts, and resolution options with the choices your team actually supports.
Collect order details, return reasons, item condition, and the customer's preferred size, color, replacement, credit, or refund path.
Capture model and serial identifiers, symptoms, error messages, attempted fixes, media, and whether the device still powers on before technical review.
Add account, invoice, purchase-order, shipping-contact, quantity, lot-number, downtime, and freight details for more complex B2B handling.
Branch instructions by channel, retain the marketplace order ID, and separate carrier damage from fulfillment errors and product concerns.
Return-request workflow
Makeform turns a plain-language brief into a working RMA form. You can then align its questions and messages with your return policy before sharing it with customers.
Tell the builder what you sell, which identifiers matter, your common return reasons, available resolutions, evidence needs, and the teams that review different cases.
Replace sample SKUs and reasons, mark lookup fields required, add help text, and reveal photos, troubleshooting, shipping, or exchange questions only when a prior answer calls for them.
Share or embed the form, then send a confirmation that summarizes what was submitted and explains the review step without implying that submission alone authorizes a return.
Send submissions to the appropriate inbox and connect your chosen workflow tools. Keep the original request, attachments, internal status, and eventual resolution linked by a consistent reference.
Form vs email vs generic template
Email is flexible but incomplete, and a generic download still needs adaptation. A generated RMA form gives customers a guided request while leaving approval decisions and policy enforcement with your team.
Field guide
The strongest return forms separate customer identity, transaction lookup, item-level facts, evidence, requested outcome, and review expectations. Use these six sections as a checklist, then apply your own return policy and operating process.
Customer and contact
Start with the details your team uses to find and discuss an order. Avoid collecting unrelated information: the goal is a reliable match and a usable contact route if an agent needs clarification.
Purchase verification
An order number alone may not be enough when customers use different emails or buy through resellers. Pair the primary identifier with a purchase date, invoice, channel, or receipt attachment that matches your systems.
Product identification
An RMA belongs to a specific product and quantity, not merely an order. Use fields that distinguish variants and individually tracked units so warehouse staff can compare the arriving package with the approved request.
Reason and condition
Offer a short list of common reasons for routing, followed by an open explanation. Ask about use, packaging, accessories, visible damage, failure timing, and symptoms only where those facts influence the next step.
Evidence and requested outcome
Photos can show transit damage, labels, serial plates, or an incorrect item before a package moves. Keep upload instructions precise, and present only resolutions that the team can actually consider for that product and reason.
Review and handoff
Place a concise return-policy summary before submission and explain what comes next. Distinguish the request receipt from an authorization, then give internal reviewers fields for status, owner, decision notes, and the issued reference number.
Related tools
An RMA request is one part of customer support. Build adjacent forms for authorization, refunds, warranty review, product returns, support issues, and recalls using real Makeform tools.
Create a focused authorization request with purchase details, item facts, reason, and review-ready evidence.
Open toolLet customers identify an item and request the available return, size, color, or replacement path.
Open toolCapture customer problems that need investigation but may not require a product return.
Open toolCollect the transaction, reason, and requested refund details for a dedicated finance or support review.
Open toolGather product identifiers, purchase evidence, symptoms, and supporting files for warranty review.
Open toolCollect affected-product details and customer contact information during a targeted recall response.
Open toolFAQ
Practical answers for e-commerce, customer-support, operations, and warehouse teams setting up product-return intake.
An RMA form collects the information a business needs to review a customer's request to return merchandise. RMA commonly means return merchandise authorization or return material authorization. The form usually captures customer and order details, the exact item, quantity, return reason, condition, evidence, and preferred outcome. Submitting the form can begin your review without automatically approving the return.
Include customer contact details, order or invoice number, purchase or delivery date, product name, SKU, quantity, and return reason. Add serial or lot numbers for tracked products, condition and accessory questions, a detailed problem description, and photo or receipt uploads when useful. Finish with the requested resolution, a policy summary, an accuracy acknowledgment, and a clear explanation of the next review step.
Not necessarily. The form can be configured as a request that your team reviews before issuing an RMA reference, shipping label, pickup plan, or packing instructions. Say this clearly near the submit button and in the receipt message. That distinction prevents customers from treating a submission confirmation as approval to ship an item.
Yes. Use conditional logic to show a relevant branch after the customer selects a reason. A damaged-in-transit branch might ask about packaging and delivery photos; a defective-device branch might ask for error messages and troubleshooting; and an unwanted-item branch might ask whether the seal is intact. This keeps the form concise while collecting the facts each reviewer needs.
Yes. Add file-upload fields for receipts, damaged packaging, the complete product, serial labels, missing contents, or a short demonstration of a fault. Tell customers exactly which images are useful instead of asking for generic proof. Your team should also decide how submitted attachments are stored, accessed, and retained within its own process.
Keep the order-level details together, but collect item-specific answers for every product being returned. Each line item may have a different SKU, quantity, condition, reason, and requested resolution. If the builder does not yet support a repeatable group in the exact way you want, create clearly numbered item sections or ask customers to submit one request per item until the workflow is adjusted.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting submissions with your RMA form. The paid tier removes the Makeform badge. You can start with a sample prompt, replace every field and instruction with your own process, and share the finished form when it is ready.
Responses are available in Makeform, and you can connect the workflow tools your team uses, including Google Sheets, Slack, and Zapier. Plan a stable reference, status, and ownership convention so customer support, warehouse staff, and product teams can discuss the same request. Review the configured integration behavior before relying on it for a production returns process.
Replace return-request email chains with structured intake.
