Shopify Theme Deployment SOP¶
Use this checklist for Shopify theme changes, whether the work is a small fix, a CRO variant, or a larger theme release.
Branching¶
| Branch | Purpose |
|---|---|
main |
Production-ready source |
feature/<name> |
Isolated feature or fix |
release/<date-or-theme> |
Optional staging branch for grouped changes |
Rules:
- Keep each branch scoped to one feature, fix, or release.
- Do not mix unrelated visual changes with tracking, checkout, or app changes.
- Keep rollback notes in the pull request or release notes.
Pre-Deploy¶
- Confirm the theme or preview URL.
- Confirm the exact pages affected.
- Check for active campaigns, sale windows, or tests that could be disrupted.
- Confirm who can approve the release.
- Take before screenshots for high-risk visual changes.
QA¶
Run the QA checklist before publishing.
High-risk areas need extra checks:
- Product pages.
- Cart drawer and cart page.
- Checkout entry.
- Variant selectors.
- Bundles, free gifts, subscriptions, or discounts.
- App blocks and scripts.
Publish¶
- Build or sync the final theme.
- Run one last smoke test on the preview.
- Publish during an agreed low-risk window.
- Smoke test production immediately.
- Record what changed, when it shipped, and how to roll it back.
Rollback¶
Rollback is required when a release breaks checkout, prevents add-to-cart, hides price or variant selection, breaks a core template, or causes severe layout shift.
Rollback steps:
- Re-publish the previous theme or revert the release branch.
- Confirm product, cart, and checkout paths.
- Record the incident and suspected cause.
- Re-ship only after the root cause is isolated.