Skip to main content

Write safety, recovery, and privacy

Preview and back up Shopify bulk edits

Open Bulk Editor binds the preview to the store and task settings. Before a recoverable write starts, it saves the original values in a local backup journal.

How a protected write is prepared

The app checks the preview, saves the task snapshot, and creates the local recovery record before a recoverable Shopify write begins.

1

Preview binding

The preview is tied to the store, API version, configuration, and selected rows. Change any of them and the app asks you to preview again.

2

Task snapshot

Relative operations are turned into final values before execution, so retry and redo do not apply the calculation twice.

3

Backup journal

Recoverable writes save original values locally before the first Shopify write begins.

4

Store check

A backup from one shop cannot be used to roll back or redo changes in another shop.

Catalog data goes directly to Shopify

Store credentials, templates, mapping profiles, previews, backups, logs, and history live in the application data folder on your computer. Open Bulk Editor does not host a copy of the catalog scans.

License activation and validation contact the license service. Shopify reads and writes go directly from the desktop app to the Shopify Admin API.

Credentials at rest

Admin API tokens and client secrets are stored locally with device-related encryption when the required cryptography package is available. The app never saves a secret in its source code or installer configuration.

Saved stores are not auto-selected when the app opens. You choose the store before a task can run.

Some operations cannot be fully restored

Recoverable updates keep original values. New metafields can be deleted during rollback. Permanent deletion and cascading operations are labeled as irreversible or snapshot-only. The app does not claim it can recreate every deleted Shopify resource.

Read the recovery guide →
  • ! The app runs on your computer, so tasks stop when the computer is shut down.
  • ! Large CSV files use standard batched mutations, not Shopify Bulk Operations.
  • ! Image tools update ALT text and filenames. They do not compress, crop, scale, or convert images.
  • ! Product creation from CSV keeps a snapshot but does not promise a complete automatic rollback.
  • ! Some analysis tasks require read_orders. YouTube migration also requires yt-dlp on the local machine.

Check the recovery rules before a large run

The backup guide explains rollback, redo, store matching, and operations that cannot be fully restored.