Understanding marketplace errors and how to fix them
Troubleshoot common Vinted, Depop, and eBay listing errors caused by marketplace security checks, account setup, or temporary sync issues.
Before you retry
When listing, editing, or delisting, the marketplace may reject the request even when the Xlistr item is valid. These errors are usually caused by security checks, stale browser sessions, account verification, rate limits, or a marketplace service issue.
Start by checking the failed action in Xlistr, then resolve the marketplace-side prompt in the same browser that runs the Xlistr extension. After the marketplace account is healthy again, retry the Xlistr action instead of manually recreating the listing from scratch.
Keep a normal marketplace tab open while retrying extension-driven actions.
Complete any captcha, SMS, two-factor, or account verification prompt shown by the marketplace.
If a browser session looks stuck, clear stale cache and cookies for that marketplace, sign in again, then retry.
Vinted: "Something went wrong", 403, captcha, or 2FA
Vinted uses browser and account checks to decide whether listing activity looks normal. A generic "Something went wrong", a 403 response, a DataDome challenge, a captcha page, or a 2FA-style interruption usually means Vinted wants the seller to verify the session before more automated listing work continues.
This can happen after listing too quickly, keeping an old session open for too long, changing network or browser state, or reaching a daily/burst activity threshold. Xlistr will pause or retry where possible, but some checks must be completed directly on Vinted.
Open Vinted in Chrome, log out and back in, and complete any sliding captcha or verification prompt.
If Vinted keeps returning a 403 challenge, clear Vinted site data/cache, close stale Vinted tabs, sign in again, and open the new item page once manually.
If SMS verification appears, list or start one item manually on Vinted, enter the code, then return to Xlistr and retry the failed action.
For bulk work, slow the pace after repeated generic errors. Large bursts can trigger Vinted protections even when the account is otherwise healthy.
Vinted pacing note
Vinted appears to enforce soft activity limits and burst checks. If you see repeated generic errors after many successful listings, wait before retrying and avoid starting another large batch immediately.
Depop: photo upload or shipping policy errors
Depop errors are commonly tied to image transfer hiccups or shipping profile state. A photo upload failure can be temporary, while a shipping policy error often means the account settings on Depop need to be refreshed before Xlistr can reuse them reliably.
If photos fail to upload, retry the listing once after a short wait.
If photo uploads keep failing, reconnect Depop, sign out and back in to Depop, then retry from Xlistr.
If Depop reports a shipping policy issue, create or update one manual Depop listing with the desired shipping profile, then import or refresh the profile in Xlistr.
eBay: policy and seller account errors
eBay rejections usually include more specific account or policy context. Common causes include restricted wording, VeRO or brand-owner protections, missing seller verification, or Managed Payments setup that has not been completed.
For policy errors, review the title and description for restricted phrases, social handles, trademarked brand terms, or wording that asks buyers to contact you outside eBay.
For seller account setup errors, open eBay Seller Hub and complete any Action Required banner before retrying in Xlistr.
Confirm identity documents, bank account details, and micro-deposit verification if eBay says more information is needed before listing.
After eBay confirms the account is ready, retry the failed Xlistr action so the inventory-backed listing state stays traceable.
When to contact support
If the same action keeps failing after the marketplace account is verified and the browser session is fresh, gather the item, marketplace, failed action, and exact error message before contacting support. This gives the team enough context to separate inventory data issues from marketplace-side blocks.
Send the inventory item title or SKU, marketplace, and action type.
Include the latest error message and whether a manual marketplace login or verification prompt appeared.
Mention whether clearing site data, signing in again, or waiting before retrying changed the result.