The online withdrawal form for your PrestaShop shop

Article L.221-21 of the French Consumer Code and decree D.221-5 require the trader to provide an online withdrawal feature, and to send the consumer without delay an acknowledgement of receipt on a durable medium. The obligation applies since 19 June 2026.

Three things must therefore exist on the shop: a visible and unambiguous entry point, a form that records the request, and a proof of receipt sent to the customer. An e-mail address in the legal notice fulfils none of the three.

The customer fills in the form: name, postal address, e-mail, order reference, and the scope of the withdrawal, the whole order or some of the items. Nothing is final at this first step: a second screen restates the declaration, and the confirmation click is the withdrawal. That date is the one recorded, in the shop's time zone.

The acknowledgement leaves at once by e-mail, with the declaration attached as a PDF, and the shop receives its copy. If sending fails, the withdrawal remains valid: the customer keeps the reference on screen and the shop is warned.

The module can match the order reference with the e-mail entered. If the match fails, the request is saved anyway and marked "to check". A guest order, an address changed since, a reference copied with a typo: none of this can prevent a right from being exercised.

A honeypot field and a limit of five submissions per hour and per IP address keep bots away without bothering a real customer. The confirmation link is an unguessable token, valid for 30 days by default.

Requests have their page under Customer Service > LNK Withdrawal, with the common skin of the LNK modules:

• the list, filtered by status with the count of each filter (to confirm, confirmed, accepted, refused, refunded, to check), a search by reference, name or e-mail, and the number of requests in progress;
• the request detail: customer, order, scope, the exact declaration confirmed by the customer, the acknowledgement (date, reference, IP address, browser) and the timestamped log of every step;
• the actions: change the status, noted in the log with the employee's name, and send the acknowledgement again to the customer.

A button exports the requests of the current filter to CSV, ready for a spreadsheet. They are personal data, so the export is framed:

• it requires the edit permission on the page, a read permission is not enough;
• every export is written to the PrestaShop log, with the employee, the filter and the number of requests;
• cells starting with =, +, - or @ are neutralised: a text typed in the form cannot become a formula in the spreadsheet.

Settings are grouped in sections: button and journey (labels in each language, colour), location (footer, customer account), acknowledgement (template, sender, copy to the shop), periods and retention. On the right, a live preview shows the button, the form and the confirmation page while you type, on desktop or mobile, and enlarges to full width.

The entry point goes where you want: a button in the footer, a link in a column of the official "Link list" module, or nowhere if you place it yourself. A link is also added to the customer account. The acknowledgement uses the module template or your shop's e-mail theme.

Tables are not dropped on uninstall: a withdrawal request is evidence, it must survive the removal of a piece of software. Conversely, an automatic purge deletes, log included, the requests older than the chosen period (60 months by default, the commercial limitation period; 0 to purge nothing). A confirmed request still awaiting your decision is never purged.

Figures measured on the shipped module, gzip compressed (level 9). A 1.0 KB stylesheet for the button and the form, loaded on the shop pages since the button can appear in the footer of each of them. A 0.66 KB script, loaded only on the form and confirmation pages. No font added, no external resource.

Every version is verified by a real installation: PrestaShop 8.1 for the 3.1.N archive, PrestaShop 9.0 for the 3.9.N archive. The tests cover installation, back office and uninstallation.