Undo the mistake.
Keep the rest of the day.
Lowcora Backup keeps an encrypted, versioned copy of your Shopify store. When a bulk import goes wrong or a collection disappears, go back to the moment before, see every field that will change, and restore only that. Images, variants, collections and channels come with it.
Each one has a precise fix, not a full rollback.
Every price in a collection is now 10× lower
Lowcora Backup flags that 42 products changed at once and shows a summary of the altered fields. You pick the version from before the import and restore prices only. Descriptions edited since stay as they are.
Field-level restoreA collection and its 80 products are gone
Deleted records stay listed under Recover deleted, with their images, variants, collections, channels and stock. Select them, read the summary, start. They come back as new records with new IDs.
Recover deletedMenus, pages and metaobjects changed overnight
Choose the data types and a moment in time. The nearest earlier version of each record is used; anything created after that moment is left alone. Review, then rewind.
Rewind to a momentSee everything that changed, the moment it changes.
One feed for the whole store: what was added, what was edited, what was deleted and when. 300 products disappear overnight, 40 get removed by an import, prices change on a Friday afternoon. It shows up with the time, the data type and how it was caught. Filter by day, type or kind of change, and open any record to see its versions and bring one back.
| When | What happened | Record |
|---|---|---|
| Today 14:12 | Deleted | 312 products Products |
| Today 09:40 | Changed | Linen Shirt, Blue Products · price |
| Yesterday 23:05 | Changed | Summer Sale Collections |
| Yesterday 11:30 | Added | Gift Wrap Products |
| Mon 16:48 | Deleted | About us Pages |
The whole catalog and the content around it.
Every night, and a few minutes after products, collections, customers or orders change. Each record keeps its own version history. Media is stored once and shared between versions, so a 2 GB catalog does not become 60 GB of backups.
| Data | Backed up | Restored |
|---|---|---|
| Products, variants, images, video, metafields | Yes | Yes |
| Sales channel publications | Yes | Yes for deleted products |
| Inventory levels | Yes | Yes automatic for deleted products, optional otherwise |
| Collections and manual memberships | Yes | Yes |
| Pages, blogs, articles, menus, redirects | Yes | Yes |
| Metaobjects and definitions, files, translations | Yes | Yes |
| Customers, addresses, marketing consent | Yes | Yes passwords are never stored |
| Themes | Yes | Not yet |
| Discounts with all codes, store policies | Yes | Yes usage counts start fresh |
| Orders, draft orders | Yes downloadable | No |
| Gift cards, shipping profiles, Markets, selling plans, store settings | Yes downloadable | No |
Nothing is written until you have read the summary.
Records, a version, or a moment
Open Recover deleted and select what disappeared. Or rewind chosen data types to before a given time. Or open one product's history and pick a version.
Every field that will change
A side-by-side, word-level diff per record: what will be recreated, what will be changed, what is identical. Limit a product restore to prices, content, status or metafields.
Backup, restore, undo
Your store is backed up again before anything is written. If that backup fails, nothing is written. Every restore has an Undo that returns updated records to how they were right before.
Every change for a week, then thinned the way an archive is.
A backup is only worth what it refuses to do.
Isolation between stores, encryption that belongs to each store, and a restore path that stops itself when something looks wrong.
What cannot be restored
- Orders, draft orders, gift cards, shipping, Markets, selling plans: stored and downloadable, never written back. A recreated order would corrupt accounting and stock.
- Restored records receive new IDs. Apps that referenced the old ID may need a look.
- Restored discounts start with a fresh usage count. App-generated discounts are not restored.
- Themes are backed up and downloadable, but cannot be restored yet.
- Customer passwords, analytics, checkout and payment settings, other apps' data: outside the vault.
One key per store
Backups and media are encrypted with AES-256-GCM using a key that belongs to your store alone. Each file is bound to its path, so a record cannot be moved into another store's vault.
Tenant isolation
Every query is scoped to the store in the session. Another store's record, version or restore job returns nothing.
Mass deletions wait for you
If 10 or more records and at least half of a type vanish in one backup, it is flagged NEEDS_REVIEW. Nothing is marked deleted on an incomplete or failed sync.
Media from Shopify only
Files are fetched only from Shopify's own domains, with a size limit. Webhook signatures are verified. Access tokens and sessions are encrypted at rest.
Your own second copy
A weekly ZIP of each data type to your S3 bucket or Google Drive. Drive access is limited to files the app creates. Credentials are stored under your store key.
GDPR by default
Customer redaction removes the customer, listed orders, all versions and files. Uninstalling destroys the key first, then the data. A full activity log lives in Settings.
One screen for every store you look after.
A store owner links your agency email in Settings and can remove it at any time. You see backup status, record counts and storage for each linked store. You never see content and cannot start a restore.
Stores linked to the same agency can be copied into one another: products, collections, pages, metaobjects and more, created as new records. Stock, channels and customers stay where they are.
Simple monthly plans. Prices in USD.
- 25 GB backup storage
- 365 days of history
- Nightly and change-triggered backups
- Recover deleted, rewind, field-level restore
- Weekly copy to S3 or Google Drive
- 100 GB backup storage
- 365 days of history
- Everything in Starter
- Agency access and store-to-store copy
- Storefront monitoring every 10 minutes
- 500 GB backup storage
- 365 days of history
- Everything in Growth
- Choose your nightly backup hour
- Priority support
Going over the order or storage limit never stops backups. You are asked to upgrade; protection continues.
Before you need a restore.
How often are backups taken?
Every night, and a few minutes after products, collections, customers or orders change. You can also start a backup of one data type by hand.
What happens if I delete products by mistake?
Open Recover deleted, select them, review the summary and start. Images, variants, collections and sales channels come back. Inventory levels are restored automatically for deleted products.
Do restored products keep their IDs?
No. Shopify gives recreated records new IDs, so apps linked to the old ID may need checking. Updated records keep their IDs.
Can I get my data out?
Yes. Download any data type as JSONL, or as a ZIP with images. Or let the app send a weekly ZIP to your own S3 bucket or Google Drive.
Where is the data stored?
On servers in the EU, encrypted at rest with a key that belongs to your store. Uninstalling the app destroys the key first, then the data.
Which languages does the app speak?
English, German and Turkish, inside your Shopify admin.
Install it before the day you need it.
The first full backup runs right after install. The Getting started page walks you through a test restore on a product of your choice.