From the start the project had a clear business goal and a demanding timeline. Based on the client’s needs we prepared a detailed functional specification, agreed the integration scope, and signed a contract to deliver the solution. One of the most important assumptions was fast delivery while keeping compatibility with different PrestaShop versions and ease of use for both the store owner and their customers.
The module was delivered on schedule and covered the entire returns process — from configuring rules in the admin panel, through the customer form and product verification, to email communication and integration with the easyreturn.eu API.
The biggest project challenge was combining advanced returns logic with native PrestaShop mechanisms so the solution would be simple to configure and usable by stores running on different platform versions.
The module was designed for PrestaShop 1.7–9, and its architecture accounted for multilingual stores and multistore environments. A key part of the work was using standard PrestaShop mechanisms — admin forms, order statuses, hooks, product data, categories, and order history — instead of building parallel mechanisms independent of the platform
The project scope covered both the admin side and the customer-facing store interface. The administrator can define core returns parameters such as the withdrawal period, refund deadline, returns address, return reasons, or automatic order status changes. Configuration is split into clear tabs so that even with many options, managing the module stays transparent.
On the customer side we built a complete return request flow — for logged-in users and for people submitting a request without logging in. The system identifies the order, verifies whether a return is allowed, presents products with photos and variants, and calculates an estimated refund amount.
An important part of the solution was also integration with the easyreturn.eu API. The module communicates with the external service, among other things to obtain a unique installation ID and to check whether the relevant returns button or process can be shown to the user. The project also handles situations where API communication is temporarily unavailable.