Deployment — Help

Last updated: August 2026

“Deployment” (or “publishing”) is how a change you make in the Seller Studio actually reaches your live, public storefront. This is the part of ShopDhoom that trips people up most, so here’s exactly how it works.

Why changes don’t appear on your storefront instantly

When you add a product, edit your store details, or change shipping settings, that change saves immediately — you’ll see it reflected right away here in the manager, and it’s safely stored. But your public storefront is a separate, pre-built version of your store that only updates when it’s rebuilt and republished. That rebuild-and-publish step is what “Deploy” does.

Think of it as: the manager is your draft, always up to date the moment you save. Deploy is “publish the draft.”

The Deploy button

Look for Deploy changes at the bottom of the sidebar. It’s only enabled when you have unpublished changes — if everything’s already live, it reads “Up to date” and is disabled. Click it, and your storefront rebuilds and republishes, usually live within a few minutes.

There’s a short cooldown between deploys (a few minutes) so that a burst of quick edits doesn’t trigger a rebuild for every single one — make several changes, then deploy them together.

What actually needs a deploy, and what doesn’t

Needs a deploy (saved instantly, but only visible to buyers after you publish):

Does NOT need a deploy (takes effect immediately, live the moment you change it):

Exception: creating a brand-new store

When you create a new store (via chat or a WordPress migration), it deploys automatically at the end of setup — you don’t need to click Deploy yourself for the very first publish. After that first launch, every further edit goes back to the normal “save now, deploy when you’re ready” pattern above.

If a deploy fails

Occasionally a deploy can fail to complete (a rare build hiccup). If that happens after creating a store via a WordPress migration, you’ll see a card explaining your store was created but needs one more publish, with a Retry Publish button right there — no need to redo the migration. For any other failed deploy, just try Deploy changes again from the sidebar; it’s safe to retry.

After a big change like a new store

If you’ve just created a store or completed a migration, you’ll also be asked to log out and log back in. That’s unrelated to publishing — it refreshes your session so the Product/Store/Order Manager buttons unlock for your new store, since your login session needs to pick up that you now own it.