Submit Listings and Track Their Status

How to submit listings to a marketplace one at a time or in bulk, and where to watch their approval status from submission to live.

Once a listing shows Ready for Submission, submitting it sends its data to the marketplace for approval — and Osello tracks every step from there until it's live.

Submit a single listing

  1. Open the listing. When it's ready, a Submit Listing button appears at the top (it reads Resubmit Listing if the listing has been submitted before).
  2. Click it and confirm. Any pending changes are sent along with the submission.

Osello re-checks the whole listing the moment you confirm, so nothing incomplete reaches the marketplace. If anything is missing or invalid — on the listing itself or on any enabled variant — the dialog stays open and tells you exactly what to fix, and nothing is sent. That check covers the parent as well as the variants, so a required value missing at the parent level blocks the listing even on marketplaces that don't carry a parent product.

The dialog also offers Schedule for later — pick a date and time and Osello submits the listing then instead. Scheduling never blocks on content, on purpose: you can schedule a submission now and finish filling the listing before it fires. The check runs when the submission actually starts, and a listing that still has gaps then fails with the reasons attached instead of going to the marketplace. See enable, disable, and schedule listings for how scheduling works.

Submit in bulk

  1. On the marketplace's Listings page, select the listings you want (or select all matching your current filter).
  2. Choose Submit to Marketplace from the actions bar.
  3. Confirm. Listings with missing or invalid required values are skipped — only the ones that are ready get submitted. Use the Action required filter to find what was left behind and fix it.

Track the status

The status badge updates live at every step, from the moment you click Submit:

  • Submitting — the submission is on its way to the marketplace.
  • Submitted — the marketplace received it and Osello is waiting for it to acknowledge the review; this usually moves to Pending Approval within minutes.
  • Submission Failed — the submission never reached the marketplace. Either Osello's own check found something missing or invalid when the submission started (content can drift between clicking Submit and the submission running — a new required field, an edit, a rejected image), or the marketplace's server errored. Hover over the badge for the reason, fix anything it mentions, and resubmit. A listing is submitted whole: if one variant fails the check, the whole listing is held back rather than sending its siblings without it.
  • Pending Approval — the marketplace is reviewing the submission.
  • Pending Publication — the marketplace accepted your content but hasn't published the product to its catalog yet. Nothing to do; the offer goes out automatically once the product is published. Some marketplaces (Nordstrom, Macy's, Bloomingdale's, Shop Simon, Dia & Co) publish on their own schedule, so this step can take a while.
  • Pending Offer — the content was approved; the price and inventory (the offer) go out next, which usually happens automatically.
  • Offer Submitted — the offer is with the marketplace, awaiting activation.
  • Live — approved and selling.
  • Changes Required — the marketplace reviewed it and asked for a fix; hover over the badge to see what. Correct it and resubmit.
  • Rejected — the marketplace isn't taking the product at all (an assortment or SKU-gating decision, say), so there's nothing to resubmit. See fix rejected listings for the difference between the two.

Editing a listing that's already been submitted rolls its status back to Ready for Submission (or a completion percentage if the edit left required fields unfilled) so it's clear the marketplace hasn't seen the new version yet; the badge tooltip also notes when changes are pending submission. The only badge that ever carries an asterisk is Live* — it means an older version of the listing is live (a plain Live badge means the latest version is live).

Listings with variants show two badges

A listing with variants tracks two things that move independently: how far along its variants are, and how much of it is live on the marketplace right now. So it shows up to two badges.

The first badge is progress. When every variant is at the same step it reads plainly (Pending Approval); when they differ it names the one that needs attention first and prefixes it — Partially Changes Required, Partially Submitted. Ordering is deliberate: anything still setting up comes first, then the states you can act on (incomplete, then changes required, then ready), then the rest of the lifecycle, and finally the states you can't act on (rejected, unlisted, suspended). Disabled variants are ignored entirely — they aren't holding anything back. Hover the badge for the full breakdown of which variants are where.

Two labels never take the "Partially" prefix. Ready for Submission doesn't, because you submit a listing as a whole, so a partial version isn't something you can act on differently. The completion percentage doesn't either, because it's calculated across the whole listing — though Partially Invalid does appear when only some variants have validation errors.

The second badge is liveness: Live, Partially Live (some variants are live, the rest aren't yet), or the same two with an asterisk when what's live is an older approved version. A listing that's fully live with nothing outstanding shows a single Live badge.

When you resubmit a live listing

Editing and resubmitting a listing that's already live doesn't take it down — the marketplace keeps selling the old version until the new one is approved. While that's in progress the first badge shows where the new version is (for example Pending Approval), and a second outlined Live* badge appears beside it to confirm an older version is still live on the marketplace. Hover over either badge for details. A banner on the listing page also tells you when a previous version is live and what to do next.

Filter by what needs doing

To watch a group of listings, open Filters on the Listings page and pick a category under Show. The same picker appears on the variants table inside a listing.

  • Action required — needs work from you: incomplete or invalid, ready for (re)submission, changes required, submission failed, or unknown.
  • Waiting — nothing to do but check back. Reason covers both sides in one list: the marketplace's (submitted, pending approval, offer submitted) and Osello's (setup, a submission in flight, an offer that hasn't gone out yet).
  • Live — selling on the marketplace. Live State starts with all four rows selected; untick to narrow.
  • Inactive — disabled by you, or rejected, unlisted, or suspended by the marketplace. Nothing here is waiting on you.
  • Any state — the two badge axes directly. Current version matches the exact progress badge, Partially forms included; Last approved version matches the liveness badge. Use this when you want the results to mirror a specific badge exactly.

Live State has four rows because liveness is two questions at once — how many variants are live, and whether any of them is live via an older approved version (the asterisk):

All up to date Some on an older version
Some variants live Partially Live Partially Live*
All variants live Fully Live Fully Live*

Tick whichever combination you want: both Fully rows for "completely live, whatever version"; both asterisked rows for "has edits that haven't gone live yet".

Outside the Live category the same picker appears as Last approved version with two extra rows: Not Live (nothing live at all) and Not Fully Live (at least one variant still isn't live — listings with nothing live count too). Pairing it with a category is how you ask a question like "needs action and isn't fully live yet", so you can chase the SKUs that are still holding a listing back. Fully Live isn't offered there, since a listing with nothing outstanding can't also be in one of those categories.

The four categories match a listing if any of its variants is in one of those states, so a listing with one SKU needing changes still shows under Action required even when its badge reads something else. That means a listing can legitimately appear in more than one category. Two exceptions: a listing you've disabled shows only under Inactive, whatever its variants say — disabling it is the whole story, so its variants read and filter as Disabled too, and nothing on it counts as live; and Any state matches the badge itself.

Every category shows a live count, so you can see at a glance where the work is — and each stays listed even at zero, because "nothing to do here" is the useful answer. Picking one narrows to exactly that many rows.

Choosing a category is usually all you need. More options underneath opens the individual states within it, each with its own count; states with a count of zero are hidden there.

Filter by source product tags or SKU

The same Filters dialog has two sections for this. Source Product Tags follows a listing back to its source products and keeps only listings made from a product matching your tag query — the same query language as the Products page (combine tags with AND, OR, NOT, and parentheses); listings that aren't linked to a source product never match a tag filter. SKUs matches the listing's own variant SKUs against a pattern, with a Doesn't match mode to exclude instead.

Dig into a specific listing

Every listing has tabs with the full paper trail:

  • Submissions — each submission with when it happened and how many variants were approved, rejected, or still pending. Open one for the details, including any rejection reason.
  • Submission Messages — the messages the marketplace sent back, including warnings and errors.
  • History — a searchable log of changes to the listing and who or what made them. It covers the whole listing: changes to the listing itself, to any of its variants, and to any field value. The Variant column says which variant each row belongs to — a specific variant by its options (linked to that variant), or Parent for the shared data every variant inherits. Changes to the listing as a whole leave the column blank.

Because editing a submitted listing rolls it back to Ready for Submission, History is where you find out why that happened. Every change that can cause it is recorded: an edited field value, a changed SKU or barcode, a swapped variant option or group image, a new category — and disabling or enabling a listing or variant, including when a scheduled task does it for you.

The marketplace also has a store-wide History page in the sidebar covering changes across all its listings.

What a submission's own status means

A submission is the record of one push. Its status describes what happened to that push — not whether the listing is selling today, which is what the listing's own badge is for. Alongside Approved and Rejected you'll see:

  • Pending Approval — the marketplace is still working through this submission.
  • Accepted — the marketplace took the data and closed out this submission without giving a verdict on it. Common on Nordstrom, Macy's, Bloomingdale's, Shop Simon and Dia & Co, where the retailer reviews on its own schedule. Nothing to do; the listing's badge tracks what happens next.
  • Superseded — you submitted the same variants again, so this older submission stopped being the current one. It can still be approved on the marketplace's side, and if it is, the listing goes live from it — a submission can't be recalled once it's been sent.
  • Expired — the marketplace no longer keeps a record of this submission (they clear them out after a few months), so its outcome can't be looked up anymore. Only affects old submissions, and never the listing itself.

Where to go next

Did this answer your question?

A real person from Osello will dig in and get back to you.