Describe your products and return process. Makeform builds an RMA request form for order and serial numbers, reasons, condition, photos, and preferred resolution before review.
Send RMA requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor it to your return policy, or send it into the builder. The preview is an example, not a return decision.
Audience
Customers returning one or more e-commerce items
Format
Order lookup and item-level return request
Prompt size
291 chars
Example form structure
Order lookup and item-level return request
Customer contact and order number
Which items and quantities are being returned?
Reason for each return
Upload item-condition photos
Preferred resolution
Suggested routing tags
Refund review
Replacement requested
Troubleshooting needed
Ask for one line item per product, including quantity and serial number, so a customer returning part of an order does not create an ambiguous request.
Step 1
Request
customer, order, item, and return reason
Step 2
Review
support checks the policy and evidence
Step 3
Authorize
instructions and an RMA reference go out
Step 4
Resolve
item received, outcome recorded, customer updated
Why use an RMA form
Instead of chasing an order, model, symptoms, and photos by email, collect that context in one structured submission.
Order, SKU, quantity, and serial fields identify each affected item.
Show troubleshooting for defects, packaging photos for damage, and condition questions for other returns.
Use reason and resolution answers to support internal routing.
Built around the return
Start with the closest flow, then add your SKUs, reasons, instructions, and routing.
Capture order details, line items, condition, reasons, and resolution preference.
Collect model, serial number, symptoms, logs, troubleshooting, and proof of purchase.
Add accounts, purchase orders, installation context, impact, pickup details, and multiple units.
Request product, carton, label, and packing-material photos.
RMA setup
Describe the products and decisions your team handles, refine the generated fields, publish the form, and connect each request to the review process you already use.
Describe your products, identifiers, return reasons, and required evidence.
Add resolution choices, require identifiers, and reveal follow-ups by reason.
Share the form and notify the appropriate review queue.
Tie the RMA reference, shipping instructions, and outcome to the submission.
Form vs email vs generic template
Good intake captures product identity, evidence, and a requested outcome in consistent fields.
Field guide
Collect the transaction, product state, requested action, and details needed for return instructions.
Customer and purchase
Capture contact and purchase details so reviewers can find the customer and transaction without another message.
Product identity
Use repeatable item groups so each quantity, variant, and hardware identifier stays tied to the right product.
Reason and symptoms
Combine a reason choice with details about symptoms, timing, context, error codes, and previous troubleshooting.
Evidence
Use specific upload prompts so customers know which documents, views, labels, or diagnostic files reviewers need.
Requested resolution
Collect a preferred outcome without presenting it as approved, then reveal any address or replacement questions.
Handling and routing
Use reason, region, product family, and urgency to support routing into your connected return process.
Related tools
Pair RMA intake with focused forms for returns, warranty claims, refunds, repair requests, orders, and post-service feedback.
FAQ
Straight answers for e-commerce, hardware, support, warranty, and operations teams designing return intake.
It is the intake a customer uses to request a return, repair, replacement, or refund review. It gathers purchase and product identifiers, reasons, evidence, and the preferred resolution without implying that the return is already authorized.
Include customer contact, order or invoice, purchase date, product, SKU, quantity, and serial number. Add the reason, symptoms or condition, troubleshooting, uploads, accessories, preferred outcome, and return location. Use conditional fields for reason-specific evidence.
Use a repeatable group with product, SKU, serial number, quantity, reason, and condition for every item. If products need different outcomes or shipping instructions, separate the requests or clearly group each outcome by item.
Yes. A defect choice can reveal troubleshooting, error-code, and log questions. Shipping damage can reveal delivery and packaging-photo fields, while a wrong-item choice can ask for the received SKU and packing slip.
Not by itself. Write the submission as a request and say your team will review it. Send any authorization reference, deadline, label, and packing instructions after the decision; do not label a pending confirmation as approval.
Yes. Request a readable receipt, product and serial labels, relevant damage angles, packaging, shipping label, screenshots, or logs. Separate upload prompts help reviewers identify each evidence type.
Yes. Makeform provides unlimited free forms and submissions, including generation, editing, publishing, and ongoing use. The paid tier removes the Makeform badge.
Responses can reach your Makeform inbox and connect with Google Sheets, Slack, or Zapier. Consistent product, reason, region, and resolution fields support filtering and routing into your operational system.
Replace incomplete return emails with structured intake.
