Last updated: Oct 21, 2026 at 10:30PM
To take a batch of SKUs off your marketplaces, upload a spreadsheet with a single sku column. Osello disables every listing variant with those SKUs and leaves everything else about your listings as it is. Add an enabled column to turn SKUs back on from the same file.
Prepare the file
Use a CSV or Excel file with one SKU per row, or start from the template: once you pick this format on the New Import page, the Template card's Download template button gives you an Excel file with these columns, a note on each header and two example rows to replace. Only the sku column is required:
| sku | channel | enabled |
|---|---|---|
| TEE-BLUE-S | ||
| TEE-BLUE-M | macys | no |
| HAT-RED | target-plus | yes |
skuis matched against the SKU on each marketplace listing and the SKU of the product it was made from, so a list exported from your store's catalog still finds listings whose marketplace SKU has since changed.channelis optional. It holds the marketplace's handle, the part of its Osello address after/channels/(for exampletarget-plus). A blank cell applies the row to every marketplace.enabledis optional.false,no,0,offor a blank cell disables;true,yes,1,onortenables. Without this column, every row disables.
When the same SKU appears on more than one row for a marketplace, the last row wins and the import notes the row it overrode.
Run the import
- Open the store menu at the bottom of the left sidebar and click Imports, then New Import.
- Choose Marketplace Listings, then Listing SKU States CSV/Excel.
- Leave Marketplace on Every marketplace to follow each row's
channelcolumn, or pick one marketplace to limit the whole file to it. - Upload the file and click Start Import.
Started from a marketplace's Listings page (open the actions menu (...), choose Imports, then New import), the import only touches that marketplace, and a row naming a different one fails.
What the import changes
It changes only whether each listing variant is enabled. Field values, categories, SKUs and other settings stay as they are.
Disabling works as it does by hand. When a listing has no enabled variant left, the whole listing is disabled, just as if you had disabled it from its page.
Enabling a variant also enables its listing if the listing was disabled. The listing's other variants stay disabled unless the file enables them too. A variant stays disabled if another active variant on the same marketplace already uses its SKU, barcode or product, and its row shows a warning naming it.
The import's page shows one row per listing it changed, with what happened to each variant. A line whose SKU isn't listed on any marketplace, that names a marketplace Osello doesn't know, or whose enabled value can't be read as yes or no fails as a row of its own, with the reason.
What reaches the marketplaces
Nothing is sent while the import is working through the file. Once every listing is done, Osello sends the changes to each marketplace at once:
- The offers of every variant switched on or off go out together in the next offer push. A Mirakl-powered marketplace (Macy's, Nordstrom, Bloomingdale's, Kohl's and others) deletes the disabled offers; on Target+ their stock is set to 0.
- On Target+, everything disabled is unlisted in a single run. A listing disabled whole is unlisted whole.
- Target+ only sells a product it unlisted again once it is submitted, so the listings the import enabled that are still unlisted there are resubmitted together, in one submission. A listing with issues to fix first is left out, and its row says so.