For a small Shopify store, backup means products, orders, and a theme. For a Shopify Plus store, the same word has to cover a lot more ground.
Picture a Director of Digital two weeks before BFCM. Her team is finalizing a metaobject migration, pushing a custom app update, and prepping three expansion stores. A single bad Flow trigger could cascade into the 3PL, the ERP, and every product detail page that references the changed schema. When she says “can we roll that back?” she is asking about a specific surface at a specific moment in time, not the storefront.
This is the pillar reference for that conversation. It covers what Shopify Backup & Restore protects out of the box, where Rewind Protection Suite layers on top, and the scenarios where one, the other, or both belong in the stack.
Why Plus is a different class of commerce system
A Plus storefront is not a bigger direct-to-consumer storefront. The data graph behind it includes components a small store never touches.
Metaobjects launched with Shopify Editions Winter ’23 on February 8 and 9, 2023. Metaobjects are custom, reusable content types with typed fields and linked references. Metafields, their close cousins, attach to many Shopify resource types. Products, variants, customers, orders, collections, companies, company locations, and draft orders all carry metafields in production Plus stores.
Expansion stores add another layer. Shopify Plus expansion stores are separate .myshopify.com stores under one Plus contract, each operating independently with its own data and settings. A Plus organization gets up to 10 stores on contract, one main plus nine expansion. Markets is a different pattern, a single storefront with multiple regional variants, launched in 2021. The two are often confused, and they have very different restore implications.
Then there is B2B. Shopify B2B catalogs on Plus allow unlimited catalogs assignable to specific company locations. The surface covers companies, company accounts, company locations, price lists, contracts, quantity rules, and payment terms. Lower Shopify tiers cap out at three active catalogs. A Plus merchant running B2B works with a richer data model than the rest of the platform.
All of it sits on top of the theme and apps.
The failure patterns that show up in production
The baseline for SaaS data loss is the same on any platform. 87% of IT professionals reported experiencing SaaS data loss in 2024, with malicious deletions as the leading cause, per the Kaseya 2025 State of Backup and Recovery Report (n=3,000+). Plus merchants sit inside that number, but the shape of their losses is distinct.
The cascading-failure pattern Plus ops teams see:
- A bad metaobject change upstream quietly breaks product detail pages downstream.
- A bad Flow automation pushes incorrect state to the ESP, 3PL, ERP, and data warehouse before anyone notices.
- A bad custom app deploy affects checkout and first shows up as a conversion dip.
- A bad theme deploy degrades a landing page for hours before anyone catches it.
Each surface has a different restore shape, and the shape is rarely “the whole store.” It is one metaobject, one Flow, one company account, or one theme section. A tool that can only bring back the whole store ends up undoing a day of correct work to undo ten minutes of incorrect work.
What Shopify Backup & Restore covers today
Shopify Backup & Restore is a first-party offering. Its scope, defined by Shopify’s public documentation, covers products, themes, and some associated metadata at the store level.
A Plus merchant should treat Shopify Backup & Restore as the floor in the stack, not the ceiling. For stores with minimal custom data, simple catalogs, and strong change-control discipline, it can be enough on its own. That is not most Plus stores.
What the Plus commerce graph actually holds
The list a Plus architect walks through when someone asks “what do we need to back up?” is long on purpose:
- Metaobjects and their schemas
- Metafields across many resource types
- B2B companies, company accounts, company locations, and catalogs
- Draft orders and discount logic
- Flow automations
- Custom apps wired into checkout and product flows
- Functions and Script editor state
- Inventory sync configuration
- Customer segments
- Theme and product catalog on top of all of the above
Every row is a buyer question: Is it covered? How granular is the restore? Can it restore to staging? Can it restore without touching the rest of the store?
Where Rewind fits
Rewind is a SaaS resilience platform built on independent architecture, not a plugin. Data stays accessible even if the SaaS vendor is compromised. Rewind is a Shopify Certified Technology Partner. More than 25,000 organizations trust Rewind, and the platform safeguards over 7 PB of customer data. The engineering team is in-house in Canada. Integrations are built and maintained in-house, not outsourced. Onboarding takes just three clicks.
Rewind Protection Suite sits alongside Shopify Backup & Restore. Shopify Backup & Restore covers the first layer, while Protection Suite adds coverage across the surfaces that define a Plus store, including metaobjects, metafields, B2B state, and multi-store considerations.
The defining capability is granular, item-level restore, so you can recover individual items, a single ticket, page, file, or configuration, without affecting the rest of the system. That’s non-destructive recovery that matches the shape of a Plus failure.
Eight criteria for evaluating Plus backup
When a Plus ops lead scores a backup layer, these rows tend to decide the outcome:
- Granular item restore for metaobjects, metafields, companies, and theme sections
- Metaobjects and metafields coverage across all resource types in use
- Staging reliability for pre-production restores and sandbox seeding
- Theme rollback at the section level, not just the theme level
- Multi-store support for expansion stores and Markets
- Custom app and Functions coverage
- Governance posture covering retention, access, and audit
- Alignment to enterprise procurement and contracting cycles
Score each row as covered, partial, or not covered. Two or more partial or missing rows signals that a layered posture is warranted.
A decision tree for the Director of Digital
Four questions keep this honest:
- Do we use metaobjects or metafields in production?
- Do we run B2B on Plus?
- Do we run expansion stores or Markets?
- Do we have a staging-to-production cadence with deploy history we would want to roll back?
Two yesses is the threshold where Protection Suite clears the evaluation. Three or four yesses means the layered posture is a design requirement, not a debate.
Scenarios where Shopify Backup & Restore alone fits
There are real cases where Shopify Backup & Restore is enough. A Plus store with a simple product catalog and limited custom-data usage. A merchant whose compliance posture is satisfied by the first-party scope. A brand with strong change-control discipline and a low rate of structural change. If that profile describes the store, stay with Shopify Backup & Restore and move on.
Scenarios where Protection Suite earns its keep
Most Plus stores look more like this:
- Any Plus store built on metaobjects and custom metafields
- Any store running B2B on Plus
- Any multi-store organization running expansion stores or Markets
- Any brand with a staging-to-production cadence for theme or custom-app deploys
- Any merchant whose governance posture requires item-level restore for audit response
For those stores, the layered posture is the fit: Shopify Backup & Restore acts as the floor, with Protection Suite as the structural layer above it.
Plus consultancies reach the same conclusion from a different angle. They look for narrow restore scope down to the section, metaobject, or company level; multi-store coordination; and a governance posture they can recommend to their clients’ legal and compliance teams. Protection Suite addresses all three, which is why agencies bring it into Plus engagements by default.
What a Plus recovery actually looks like
The restore conversation at Plus scale is almost never about the whole store. It is about a specific product detail page after a metaobject value went sideways during a Tuesday content update, or a specific company account after a B2B catalog merge, or a specific Flow automation after a staging deploy pushed bad state to inventory, or a specific theme section after a designer’s edit broke the cart.
Each asks for a different restore shape: A single metaobject. A single company. A single Flow. A single theme section.
Here is what that looks like in the wild: An admin spots a product detail page showing the wrong price before a BFCM promo goes live. She opens Rewind, finds the pre-incident version of the metaobject, and restores it. The page is recovered with no other metaobjects touched and no other products touched.
That is item-level restore in practice. It is the reason Plus merchants describe Rewind as operational muscle, not insurance.
What Plus merchants say
“We were able to recover 11,000 products that were mistakenly overwritten with false information in just 30 minutes,” says Jonas Forth, Head of Digital at Moomin.
“Protection Suite is definitely next-level. It represents a whole new generation of apps for Shopify merchants,” says Paul Rosenwald, Director of Business Development at SeaMonster Studios.
“Rewind is like insurance. You probably won’t think about Rewind much until you need it. It gives you an additional sense of security, and when you do need it, the ROI is high.” That’s Jonas Forth again, at Moomin.
Governance practices for a Plus ops team
A few lightweight rituals close most of the gaps that cause incidents:
- Name an owner for metaobject schema changes
- Name an owner for Flow automations in production
- Keep a staging-to-production checklist that a human signs
- Run a quarterly restore drill on the three surfaces most likely to break: metaobject schema, Flow automation, and theme section
Restore drills are the point at which a team stops assuming the backup works and starts knowing it does.
Three moves for this month
For a Plus merchant ops lead, a Director of Digital, or a Plus agency principal:
First, audit your Plus commerce graph against the eight criteria. Score each row covered, partial, or not covered.
Second, run the four-question decision tree. Two or more yesses means the layered posture is the fit.
Third, if you are working with a Plus agency, forward the eight criteria and align on a joint recommendation. The conversation gets sharper when the ops team and the agency are scoring the same rows.
Learn more about Rewind for Shopify at rewind.com/shopify.
Rewind">
