Our work on an existing PrestaShop store covered upgrades, module maintenance and sales in two additional languages. The central challenge was keeping catalogues, prices and stock consistent across a BaseLinker integration and a multistore setup. The project combined configuration, custom scripts and follow-up support after launch.

Taking over an existing store and planning updates

The shop sold board games and accessories. It used multiple extensions, while the new language versions needed shared sales data. Before expanding the setup, we reviewed its modules and disabled agreed features that were no longer needed. The work also covered PrestaShop and extension updates.

An update to one integration module caused a conflict, so we restored that extension to its previous version. The remaining agreed updates and module changes were carried out. Supporting an existing store requires examining dependencies between the platform, extensions and external integrations.

Multistore and shared data

English and German versions were prepared on separate domains within a multistore setup. Deployment involved configuring data sharing in the store group and transferring existing elements. Some content belonged to individual modules and therefore needed explicit assignment to the additional stores.

Stock records became an important part of the work when the sharing model changed. We restored the appropriate data from a backup and adjusted its assignment to the store group. We also corrected data associations related to BaseLinker imports. The solution had to match the store’s shared catalogue and inventory model.

The deployment checklist also covered menus, footer content, checkout messages, additional product tabs and available payment methods. Acceptance therefore involved the purchasing journey as well as the new domains.

Currencies and price synchronisation

We added EUR and USD alongside PLN, with a currency selector in the header. Daily exchange-rate updates and agreed price-rounding rules were configured. We also adjusted the header so language and currency controls worked alongside the other navigation elements.

Follow-up support addressed discrepancies between prices in the Polish store and the other sales contexts. We implemented recurring propagation of price changes from the Polish version. This was a separate maintenance issue handled after the language versions had launched.

AI translation and specialist terminology

We prepared a ChatGPT-based script for translating products, categories and attributes. A deployed schedule ran the translation process daily, while a cache of existing translations helped limit repeated processing.

Board game terminology needed particular attention. A Polish word for gaming dice can be translated in the wrong context even when the resulting sentence reads fluently. Our work included refining translation instructions and the approach to rerunning selected content. Store-side editorial review remains part of this workflow.

The outcome and the role of support

The delivered scope combined additional language versions, currencies, translation automation and corrected shared data. The work history also includes subsequent integration and price-update requests. It illustrates PrestaShop support in which configuration, custom code and verification are closely connected.

Facing a similar multistore, module or synchronisation issue? Explore our PrestaShop support service and PrestaShop multistore payments and shipping guide. Describe the symptoms in the form below so we can discuss a practical scope.

View online
AI - sztuczna inteligencja, Baselinker, Laravel, PHP, PrestaShop
Project date:  September, 2025
Cooperation date:  July, 2025
Back