01Enable embed
02Place app block
03Assign product
04Publish and test
Recommended approach: Publish in small, understandable releases.
Separate editing from release
Draft saves support iteration without silently changing the storefront. Publish creates a pinned snapshot for customers and records a revision for later review.
Use history as an operational record
Paginated history keeps large revision sets efficient. Review timestamps, labels, and changes before restoring an earlier version, then test the new published state.
Combine behavioral and technical signals
Insights shows whether customers start and complete the journey. Diagnostics checks installation, assignment, publishing, design rollout, and checkout readiness. Use both before assuming a theme defect.
Common questions
Does rollback change completed orders?
No. Completed orders keep their immutable configuration and render snapshots.