Prepare to publish
Check store setup, payments, changes, and build readiness before putting a storefront online.
Entry path: Workspace → select a store → Storefront → Publish, Publish Changes, or Republish (label depends on publication state) → Confirm Deployment
When conditional conversation version cards are enabled, Publish on an unpublished Current Version work card opens the same publication checks. Historical version cards do not publish directly.
What this covers
Reach a successful publication check with the store details you intend to launch, or make an informed choice about any incomplete setup Runner asks you to acknowledge.
Why and when to prepare
Use this checklist before the first Publish and before important Publish Changes. It reduces the risk of launching a polished page with no sellable product, incomplete shipping, paused payments, or a failed build.
Runner can sometimes let you publish after acknowledging incomplete setup. That is a deliberate exception, not proof that the store is ready to take orders.
The exact checks and handoff depend on the publication experience enabled for the workspace. Some workspaces show a payment warning before publication and a success toast afterward; others show Store Operations checks before publication and checkout status after publication. Follow the labels shown in your flow.
Availability and prerequisites
- You need a project with a ready storefront preview.
- Publishing can depend on plan eligibility and project access.
- The storefront workspace must be connected and Runner must be idle.
- Store readiness varies by business. Runner can check store basics, products, shipping or stock details, payment connection, detected changes, and whether the storefront builds.
Open the readiness flow
- Open your project and select Storefront.
- Review the latest Current version.
- Select Publish, Publish Changes, or Republish, depending on the label shown.
- Runner checks access, refreshes the detected changes and setup status, then opens Confirm Deployment.
Preparation controls
| Control | When it appears | What happens when you select it |
|---|---|---|
| Open Store Operations | The confirmation says store setup is incomplete. | Runner closes the confirmation and opens Store Operations. |
| Retry setup status | Runner could not verify Store Operations. | Runner checks the setup status again. |
| Retry check | Runner could not reach the storefront workspace. | Runner reruns the publication build check. |
| Fix with AI | The storefront build check fails and Runner can repair it. | Runner closes the confirmation and sends the build error into the conversation for repair. No publication starts. |
| Warning checkbox | Depending on the publication flow, no changes, incomplete or unavailable Store Operations, or no payment connection needs explicit acknowledgment. | Selecting the checkbox confirms that you understand the named risk; it can enable Confirm after the build check succeeds. |
| Cancel | You are not ready to continue. | Runner closes the confirmation without publishing. |
| Confirm | The build check succeeded and required warnings have been resolved or acknowledged. | Runner starts publication. The button remains disabled while checks are incomplete or Runner is working. |
Complete the launch checklist
- In Preview, check the home page, navigation, product page, cart entry, and phone layout.
- Open Store Operations and confirm the business and store details shown there are correct.
- Confirm at least one intended product is visible, sellable, and uses the correct price, options, and media.
- Confirm the stock location and shipping setup needed for that product.
- Decide whether checkout must accept payments at launch. If yes, connect Stripe before publishing. Some workspaces show this warning before publication and others report checkout status afterward; neither is a substitute for testing checkout.
- Return to Storefront and select the publication button.
- Wait for Your store is ready to publish!
- Resolve every warning. Use an acknowledgment only when you accept its exact customer impact.
- Select Confirm.
- After publication, verify the live storefront, catalog, cart, and checkout separately.
Readiness states and troubleshooting
| What you see | Meaning | What to do |
|---|---|---|
| Verifying your store is ready to publish… | Runner is checking the current storefront build. | Wait for success or a named failure. |
| Your store is ready to publish! | The build check passed. | Resolve warnings, then select Confirm. |
| Something went wrong while building your store | The storefront cannot be published in its current form. | Select Fix with AI, review the repair, and start the readiness flow again. |
| We couldn't reach your workspace | The check could not access the current workspace. | Select Retry check. If it repeats, reconnect the workspace. |
| No code changes detected | Runner did not find a change since the last publication. | Cancel, or select the explicit redeploy acknowledgment only if you intend to republish the same state. |
| Store setup is incomplete | Important operating details remain unfinished. | Select Open Store Operations. Publish with acknowledgment only if you accept the limitations. |
| We couldn't verify Store Operations | Setup status is unavailable, not necessarily complete. | Select Retry setup status before considering the acknowledgment. |
| Payment integration is not configured | In publication flows that show this warning before launch, Runner did not find an enabled payment connection. | Connect Stripe, or acknowledge only if a browse-only launch is intentional. Other flows report checkout status after publication instead. |