Skip to content

Backups and exports: your data is yours, so keep your own copy and test the restore

A cloud POS backs up for you, but a vendor’s backup is not the same as your copy. A monthly export of products, customers, sales and invoices, stored where you control it, is the cheapest insurance in the business.

By Wameed field teamOnboarding and support

6 min read

In short: protect your business data at three levels:the vendor’s backups (a cloud POS keeps its own, which is not your copy),your own scheduled exports (products, customers, sales, invoices, stock, books) stored in a place you control, andlocal device backups where a till keeps a local database. Exportmonthly at least, keeptwo copies in two places,encrypt them,test a restore twice a year, take afull export before any change of system, and make sure you can leave with your data. Wameed lets you export your own data at no charge; ask any vendor the same question. Not legal advice; confirm retention duties with your accountant.

“We have backups” is a sentence that should be followed by “and we tested a restore.”

What can go wrong

EventWhat a backup protects against
Hardware failureA dead till or disk
Accidental deletionSomeone deletes a product list
Ransomware or malwareEncrypted or corrupted data
Fire, flood, theftLoss of the premises
Vendor failureThe provider stops or restricts access
A bad import or bulk editPrices overwritten across the catalogue
A dispute or auditYou need old records
Changing systemsYou must take your history with you

Who backs up what

LayerWhoNotes
Cloud platform dataThe vendorAsk how often, how long kept, where, how restored
Local database on a tillThe app and youLocal backups protect offline work; a terminal that breaks must not lose unsynced sales
Your exportsYouThe copy you control
Accounting dataYou and your accountantBooks, VAT returns, attachments
DocumentsYouContracts, licences, IDs

Do not outsource the whole question to the vendor.

What to export

DatasetFormatHow often
Products and prices (with barcodes, cost, tax category)CSV/ExcelMonthly, and before bulk edits
Customers (with consent)CSVMonthly
Sales and invoices (XML and PDF)XML/PDF/CSVMonthly or daily if you can automate
Inventory (stock levels, movements)CSVMonthly
Suppliers and purchase ordersCSVQuarterly
Staff and payrollCSV/PDFPer payroll
Accounting booksExport/PDFMonthly close
Settings (roles, taxes, hardware)Screenshots or exportAfter changes

Wameed supports export of structured data in standard formats so you can take your information with you; you pay no fee to export your own data.

The 3-2-1 idea

  • 3 copies of important data (the live one plus two backups),
  • 2 different places (for example a company cloud drive and an external disk),
  • 1 off-site (not in the shop).

Good enough for a small business, simple to explain.

Schedule

WhenTask
DailyCheck the platform’s status; confirm the till synced
WeeklyExport sales if you want a short cycle
MonthlyFull export set; store and label by month
QuarterlyOpen a sample file to verify it is readable
Twice a yearRestore test
Before any system changeFull export, verified

Put these in a calendar with an owner.

Store it safely

  • Encrypt files that hold personal data. Seecustomer data and PDPL.
  • Restrict access to owners and finance.
  • Use a business account rather than a personal one.
  • Name files consistently (2026-11-sales.csv).
  • Do not email unencrypted exports.
  • Remove old copies according to your retention policy.
  • Keep a record of where backups are and who has access.

Test the restore

A backup you have not restored is a hope.

  1. Open a recent export and check it has the right rows and columns.
  2. Try an import into a test environment, or at least a spreadsheet, and compare counts with the live system.
  3. Check invoices: open a handful of XML/PDF files.
  4. Time it: how long would it take to rebuild? That is your recovery time.
  5. Write the steps down.

Offline devices and local backups

Tills that keep a local database should back it up regularly, verify it and rotate old copies. They must not lose a sale made offline if the device fails before syncing: keep the device charged and online as soon as practicable. Seehow offline works andPOS downtime procedures.

Before you change vendors

  1. Export everything while you still have access: products, customers, sales, invoices, books, settings.
  2. Verify the export.
  3. Keep it for the retention period. Seeinvoice archive and retention.
  4. Ask the old vendor how long they retain your data after you leave, and how to request deletion.
  5. Revoke ZATCA device certificates you no longer use. SeeFatoora portal guide.

Seemigrating POS systems andcontract traps.

Questions to ask any vendor

  1. How often do you back up my data, and how long do you keep it?
  2. Where is it stored, and is it encrypted?
  3. How do I export my data, in which formats, and is there a fee?
  4. What happens to my data if I stop paying?
  5. How quickly can you restore a deletion?
  6. Can I get a copy of my invoices (XML) in bulk?
  7. What is your disaster recovery plan?

Mistakes to avoid

  • Assuming the cloud means you need no copy.
  • Backups on the same device as the data.
  • Never testing a restore.
  • Exports left on a personal laptop.
  • No export before leaving a vendor.
  • Unencrypted files in email.

Frequently asked questions

Do I need my own backup if I use a cloud POS?

Yes, an export you control protects you against vendor failure and lets you change systems.

How often should I export?

Monthly at least; weekly or daily for sales if you can automate it.

Does exporting cost anything?

In Wameed, no; you can export your own data without charge.

What is the most important export?

Invoices (XML and PDF) and your books, because of the retention duty.

  • #النسخ الاحتياطي
  • #تصدير بيانات المحل
  • #استعادة البيانات
  • #ملكية البيانات
  • #POS backup
  • #export data
  • #data ownership

Share this article

Ask about your own shop

Thirty minutes on your products, your tax setup and your hardware — not a slide deck.

Keep reading