Last updated: Oct 13, 2026 at 9:19AM
When a marketplace turns a listing down, Osello shows you the reason it gave. Most of the time it's a single field the marketplace didn't like — fix it and resubmit.
Two different badges
Marketplaces send both "fix this" and "we're not taking this" through the same channel, so Osello reads the reason and splits them into two badges:
- Changes Required (amber) — the marketplace named something to correct. Fix what the reason describes and resubmit. This is by far the common case, and it's grouped under Action required in the filters.
- Rejected (red) — the marketplace isn't taking the product: an assortment or SKU-gating decision, or a structural rejection with no stated path back. Resubmitting won't change the answer, so it's grouped under Inactive and doesn't count toward your work queue.
Two more reasons arrive through the same channel status but aren't rejections at all, so they show as their real state instead:
- Unlisted — the item was pulled, usually because it was discontinued or someone asked for its removal. To put it back on sale, resubmit it: the badge moves through Submitting, Submitted and Pending Approval exactly like a first submission, and it won't flip back to Unlisted while the marketplace is still looking at the new submission.
- Suspended — your marketplace account is inactive, and the marketplace parked the listing until it's reinstated. These come back on their own once the account is active again; resubmitting one works the same way as an unlisted listing, but the marketplace will hold it until the account is active.
Find the reason
There are three places to look, from quickest to most detailed:
- The status badge. Hover over the Changes Required or Rejected badge on the Listings page, or on the listing itself, to read the marketplace's reason.
- The Issues tab. Open the listing and go to Issues to see everything the marketplace sent back, sorted into categories like Imagery or Content and tied to the specific variant or field it affects. Each issue quotes the marketplace's own wording underneath. When one message raises several unrelated problems (a cropping complaint and a missing measurement in the same sentence), you'll see one issue for each, so nothing gets fixed halfway. When Osello doesn't recognize the wording straight away, the issue is named by the marketplace's own words instead of a label, so it still reads as what it is; shortly after, Osello's AI reads the message and, when it is sure, sorts the issue into its category and onto the field it is about. Wording the AI can't place stays under the marketplace's own words.
- The Submissions tab. Each submission shows how many variants were approved, rejected, or pending. Open a submission to see its details, including the recorded Rejection Reason.
Some marketplaces reject with a note that only points elsewhere, such as Nordstrom's "Review and resolve all Synchronization errors - Look at the integration errors below". Osello reads the errors that note points to and shows each one as its own issue, on the field it names where Osello can match it (for example "the attribute CPSC Sharp Points must be provided" lands on the CPSC sharp points field). The submission's Rejection Reason lists the same errors.
On a listing with variants, the marketplace usually objects to the variants rather than the listing, so the listing's own page can look clean while its variants are the problem. The Variants tab carries an amber count of how many need changes; hover it for the problems behind that count and how many variants report each.
To round up everything that needs work at once, open the marketplace's Listings page, open Filters, and pick Action required — or narrow to just Changes required under More options.
Fix the listing
This is the path for a Changes Required listing. Once you know what the marketplace objected to:
- Correct the field on the listing's Fields tab — edit the value directly, or use the field's Update with AI action to have Osello redo it.
- Rejected image? The Primary Image field has an Update If Needed action that checks the photo against the marketplace's background and shape rules and corrects it, and new listings are cropped to the required shape automatically.
- AI keeps making the same mistake? Add custom instructions for that field so every future fill follows your guidance — see custom instructions.
- Wrong category? If the rejection suggests the product doesn't belong where you listed it, change the category via Edit Structure — the required fields will update to match.
Resubmit
After fixing, click Resubmit Listing at the top of the listing. The badge moves back to Pending Approval while the marketplace reviews it again. You can resubmit as many times as needed.
Marketplaces don't always look at the new version straight away — some take hours. Until yours does, the listing stays on Submitted or Pending Approval; it won't flip back to the earlier reason while it waits.
Some rejections are settled on the marketplace's side rather than in Osello — for example a sustainability claim that needs documentation registered with the marketplace. Once the marketplace puts the product back under review, the badge moves to Pending Approval on Osello's next status check without a resubmit.
When it says Rejected
A Rejected listing is a decision on the marketplace's side, not a data problem, so there's usually nothing to fix in Osello. If you think it's wrong — or the reason is about assortment and you've since been approved for that category — take it up with your marketplace contact. Once they change their mind, Osello picks the new status up on its next check.
When Osello's status looks out of date
Osello checks each marketplace on a schedule, so a status can lag behind what the marketplace shows you, and a listing you fixed outside Osello can sit on an old badge. Refresh Status re-reads the marketplace right now and replaces what Osello holds for that listing.
Find it under Content in the actions menu (...) on a listing, in the actions menu on a variant, or select rows on the Listings page or a listing's Variants tab and pick Refresh Status under Marketplace. The refresh runs in the background; the listing updates on screen when it finishes.
It overwrites rather than merges, which is the point and also the catch:
- The badge, the marketplace's message and the live indicator all come from the marketplace's current answer. A listing marked live under an older approved version stops reading live if the marketplace no longer says so.
- Issues are rebuilt. Anything the marketplace has stopped reporting goes away, and anything it still reports comes back as open even if someone dismissed it. Issues Osello raised itself, from a content check or an AI agent, are left alone.
If a listing is mid-submission, wait for the marketplace to answer before refreshing — otherwise you get its verdict on the version you just replaced.
When it's not the listing's content
Sometimes the problem is with syncing rather than your listing's data — for example, the marketplace's system returned an error while Osello was pushing updates. Those show up as sync issues: you'll see a "Sync issues detected" alert on affected records, and each marketplace has a Sync Issues page (in the actions menu on its Settings page) listing every open issue with its details.
If a rejection reason is cryptic — marketplaces are not always articulate — click Get Help and include the listing. We read these all day and can usually translate.