Cleanup Revolution removes obsolete PrestaShop records, orphaned images and unused files from one maintenance centre. Installation adds the workspace to your back office; the first removal preview takes one click.
Abandoned carts, guest records, old visit data and module leftovers accumulate as a shop runs. They enlarge backups and occupy hosting space long after their original purpose ends.
You set retention periods, a row ceiling per run and scheduled cleanup. Every cleaner starts with a preview, and removed images stay recoverable in dated trash for your chosen period. Orders, invoices and paying customers are protected; accounts without orders require separate double confirmation before removal.
Before-and-after sizes and a history of each run show which cleanup reclaimed space, giving routine maintenance a measurable outcome.
Cleanup Revolution is the maintenance centre of a PrestaShop store: it measures what has accumulated, removes what is ballast and proves what it did. Six features combine cleanup, safeguards, reporting and scheduled maintenance in the back office.
The cleaners cover what actually grows: abandoned carts and their orphaned lines, guest records, connection logs with their sources and visited pages, system and mail logs, search and page statistics, page-not-found entries, expired vouchers with nothing left to redeem, and closed customer messages. Each type has its own retention period in days, and each shows a live count of removable rows before any run.
Orders, invoices and paying customers are structurally out of reach: no cleaner touches them. Accounts without a single order, guest or registered, are handled separately and disappear only after a double confirmation, so a commercial record never falls to a routine cleanup.
The image scan walks the product, category, brand and supplier folders and reports files that no record points to. A second report groups images with pixel-identical content and states how much space the copies waste, and a third lists records whose file is missing, so a broken product photo is found before a customer finds it. Removed images go into a dated trash first, restorable for the retention period you set and emptied only afterwards.
On the file side the module clears temporary and regenerated working files, import remainders and old log files, and inventories module folders: genuinely uninstalled modules are removable under guard, while anything ambiguous is only reported. Duplicate products by name, reference or barcode number, duplicate categories and duplicate attribute names get their own diagnostic screen, linked back to the affected records.
Every cleaner runs as a preview first: it counts and lists what would be removed, and actual deletion is a deliberate second step. Runs respect a configured batch size and one row ceiling for the whole run, images go to the trash instead of oblivion, and a master switch halts every cleanup path at once.
The history records each preview and each execution with operator, affected rows, freed space and outcome, including failures. When a hosting bill or an auditor asks what happened to the data, the answer is a report, not a shrug.
The dashboard shows the database's total size, its largest tables and the space tables reserve but no longer use. After a cleanup the module compacts those tables, so deleted rows turn into disk space the host actually gives back, and the health screen watches fragmentation, cleanable rows, leftover module code and disk capacity in one place.
The result is measurable rather than felt: the merchant sees the size before, the size after, and which tables account for the difference.
Yes. The database routine, the file cleanup and the maintenance tasks run on a schedule you define, with a run-now button for testing and an email report after each run or as a daily digest, so the cleanup you approved in month one is still happening in month twelve.
Setup ends at installation: the module lives entirely in the back office, changes nothing on the storefront and nothing in the theme, and speaks six interface languages. The store a customer sees is exactly the store they saw before, only running on a lighter base.
Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.
30 days return right
Plug & Play Modules
Dedicated Support First
Built and maintained by David Miller and mypresta.rocks. David Miller has worked with PrestaShop since 2013, and the company behind this shop has been registered since 3 December 2018. Every module in this catalogue is our own work, so your questions to support reach the people who wrote the code. The changelog on this page lists every update with its date.
Cleanup Revolution removes database clutter, orphaned images, duplicates and unused files, and Performance Revolution makes what remains fast with Redis, page and fragment caching and asset optimization. Clean first, then accelerate.
Cleanup Revolution clears out unused files and module leftovers, and Security Revolution guards the rest with a firewall, file integrity checks and vulnerability alerts. A smaller footprint is a safer one.
Cleanup Revolution finds orphaned and duplicate images and unused files, and SEO Revolution makes sure the pages you keep are crawled and described well, with sitemaps, canonical control and image alt text. A tidy catalogue and a well-indexed one go together.
Compliance & Legal
News & Updates
News & Updates
News & Updates
News & Updates
News & Updates
