Store statuses
Distinguish a live store from an unpublished draft, a ready preview, and a completed task.
The store summary tells you whether a public version exists. Open Storefront to check whether your latest change is part of that version.
Entry path: Current store name and summary → Storefront.
Read the summary
| Label | What it tells you | What to check next |
|---|---|---|
| Unpublished draft | The store does not have a published version to use as its live storefront. | Review the current preview and prepare its first publication. |
| Live | A public storefront exists. | Open the public URL and confirm the intended changes are visible. |
| Current Version in the storefront | This is the latest project version. | Compare it with the published version before assuming it is live. |
| Published on a version | That version is associated with a completed publication. | Verify the public page and checkout separately. |
Older store-card layouts can use Drafted, Deploying, and Published. Read Deploying as an in-progress operation and wait for its result. A live or published label can still refer to an older successful version after a later attempt fails.
English callouts highlight the controls. Select the image to enlarge it.
This is the current project preview. Use its version and publication controls to compare it with the live store; a visible preview alone does not make it public.
Verify a recent change
- Confirm the current store name.
- Open the task that requested the change and review its latest status and Details.
- Open Storefront and confirm the expected change in the current ready preview.
- Check whether that version was published.
- If it was, open the public URL and repeat the relevant customer action.
You have verified the change only when the intended version and its visible result agree. Task completion alone does not prove a preview, publication, payment, or provider action succeeded.
If the summary seems wrong
- Let any active publication finish before starting another attempt.
- Refresh the current view once and read the latest publication result.
- Compare the current and published versions in Version history.
- If the public store still shows older content, review the newer preview before using Publish Changes.
- If publication failed, follow the named error instead of repeating the same action.