01
Customer and entitlement
- Customer
- Contact
- Order or invoice
- Purchase date
- Contract or warranty
Establishes the relationship and applicable policy.
RMA request intake
RMA request form for faster authorization
Collect customer, order, item identity, failure, troubleshooting, evidence, requested outcome, return constraints, and contact details in one review-ready request.
Generate the RMA only after submission or approval. The requester should provide facts and evidence; the authorization team should own eligibility, route, and disposition decisions.
- Automatic request and RMA identification
- Conditional product, failure, evidence, and return questions
- Clear confirmation, evidence-needed, approved, and rejected paths
Ask for the facts that change eligibility or handling
Use conditional sections so simple returns stay simple and technical cases capture the evidence a reviewer needs.
02
Item identity
- Product
- Model
- Serial or lot
- Quantity
- Location
Prevents authorization and receipt mismatch.
03
Failure and troubleshooting
- Observed symptom
- Event date
- Operating context
- Steps tried
- Current condition
Supports technical triage without asking the requester to declare root cause.
04
Evidence and logistics
- Photos or files
- Packaging
- Hazard or handling need
- Pickup or shipping constraints
Plans a safe return and reduces evidence requests.
05
Requested outcome
- Repair
- Replacement
- Refund or credit
- Urgency
- Contact preference
Clarifies the customer need without pre-approving the remedy.
Branch the form by the return you are actually reviewing
Not every request needs the same questions.
| Selected context | Show next | Route to |
|---|---|---|
| Failed in use | Operating condition, failure sequence, troubleshooting, error or fault code, evidence | Technical authorization or warranty review |
| Damaged on arrival | Packaging, carrier, received date, damage photos, usable condition | Delivery claim or replacement review |
| Wrong item | Ordered item, received item, packaging label, quantity, photos | Warehouse or fulfillment correction |
| No longer needed | Condition, unopened status, return window, restocking rule | Standard return policy |
| Safety concern | Immediate condition, affected people, containment, contact availability | Urgent quality and safety escalation |
Tell the requester what the number means and what happens next
Avoid displaying an RMA number as though the return is approved if the case still needs review.
- 01
Request received
Confirm the request reference and show the expected review window.
Is the information complete and is urgent escalation required? - 02
Evidence or eligibility review
Ask for missing detail in the same case and record the rule or exception used.
Approve, reject, or route for specialist review? - 03
RMA authorized
Issue the RMA number, conditions, destination, return method, validity date, and next instructions.
What exactly may be returned and under what conditions?
Reduce back-and-forth before authorization
What information should an RMA request form collect?
Customer and contact, order or entitlement, product and serial or lot, quantity, failure or reason, troubleshooting, current condition, evidence, requested outcome, urgency, and shipping constraints.
Is an RMA request the same as an approved RMA?
No. A request asks for authorization. The approved RMA should state the authorization number, items, conditions, destination, method, validity, and instructions.
Should RMA numbers be generated automatically?
Yes. Automatic numbering reduces duplicates and keeps the request, shipment, receipt, inspection, decision, and communication traceable.
Can Jodoo show different questions for different return reasons?
Yes. Conditional fields can reveal product, damage, failure, safety, logistics, or policy questions based on earlier answers.
Publish a decision-ready RMA request
Use the RMA request formStart the RMA with complete facts and a clear review promise
Use the Jodoo form to test conditional questions, evidence requests, automatic numbering, approval, and confirmation before publishing it to customers or partners.