Bulk crossposting

Queue many items to many marketplaces in one action, then walk away.

Bulk is where a crosslister either saves you an afternoon or quietly wastes one, so this page is mostly about how to set it up so the failures are rare and the ones that happen are easy to clear.

Before your first bulk run

Crosspost one item by hand first, to each marketplace you plan to use, and open the result on the marketplace. If the category mapping or the title length is wrong for how you list, you want to find that on one listing rather than sixty.

Your first crosspost covers what to check.

Queue a batch

1. Open Crosspost (go).
2. Filter to what you want — by source marketplace, or "not listed on" a destination.
3. Select the items.
4. Choose the destination marketplaces.
5. Press Crosspost.

Every item-and-marketplace pair becomes its own job. Twenty items to three marketplaces is sixty jobs, each succeeding or failing on its own.

Fix the blockers first

Items missing something the destination requires are flagged before the queue starts, rather than being allowed to fail one at a time.

Fix them in the item, not the job. A missing size added to the item is there for every future crosspost; the same fix made per-job has to be made again next time.

The usual blockers in a bulk run:

• No size on fashion items.
• No weight or dimensions, blocking shipping quotes.
• Brand that does not match the destination's list.
• Category that has no clean equivalent on the destination.

While it runs

The queue paces itself. A large batch takes a while — this is deliberate, not slowness to be worked around. Bursts of listing activity are what gets sellers rate-limited, and on some marketplaces suspended.

For Mercari, Depop and Vinted, leave your browser open. Those jobs run through the extension in background tabs. You can work in other tabs; you cannot close the browser or put the machine to sleep.

eBay and Discogs jobs run server-side and finish regardless.

You can close the Reskale tab and come back. The queue lives on our servers and is worked through by the extension, not by the page — so closing this tab, or opening a different part of Reskale, does not stop it. Come back and the list shows wherever the run actually got to.

What it does still need is Chrome, open, with the Reskale extension installed. Shut the laptop and the Mercari, Depop and Vinted jobs pause where they are and carry on when you open it again.

How fast it goes

Slower than your internet connection could manage, on purpose.

Marketplaces watch for accounts that list faster than a person could, and the penalty is not a polite error — it is a temporary block, and on a bad day a suspension. So Reskale spaces its listings out, by different amounts on different marketplaces:

A batch of 60 to Vinted is therefore about half an hour of background work, not a minute. It keeps going while you do something else.

If you reach a day's limit, the rest of the queue waits and goes out after midnight. Nothing is lost and nothing needs re-queueing — Reskale tells you which marketplace is waiting and roughly when it resumes.

Why a marketplace tab sometimes opens

Most listings are posted quietly in the background. Some still need a real page: Depop's brand picker and Vinted's upload form are built in a way that only works when the page is actually being drawn on screen, so if a quiet attempt does not work, Reskale opens that one listing's page, finishes it, and hands your window back.

It is not an error, and it does not mean the listing failed. If it happens on every Depop listing, check the extension's popup — Depop photo access may be switched off, which forces every Depop listing onto the slower route.

When some fail

Expect a few in any large batch. A failure is one job; the rest keep going.

Work the list by reason rather than one at a time — bulk failures cluster, and usually three or four causes account for the whole list:

1. Filter the queue to failures.
2. Read the reasons. Look for the pattern.
3. Fix the cause on the items.
4. Retry.

Retrying never duplicates. A retry resumes the same job, and jobs that already produced a live listing are not run again.

Crosspost error messages has every message and its fix.

Bulk delisting

The same selection model works in reverse. Select items, choose marketplaces, Delist.

For the specific case of "this sold somewhere, pull the others down", use Auto-Delist instead — it finds the affected items for you rather than making you remember which ones.

Practical limits

• Do not queue your entire inventory on day one. Run fifty, check the results on the marketplaces, then scale up. A mapping mistake found at fifty costs an hour; found at a thousand it costs a week.
• Watch the first few results of any new destination before trusting the rest of the batch.
• Bulk runs are not instant, by design. If a run is still going after an hour, that is usually normal. If nothing has moved at all, see troubleshooting.