How Bed World recovered 18,359 products after a security incident

What happened

Bed World Online runs one of the larger furniture catalogs on Shopify: more than 18,000 products, each carrying detailed specifications, variant pricing, imagery, and structured metafields built up over years of trading.

On an ordinary trading day, an unauthorised party reached the store admin and deleted the full product catalog along with every collection. With nothing live, product and category pages started returning errors and the storefront was unsellable. Every hour offline meant lost sales and slipping search visibility.

Here is the part most merchants only learn the hard way: Shopify keeps the platform running, but the data inside your store is yours to protect. There is no native way to bring back a product once it has been deleted from the admin, so recovery is only possible from a backup taken before the event. Bed World had installed TinyBackup months earlier, so a clean, complete snapshot from 20 April was already waiting.

How the store was recovered

A full restore was the obvious move, but it was not the safe one. The store had kept trading after 20 April, so writing the whole snapshot back would have overwritten every product edited or added in the two weeks since. That trades one data-loss event for a smaller one. The team used a targeted restore instead.

Two ways to restore

A verified restore point already existed, so the work was recovery, not reconstruction. Here is how it unfolded.

1. 4 May · 13:06
   Incident reported
   The agency flags that all products and collections have been deleted after unauthorised admin access.
2. 4 May · 14:00
   Restore point agreed
   Merchant, agency, and TinyBackup settle on the 20 April snapshot, the last clean capture before the breach.
3. 4 May · 14:09
   Deleted-only restore approved
   Rather than overwrite two weeks of valid edits, the team proposes a deleted-products-only restore. The merchant approves.
4. 4 May · 15:18
   Restoration begins
   The new restore mode goes live and all 18,359 products are queued back into the store.
5. 5 May · 08:00
   Past the halfway mark
   11,879 products are back and visible to shoppers. Shopify's API rate-limits the writes, as expected at this scale, and the restore keeps running.
6. 5 May · 17:08
   Fully restored
   The final product lands. The catalog matches its 20 April state with no active edits lost. Total time from the first message: about 26 hours.

The outcome

The full catalog returned to its 20 April state. Every attribute came back: titles, descriptions, images, variants, pricing, metafields, and SEO fields. No active edits made between 20 April and the incident were lost.

The weeks-versus-hours gap grows with catalog size. Drag the slider to your own store and see what a by-hand rebuild would take.

"Rebuilding the catalog by hand would have taken weeks. Instead we restored the whole store and were trading again the next day. Honestly, next level."Bed World Online, via their Shopify agency

Editor's note: the incident timeline, quotes, and recovery figures shown here are illustrative; confirm the exact details with the merchant before publishing. The business facts below are from Bed World's public store.

Keep your store safe

This incident was unusual in scale, not in kind. Smaller versions happen on Shopify stores every week: a misfiring app, a bad import, a staff member with too much access. Shopify protects the platform; you protect your store data, and TinyBackup makes that effortless. Six habits keep a store recoverable.

• Turn on two-factor authenticationFor every admin and staff account, without exception. Most unauthorised-access incidents trace back to a password with no 2FA.
• Give the narrowest access that worksStaff and agencies rarely need full admin. A marketing role does not need permission to delete products.
• Audit installed apps quarterlyAny app that can write products can also delete them. Remove anything you no longer use, and read the scopes on new ones.
• Run automatic daily backupsManual exports get forgotten precisely when they matter. Keep enough history to survive a late discovery, since incidents are often noticed days later.
• Test a restore before you need itRun a restore on a development store at least quarterly. An untested backup has a habit of surprising you mid-incident.
• Agree your recovery plan in advanceDecide who you contact and which snapshot you choose if something goes wrong. Under pressure, that decision is much harder to make well.

FAQ

About Bed World Online

Bed World Online is a family-run retailer of beds, mattresses, and bedroom furniture, trading for more than 20 years from Osborne Park in Perth, Western Australia. It runs a large, multi-brand catalog on Shopify and holds a 4.9-star Google rating across 387 reviews. The size of that catalog is exactly why a fast, complete restore mattered so much.