PrestaShop module · version 1.8.0
EU Withdrawal Manager connects online withdrawal requests to a traceable returns and RMA-like process for registered and guest customers—without pretending to execute the payment refund.
Product decision
The customer sees the selected scope and must make an explicit statement before EUWM creates a withdrawal request.
Fit and limits
Good fit
Not a fit or not yet verified
Why this module exists
Directive (EU) 2023/2673 amended the Consumer Rights Directive and inserted Article 11a. It establishes an online withdrawal function framework for covered consumer distance contracts concluded through an online interface where a withdrawal right exists.
Member States were required to apply national measures from 19 June 2026. Merchants still need to check the rules that apply in each market and contract.
EU Withdrawal Manager implements a tested online withdrawal workflow in supported PrestaShop environments. It supports the operational sequence; it does not decide whether a particular contract is covered or execute the payment-provider refund.
Read the regulatory backgroundArticle 11a defines the customer statement, distinct confirmation and durable acknowledgement framework.
An affected store must connect the customer-facing function to orders, records, notifications and merchant follow-up.
EUWM also supports total and partial product or quantity selection. Partial selection is not a universal Article 11a interface requirement.
Four verified workflows
Each scenario used a deterministic synthetic order, the real front-office flow, persisted records, acknowledgement and Back Office visibility.
Verified runtime scenario
The registered customer selects the complete eligible quantity and receives a durable acknowledgement.
This verified scenario remains documented without loading a missing or non-English image.
Merchant workflow
EUWM keeps history and actor context as the request moves from submission to return, review, economic follow-up and completion.
requestedCreated by the confirmed customer submissionwaiting_returnEmployee starts the return stagecancellation_requestedCustomer asks to cancel an open casereceivedEmployee records physical receiptreviewingEmployee opens inspectionacceptedEmployee records the inspection decisionrejectedEmployee records a rejected outcomerefund_pendingEconomic result awaits external actioncompletedEmployee confirms the final economic resultcancelledApproved cancellation closes the caseexpiredDeadline processing closes an eligible waiting caseA boundary that builds trust
What EUWM does
What happens outside EUWM
Operational coverage
Capabilities are stated at their verified boundary, including what was not automated.
Synchronous HTML and text templates with recorded delivery attempts.
German, English, Spanish, French, Italian, Dutch, Polish and Portuguese.
Blank and prefilled forms. A PDF does not submit a withdrawal.
Tested in the documented two-shop lab topology.
Pack item and quantity behavior covered by functional evidence.
Exact selected eligible quantities remain part of the case.
Data and privacy facts
No whole-product GDPR conclusion is made. The merchant remains responsible for lawful use, privacy information, retention and handling data-subject requests in its own context.
They hold order/shop links, identity and declaration snapshots, selected products and quantities, states, timestamps, notifications, incidents, stock and refund evidence.
The raw token is stored in the PrestaShop cookie; only its hash is stored in the database. Temporary access and rate-limit data is short-lived.
PDFs are generated in memory and streamed. Back Office CSV exports are streamed rather than retained as module files.
Closed-record retention is 2–20 years per shop, with a six-year default. The default is not a universal statutory period.
Cron anonymizes eligible terminal records only after the chosen period. Holds, open incidents, pending refunds and missing terminal dates block the action.
Export covers selected module data. Deletion conditionally anonymizes eligible records; it does not mean every record is immediately deleted.
Uninstall removes active integration and temporary security data while preserving historical requests and economic evidence.
No customer withdrawal payload was found in external HTTP clients. Licensing and updates communicate installation and merchant technical metadata only.
5 published English captures
The approved plan is 14 English and 14 Spanish screenshots. Five English captures are currently approved and published here; the remaining captures are not presented as public evidence until the real localized assets and publication review are complete.
FO-001 · Front office
A guest starts with the order email and reference. Real EUWM UI with synthetic data; PrestaShop 8.2.7, EUWM 1.8.0 RC, captured 2026-08-30.
Select the image to open a viewport-fitted preview.
Compatibility · tested 2026-08-30
EU Withdrawal Manager is designed and developed to cover PrestaShop 1.6.x–9.x. The current verified release and test evidence covers PrestaShop 8.x, with exact evidence on 8.2.7. Additional version releases are being validated and are not presented as verified.
| Layer | Version | Result |
|---|---|---|
| PrestaShop | 8.x | Available · verified |
| Release evidence | 8.2.7 | Exact runtime verified |
| PHP | 8.1.33 | Exact runtime verified |
| Database | MySQL 8.0.46 | Exact runtime verified |
| PrestaShop | 1.6.x–1.7.x | Target · tests/releases pending |
| PrestaShop | 9.x | Target · tests/release pending |
| Database | MariaDB | Target · test pending |
Product lifecycle
Documentation is available for technical evaluation. Changelog publication remains tied to signed package records rather than an inferred release history.
Fit questions
Answers stay within the verified product and commercial policy boundaries.
EU Withdrawal Manager 1.8.0 is currently available and verified for PrestaShop 8.x. The exact release-evidence runtime is PrestaShop 8.2.7, PHP 8.1.33 and MySQL 8.0.46. Coverage from PrestaShop 1.6.x through 9.x is a target; the remaining branches need refactoring, tests and their own releases before they can be shown as verified.
Yes. Registered total, registered partial, guest total and guest partial scenarios all passed with deterministic synthetic orders.
Yes. Total and partial requests were verified. Partial behavior is limited to selected eligible products and quantities.
Shop-scoped multistore isolation and Pack item and quantity handling passed in the tested lab topology. This does not generalize compatibility beyond that evidence.
No. EUWM records stock and credit-slip consequences and lets an employee record the result of a refund executed outside the module. It does not call a payment provider, bank or card API.
The audited version contains thirteen synchronous HTML and text notification families in German, English, Spanish, French, Italian, Dutch, Polish and Portuguese. Authorized blank and prefilled PDF forms are available, but a PDF does not submit a withdrawal and no automatic post-submission attachment was verified.
The current policy is a perpetual licence for one production installation and one shared non-production or staging installation. Multistore is included within the licensed installation, with perpetual update entitlement.
Six months of support covers installation, configuration, use and reproducible EUWM defects. It excludes customization, third-party modules, hosting or server work, and general store maintenance. No public SLA is offered.
Product documentation is linked from this page. The public changelog remains gated until entries are signed and mapped to identifiable packages; documentation alone does not open checkout.
No. EU Withdrawal Manager 1.8.0 is available for the verified PrestaShop 8.x product scope, but this site keeps checkout closed until the independent release, legal, commercial and operational sales gates all pass. No checkout-opening date is published.
Version 1.8.0 · sales unavailable
Use the documentation and real evidence to decide technical fit. If the verified workflow does not match, define one new bounded PrestaShop addon instead.