Use this form to record and monitor any item you send back to an online seller. Complete one form per return shipment, or use the tracking table further down to list several items returned together. There is no required format for reference numbers or merchant names, so simply copy them exactly as they appear on your receipt, label or order confirmation.
Fields marked as required must be completed before the form can be submitted. Everything else is optional but helpful. If you are unsure about a detail, leave it blank or add a note in the final comments box rather than guessing.
This form is a personal record-keeping and tracking tool. It does not create, replace or interpret any seller policy, carrier contract, warranty or consumer entitlement. Where a question asks about expectations, please answer with your own understanding of the situation.
Full name of the person who placed the order
Email address used for the order
Contact phone number (include country code if applicable)
Customer account or membership ID with the merchant
How would you prefer to be contacted about this return?
Phone call
Text or messaging app
In-account message centre
No contact needed
Best email address for updates
Best phone number and time window to call
Messaging handle or number to use
Is this return being filed on behalf of someone else?
Please give their name, your relationship to them and how they can be reached
Would you like a copy of this record sent to a second contact, such as a household member or assistant?
Second contact name and email
Copy these details from your order confirmation or account history. They help match the return to the correct purchase if the merchant needs to investigate.
Store or merchant name
Order or purchase reference number
Date the order was placed
Date the order was delivered to you
Where was the purchase made?
Merchant website
Merchant mobile app
Third-party marketplace listing
Phone or chat order
Social media storefront
Other
Please describe where the purchase was made
Total value of the original order
How was the order paid for?
Credit card
Debit card
Digital or mobile wallet
Bank transfer or direct debit
Store credit or gift card
Buy-now-pay-later style instalment plan
Cash on delivery
Other
Please name the instalment provider and plan reference
Please describe the payment method used
Was the returned item part of a multi-item order?
List the other items in the same order and whether they were kept
Was any discount, promotional code or loyalty reward applied to this order?
Please note the code or reward used and how it affected the price
Item description as shown on the order
Brand, model, SKU or product code
Quantity of this item being returned
Price paid per unit after discounts
What condition is the item in as it is being returned?
Unopened, original packaging sealed
Opened but unused
Used lightly, like new
Used with visible signs of wear
Damaged on arrival
Faulty or not working as expected
Missing parts, accessories or manual
Other
Please describe the damage and how it was noticed
Please describe the fault and when it appeared
Please list what is missing
Please describe the item's condition
What is the reason for this return? Choose all that apply.
Wrong size or fit
Wrong item or variant received
Changed my mind
Arrived damaged
Faulty or stopped working
Not as described or pictured
Arrived later than expected
Duplicate order
Gift return
Found a better price elsewhere
Other
How did the item differ from the listing?
When was it expected and when did it actually arrive?
Please describe the reason for return
Upload photos of the item and any damage or defects
Upload the order confirmation, receipt or return label (PDF or image)
Did you contact the merchant about this issue before returning the item?
When did you contact them, through which channel, and what reference or case number were you given?
Is there a reason you returned the item without contacting the merchant first?
Record exactly how the parcel was handed over. Keeping the drop-off date, location type and receipt number together makes it much easier to trace a parcel if the tracking stops updating.
Return authorisation, RMA or return request number
Date the return was authorised or requested
How was the return shipping arranged?
Prepaid label supplied by the merchant
Label purchased by me
Label printed at the drop-off location
Merchant arranged a collection from my address
Handed back in person at a shop or counter
No label required, return code used instead
How much did you pay for the return shipping label?
Collection date and any reference given by the courier
Return code or QR reference used
Which carrier or drop-off method did you use?
Parcel Drop-off Point
Post Office Counter
Courier Service Centre
Parcel Locker
Other
Please name the carrier or drop-off point used
Drop-off location name or address
Date the parcel was dropped off
Approximate time of drop-off
Tracking or receipt number given at drop-off
How was the item packaged for the return?
Original product packaging only
Original box plus outer shipping bag
Dedicated shipping box
Padded envelope
Merchant-supplied return bag or box
Other
Please describe the packaging used
Parcel weight as recorded at drop-off
Did you keep the drop-off receipt or photographic proof of handover?
Please upload a scan or photo of the drop-off receipt
Is there any other evidence of handover, such as a staff name or location reference?
Was any extra cover, insurance or signature service added to the return shipment?
Please note the level of cover, the provider and the cost
List every item in this return shipment below. Enter the drop-off date exactly as printed on your receipt, and copy the tracking or receipt number carefully, including any letters, dashes or spaces. For Carrier Used, enter one of: Parcel Drop-off Point, Post Office Counter, Courier Service Centre, Parcel Locker, or the name of another carrier or counter. For Refund Status, enter one of: In Transit, Dropped Off, Refund Processed, or another status that reflects your situation.
Update the Refund Status column whenever the situation changes, for example when tracking shows delivery to the merchant or when the refund appears in your account.
Returned items, drop-off details and refund status
Store/Merchant | Item Returned | Drop-off Date | Carrier Used | Tracking/Receipt Number | Refund Status | ||
|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | ||
1 | Northwind Outfitters | Waterproof trail jacket, size L, navy | 3/14/2026 | Post Office Counter | RX482100765 | In Transit | |
2 | Harborline Home Goods | Ceramic serving bowl set, 3 pieces | 3/18/2026 | Parcel Locker | AL-77213-4409 | Refund Processed | |
3 | |||||||
4 | |||||||
5 | |||||||
6 | |||||||
7 | |||||||
8 | |||||||
9 | |||||||
10 |
Total number of items listed in this return shipment
Are any of the listed items being returned to different merchants?
Please group the items by merchant and note any differences in the return process
Refund amount you expect to receive
Currency of the expected refund
How was the refund expected to be issued?
Back to the original payment method
Store credit or account balance
Gift card or voucher
Bank transfer
Replacement or exchange item
Not yet agreed with the merchant
Last four digits or reference of the payment method used
Account or store credit reference
Replacement item details and any new order reference
What is the current overall refund status for this return?
Not yet shipped back
Dropped Off
In Transit
Delivered to merchant, awaiting inspection
Refund Processed
Refund Partially Processed
Refund Declined
Under review or dispute
What amount was refunded and what reason was given for the shortfall?
What reason was given for declining the refund?
Date the merchant or seller indicated the refund would be issued
Has the refund actually reached your account or credit balance?
Date the refund arrived, the amount received and any reference shown on your statement
How many days have passed since the parcel was dropped off?
Was any deduction taken from the expected refund, such as a restocking, handling or shipping fee?
Please state the amount deducted and the reason given
Was part of the order refunded earlier or as a separate transaction?
Please give the earlier refund date, amount and reference
Number of days you were told the refund would take after the merchant receives the item
Use this section if anything has gone wrong. Detailed notes here make it easier to describe the situation accurately if you need to contact the merchant or carrier later.
Which problems, if any, have you experienced with this return?
Tracking has not updated
Parcel appears lost
Parcel arrived damaged at the merchant
Drop-off was refused or the label was rejected
Merchant says the item was not received
Refund is taking longer than expected
Refund amount is lower than expected
Merchant or carrier has been unresponsive
Return window or eligibility was disputed
Wrong item was sent back by mistake
Other
When was the last tracking update and what did it say?
Where and when was the drop-off refused, and what reason was given?
What did the merchant say and when did they say it?
Please describe the problem in your own words
How many days have you been waiting since drop-off?
How many times have you contacted the merchant or carrier about this return?
Please describe what has happened so far, in date order if possible
Upload any supporting documents, such as correspondence, screenshots of tracking, or receipts
What outcome are you hoping for?
Full refund to the original payment method
Partial refund with an explanation of the amount
Replacement item or exchange
Store credit
Simply confirmation that the return was received
Help tracing the parcel
What partial amount would you consider acceptable?
Which tracking or receipt number should be traced?
Would you like this record to include a case reference so the details can be looked up later?
Preferred case or reference label for your own records
How would you like to be reminded about this return? Choose all that apply.
When tracking first updates
When the parcel is marked delivered to the merchant
If no update appears after a set number of days
When the refund is issued
Weekly summary until closed
No reminders needed
After how many days without an update should a reminder be sent?
How often would you like a status summary while this return is open?
Daily
Every few days
Weekly
Only when something changes
No summary required
Would you like to keep this record after the refund is complete, for example for warranty or budgeting purposes?
How long would you like the record kept?
Please rate the following aspects of the return process so far
Very poor | Poor | Average | Good | Excellent | Not applicable | |
|---|---|---|---|---|---|---|
Ease of starting the return with the merchant | ||||||
Clarity of the return instructions and label | ||||||
Convenience of the drop-off location and opening hours | ||||||
Accuracy and frequency of tracking updates | ||||||
Speed of the refund after the item was received | ||||||
Quality of communication from the merchant or carrier |
Overall, how would you rate this return experience so far?
How do you feel about the return process at this point?
What worked well, and what could have made the return easier?
Please check the tracking table and the refund details before submitting. Small errors in a tracking number or drop-off date are the most common reason a return becomes hard to trace.
I confirm that the information I have entered is accurate to the best of my knowledge
I understand this form is a personal tracking record and does not create or change any agreement between me and a merchant or carrier
I agree that the details entered may be stored so that this return can be tracked until it is closed
Any final notes, questions or special circumstances we should be aware of
Please sign to confirm this record
Date of confirmation
Name of the person signing, if different from the name given at the start of this form
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 personal record-keeping tool designed to help e-commerce shoppers log, monitor and follow up on item returns from drop-off through to refund payout. The form spans ten clearly delineated sections—contact details, order information, item specifics, return authorisation and drop-off logistics, a multi-row tracking table, refund expectations, problem escalation, reminders, experience feedback, and a review/confirmation step. This progressive structure mirrors the natural lifecycle of a return, making it intuitive for respondents to follow. The inclusion of a dedicated tracking table with columns for Store/Merchant, Item Returned, Drop-off Date, Carrier Used, Tracking/Receipt Number and Refund Status directly addresses the stated purpose of the form and provides a consolidated at-a-glance summary. The form also wisely disclaims any role in interpreting seller policies or consumer entitlements, setting clear expectations from the outset.
The introductory paragraphs set helpful context by explaining the form's purpose, clarifying which fields are required versus optional, and advising users to leave uncertain details blank rather than guess. This reduces the risk of inaccurate data entry and establishes the form as a personal tracking tool rather than an authoritative policy document. The guidance to copy reference numbers and merchant names exactly as they appear on receipts or labels is a practical data-quality measure.
This field establishes the primary identity of the person responsible for the return, which is essential for linking the record to the correct order and for any follow-up communication. Collecting the full name at the start of the form provides a clear anchor for the entire record.
Capturing the order email address helps match the return to the correct account or order history with the merchant. It also serves as a primary communication channel for status updates. The placeholder example helps users understand the expected format.
An optional phone number field provides a secondary contact channel. The instruction to include a country code is a thoughtful detail for international users. Keeping this optional respects that not all users may wish to share a phone number.
This optional field supports cross-referencing the return with the merchant's own records, which can be helpful if the return needs to be traced through a customer service interaction.
This single-choice question with conditional follow-ups is an effective design choice. It collects contact preference and then conditionally asks for the relevant contact detail (email, phone, or messaging handle), avoiding unnecessary fields and reducing form length. The 'No contact needed' option respects users who simply want a personal record.
This yes/no question with a conditional follow-up captures third-party return scenarios—such as gift returns or household purchases—ensuring the record reflects who is actually involved. The follow-up asks for the other person's name, relationship and contact details, which is proportionate for this purpose.
This optional convenience feature allows users to share the record with a trusted second party. The conditional follow-up collects just the name and email of that contact, keeping the request simple.
Recording the merchant name is fundamental to identifying which seller the return relates to. This is especially important when a user is tracking multiple returns from different stores simultaneously.
The order reference number is the primary key for matching a return to a specific purchase. Its mandatory status reflects its central role in any return tracking or merchant enquiry. The placeholder example illustrates the expected format without prescribing one.
This optional date field provides context about the original purchase timeline, which can be relevant when assessing return windows or delivery expectations.
The delivery date helps establish the timeline from receipt to return, which is useful for understanding whether a return was initiated within a typical return period.
This single-choice question captures the purchase channel, which can affect return processes and policies. The conditional follow-up for the 'Other' option allows users to describe non-standard purchase methods.
Recording the order value provides a reference point against which the expected refund can be compared. The currency input type is appropriate for monetary values.
Payment method details are relevant because refund routes typically follow the original payment method. The conditional follow-ups for instalment plans and other payment methods show careful attention to edge cases.
This yes/no question with a conditional follow-up helps clarify whether only part of an order is being returned, which can affect refund calculations and merchant processing. The follow-up asks users to list other items and whether they were kept.
Discounts and promotions can affect the refund amount a user should expect. Capturing this information helps reconcile discrepancies between the original price and the refund received. The conditional follow-up asks for specifics about the code or reward.
Describing the item as it appears on the order ensures the return record matches the merchant's own product listing. This is critical for identifying the correct item, especially in multi-item returns.
Product codes and SKUs provide precise identification beyond a text description, reducing ambiguity when the merchant processes the return.
Specifying quantity is important when an order included multiple units of the same product. The numeric input with decimals disabled is appropriate for countable items.
Recording the per-unit price after discounts supports accurate refund expectation calculations. This is a practical detail for reconciling partial refunds.
Item condition is a key factor in many return processes. The eight detailed options cover a wide range of realistic scenarios. The conditional follow-ups for damaged, faulty, missing-parts and 'Other' conditions prompt users for descriptive details, which strengthens the record. This design avoids forcing users through irrelevant follow-up questions.
The multiple-choice format with eleven options accommodates the variety of reasons shoppers return items. Allowing multiple selections reflects real-world situations where more than one factor may apply. The conditional follow-ups for 'Not as described', 'Arrived later than expected' and 'Other' capture additional context only when relevant.
Image uploads provide visual evidence that can support a return claim or help a merchant assess condition. This is an optional field, which is appropriate since not all returns involve damage or defects.
Document uploads consolidate key paperwork in one place, making the record more complete and easier to reference later. Accepting both PDF and image formats is user-friendly.
This yes/no question with dual follow-ups (for both 'Yes' and 'No') is well designed. It captures pre-return communication details when contact was made, or the reason for returning without contact when it was not. This provides useful context for understanding the return's history.
Capturing an RMA or authorisation number links the return to any formal process initiated by the merchant. While optional, this is valuable when the merchant uses such references.
The authorisation date establishes when the return process formally began, which can be relevant for tracking timelines and return window compliance.
This single-choice question covers the main return shipping arrangements, from prepaid labels to in-person returns. The conditional follow-ups capture label cost, collection references and return codes as appropriate—each tailored to the selected option.
This multiple-choice question aligns with the form's stated purpose, listing specific carrier and drop-off options (Parcel Drop-off Point, Post Office Counter, Courier Service Centre, Parcel Locker) alongside an 'Other' option with a conditional follow-up. This ensures structured data while accommodating non-standard methods.
Recording the specific drop-off location adds precision to the record, which can be useful if the parcel's journey needs to be traced from a particular point.
The drop-off date is a critical tracking milestone. It marks the point at which responsibility for the parcel typically transfers to the carrier or merchant.
Capturing an approximate time adds granularity to the drop-off record without overburdening the user with precise timestamp requirements.
The tracking or receipt number is the primary identifier for following the parcel's journey. The placeholder example shows two different formats, helping users recognise what to look for.
Packaging details can be relevant if the item arrives damaged or if the merchant has packaging requirements. The six options cover common scenarios, with a conditional follow-up for non-standard packaging.
Recording the parcel weight provides an additional data point that may help resolve disputes about what was sent. The decimal precision setting (up to 2 places) is appropriate for weight measurements.
This yes/no question with dual follow-ups is practical. If a receipt exists, the form asks for an upload; if not, it prompts for alternative evidence such as staff names or location references. This maximises the chance of capturing some form of proof.
Additional shipping services can affect liability and tracking. The conditional follow-up captures the level of cover, provider and cost, which is proportionate for this purpose.
The tracking table is the centrepiece of the form's stated purpose. Its six columns—Store/Merchant, Item Returned, Drop-off Date, Carrier Used, Tracking/Receipt Number and Refund Status—directly match the key information specified for collection. The example rows demonstrate realistic entries and help users understand the expected format. The accompanying paragraphs provide clear guidance on data entry conventions, including which values to use for Carrier Used and Refund Status. The instruction to update the Refund Status column as the situation changes encourages ongoing use of the form as a living record.
A simple item count serves as a cross-check against the table entries, helping identify omissions or errors.
This yes/no question with a conditional follow-up addresses multi-merchant returns, prompting users to group items and note process differences. This is a practical design choice for complex return scenarios.
Recording the expected refund amount sets a benchmark against which the actual refund can be compared, helping users identify shortfalls.
Specifying the currency avoids ambiguity, particularly for international purchases. The placeholder examples are helpful.
Understanding the expected refund route helps users verify that the refund arrives in the correct account or form. The conditional follow-ups capture payment method references, store credit references or replacement item details as appropriate.
This single-choice question provides a clear status snapshot with eight options covering the full refund lifecycle. The conditional follow-ups for partial and declined refunds capture important details about amounts and reasons.
Capturing the merchant's stated refund date provides a reference point for assessing whether the refund is on schedule.
This yes/no question with dual follow-ups is well designed. If the refund has arrived, it captures the date, amount and reference; if not, it asks how many days have elapsed since drop-off. This helps users assess whether follow-up is needed.
Deductions are a common source of confusion in returns. The conditional follow-up captures the amount and reason, helping users understand and potentially challenge unexpected charges.
Separate or earlier refunds can complicate the overall refund picture. This question with its conditional follow-up helps users maintain a complete financial record.
Recording the stated refund timeline provides a benchmark for assessing whether the refund is progressing as expected.
This multiple-choice question covers eleven common return problems, from tracking issues to refund disputes. The conditional follow-ups for specific problems (tracking not updating, drop-off refused, merchant says not received, 'Other') capture targeted details. This structured approach makes it easier to describe issues accurately in any subsequent communication.
A simple elapsed-time metric helps contextualise the severity of any delay.
Tracking the number of contact attempts provides evidence of the user's efforts to resolve the issue, which can be useful in escalation scenarios.
This open-ended multiline field allows users to provide a chronological narrative, which is often the most useful format for understanding a return's history. The placeholder example illustrates the expected structure.
Supporting document uploads consolidate evidence in one place, strengthening the record for any future enquiry or dispute.
Understanding the user's desired outcome helps frame any subsequent action. The six options cover realistic expectations, and the conditional follow-ups for partial refunds and parcel tracing capture specific details.
Offering a user-defined case reference is a practical organisational feature. The conditional follow-up lets the user choose their preferred label.
This multiple-choice question lets users customise their reminder preferences across six trigger points. The conditional follow-up for inactivity reminders (asking after how many days) adds useful specificity.
Summary frequency preferences help tailor the level of communication to the user's needs, from daily updates to change-only notifications.
This question addresses record retention preferences, with a conditional follow-up for specifying the desired retention period. This is a thoughtful touch for users who maintain personal records.
The matrix rating covers six key aspects of the return experience with a six-point scale including 'Not applicable'. This provides structured feedback that can reveal specific pain points or strengths in the return process.
A five-star overall rating provides a quick summary metric that complements the detailed matrix ratings.
Capturing emotional response adds a qualitative dimension to the feedback, reflecting the user's subjective experience beyond numerical ratings.
This open-ended question invites constructive feedback in the user's own words, often yielding insights that structured questions miss.
This confirmation checkbox encourages users to review their entries before submitting, which supports data quality. Its mandatory status reflects its role as a final accuracy check.
This acknowledgement checkbox reinforces the form's disclaimer, ensuring users understand the record's limited scope. Its mandatory status helps ensure this understanding is explicitly confirmed.
This optional consent checkbox addresses data storage in a straightforward manner. Keeping it optional respects user choice regarding data retention.
A catch-all notes field accommodates unusual situations that structured questions may not cover, such as temporary addresses or communication preferences.
A signature field adds a layer of formality and personal accountability to the record, which can be useful if the record is referenced in a future enquiry.
The confirmation date anchors the record at a specific point in time, which is important for a document that may be updated over the course of a return.
This field accommodates scenarios where someone other than the original orderer signs the record, maintaining clarity about who confirmed the information.
Strengths: The form is exceptionally well structured, following the logical lifecycle of an e-commerce return from initial order through to refund resolution. Its use of conditional follow-ups throughout is a standout design choice, ensuring users only see relevant questions and reducing form fatigue. The tracking table directly fulfils the form's stated purpose with clearly defined columns and helpful example rows. The inclusion of problem escalation, experience feedback and reminder preferences makes this more than a simple log—it is a comprehensive return management tool. The introductory disclaimers set appropriate expectations, and the guidance paragraphs throughout provide practical data-entry advice.
Areas for consideration: The form is quite long, which may deter some users from completing it in one sitting. Consider whether a progress indicator or section-by-section saving could improve completion rates. Some sections—such as 'Parcel weight as recorded at drop-off'—collect data that may be difficult for users to provide; it may be worth noting that approximate values are acceptable. The experience feedback section, while valuable, could optionally be deferred to a follow-up request after the return is resolved, when the user has a complete picture. Additionally, the form collects a range of personal and financial details; ensuring clear privacy notices and data-handling practices are communicated alongside the form would be a prudent operational measure.
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.
Question: Full name of the person who placed the order
Recommendation: Requiring this field supports accurate record-keeping by establishing the primary identity associated with the return. A name helps link the record to the correct order and provides a clear point of reference for any follow-up communication. Form administrators should consider whether capturing a full legal name or a display name better suits their intended record-keeping needs.
Question: Email address used for the order
Recommendation: Marking the order email as mandatory ensures that the return record can be matched to the correct account or order history with the merchant. It also provides a reliable communication channel for status updates. Depending on how the form data is stored and used, consider including a brief privacy notice explaining how submitted contact details will be handled.
Question: Store or merchant name
Recommendation: Requiring the merchant name ensures each return record is clearly attributed to a specific seller, which is fundamental for organising and retrieving records—especially when a user is tracking multiple returns simultaneously. This field is central to the form's purpose and its mandatory status is well justified for operational processing.
Question: Order or purchase reference number
Recommendation: The order reference number serves as the primary identifier for matching a return to a specific purchase. Requiring this field supports data completeness and makes it significantly easier to trace the return if the merchant needs to investigate. Its mandatory status is proportionate given its central role in return tracking.
Question: Item description as shown on the order
Recommendation: Requiring an item description ensures that each return record clearly identifies what is being sent back. This supports accurate record-keeping and helps prevent confusion in multi-item returns. The instruction to copy the description as shown on the order is a helpful data-quality measure.
Question: I confirm that the information I have entered is accurate to the best of my knowledge
Recommendation: Requiring this confirmation checkbox encourages users to review their entries before submitting, which supports overall data quality. It establishes that the respondent has made a good-faith effort to provide accurate information. This is a practical operational measure for a record-keeping tool of this nature.
Question: I understand this form is a personal tracking record and does not create or change any agreement between me and a merchant or carrier
Recommendation: Requiring this acknowledgement helps ensure that users understand the form's scope and limitations before submitting. It reinforces the disclaimer provided at the start of the form and reduces the risk of misunderstandings about the record's purpose. This is a reasonable operational safeguard for a personal tracking tool.
The form effectively limits mandatory fields to seven key touchpoints: primary identity (name and email), core return identification (merchant name, order reference, item description), and two confirmation checkboxes. This is a well-balanced approach that captures the minimum information needed to create a meaningful return record while keeping the large majority of fields optional. This strategy supports higher completion rates by reducing the effort required to submit the form.
Form administrators should periodically review the mandatory field set based on user feedback and the specific operational needs of how the records are used. Requirements may vary depending on whether the form is used for personal record-keeping, shared with a merchant, or used as part of a larger returns management process.
To configure an element, select it on the form.