Purpose #
This article explains how Shopstars manages backups, version control, and rollback procedures for Shopify stores. It covers what data is backed up, how code and themes are versioned, and what steps are taken to restore a store if an issue occurs. Clients should use this as the reference for understanding how store continuity is protected.
Why Backups and Versioning Matter #
Shopify is a hosted platform with built-in reliability, but it does not automatically provide granular backups of store data, themes, or custom code. Mistakes during catalog changes, app conflicts, or theme edits can disrupt operations. By maintaining structured backups and version control, Shopstars ensures that every change can be reversed quickly without losing data or uptime.
Data Backup Standards #
Products and Content
- Product, collection, and customer data is exported periodically as CSV.
- Policy pages, blog posts, and static content are archived as part of quarterly maintenance.
Orders and Transactions
- Orders are stored securely within Shopify and synced to accounting or ERP systems where applicable.
- Exports are scheduled for redundancy in case reporting data needs to be restored.
Theme and Custom Code
- Theme files are backed up before any significant update or customization.
- Git-based version control is used for custom themes, allowing developers to roll back to stable commits.
- Duplicate themes are maintained within Shopify as staging environments.
Apps and Integrations
- App configurations are documented in Basecamp.
- Where apps provide export or backup functionality, it is enabled and logged.
Version Control #
Custom themes and scripts are managed through Git or equivalent systems.
- Every change is committed with notes on purpose and scope.
- Branching strategies (main, staging, feature branches) are used for collaborative development.
- Pull requests undergo review before merging to the live theme.
This ensures traceability and prevents unreviewed changes from reaching production.
Rollback Procedures #
Theme Rollbacks
- Shopify’s duplicate theme functionality allows instant reversion to a stable copy.
- Git commits provide an additional rollback option for custom codebases.
- Rollbacks are logged in Basecamp to document when and why they were performed.
App Rollbacks
- If a newly installed app disrupts the store, it is disabled immediately.
- Previous app versions or configurations are restored if supported.
- Shopstars maintains a record of approved apps to speed recovery.
Data Rollbacks
- Catalog changes (e.g., accidental product deletions or price errors) are restored from CSV backups.
- Clients are advised to approve bulk uploads in staging before they go live to minimize rollback needs.
Testing Before Rollbacks #
Before rolling back, Shopstars tests fixes in staging when time allows. Critical issues (checkout failure, store downtime) are addressed immediately with live rollbacks, but standard rollbacks are validated first to prevent new problems.
Client Responsibilities #
Clients must:
- Avoid making live theme edits without coordination, as these changes bypass version control.
- Notify Shopstars immediately if accidental deletions or bulk edits occur.
- Approve rollback actions in Basecamp when non-critical changes are involved.
- Provide updated product and catalog files if client-side edits are the cause of errors.
Summary #
Backups, version control, and rollbacks at Shopstars protect store continuity by ensuring every change is traceable and reversible. Data is exported regularly, themes are versioned with Git, and rollbacks are executed through duplicate themes, commits, or CSV restores. Clients are expected to coordinate changes and approve non-critical rollbacks in Basecamp. This structured approach guarantees that even when issues occur, stores can be restored quickly and safely.
