PRESTASHOP EXPERTS
PrestaShop audit and repair: what to do when your online shop suddenly stops working and you lose orders
PrestaShop potrafi działać stabilnie przez miesiące, dopóki hosting po cichu nie zmieni wersji interpretera PHP, a zewnętrzny moduł kurierski nie zablokuje kasy po nocnej aktualizacji. Kiedy w koszyku sypią się błędy, próby nerwowego klikania w panelu czy instalowania kolejnych modułów-łatek zazwyczaj tylko pogarszają sprawę. Usunięcie awarii wymaga przejścia ścieżki eliminacji: od logów serwera, przez weryfikację nadpisań w kodzie, aż po porządki w bazie danych.
When a restart doesn’t help: what a comprehensive check looks at PrestaShop audit?
Simply rectifying the effects of a fault restores normal operations, but rarely eliminates the root cause of the problem. If the shop has structural flaws, the fault will recur during the next promotion or product range update.
One of the main problems that arises after the shop has been running for several years is the presence of override files in the /override/classes/ and /override/controllers/ directories. Various plugins attempt to modify the same core file (often Cart.php, Order.php or Product.php) at the same time. This results in methods being overwritten, data being lost and random errors when calculating discounts. An audit allows you to resolve these conflicts and move the modifications to standard hooks.
The second bottleneck is the database. Tables containing connection logs (ps_connections), referring page statistics or abandoned shopping baskets can reach sizes of over a dozen gigabytes. The database becomes bloated, a single SELECT query locks the entire table, and the server’s response time (TTFB) increases dramatically. We discuss the detailed mechanisms behind this phenomenon in our article on why a PrestaShop shop runs slowly.
During the audit, we also check the integrity of files for malware. Out-of-date plug-ins are often the target of malware attacks – scripts are embedded in them to alter account numbers in traditional bank transfer modules or to steal data from forms.
Disruptions in the wholesale sector – the specific nature of errors in PrestaShop B2B
In retail (B2C), a shop being unavailable means the loss of a few transactions from individual customers. In wholesale, the consequences are incomparably greater. Platforms based on PrestaShop B2B process complex trading rules:
- assigning individual discount grids to customer groups,
- verification of tax identification numbers (NIP) in the VIES/GUS databases,
- trade credit limits and deferred payment terms,
- Hiding stock levels and prices from business partners who have not activated their accounts.
A system failure in a B2B environment usually affects the automated integration of the shop with the ERP system (Comarch ERP Optima, Subiekt GT or Symplex Small Business). When the integration system stops synchronising data, discrepancies in stock levels arise. The goods appear in the shop, a customer places an order for a pallet of products, but the stock is missing from the physical warehouse. In such systems, an audit of the stability of the data exchange modules is crucial for the continuity of sales.
Call
+48 575 330 370
Years of experience
Regular customers
Frequently asked questions about PrestaShop audits and repairs
How much does a PrestaShop audit cost?
It depends on the scope – a quick diagnosis of a single shopping basket fault is quite different from a full technical audit of a shop that has been operating for several years, with dozens of modules and code overwrites. We provide a quote following an initial review of the logs and the shop’s current status.
How long does it take to fix a PrestaShop shop?
A simple module error or conflict during checkout can often be fixed within a few hours. More serious issues – such as a corrupted database, multiple overwrites of the core files, or a file infection – require work on a test environment spread over several days, to avoid causing another failure whilst fixing the previous one.
Technical support and repair at 4AD Studio
When resolving faults, we work directly on the test environment: we back up the data, reproduce the error using the logs, implement a fix in the code and test the entire order flow. Only once the solution has been verified is it deployed to the production server.
In addition to ad hoc maintenance interventions, we carry out the day-to-day administration of PrestaShop shops. This includes regular log checks, engine updates in a controlled environment and database optimisation, which helps to eliminate faults before they affect the shop’s conversion rate.
If your shop is experiencing errors following an update, the shopping basket is not processing payments, or the platform requires a technical audit, please contact us – we will analyse the logs and implement the necessary fixes.