Losing store data with no backup to return to
An Egyptian merchant bulk-deletes products or orders by mistake, or imports a file that wrecks prices, then discovers there is no saved backup in /dashboard/backup to return to. The result is hours of manual re-entry and orders that can no longer be traced.
Why this happens
Because backups are an always-postponed chore: Vareons has no automatic schedule for tenant backups, so the merchant relies on memory, runs bulk deletes and imports without a precautionary snapshot, and never opens the backup history until data is already gone.
What Vareons does about it
Vareons puts recovery tools in the merchant's hands at /dashboard/backup: full or partial snapshots across 12 categories (products, orders, customers, coupons, website design and more) with typed confirmation, a detail page per backup with document counts and expandable previews, JSON download and ZIP export, restoration from a saved backup with overwrite or merge (one restore at a time), or restoration from an uploaded file — per the facts registry.
- store.backup.self-service.supported — Self-service store backup: Available
- store.backup.detail.inspection.supported — Per-backup detail inspection: Available
- store.backup.export-restore.supported — ZIP export and restore: Available
- platform.country.egypt — Egypt market focus: Yes
Limitations
No automatic backup will save you if you never back up yourself; overwrite restore deletes the selected categories' current data; product images are outside the backup; and the page is gated by subscription and backup permissions.
Last verified: 2026-09-20