BulkGauge copies your catalogue data every night, encrypts it before it leaves your store, and keeps it where you choose. When you restore, you see every change first — including the ones that cannot be made, and why.
Products and variants, metafields and metaobjects, collections, pages, blogs and navigation, inventory levels, discounts and price rules, and theme settings data.
Products cannot be excluded from a copy. Every other type references them, and a copy without them cannot be restored from.
or weekly, or manual. At an hour you choose, in your store's timezone.
restore points on Growth. 7 on Core, 90 on Scale and Compliance.
of encrypted storage included per store — Core’s 7 restore points fit inside it. Then 40¢ a GB.
to restore. However many times, however large the job.
There is no API that returns a store to an earlier moment. BulkGauge writes your saved values back through the same API any app uses, which means a restore has four outcomes per object — and you read all four before anything is written.
The product still exists. Its saved values are written back, and the job can be undone from Jobs like any other.
The product was deleted. It comes back as a new product with a new ID, which cannot be undone.
Nothing in the backup differs from what is in your store now, so nothing is touched.
Shopify refuses the write — a gift card, a handle another product now uses, a value it rejects. Named on its row, with the reason.
Never copied and never restorable. Shopify has no way to write an order back.
Not copied. Customer records and their consent state stay in Shopify only.
Liquid and assets. Shopify's own theme versioning covers those.
Anything another app keeps in its own database is outside this backup.
This is the same list you see before you configure your first backup, and it is on the Backups page afterwards. A merchant who learns it during a real emergency has been failed by the product, not by the platform.
We ask Google or Dropbox for permission to one folder. There is no field anywhere in BulkGauge for a storage password or a broad-scope API key.
Both consequences are on screen before the choice, and the second one has to be typed out rather than ticked.
No, and we do not call it one. It covers catalogue data — products, variants, metafields, collections, pages, navigation, inventory levels, discounts and theme settings. Orders, customers, theme code and other apps' data are not in it.
$9 per store per month on any paid plan, including 2 GB of encrypted storage for that store — enough for the 7 restore points Core keeps. Above that it is 40¢ per GB, charged on the period's peak. Writing to your own Drive or Dropbox removes the per-GB part. Restores are never charged.
You are emailed and the Backups page states the cause in the first sentence, the age of your newest usable restore point, and the two actions that fix it. A backup product that fails silently is worse than no backup, so nothing about a failed run is hidden behind a link.
Yes. The preview lists every object with its outcome and exports to CSV, and you can restore a scope rather than the whole point. What you cannot do is restore selectively without seeing the list first.
No. That is the point of holding it yourself: we never receive it, so there is nothing for support to look up, reset or verify. If that is a risk you would rather not carry, let us hold the key — restore then always works.
Not immediately. Scheduled runs stop that night, your restore points stay readable and downloadable for 30 days, then they are deleted. The charge ends with the current period.