Feature docs

Backing up your store data on Vareons

Backups on Vareons live at /dashboard/backup, where the merchant snapshots their own store data — products, orders, customers, coupons, website design, settings and more — then downloads it or restores it later by overwriting current data or merging with it.

Last verified: 2026-09-20

The merchant backup page lives at /dashboard/backup. Access is gated by your subscription (it appears on advanced paid tiers) and by your team permissions: backup.view to view, backup.create to create, and backup.edit to restore and delete.

Four buttons sit at the top of the page: Create Backup opens the creation dialog, Export All Data (ZIP) opens the export dialog, Restore from File opens the upload dialog, and Restore opens the restore-from-history dialog. Below the buttons a stats bar shows backup count, success rate and storage used versus your plan limit, then three tabs: Backups (the history), Settings, and Statistics (charts and database info).

The creation dialog offers four types: full for all selected categories, partial for chosen categories only, incremental for what changed since the last backup, and complete database (every category plus every collection). Twelve categories can be selected: products (with stock, movements, reservations, suppliers), orders (with appointments, bookings, invoices, bills, expenses), customers (with CRM customers, leads, segments), analytics, settings (shipping, loyalty, calendar, locations, notifications), components (the whole website design: layout, global components, static pages, page data), coupons (with bundles), staff (with attendance, leaves, performance, payroll), tracking, finance, content (reviews, QR codes, short links), and logs (off by default).

Before creation a warning appears and a literal typed confirmation is required: "I am sure I want to create a backup" in English and its Arabic equivalent. The snapshot is stored whole inside a Backup document in the database with an integrity checksum, a size, and a default 30-day retention.

The history in the Backups tab shows each backup with its status: pending, in progress, completed, failed (with the error message), restoring, or restored. Each row offers: JSON download (completed backups only), View Details (opens the backup page), delete the backup record, and refresh the list.

The backup detail page at /dashboard/backup/[backupId] shows the document count per category with expandable data previews and an icon per category — the right place to inspect a backup before restoring it.

Restoring from a saved backup runs from the top Restore button: pick a completed backup from the list, choose overwrite (deletes the selected categories' data then inserts the backup rows) or merge (inserts without deleting), pick the categories, then type the confirmation literally. Two restores never run together for the same store. When the components category is restored, the store caches are purged so the restored website shows immediately.

ZIP export downloads every collection as separate JSON files for offline archiving, migration or manual inspection, and creates no history record. Restore from File accepts a ZIP by drag-and-drop: the browser reads its contents, you pick the collections, type the confirmation, and it uploads to the server for restoration — handy when moving between two stores or recovering from an offline copy.

Setup steps in Vareons

  1. Create your first backup from /dashboard/backup

    Open the backup page from the dashboard (you need the backup.create permission), click Create Backup, choose the full type and tick the categories you care about, then type the confirmation literally. The backup appears in history as completed when it succeeds.

  2. Inspect the backup before you need it

    Click View Details on any completed backup to open its page: check the document count per category and expand the previews to confirm your data is really there. Also try the Download button to keep a JSON copy outside the platform.

  3. Export a ZIP for archiving or migration

    Click Export All Data (ZIP) to download every collection as separate JSON files. Keep the file somewhere safe: it works as an archive, or as input for the Restore from File dialog when moving between two stores.

  4. Restore carefully: overwrite or merge

    Click the top Restore button, pick a completed backup and the wanted categories, then decide: overwrite deletes those categories' current data first, merge adds without deleting. Type the confirmation, and remember that restoring the website design updates your storefront immediately.

Frequently asked questions

Where is the backup page?

In the merchant dashboard at /dashboard/backup. If you cannot see it, check your subscription (it appears on advanced tiers) and the backup.view permission on your team account.

Does restoring delete my current data?

Only if you choose overwrite: it deletes the selected categories' data then inserts the backup rows. Merge adds without deleting. Either way a literal typed confirmation is required before anything runs.

Are product images included in the backup?

No. The backup stores database records (and image references) while binary files stay in media storage. A restore does not re-upload images.

Are backups automatic or manual?

Manual, merchant-triggered from the backup page — there is no tenant auto-backup schedule. The Settings tab shows automation and retention options but currently keeps them as local UI state only.

The Restore item in the row menu does nothing — what should I do?

That is a known gap: the row menu Restore item is not wired. Use the top Restore button in the page header to open the restore-from-history dialog.

Troubleshooting

Backup failed? 1) Open history and read the error message on the failed backup. 2) Narrow the selected categories (try a partial backup with one category) then retry. 3) Refresh the list to confirm the final status before any restore. Restore did not change the website? 1) Confirm the components category was among the restored categories. 2) Reload the storefront after the restore finishes (cache purge should have run automatically). Search shows old products after restore? 1) The search index can lag behind the database; wait for the index sync then search again.

Important limitations

• The page is gated by subscription (advanced tiers) and backup.view/create/edit permissions. • No automatic schedule for tenant backups; backups are manual from the page, and the Settings tab is local UI state not saved to the server. • The row menu Restore item is not wired — use the top Restore button. • Product images and binary files are outside the backup (they stay in media storage). • The search index can lag after a product restore until the index syncs. • Default retention is 30 days; only one restore per store at a time.

Related links

تواصل معنا على واتساب