You can watch the sync happen.
Cross-listing is the easy half. What decides whether a tool is worth paying for is the ninety seconds after something sells - so that is the part built first, and the part you are allowed to inspect.
Auto-delist, in detail.
Polled, not guessed
Each connected account is checked on its own cadence against the marketplace's official API, with the window computed so a slow poll cannot skip orders.
Recorded idempotently
A sale is stored against the marketplace's order id under a unique constraint, so the same order can never be booked twice.
Delisted everywhere else
Every other placement of that item gets its own durable job, run ahead of imports and routine syncs because it closes an open double-sell window.
Accounted for
Success is recorded with the time it took. Failure retries, then dead-letters where you can see it and raises its own alert.
Cross-listing
Build the item once - title, description, price, condition, brand, SKU and multi-image upload with drag-to-reorder and a chosen primary photo. Pick the destinations and publish; the jobs fan out immediately.
- Per-marketplace category and required-field mapping
- Title and price overrides per destination, kept across relists
- Edits push to everywhere the item is live, or tell you what cannot change in place
The transparency layer
The whole job queue is yours to read: queued, running, failed, dead-lettered - with the error the marketplace actually returned and a retry button. This is the difference between trusting a claim and checking one.
- Exponential-backoff retries on every marketplace write
- Dead-letter visibility instead of a job that quietly vanished
- A failed delist raises an immediate, separate alert
Inventory and analytics
One view of active, sold and ended items. Sell-through and revenue by marketplace, rendered server-side from your own data - and never summed across currencies, because that total would not be an amount of anything.
- Bulk relist and delist within each marketplace's rate limits
- CSV export of your sales
- Marketplace credentials encrypted at rest, data isolated per account
8 live integrations
All through official public APIs, server-side. No browser extension, no scraping, and we never ask for your marketplace password.
Planned - official API exists (4)
An official API exists and our integration is planned. No date is promised, and nothing can be published to these yet.See it delist something.
Fourteen days, unlimited, no card required.