Skip to main content

Saving and Publishing

Composer can put your work in three different places, and they are not interchangeable. Knowing which is which prevents the two most common confusions: work that seems lost, and changes that unexpectedly went live.

Save​

Save stores your work in the project, in the app. Nothing reaches your storefront.

Composer also saves periodically on its own, so a closed tab is rarely a disaster, but pressing Save before you walk away is a good habit.

Save as often as you like. This is the equivalent of saving a document.

Publish​

Publish sends the configurator to the products the project is linked to. This is the moment your changes become visible to customers.

It is a separate button from Save on purpose. You can spend a week reworking a configurator, saving throughout, while the version your customers see stays exactly as it was. Nothing goes live until you decide it does.

Before publishing, press Play and go through the configuration as a customer would. It takes a minute and catches almost everything.

Publishing keeps a snapshot, so you can look at what was live at any point and restore an earlier one if a change turns out badly. Those are on the project's page in the app.

Files​

The Files menu is for moving a configuration out of the app or into it. Two different things live here.

Download scene config gives you the configuration alone, which is the part that describes your product.

Download project file gives you that plus your editor state, meaning your camera position, what you had hidden while working, and similar. This is the one to use for a backup or for handing work to a colleague, since it restores the editor exactly as you left it.

Copy to clipboard is the same configuration as text, and Import loads either kind back in.

Use these for backups outside the app, for moving a configuration between stores, or for sending us something when you need help. They have nothing to do with publishing.

Which do I want?​

Working on it, want to come back later: Save.

Happy with it, want customers to see it: Publish.

Want a copy outside the app, or to send it to someone: Files.

Publishing to more than one product​

A project can be linked to several products, and publishing updates all of them at once. That is how one configurator serves a whole range that shares a design.

You link products on the project's page in the app rather than in Composer.

If publishing is refused​

Publishing can be blocked, and this is deliberate. The most common reason is a pricing setup that could not be charged correctly, because shipping a configurator that undercharges you silently is worse than an error message.

The message says what needs fixing. Pricing troubleshooting covers the usual cases.

If nothing appears to happen​

If Save or Publish seems to do nothing, look for a form error in the editor. Composer will not assemble a configuration containing an invalid field, so everything downstream quietly stops. The Fix in UI button takes you to it. See Troubleshooting.