Where do I send an after-sales request, and what should I include?
Start in the account where you paid for the item or booked the parcel. Use the item record for an option problem and the parcel record for a shipping issue; if both are involved, include both references. Send a short timeline, readable evidence and the specific outcome you want.
- Locate the paid item or parcel record.
- Attach evidence that shows the exact issue.
- Use the message template below and retain the case reference.
Find the support route for the record you need
Open the signed-in account on the service that took the payment or booked delivery. Go to the individual order or parcel rather than a public product page. The table shows the record to look for; it does not assume that different services share the same menu labels.
| Problem | Record to open | If the action is missing |
|---|---|---|
| Wrong model, colour, size or quantity | Paid item order | Ask support to connect the request to that item reference |
| Warehouse matching or inspection | Stored item and original order | Include domestic tracking and receipt evidence |
| Delay, missing parcel or transit damage | International parcel | Ask whether the booking platform or sender must contact the carrier |
| Refund approved but unlocated | Original payment and refund record | Ask for the refund reference, amount, currency and next processing event |
Build a brief timeline with verifiable events
Write the important events in order: payment, purchase status, warehouse receipt, inspection, dispatch, delivery and discovery of the issue, as relevant. Include dates shown by the records. Separate a carrier scan from an estimate or an event you inferred.
Keep the account factual. Explain the paid option, what you received or observed, and what you have already tried. If an earlier support response is relevant, quote its case reference and describe the action it requested. A clear timeline helps the next person understand the situation without reconstructing several disconnected conversations.
Collect the evidence that answers the first questions
Match each attachment to a point in the report. Readability matters more than the number of files. Keep the original records available and avoid cropping out the identifier or context needed to connect an image with the order.
| Information | Useful attachment | Purpose |
|---|---|---|
| What was paid for | Option summary and quantity | Defines the expected item |
| What stage the order reached | Relevant status or tracking event | Identifies the process available |
| What went wrong | Label, close-up, overall view or contents photograph | Shows the specific issue |
| How it connects to the shipment | Parcel label or packing record | Links item and parcel references |
| What was already agreed | Earlier case response | Avoids repeating a completed step |
Ask for an outcome that fits the stage
State whether you want a cancellation check, a seller return, an exchange, a delivery investigation or clarification of an existing refund. If you do not know which action is available, ask the provider to explain the options for the current status rather than selecting an inaccurate reason.
Before agreeing to a proposed action, confirm any costs, required evidence and the next deadline. Ask who needs to act first and how you will see completion. Keep an approved return address, replacement option or refund destination in writing.
Keep the case easy to follow
Reply in the existing case where possible, include the requested additional evidence and keep the reference number. If another team or carrier must become involved, ask how the linked enquiry will be identified. Save the response explaining the handover.
Share only what the enquiry requires through the verified account or support channel. Keep passwords, sign-in codes and full payment-card details out of the message. If a document contains unrelated personal information, ask the provider what information is necessary before sending it.
Example: a report needs a clearer size photograph
Suppose support cannot read the size tag in your first attachment. Reply to the same case with a well-lit overall view and a readable close-up, explain that these show the same item, and restate the paid size. This directly addresses the missing evidence instead of reopening the request with the same blurred image.
Confirm the result through the relevant record
Track the promised action as a distinct event. A return approval needs approved instructions and a return journey. A replacement needs the confirmed option and a new progress record. A refund needs an amount, currency, destination and status that can be checked against the original payment.
If the next step is unclear or a stated update is overdue, ask for the current case status and the specific action outstanding. Refer to the earlier response and its date. Keep the evidence and case history until the agreed outcome can be reconciled; an acknowledgement alone is not the same as a completed resolution.
Before you continue
- Choose the item order or parcel record that matches the issue.
- Send one concise account of events with relevant, labelled evidence.
- Track the agreed next action, deadline and financial outcome separately.
Frequently asked questions
Should I open several cases to receive a faster response?
Keep one coherent case for the same issue unless the platform asks you to use another channel. Repeated requests can split the evidence and responses. If the case is handed over, keep the reference that connects the records.
How can I make a vague response actionable?
Ask which exact information or decision is outstanding, who needs to provide it and what the next recorded event should be. Use the order and case references so the question is connected to the existing history.
Who should I contact about an order found through this spreadsheet?
Use the platform where the order or parcel was placed. The local product page and purchase link can help you reopen the relevant listing, but order status, payments, returns and shipping enquiries belong in the transaction platform’s support process.