Backups and protection
Choose protected resources, inspect retained history, and understand restore boundaries.
Protection policies
A protection policy tells Catalog Armor which supported products or collections should retain history. Coverage and retention are bounded by the current plan and the access granted to the app.
Snapshot history
Snapshots record supported catalog fields at a point in time. Use the history view to:
- Confirm that capture completed.
- Compare the current resource with a retained snapshot.
- Select a supported field for recovery.
- Review the intended change before confirmation.
Recovery boundaries
Catalog Armor does not promise a complete store rollback. Recovery depends on:
- The resource having retained history.
- The selected field being supported by Catalog Armor and Shopify APIs.
- Required Shopify access still being granted.
- The operation fitting current plan and safety limits.
Images and related resources may be shown as differences without being eligible for automatic restoration. The interface identifies the available action before confirmation.
Safe restore practice
- Compare the historical and current values.
- Confirm the resource and field match the intended target.
- Avoid simultaneous manual edits to the same field.
- Read the operation result before making another attempt.
Restore requests use idempotent operation tracking. If a response is interrupted, Catalog Armor checks the recorded operation instead of blindly repeating the Shopify mutation.