PrestaShop Technical Help

The most common reasons for a ticket: a white screen or 500 error after installing a module, a broken checkout (missing payment methods, an error when placing an order), order confirmation emails that never arrive, a store redirecting to foreign sites after a hack, problems after a core or module update, and performance drops under heavier traffic. If any of these sound familiar, start by collecting information: what stopped working, since when and after which change. That halves the diagnosis time.

The process is always the same: ticket intake with a description and secure access handover → files and database backup → diagnostics on a store copy (logs, debug mode, module isolation) → a report with the cause and a repair plan → the fix → full purchase path tests → preventive recommendations. We do not stop at "fixed" — you get to know what the cause was and how to prevent a repeat. For sales-blocking outages (checkout, the whole store) I work in priority mode.

Included: diagnosis and repair of store, module and theme errors, PrestaShop, module and PHP updates with staging tests, configuration and repair of payments, shipping, emails (SMTP) and integrations, backups and store restoration after a failure, malware removal and hardening after a compromise, a performance and security audit with a report, and minor code and template modifications within an hourly package. Not included (quoted separately): building new modules and store features, entering products and content, rewriting the store from scratch, and changes that require a project and a multi-week delivery.

An ad-hoc fix of one problem (up to 1 hour of work): 200–600 PLN net. Diagnostics with a report and a repair plan: 500–1,500 PLN net. Malware removal with hardening: 800–2,500 PLN net. An hourly package for minor work (5 hours): from 900 PLN net. Ongoing store care with an hourly package and a response time: from 400 PLN net per month. Emergency migrations and updates are quoted after analysis. Prices are given up front, after a short scope review — no hidden costs and no billing "by feel".

I split tickets by priority. A sales-blocking outage (the store is down, the checkout is not accepting orders): first response within 4 hours during business hours. Important but non-blocking issues (an error on a subpage, slow performance): up to 1 business day. Planned changes and minor work: up to 2 business days. Tickets come in by email and phone, and you hand over store access via a password manager or a temporary admin account — never by ordinary email.

A single repair makes sense when the store is stable and the problem is rare. If failures return every month, ongoing care is cheaper and safer: updates done on time (before something breaks), backups with a restore test, uptime and security monitoring, and an hourly package for current fixes. Ongoing care also means a predictable budget — instead of paying for every fire separately. We tailor the scope and package to the store size and the pace of change.