After you click publish, the workflow moves through validation, submission, and tracked status updates. You can follow that result through Stockroom and Activity Feed.
Before you start
Your products are already prepared in the Listing Grid.
At least one destination is connected in Set up Marketplaces & Cross-listing.
If you are publishing to Depop or Vinted, keep Chrome open with the Dropstitch extension installed and the marketplace session authenticated.
If Vinted is newly connected, run Build a trusted Vinted browser session for reliable Dropstitch publishing so early-session behavior does not look like random failure.
How it works
Publishing starts when you submit products from Bulk List.
After that, the flow usually moves through 4 stages:
Stage | What happens | Where you check it |
Validation | Checks selected marketplaces and catches missing required fields before or during submission | Bulk List |
Submission | Sends the product into the marketplace-specific publish flow | Bulk List / queue |
Tracked processing | Monitors what happens after submission, including extension-based work that may still be running | Activity Feed |
Live-status tracking | Shows the product's marketplace status after publish starts or completes | Stockroom |
Different channels can move at different speeds:
Shopify and eBay use app or API-style connections.
Vinted and Depop depend on the Dropstitch Chrome extension and an active logged-in browser session.
That is why a product can appear in Stockroom while the queue is still finishing work in the background, especially on extension-based channels.
How to use it
Submit the product from Bulk List.
Wait for the publish flow to finish its initial checks.
Open Stockroom and find the product.
Check the marketplace icon on that product row.
If the listing looks delayed, open Activity Feed.
Review whether the action is still running, paused, or blocked by a connection issue.
Re-authenticate the marketplace if Dropstitch asks for it.
Confirm the live listing directly on the destination marketplace once the status looks correct.
Success check
The product appears in Stockroom with the expected marketplace icon.
The listing opens or appears on the marketplace itself.
Activity Feed no longer shows the publish action as delayed or unfinished.
Tips
Publish a small test batch first when you are setting up a new channel.
Treat Stockroom as the product-level status view and Activity Feed as the queue-level debug view.
For Depop and Vinted, keep Chrome open until the queue finishes its work.
If a publish flow catches missing data early, fix that before retrying instead of resubmitting the same broken batch.
Advanced settings
Best operating pattern: separate the workflow into 3 checks:
prepare products in the grid
submit from Bulk List
verify outcome in Stockroom and Activity Feed
This works well because it separates data preparation from queue monitoring and from final live-status confirmation.
For teams, one person can prep and submit while another spot-checks Stockroom and queue behavior.
Troubleshooting
The item is stuck in processing: open Activity Feed first and confirm whether the queue is still running or waiting on an extension-based step.Depop or Vinted did not start properly: keep Chrome open, make sure the extension is active, and use Why didn't my Depop or Vinted publish start?.Vinted keeps logging out during the first days: this is often session warm-up behavior. Use Build a trusted Vinted browser session for reliable Dropstitch publishing.The listing is not visible yet: short delays can be normal, especially on extension-based channels. See When listings appear on Vinted and Depop after publishing.Publish is blocked by missing information: return to the Listing Grid, fill the required fields, and submit again.A marketplace asks you to log in again: re-authenticate that channel before expecting the publish queue to continue.
Value reflection
Without a clear post-publish model, sellers end up guessing whether a listing is live, delayed, or broken. This gives you one tracked path after submit, so one-of-one inventory can be monitored from one system instead of from scattered marketplace tabs. That makes publish behavior easier to trust at scale.