PratikYedek for retail stores
A real scenario
A 3-store clothing retailer in Izmir (anonymised reference: Store-D) suffered an electrical surge at HQ in September 2024 after a lightning strike. The POS PC, without a surge protector, lost its disk. 11 months of POS sales (~42,000 transactions), daily Z-reports and stock-change logs were lost. The New-Generation POS data existed at GİB, but daily management reports (best-selling items, loyalty-card data) were gone.
Root cause: No backups were taken. The assumption "the POS vendor backs us up" was wrong — the contract had no backup clause.
How PratikYedek solves it
- Desktop app on each branch —
POS/data/folder backed up on every branch PC. - HQ consolidation — At 23:30 all branch DB dumps are pulled to the HQ server; PratikYedek backs up everything from a single point.
- Daily stock snapshot — Reference point for stocktake vs. system delta.
- Automatic Z-report backup — New-Generation POS outputs saved as PDF in
Z-Reports/YYYY-MM/→ triggered backup. - Monthly restore drill — A past day's stock dump restored on the manager's PC and cross-checked with the New-Generation POS.
KVKK + VUK alignment
- VUK art. 253: Books and records must be kept 5 years; PratikYedek default audit retention is 5 years with 7-10 years configurable.
- KVKK § 12 (Turkey's GDPR-equivalent): Loyalty-card data (national ID, GSM, date of birth) is PII → AES-256-GCM encrypted backup.
- New-Generation Cash Register Communiqué: GİB transmission is automatic; PratikYedek backs up the local copy and reports (fast access during audits).
Recommended plan
- Single store: Starter (50 GB is enough — POS data is typically 10-20 GB/year)
- Chain of 2-5 branches: Professional (team management + 2FA)
- 5+ branches with a loyalty programme: Enterprise (PII protection for customer data)
FAQ
Does it work with my POS software? Yes. PratikYedek operates at the file/DB level; the POS brand does not matter. MySQL/SQL Server/SQLite/Access dumps are all supported.
Are card numbers backed up? POS systems do not store card numbers (PCI-DSS); only the last 4 digits + auth code. PratikYedek backs up that data as-is.
There is no VPN between branch and HQ. Is that a problem? No. Each branch backs up directly to the PratikYedek cloud via the desktop app; no file transfer to HQ is required. HQ only pulls reports.
Will a power cut at the store corrupt the backup? PratikYedek uploads chunk-by-chunk — it resumes where it left off. A snapshot stays "in-progress" until complete; incomplete snapshots are not exposed.
New-Generation POS data already lives at GİB. Why back it up? GİB stores fiscal records — management reports, customer demographics and product-performance analytics never reach GİB. Those belong to you and only you. Backup is critical for them.