Skip to content

Backups

Recorded as you work, swept again every night.

Two mechanisms, because one is not enough. Events catch changes within seconds; the nightly sweep catches the ones BigCommerce never announces.

Overview

Last verified backup

4min ago

Products12,480
Variants31,902
Categories612
Orders88,104

Real time by webhook, plus a full sweep at 00:00 store time.

  1. 01

    A change lands

    BigCommerce sends an event carrying an id and nothing else, so every event is followed by a read of the real record.

  2. 02

    We hash it

    The fetched record is content-hashed and compared with the last version we hold. Identical means nothing is written.

  3. 03

    Changed records are versioned

    A new version is stored with its field-level difference, which is what makes a preview possible later.

  4. 04

    A nightly sweep checks the rest

    BigCommerce does not emit an event for every inline edit. A full sweep at midnight store time is the backstop, not an extra.

When our endpoint fails

BigCommerce tells us when deliveries to our side start failing. We subscribe to that, and we show it: the dashboard says your backup is stale and how long it has been. A backup tool that cannot tell you it has stopped working is worse than none, because you stop checking.

What is kept

Every version, for 365 days, on every plan.

  • Products, variants and SKUs
  • Product and variant images
  • Inventory levels
  • Bulk pricing rules
  • Custom fields and metafields
  • Modifiers and complex rules (V3)
  • Option sets (V2)
  • Categories and category images
  • Brands
  • Customers and addresses
  • Orders and transactions
  • Price lists and records
  • Product reviews
  • Pages and blog posts
  • 301 redirects
  • Gift certificates
  • Stencil themes

What cannot be

Not an oversight and not a roadmap item — the BigCommerce API does not expose these, so no backup app can reach them. You should know before you buy, not after you need them.

Blueprint themes

No API exists for them at all.

Store settings and shipping

Not exposed for writing.

Script tags

Owned by the apps that created them.

Page-builder widget edits

Theme configuration is readable, never writable.

Shared variant options

No endpoint.

V2 option-set complex rules

We can back these up. BigCommerce cannot take them back.

Digital product files

Not retrievable.

Third-party app data

Lives in those apps, not your store.

Multi-storefront resources

Not covered by the APIs we are given.