Your first crosspost

One item, one destination marketplace, start to finish. Do this before you crosspost sixty things, because it is where you find out whether the field mapping matches how you actually list.

Pick a good first item

Not a random one. You want a boring success, and some items are much more likely to give you one:

• Clear brand. Branded items match a marketplace's brand list cleanly. No-brand items land in "unbranded" or fail a required field.
• Common category. Women's tops, sneakers, jeans. Not vintage militaria, not a bundle, not something ambiguous.
• Good photos already. Crossposting reuses the photos on the item; it does not improve them.
• You know its size and condition. These are required nearly everywhere.

Then pick one destination. eBay if you have OAuth connected and want the richest test; Vinted or Depop if that is where you actually plan to expand.

Post it

1. Open Crosspost (go).
2. Find your item and open it.
3. Tick the destination marketplace.
4. Work through the form for that marketplace.
5. Press Crosspost.

About that form

Each marketplace shows its own fields, prefilled from the item. Anything missing that the marketplace requires is flagged before you can submit — that check exists so you find out here, in one screen, rather than after a queue of sixty failed jobs.

You will most often be asked for:

• Category — Reskale suggests one; confirm it. This is the field most worth getting right, because the marketplace derives half its other requirements from it.
• Condition — the wording differs everywhere. Reskale maps between them; check the result reads how you would have written it.
• Size — required on fashion categories nearly everywhere.
• Shipping — weight and dimensions, or a shipping profile.

More detail: listing fields and requirements.

What happens after you press it

A job is created. Jobs are visible on the Crosspost screen and move through these states:

For eBay and Discogs this is a server-side API call and takes seconds.

For Mercari, Depop and Vinted the extension opens a background tab on the marketplace, fills the sell form and submits it. That tab is inactive — it will not steal focus — and closes itself when done. Leave the browser open while it runs, but you can keep working in another tab.

Check the result

Do not trust the green tick alone the first time. Open the listing on the marketplace and read it:

• Is the title right, and not truncated somewhere awkward? Marketplaces have different length limits.
• Are all the photos there, in the right order?
• Is the price what you meant, in the right currency?
• Is the category where a buyer would look for it?
• Does the condition read the way you would have written it?

Anything wrong here is a mapping problem, and it will repeat on every future crosspost until it is corrected. Fixing it now on one listing is a great deal cheaper than finding it later on sixty.

If it failed

The job carries the reason in plain English. The common first-time causes:

• Missing required field — the marketplace wants something for that category that the item does not have. Add it and retry.
• Category rejected — the suggested category does not accept this kind of item. Pick a different one.
• Connection expired — reconnect at Connections and retry.
• Extension not responding — reload the Reskale tab and check the extension is enabled.

Every message, with fixes: crosspost error messages.

Retry from the job itself. Retrying a failed job never creates a duplicate — it resumes the same job.

Then do it in bulk

Once one item comes out clean, the same mapping applies to everything like it. Bulk crossposting covers queuing many at once and what the queue does when one of them fails.

Before you scale up, set up auto-delist. The more places one item is listed, the more it matters that the copies come down when it sells.