Identify where the problem occurred
Separate issues that happen before payment, during preparation, in transit or after delivery. Each stage needs different information. A declined payment does not require the same evidence as a damaged parcel or a product that differs from its listing.
Check the promised timeframe as well. An order that is still within its stated preparation window is different from a parcel that has stopped moving after dispatch.
Preserve evidence that explains the case
Record the order number, date, product and exact discrepancy. Screenshots can help when a status changes or an important agreement would otherwise be hard to reconstruct. Crop or cover personal information that is not relevant to the issue.
A short timeline is more useful than a large folder of unsorted images: order placed, confirmation received, expected dispatch, latest status and what you see now.
Contact the seller with one clear question
Describe the observable issue without guessing at the cause. If tracking is missing, ask when the parcel was handed over. If the item differs from the agreement, name the specific listing or chat detail that does not match.
Keep the conversation in the marketplace chat. It connects the discussion to the order and leaves a reviewable record if support is needed later.
Know when to involve support
Contact support when a technical step cannot be completed, a reasonable response does not arrive, or a material discrepancy cannot be resolved directly. Explain what you have already tried and what outcome you need help with.
Support can assess only the information available in the platform. A complete, calm summary is easier to review than repeated messages or accusations.
Handle payment and account issues separately
For a payment issue, establish whether the transaction is completed, declined or pending. Do not trigger a second payment while the first status remains unclear. Share sensitive financial details only through a specifically designated secure channel.
For sign-in trouble, use account recovery and confirm that you can access your own email address. Passwords and full payment credentials never belong in a support message.
Close the case only after checking the outcome
Confirm that the agreed correction has actually happened. Keep essential records until payment, delivery or refund has reached a clear end state.
If you leave a review afterwards, describe both the original issue and how it was handled. That gives future buyers useful context instead of a verdict without detail.
What a useful support request includes
- Order number and affected step
- Expected outcome and observed result
- A short timeline with relevant dates
- What you already tried
- One concrete question or requested next step
Review the specific issue in more detail
Use the relevant guide to check authenticity, payment, reviews or the product after delivery without mixing separate concerns.
