Use this form to report an item you wish to return and to tell us how you would like the outcome handled. Complete each section as accurately as you can. Answers you provide here are used only to organise your return, estimate any refund, and keep you updated on progress.
Fields marked as required must be completed before the form can be submitted. Where you are unsure of a detail, provide your best estimate and add a short note in the comment fields so the review team can follow up with you.
Please note: refund eligibility, timeframes, and any shipping cost responsibility depend on the seller or retailer you purchased from and on the options they offer. This form does not determine or guarantee an outcome; it simply records your request for review.
Full name of the person who placed the order
Email address for return updates
Phone number (with country/area code)
Would you like a second contact person to receive updates about this return?
Customer or account reference (if available)
Was this order placed as a guest, without creating an account?
Order number
Date the order was placed
Date the item was delivered or collected
Where was the purchase made?
Online store website
Mobile shopping app
Marketplace or third-party seller platform
Telephone or mail order
Physical store, then delivered to me
Other
Seller, store, or brand name shown on the receipt
Total amount paid for the order
Do you still have the original receipt, invoice, or order confirmation?
Was this item purchased with a discount, promotion, or gift card?
List every item included in this return. Add one row per product. The estimated refund column calculates automatically from the unit price and quantity you enter.
Returned Items List
Product name | SKU, model, or item code | Quantity | Unit price paid | Estimated item refund | Short reason for return | |
|---|---|---|---|---|---|---|
Insulated travel bottle, 750 ml | TB-750-GRN | 1 | $34.99 | $34.99 | Arrived with a dented base | |
Replacement filter pack | FLT-3PK | 2 | $12.50 | $25.00 | Ordered by mistake | |
$0.00 | ||||||
$0.00 | ||||||
$0.00 | ||||||
$0.00 | ||||||
$0.00 | ||||||
$0.00 | ||||||
$0.00 | ||||||
$0.00 |
Total number of items included in this return
Are you returning only part of the original order?
What is the main reason for this return?
Item arrived damaged or broken
Item appears to be defective or does not work
Wrong item, colour, size, or model was sent
Item does not match the description or photos
Item is missing parts, accessories, or instructions
Item arrived later than expected and is no longer needed
Changed my mind or no longer need the item
Size or fit is not right
Duplicate order or accidental purchase
Item was damaged during use sooner than expected
Other
Did you contact customer support about this issue before submitting the return?
Is there any risk of injury, property damage, or further harm if the item is used again?
Anything else the reviewer should know about the reason for return
How would you describe the current condition of the item?
Unused, unopened, seals intact
Opened and inspected, but not used
Used lightly, no visible wear
Used, with visible wear or marks
Damaged or incomplete
Not applicable, item is faulty or unsafe to use
Do you still have the original packaging, tags, labels, and manuals?
Which best describes the state of the item you are sending back?
Clean and ready for inspection
Needs cleaning before inspection
Contains personal data on the device or storage (for example a phone or laptop)
Requires special handling or disposal
None of the above
Does the item contain batteries, liquids, or other components that may need special transport handling?
Please upload a photo of the item as it is now
Please upload a photo of the packaging and shipping label
How would you prefer to send the item back?
Drop off at a nearby collection point
Courier pickup from my address
Post or mail it using a prepaid label
Return it in person to a store or service counter
I need advice on the best option
Collection or return address
City or locality
Postal or ZIP code
Country or region
Landmark or delivery instructions for the courier
Preferred time window for pickup or drop-off
Approximate weight of the packed return (in kg)
Approximate package dimensions (length x width x height)
Is the parcel unusually heavy, oversized, or awkward to handle?
What outcome would you prefer?
Refund to the original payment method
Refund as store credit or account balance
Refund to a bank account or transfer service
Replacement item of the same product
Exchange for a different size, colour, or model
Repair of the item
Not sure yet, please advise on the available options
Refund amount you are requesting (excluding shipping, if known)
Did you pay any shipping or delivery fee on the original order?
Would you like the return shipping cost to be considered for reimbursement?
How quickly do you need the outcome resolved?
As soon as possible, the item is urgent
Within the standard processing timeframe
Flexible, no particular deadline
Before a specific date (please specify below)
I understand that the final refund amount, any deductions, and the timeframe depend on the seller's review of the returned item
Clear evidence helps the reviewer assess your request faster. Photos taken in good light, showing both the whole item and the specific problem, are usually the most useful.
Photo showing the specific damage, fault, or discrepancy
Photo of the product label, serial number, or batch code
Any additional documents (for example a repair report, message transcript, or delivery note)
Do you have a video showing the fault in action?
Was anyone else present when the problem was noticed?
Any additional comments, timeline of events, or context for the reviewer
How would you like to receive updates about this return?
SMS or text message
Phone call
In-app or account notifications
Postal mail
How often would you like to receive progress updates?
At every key step (received, inspected, decision, refund sent)
Only when a decision is made
Only if there is a delay or a problem
One summary update at the end
Best time of day to reach you by phone
Preferred language for written updates
Would you like to receive a short feedback survey after the return is completed?
Do you need any accessibility or communication adjustments during this process?
Please rate how much you agree with each statement about your experience so far
Strongly disagree | Disagree | Neutral | Agree | Strongly agree | Not applicable | |
|---|---|---|---|---|---|---|
The product information at the time of purchase was clear | ||||||
The delivery experience met my expectations | ||||||
It was easy to find out how to start a return | ||||||
I feel confident my return will be handled fairly | ||||||
I would consider purchasing from this seller again |
How urgent is this return for you, on a scale where 1 is not urgent and 10 is extremely urgent?
What would a good outcome look like for you?
Please review your answers before submitting. The details you provide will be used to process and track this return request and to contact you about any follow-up questions.
I confirm that the information in this form is accurate and complete to the best of my knowledge
I confirm that the items listed are the ones I will send back, and that I have removed any personal data from returned devices
I agree to be contacted about this return request using the details I have provided
Type your full name to confirm this declaration
Please sign in the box below
Date of submission
Reference code for your own records (optional)
Analysis for Online Return & Refund Tracking Form
Important Note:
This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.
AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.
This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.
Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
This Online Return & Refund Tracking Form is a comprehensive, well-structured document designed to capture every stage of a return and refund journey—from initial request through shipping logistics, evidence collection, refund preference, and final declaration. The form spans twelve clearly delineated sections, each with a descriptive sub-heading, which gives the respondent a logical progression through what could otherwise be a complex process. The introductory section titled How This Form Works sets clear expectations about how answers will be used, what is required, and that the form does not guarantee an outcome. This transparency is a notable strength that helps manage respondent expectations from the outset.
Overall, the form demonstrates thoughtful design through its extensive use of conditional follow-up questions, multi-format input types (dates, currency, numeric, file uploads, image uploads, signatures, matrix ratings), and a structured table for itemised returns with an automatic calculation column. The balance between mandatory and optional fields is generally reasonable, with core identity, order, and declaration fields required while many supplementary details remain optional. The form is lengthy, which may present a completion friction point, but the sectional structure and contextual guidance paragraphs help mitigate this. Below is a section-by-section breakdown.
The three introductory paragraphs serve as an orientation layer. They explain the form's purpose, clarify which fields are required, and set realistic expectations about refund eligibility and timeframes. This is an effective design choice because it reduces confusion and potential disputes later in the process. The instruction to provide best estimates and use comment fields for uncertainties is practical and encourages completion rather than abandonment.
Full name of the person who placed the order — This field establishes the primary identity of the requester. Operationally, it links the return request to the individual who made the purchase, which supports record matching and accountability. The placeholder example is helpful for format guidance.
Email address for return updates — Collecting an email address provides a reliable digital channel for status updates and follow-up communication. This is a practical choice given the form's stated purpose of tracking progress over time.
Phone number (with country/area code) — An optional field that offers an alternative contact channel. Keeping it optional is sensible since not all respondents may wish to share a phone number, and email is already captured as the primary channel.
Would you like a second contact person to receive updates about this return? — This yes/no question with conditional follow-up is a thoughtful inclusion for cases where a gift recipient, household member, or assistant needs to be kept in the loop. The no-branch provides reassuring confirmation text.
Customer or account reference (if available) — An optional field that can accelerate account lookup if the respondent has an existing account. The conditional phrasing 'if available' appropriately reduces pressure on guest purchasers.
Was this order placed as a guest, without creating an account? — This conditional question captures the checkout email for guest orders, which is operationally important since there may be no account record to reference. The follow-up only appears when relevant, keeping the form streamlined.
Order number — The order number is the primary reference key for locating the transaction in any order management system. Requiring it supports efficient record retrieval and reduces ambiguity.
Date the order was placed and Date the item was delivered or collected — These optional date fields help establish a timeline, which can be useful for assessing return windows and processing expectations.
Where was the purchase made? — This single-choice question with multiple options covers a wide range of purchase channels. The conditional follow-ups for marketplace and 'Other' options add useful specificity without burdening all respondents. The broad option set reflects the reality of modern multi-channel commerce.
Seller, store, or brand name shown on the receipt — Identifying the seller or brand is operationally important for routing the request to the correct party. The placeholder example clarifies the expected input.
Total amount paid for the order — An optional currency field that provides a reference figure for refund calculations. Making it optional is reasonable since the itemised table below also captures pricing.
Do you still have the original receipt, invoice, or order confirmation? — This conditional question routes respondents to either upload proof of purchase or describe alternative evidence. The no-branch helpfully suggests alternatives such as bank statements or confirmation emails.
Was this item purchased with a discount, promotion, or gift card? — This question helps clarify the effective purchase price, which may affect refund calculations. The conditional follow-up allows the respondent to describe the promotion details.
The introductory paragraph explains the table structure and the automatic calculation of estimated refunds. The Returned Items List table is a strong design element: it captures product name, SKU, quantity, unit price, an auto-calculated estimated refund column (using the formula quantity × unit price), and a short return reason per item. The pre-filled example rows demonstrate the expected format clearly. This structured approach supports accurate itemisation and reduces the need for free-text descriptions of what is being returned.
Total number of items included in this return — This numeric field provides a quick summary count that can be cross-checked against the table. Requiring it helps ensure the respondent has reviewed the itemised list.
Are you returning only part of the original order? — This conditional question captures details about partial returns, which is operationally relevant for inventory reconciliation and refund calculation. The follow-up asks the respondent to list both kept and returned items.
What is the main reason for this return? — This is one of the most operationally significant questions in the form. The eleven-option single-choice list covers a broad spectrum of common return reasons. The extensive conditional follow-ups—ten in total—tailor the next question to the selected reason, which is excellent design. For example, selecting 'Item arrived damaged' prompts a description of the damage, while 'Defective' triggers a fault-type question. This branching logic collects targeted detail without overwhelming respondents with irrelevant questions.
Did you contact customer support about this issue before submitting the return? — This yes/no question helps establish whether there is prior interaction history. The follow-up captures a reference number or agent name, which can accelerate case linking. The no-branch provides reassuring text.
Is there any risk of injury, property damage, or further harm if the item is used again? — This safety-oriented question is important for flagging potentially hazardous items. The yes-branch includes a mandatory follow-up description and advises the respondent to stop using the item. This is a responsible design choice that helps surface safety concerns early.
Anything else the reviewer should know about the reason for return — An optional open-text field that captures context not covered by the structured options. The placeholder example is helpful.
How would you describe the current condition of the item? — This single-choice question with six options captures the item's state, which is directly relevant to refund eligibility assessment. The 'Not applicable' option for faulty or unsafe items is a thoughtful inclusion.
Do you still have the original packaging, tags, labels, and manuals? — This conditional question routes to either a multi-select list of what will be included or an explanation of what is missing. This is practical for logistics planning and return processing.
Which best describes the state of the item you are sending back? — This multi-select question covers cleaning needs, personal data on devices, and special handling. The conditional follow-ups for personal data and special handling are particularly useful for operational planning and data protection awareness.
Does the item contain batteries, liquids, or other components that may need special transport handling? — This question addresses shipping logistics and safety considerations. The follow-up captures component type and quantity.
Please upload a photo of the item as it is now and Please upload a photo of the packaging and shipping label — Image uploads provide visual evidence that can support the review process. These are optional, which is reasonable given that not all respondents may have photos readily available.
How would you prefer to send the item back? — This single-choice question with five options covers the main return logistics methods. The conditional follow-ups—pickup date, prepaid label tracking number, or store location—capture the specific details needed for each method. This is well-designed branching logic.
Collection or return address and City or locality — These address fields are required, which is operationally important for arranging pickup or return shipping. Together with the optional postal code, country, and landmark fields, they form a complete address block.
Landmark or delivery instructions for the courier — An optional field that can prevent failed pickup attempts. This is a practical inclusion.
Preferred time window for pickup or drop-off — An optional time field that helps coordinate logistics scheduling.
Approximate weight of the packed return (in kg) and Approximate package dimensions — These optional fields support shipping cost estimation and carrier selection. The decimal precision specification (max 2 decimal places) for weight is a good detail.
Is the parcel unusually heavy, oversized, or awkward to handle? — This conditional question flags special handling needs, which can prevent logistical issues during return transport.
What outcome would you prefer? — This single-choice question with seven options covers the full range of common resolution outcomes. The conditional follow-ups are well-targeted: bank transfer details for transfer refunds, delivery address for replacements, desired specifications for exchanges, and fault description for repairs. This is one of the form's strongest conditional logic implementations.
Refund amount you are requesting (excluding shipping, if known) — An optional currency field that captures the respondent's expectation. The 'if known' qualifier reduces pressure.
Did you pay any shipping or delivery fee on the original order? and Would you like the return shipping cost to be considered for reimbursement? — These conditional questions address shipping cost considerations, which are often a point of discussion in returns. The follow-ups capture specific amounts and supporting estimates.
How quickly do you need the outcome resolved? — This single-choice question with a conditional date follow-up helps set processing expectations and identify urgent cases.
I understand that the final refund amount, any deductions, and the timeframe depend on the seller's review of the returned item — This acknowledgement checkbox sets realistic expectations and reduces potential misunderstandings. It is not marked mandatory, which is a design choice worth noting.
The introductory paragraph provides practical guidance on photo quality and content, which is helpful. The section offers multiple evidence upload points: Photo showing the specific damage, fault, or discrepancy, Photo of the product label, serial number, or batch code, and Any additional documents. These are all optional, which is appropriate since evidence availability varies.
Do you have a video showing the fault in action? — A conditional file upload for video evidence, which can be particularly useful for intermittent faults.
Was anyone else present when the problem was noticed? — This conditional question captures witness information, which may support the review in some cases.
Any additional comments, timeline of events, or context for the reviewer — An optional open-text field with a helpful placeholder example showing a timeline format.
How would you like to receive updates about this return? — This multi-select question with five channel options respects respondent preferences. Making it mandatory ensures the review team has at least one communication channel.
How often would you like to receive progress updates? — This single-choice question with four frequency options helps manage communication volume and respondent expectations.
Best time of day to reach you by phone and Preferred language for written updates — These optional fields support personalised communication and accessibility.
Would you like to receive a short feedback survey after the return is completed? — An opt-in question for post-process feedback, with a conditional follow-up for contact details.
Do you need any accessibility or communication adjustments during this process? — This is an inclusive design choice. The conditional follow-up invites the respondent to describe specific needs such as large-print documents or written-only contact.
Please rate how much you agree with each statement about your experience so far — This matrix rating question with five sub-questions and a six-point scale (including 'Not applicable') captures sentiment across key experience dimensions. The sub-questions cover product information clarity, delivery experience, ease of finding return information, confidence in fair handling, and likelihood of repurchase. This is a well-rounded satisfaction assessment.
How urgent is this return for you, on a scale where 1 is not urgent and 10 is extremely urgent? — A digit rating that quantifies urgency, which can help with prioritisation.
What would a good outcome look like for you? — An open-text field that captures respondent expectations in their own words. This can be valuable for setting realistic expectations and identifying potential areas of dissatisfaction early.
The introductory paragraph prompts the respondent to review their answers and explains how the data will be used. The declaration section includes two mandatory confirmation checkboxes, a typed name, a signature, and a submission date—all mandatory. This creates a clear record of the respondent's attestation. The optional reference code field is a thoughtful addition for respondents who want to track their own submission.
Strengths: The form excels in several areas. Its sectional structure with clear sub-headings provides excellent navigability. The extensive use of conditional follow-up logic (over twenty instances) tailors the experience to each respondent's situation, collecting relevant detail without unnecessary burden. The itemised returns table with automatic calculation is a particularly effective data collection tool. The introductory guidance paragraphs set clear expectations. The variety of input types—dates, currency, numeric, multi-select, matrix ratings, file uploads, image uploads, and signature—ensures appropriate data capture for each field type. The inclusion of accessibility preferences and safety risk flags demonstrates thoughtful, inclusive design.
Areas for improvement: The form is quite lengthy, which may affect completion rates. Consider whether all sections are essential for every return type or whether some could be conditionally shown based on early answers (for example, the 'Experience & Expectations' section might be optional or skippable). The mandatory field count is moderate but spans several sections; ensuring that the most critical fields appear early can help maintain momentum. Some optional fields (such as postal code and country) might benefit from being required if the return shipping method selected involves courier pickup, since a complete address is operationally important. The acknowledgement checkbox in the refund section is not marked mandatory; the form creator may wish to consider whether this should be required to ensure respondents are aware of the review-dependent nature of outcomes. Overall, this is a well-designed form that balances thoroughness with user guidance effectively.
Mandatory Question Analysis for Online Return & Refund Tracking Form
Important Note:
This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.
Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.
Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
The following questions are currently set as mandatory in the form. Each analysis explains how requiring the field may support data completeness, operational processing, or record-keeping in the context of a return and refund tracking process.
Full name of the person who placed the order
Recommendation: Requiring this field ensures that each return request can be clearly associated with the individual who placed the order. This supports accurate record-keeping and helps prevent confusion when multiple orders exist under similar identifiers. The form creator should confirm whether capturing a full legal name or a preferred display name better serves their specific processing needs.
Email address for return updates
Recommendation: Marking this field as mandatory supports reliable ongoing communication throughout the return process. Since the form is designed for tracking progress over time, having at least one confirmed digital contact channel helps ensure the respondent can be reached for status updates and follow-up questions. Depending on the organisation's data handling practices, consider providing clear information about how submitted contact details will be used and stored.
Order number
Recommendation: The order number serves as the primary reference key for locating the transaction in order management systems. Requiring it helps ensure the return request can be efficiently matched to the correct purchase record, reducing administrative processing time and the risk of ambiguity. If some purchase channels do not generate order numbers, the form creator may wish to consider offering an alternative reference option.
Where was the purchase made?
Recommendation: Requiring this field helps establish the purchase channel, which can be operationally relevant for routing the request to the correct processing workflow and for understanding the context of the return. The broad option set covers most common scenarios. The form creator should confirm whether all listed channels are relevant to their return processing operations.
Seller, store, or brand name shown on the receipt
Recommendation: Identifying the seller or brand supports accurate routing and record association, particularly in multi-vendor or marketplace contexts. Requiring this field helps ensure the request can be directed to the appropriate party for review. The placeholder example provides helpful format guidance.
Total number of items included in this return
Recommendation: Requiring this numeric field encourages the respondent to review the itemised table and provides a quick summary count that can be cross-checked against the listed items. This supports data consistency and helps prevent discrepancies between the itemised list and the overall return scope.
What is the main reason for this return?
Recommendation: This field is central to the return review process. Requiring it ensures that every request has a clearly stated reason, which supports categorisation, routing, and assessment. The extensive conditional follow-up logic depends on this selection, so making it mandatory ensures the branching questions can function as intended. The form creator should periodically review the option list to ensure it remains aligned with the types of returns they process.
Please describe the concern in detail and stop using the item until it has been reviewed (conditional follow-up to the safety risk question)
Recommendation: Requiring this follow-up description when a safety risk is flagged helps ensure that potentially important information is not omitted. This supports operational awareness and may help the review team assess the situation appropriately. The form creator should consider how flagged safety concerns will be handled in their review workflow.
How would you describe the current condition of the item?
Recommendation: Requiring this field ensures that every return request includes a description of the item's current state, which is directly relevant to processing and assessment. The six-option list provides clear categories that should cover most scenarios. This field supports consistent data capture across all submissions.
How would you prefer to send the item back?
Recommendation: Requiring this field ensures that a return logistics method is identified for every request, which supports operational planning and coordination. The conditional follow-ups capture the specific details needed for each method. The form creator should confirm that all listed return methods are available in their operating context.
Collection or return address
Recommendation: Requiring this address field supports the practical logistics of arranging pickup or return shipping. Without a complete address, the return transport cannot be coordinated effectively. The form creator should consider whether this field should be conditionally required based on the selected return method—for example, it may be less relevant for in-person store returns.
City or locality
Recommendation: Requiring the city or locality complements the address field and supports accurate logistics planning. Together with the address, it helps ensure the return location can be identified. Consider whether making postal code and country required as well would further support complete address capture for courier-based returns.
What outcome would you prefer?
Recommendation: Requiring this field ensures that every request includes a stated preference for resolution, which supports processing and helps set expectations. The seven-option list covers a broad range of outcomes. The conditional follow-ups capture the specific details needed for each preference type. The form creator should confirm that all listed outcomes are available through their return process.
How would you like to receive updates about this return?
Recommendation: Requiring this multi-select field ensures that at least one communication channel is identified for every request, supporting reliable progress updates and follow-up. The five channel options provide flexibility. The form creator should confirm which channels they can operationally support and consider whether any should be removed if not available.
I confirm that the information in this form is accurate and complete to the best of my knowledge
Recommendation: Requiring this confirmation checkbox supports data quality by prompting the respondent to review their answers before submission. It creates a record of the respondent's attestation to accuracy. This is a common and practical design choice for forms that collect information used in processing decisions.
I confirm that the items listed are the ones I will send back, and that I have removed any personal data from returned devices
Recommendation: Requiring this checkbox supports operational clarity about what will be returned and encourages awareness of data protection considerations for returned devices. This is a practical design choice that helps set clear expectations. The form creator should consider how this confirmation will be referenced in their return processing workflow.
Type your full name to confirm this declaration
Recommendation: Requiring a typed name as part of the declaration creates a clear record of who is making the attestation. This supports accountability and record-keeping. The form creator should confirm whether this should match the name captured at the beginning of the form or whether a different name may be appropriate in some cases.
Please sign in the box below
Recommendation: Requiring a signature supports the formality and record-keeping value of the declaration section. A signature provides a visual confirmation of the respondent's attestation. The form creator should consider whether a digital signature is sufficient for their record-keeping needs or whether additional verification is desired.
Date of submission
Recommendation: Requiring the submission date establishes a clear timestamp for the request, which supports processing timelines and record-keeping. This is a standard and practical field for any form that initiates a tracked process. Consider whether auto-populating this field from the system date would improve accuracy and reduce respondent effort.
The form includes approximately nineteen mandatory fields (including conditional follow-ups and declaration elements) spread across all twelve sections. This distribution ensures that core identity, order, return, logistics, and declaration information is captured for every submission. However, the number of mandatory fields is notable and may present a completion barrier for some respondents, particularly given the overall length of the form.