Order Archive for OpenCart — archive old orders without losing their history

Order Archive for OpenCart is a module for stores that have collected tens of thousands of orders over the years. Standard OpenCart keeps all orders in the same tables: every list, search, filter and counter in the admin header goes through both fresh orders and those completed three years ago. Deleting old orders is not an option: customers open them in their account, accounting needs reports, and returns and CRM need the history.

The module moves old completed orders to separate archive tables and makes sure OpenCart “does not notice”: the customer still sees all his orders in the account, the order page and invoice open in the admin, and reports still count archived orders. Any change to an archived order — a new status, a payment callback, a status from a CRM — first brings it back to the store. The module does not touch the OpenCart core, templates or OCMOD patches.

Running WooCommerce? There is a separate Order Archive for WooCommerce plugin with the same approach: old orders go into a compressed archive, reports and customer totals stay the same, search and one-click restore.

What the customer sees

Nothing changes for the customer. He opens “Order History” and sees all his orders — new ones and three-year-old ones — in one list, in the same order and with the same pages. He opens an old order and sees the products, totals, addresses and status history. “Reorder” puts the product into the cart, “Return” opens the return form filled with the order data.

The archive does not affect new orders: the standard checkout and One Page Checkout work as usual, and new order numbers continue after the archived ones.

What the admin gets

An “Order archive” item in the “Sales” menu with three tabs.

Overview

How many orders are in the store and in the archive, table sizes, the oldest order in the store. The rules are written in plain words (“Orders placed more than 24 months ago, in the statuses Complete, Canceled, not changed for 90 days”). “How many would go now?” counts the candidates, “Archive now” moves them step by step with progress — the run can be stopped at any time. Below are “Optimize tables” (gives the freed space back to the disk after the first big run) and the log: what was archived or restored, when and by whom.

Archive

Search by order ID, customer, e-mail, phone, date and status. An archived order can be viewed and printed without restoring it. “Restore” brings one order back to the store, “Restore selected” and “Restore all found” — a group. In Pro the found orders can be exported to CSV right here.

The standard order list

The Sales > Orders list stays as it was and shows only the orders in the store — that is why it is fast. When you filter the list (by customer, order ID, e-mail, status), a line appears under it: “The archive has N more orders that match this filter.” with a link to them.

Settings

• Rules: order age in months (24 by default), the statuses that may be archived (by default — the store’s “complete” statuses), how many days the order has not changed (90), the batch size.
• Safeguards: keep orders with downloads in the store; do not archive orders with a return changed within the last N days (180); how many days a restored order stays in the store (90).
• Compatibility: customer account, admin order page, reports, the line under the order list, “restore when opened”, dashboard counters — each layer is switched on separately.
• Pro: schedule, unfinished checkouts, final deletion.

How it works — step by step

1. Install. The module creates archive tables with the same structure as the order tables of your store (order, order_product, order_option, order_total, order_history, order_voucher; plus order_custom_field in 2.3). Columns added by other modules are picked up by the archive before every run.
2. Choosing candidates. Orders older than N months, in the selected statuses and not changed for N days. Never archived: the newest order, orders with a subscription or recurring payment, with a sold gift voucher, with downloads (a setting), with a recent return, recently restored from the archive, and those a CatCode module is still working on: a queued Nova Poshta waybill, an unsent KeyCRM / SalesDrive / KeepinCRM sync, an unfinished PRRO receipt, an open Returns & Exchanges request, an unchecked payment in Payment Status Sync.
3. Moving. In steps of 200 orders (configurable). Every step is one transaction: the rows are copied to the archive, the counts are compared for every table, and only then the rows are deleted from the store. If they do not match, the whole step is rolled back.
4. Reading. When OpenCart looks up one order through its models (account, order page, invoice, modules that read orders the standard way) and does not find it in the store, the module repeats the same query in the archive. The account list merges both sources with correct paging, reports read the store and the archive together.
5. Changing. Any attempt to change an archived order through OpenCart (a new status, editing, an invoice number, deletion), as well as a Multi PRRO refund receipt and actions on a Returns & Exchanges request, first brings it back to the store. A restored order stays in the store for 90 days.
6. Restoring by hand. From the “Archive” tab — one, selected or all found; the rows come back exactly as they were.

Under the hood

• No core edits and no OCMOD. OpenCart events only: order models in the account, checkout and admin, reports, the order list, the order page.
• The archive is a copy of the structure, not a new format. The cc_oarch_* tables are created with CREATE TABLE … LIKE, so a row in the archive is the same order row, and a restore is an exact copy back.
• Transactions and locks. Every archiving or restore step is one InnoDB transaction and one named database lock, so scheduled archiving and a manual restore never overlap.
• Reports. While a report model runs, the order tables are replaced with “store + archive”; on the dashboard — only with a separate switch, so the admin home page stays fast.
• What stays in place: customer transactions and reward points, coupon history (coupon limits still count old orders), returns, gift vouchers, subscriptions, tables of other modules.
• Honest about the limits. Modules by other developers that read the order table with their own SQL do not see archived orders — that is why only long-completed orders go to the archive, and the admin order page by default brings an archived order back to the store. A status changed in KeyCRM for an order that is already in the archive is not applied until the order is restored. The storefront “Bestsellers” block counts only the orders in the store. Reports that also read the archive run slower than before archiving (measurements are in the FAQ).

How to install

1. Download the archive for your version: cc_orderarchive.ocmod.zip (OpenCart 4.x), cc_orderarchive-oc3.ocmod.zip (3.x) or cc_orderarchive-oc2.ocmod.zip (2.3).
2. OpenCart 4 and 3: Extensions > Installer > “Upload”. OpenCart 2.3: copy the contents of the upload/ folder from the archive to the store root.
3. Extensions > Extensions > Modules > CatCode Order Archive > “Install”.
4. Open Sales > “Order archive” > “Settings”, check the rules and statuses, save.
5. On the “Overview” tab press “How many would go now?”, then “Archive now”. Run the first big archiving at a quiet hour, and “Optimize tables” after it.