Delete Orders: setup and help

1. Upload and install the module ZIP in Modules > Module Manager.
2. Open Delete Orders > Configure.
3. Check Enable and leave Require confirmation on, then click Save.
4. On a backed-up test shop, open a disposable order and find the Delete Order panel.
5. Click Move to Trash and confirm on the module confirmation page.
6. Open Deleted Orders and confirm the audit row, then verify that the original test order is absent.

Open Modules > Module Manager > Delete Orders > Configure. In Delete Orders Settings, both options default to Yes.

Click Save. The server checks Enable and Require confirmation before removing an order, including requests sent directly to the admin action. Order removal requires a POST request, a valid admin token, delete permission and authorization for the order. Disabling confirmation skips the extra confirmation step when using the panel button.

Use a backed-up test shop for your first check. Open a disposable order detail page. The module renders through displayAdminOrderMain on newer order pages and displayAdminOrder for the legacy layout. Find Delete Order, click Move to Trash, and confirm if prompted.

For an existing order, the action attempts to save an audit record and delete the original order. It does not keep a complete restorable copy in separate storage.

The module checks the audit insert, order deletion and transaction commit, and reports success only after the commit succeeds. It requires InnoDB for the orders and trash tables and attempts a rollback if an operation fails. After a test, check that the original order is gone and that the trash row exists.

The module makes no payment-provider refund call and sends no customer notification itself. It does not reverse payments or provide a full accounting reversal. Keep a database backup if you need recovery.

Open Deleted Orders in the module menu. You can inspect and filter these columns:

The audit snapshot contains id_order, reference, id_customer, total_paid from the tax-inclusive order total, date_add, and current_state. It does not include all order lines, addresses, payment records, or the data needed for complete restoration. There is no restore action.

Use a row's Delete action to permanently remove that audit record, or select rows and use Permanently delete selected to remove them together. Both actions require a valid admin token, delete permission and authorization for all shops. They remove audit records, not additional orders.

To inspect recent records with a read-only query, replace ps_ with your database prefix:

SELECT id_trash, id_order, order_reference, deleted_by, date_deleted
FROM ps_mprdeleteorders_trash
ORDER BY date_deleted DESC
LIMIT 50;

The table stores order_data as LONGTEXT, an order reference up to 16 characters, and an index on id_order.

The module's integrity page checks feature enablement, confirmation, the trash table, backlog, and missing reference or payload data. It offers repair actions to enable the feature, enable confirmation, or recreate a missing trash table. Recreating the table does not recover deleted audit records or orders.

If the panel is absent, check Enable, the order ID, hook rendering, module installation, and employee access to the module page. If the list or action fails, check the trash table and database errors. Keep access to this admin page limited to employees who should remove orders. The action checks delete permission and whether the employee may modify the selected order. If removal fails, also check confirmation, the admin token and InnoDB storage for both the orders and trash tables.

After a test, verify the actual order and audit row. Audit insertion and order deletion run in one transaction; a failure triggers a rollback attempt. Use module diagnostics and PrestaShop logs to investigate failures, including rollback failures.

The module has no storefront output. Your verification happens in the Back Office and database.

The button uses views/templates/hook/delete-button.tpl. It receives mprdelo_trash_url and mprdelo_id_order. Keep the POST form, the hidden trash_order field and the generated admin URL when customizing it. The server handles the confirmation step with views/templates/admin/confirm-trash.tpl.

Set Enable to No and save to block order removal and hide the order-page panel. Uninstall from Module Manager to remove module settings and menu entries. Uninstall retains the trash table, as stated in the confirmation prompt. Back up the table if you need the audit history. Uninstall does not restore deleted orders.

Requires PrestaShop 1.6 or later and PHP 7.1 or later. The orders table and module trash table must both use InnoDB.