To show you requested a return before a deadline, keep a record of the message you sent, the order and item it identified, and its date and time. A confirmation or case reference strengthens the chronology. Also check what the deadline required: proof of timely notification does not automatically prove timely shipment, arrival or overall return eligibility.
The return-window and deadline guide explains those separate stages. Your evidence should show the specific action required under the policy or applicable rule, rather than using one screenshot to stand in for the entire return process.
Make the request unambiguous
Identify the order number, item and decision to return or cancel. Use a direct statement instead of only asking what the return policy is. A general information question may not demonstrate the same intention as a clear request. Include enough information for the seller to connect the message to your purchase.
State the reason accurately when needed for the relevant process. A defect complaint, cancellation and ordinary preference return can use different routes. Do not claim a fault you have not observed or describe an authorized purchase as fraud. Keep the wording consistent across the merchant, marketplace and payment-provider records.
Save the submitted message and confirmation
For a return portal, retain the completed submission, success screen, confirmation email and any authorization number. Where practical, save a copy showing the item, request text and timestamp together. A screenshot of an empty form demonstrates preparation, not successful submission. Check that the portal did not reject the request after you clicked submit.
For email, keep the original sent message and any automated acknowledgement. Retain attachments and delivery-error notices. If a message bounced, use an appropriate alternative promptly and explain the sequence. A record in a drafts folder is not the same as a sent message.
Calls and live chats need a useful record
After a phone call, note the date, time, number contacted, representative’s name and case reference. Ask for email confirmation of the request and agreed next steps. A short follow-up message summarizing the conversation can help create a written chronology, although it does not independently prove every disputed statement.
For chat, download or save the transcript before closing the session where that option exists. Preserve the opening message and conclusion, including whether the agent actually submitted a return or only explained the process. A statement that you can apply later is not necessarily confirmation that the application was made during the chat.
Legal notice rules can specify what matters
For a labeled UK example, regulation 32 of the Consumer Contracts Regulations 2013 permits a clear cancellation statement and addresses communications sent before the period ends. It also places the burden of showing timely cancellation on the consumer in a dispute. Coverage and related provisions must still be checked.
That example is not a universal evidence rule for every store. Identify the relevant policy or legal route before deciding which timestamp matters. A merchant’s voluntary return program may require a particular authorization step, while a statutory route can have different requirements. Ask for the basis of any refusal rather than assuming those systems are identical.
Preserve technical-error evidence
If a portal is unavailable, save the error with the date and item information where possible. Try a suitable alternative route such as the seller’s published customer-service address. State that you intend to return and explain the portal problem. Do not repeatedly wait for a failing system until every possible cutoff has passed.
An error screenshot can support a request for review, but it does not automatically extend the deadline or prove the seller received notice. Keep the follow-up communication and response. Ask whether the business will preserve eligibility while resolving the problem and whether a separate shipping deadline still applies.
Connect notice to shipment without confusing them
Keep the authorization, label, carrier acceptance receipt and delivery tracking alongside the original request. The guide to shipping versus arrival deadlines explains what those records establish. Do not replace the label-created date with the later carrier acceptance date when the distinction matters.
If the seller disputes timeliness, provide a concise chronology with each event and its supporting record. Ask which event it considers late and which deadline it applied. The guide to late returns and extensions covers exception requests when the evidence shows an action actually occurred after the required date.
FAQs
Should I alter screenshots to simplify them?
Keep the original. If you provide a cropped copy for readability, retain the full record with surrounding context and timestamps.
Does a timely request guarantee acceptance?
No. Product eligibility, condition, applicable exclusions and separate return steps still matter. The record establishes chronology, not every requirement for a remedy.
How should I handle different time zones?
Preserve the original displayed timestamp and explain any conversion separately. Ask which zone governs the cutoff. A consistent record lets the reviewer compare the message and deadline without guessing which local clock you used.