Order Editor changes products, prices, addresses, delivery and payments directly on a placed PrestaShop order. Installation adds the editor to each order page with no configuration needed before the first correction.
A wrong size or street needs a correction without rebuilding the whole sale. The editor recalculates totals and keeps related records together, while the order timeline preserves the original and changed values.
You enable operation types separately, require reasons and enforce staff permissions. Unsafe address structures are refused; shipped or tracked orders require acknowledgement and a reason. Partial refunds remain within the refundable balance and produce a credit slip. A customer update email is optional.
When a manager asks why an order total changed, its timeline identifies the edit, the employee and the recorded explanation.
Order Editor turns a placed order from a frozen record into a governed, auditable working document.
Everything the order is made of. Products are added, removed, requantified and repriced, with totals recalculated. The carrier, the shipping cost and the tracking number change in place. Payments and discounts are adjusted, the status moves through the native history, invoice number and dates are corrected, an internal note holds the context, and the invoice PDF is one click away.
The bigger levers are there too: the order moves to a different customer with cart and address ownership carried along safely, the reference is renamed with its payment records following, and the currency is corrected when an order was placed in the wrong one. When a whole order needs re-doing for a new buyer, duplication creates a reviewed copy, with the customer, addresses and carrier chosen deliberately before anything is saved.
Because the change is one transaction or no change at all. The order, the cart and the dependent delivery records update together, with every address field available, name, company, street, postcode, city, country, region, tax number, phone. When the module meets a structure it cannot update reliably, split carts, inconsistent ownership, multiple shipment records, it refuses and says why, instead of writing half a change.
Orders that already shipped or carry tracking demand more: an explicit acknowledgement and a written reason before anything moves. The parcel that would have gone to the old address is the whole point of that friction.
The refund workspace shows what is refundable, what was already refunded, and the remaining balance, and everything staff enter is checked against those ceilings twice, in the editor and again on the server. Quantities per line, partial line amounts, shipping in full or in part: the combination is free, the limit is not.
Each refund ends in a proper credit slip and a recorded, reasoned event with its context, so the books agree with the parcel that came back, and no order is ever refunded past what remains on it.
The order carries its own memory. Every edit is recorded with before and after values, the staff member or system that made it, the reason given and the source, and the result is a filterable timeline on the order, merged with the native status history. A dashboard adds the wider picture: how many edits, on how many orders, by which editors, of which types.
The customer is part of the loop when you want them to be. One choice in the editor sends a single clear email in the order's language: what changed, item by item, and the new total. The support ticket asking why the total moved never gets opened, because the answer arrived first.
With policy, not trust. Each operation family has its own switch, customer changes, address changes, carrier changes, discounts, product additions, so a shop that wants support to fix addresses but never touch prices configures exactly that. A reason requirement turns every sensitive change into an explained change, and the server enforces both the switches and the employee's own view and edit permissions on every request, so the rules hold even against a hand-crafted call.
The editor speaks the language of your admin panel, works on the order page where staff already are, and adds nothing to the storefront: shoppers never see it, and the shop's speed never pays for it.
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.
Order Editor lets your team change products, shipping, discounts and customer details on an existing order with a full audit trail, and Advanced Order Workflow routes orders between teams with internal comments and real-time notifications. The right person fixes the order, and everyone can see what changed.
Compliance & Legal
News & Updates
News & Updates
News & Updates
News & Updates
News & Updates
