Troubleshoot publishing, checkout, and apps
Separate publication, live-store, checkout, and provider problems so you can fix the right layer.
A successful build does not by itself prove publication, catalog data, checkout, or an outside provider. Verify each layer separately.
Entry paths: Affected store → Online Store → Publish for readiness checks; Sell → Apps for provider connections.
English callouts highlight the controls. Select the image to enlarge it.
The build check passes, but incomplete setup leaves Confirm disabled. Resolve the named requirement before retrying publication.
Before you start
- Record the affected store, public URL, provider, and exact visible state.
- Stop before a real charge, order, provider disconnect, or other consequential action unless the test is authorized.
- Verify one layer at a time; a working Preview does not prove publication or checkout.
Important controls and results
| Control | What happens after you select it |
|---|---|
| Retry check | Runs the failed publication or checkout readiness check again. It does not fix the named cause. |
| Publish / Republish | Starts publication after required checks pass; it does not prove catalog or checkout behavior. |
| Connect Stripe | Opens the payment connection path. No payment is accepted until the provider and live checkout are usable. |
| Reconnect in Apps | Restarts the provider’s official authorization flow for the existing connection. |
Identify the failing layer
| Layer | Proof to look for | If it is missing |
|---|---|---|
| Preview | The intended page and interaction work in Online Store. | Fix the build or content before publishing. |
| Publication | Runner shows a successful published state and a live URL. | Open publication status and resolve the named requirement or error. |
| Live storefront | The live URL shows the intended version in a fresh visit. | Check whether newer changes require Republish. |
| Catalog | The expected product, price, availability, and shipping choice are visible. | Correct Store Operations data and storefront availability. |
| Checkout | A safe test can reach the expected checkout and payment/shipping choices. | Check payment, shipping, store mode, and provider status. Do not place a real order unless authorized. |
| Provider | The app shows connected and the provider confirms the expected account. | Reconnect through the official app flow and recheck permissions. |
Publish recovery
- Open Online Store → Publish and read the readiness checks. Stop at a missing Stripe, shipping, or other named requirement; resolve it using Prepare to publish before retrying.
- Check whether another publication is already Deploying.
- If publication fails, preserve the displayed error.
- Retry once only after the named cause is resolved.
- Open the live URL after success and verify the intended page.
Checkout recovery
- Confirm at least one sellable product is visible on the live store.
- Confirm shipping applies to the test destination.
- Confirm the payment app is connected to the intended mode and account.
- Reach checkout through the live storefront rather than a direct guessed URL.
- Stop before a real charge or order unless the test is explicitly authorized.
App recovery
- Open Sell → Apps and select the provider.
- Read the displayed state: not connected, connected, needs attention, or unavailable.
- Reconnect only through the provider’s official authorization window.
- Confirm the returned account and permissions.
- Verify the actual downstream result; a green connection badge alone is not end-to-end proof.
Watch: inspect a publication blocker
The recording reviews readiness checks, then chooses Cancel. No store is published and no checkout is completed.