PrestaShop repairs and technical support

PRESTADEV / PRESTASHOP SERVICES

PrestaShop technical support covers diagnosing and resolving problems with the store, modules and integrations. At PrestaDev, we start by identifying the cause and the conditions in which an error occurs, so the repair addresses the actual problem.

Describe the problem with your store

When something stops working

Is it impossible to add a product to the cart, is an order not being saved correctly, is the back office displaying an error, or has a module stopped fetching data? The same symptom can have different causes: store code, configuration, the server or an external service. A screenshot of a message is therefore often just the beginning of the diagnosis.

What does the service include?

Errors during purchases

Problems with products, variants, the cart, customer accounts and the steps involved in placing an order.

Modules and integrations

Conflicts, incorrect configuration or faulty data exchange with an external system.

Back office

Errors when saving data, processing orders or using specified back-office features.

Database and server environment

Checking whether the problem relates to data, PHP, hosting configuration or a protection layer such as Cloudflare.

What needs to be agreed separately?

Fixing a specific error does not automatically include rebuilding the store, auditing the entire system's security or ongoing maintenance. If the source of the problem is with the hosting or integration provider, their involvement may be required. We confirm availability and a start date for each request.

How does the work proceed?

  1. Reproduce the problem

    We gather the exact steps, the page URL and the circumstances in which the error occurs.

  2. Identify the cause

    We review logs, configuration and related components. We distinguish the symptom from where the problem originates.

  3. Agree on the repair

    Once the cause is understood, we define the necessary changes and how to make them safely.

  4. Repeat the relevant test

    We return to the reported scenario and check related actions, such as saving an order after completing checkout.

What should you prepare for our discussion?

  • The exact page URL and steps leading to the error.
  • A screenshot or the message text, without customer data.
  • The approximate time of the incident and information about who is affected.
  • A list of recent changes: updates, module installation, or hosting or configuration changes.

Do not send passwords or customer data at the initial stage. We will agree separately on how to provide any necessary access.

What does the quote depend on?

The time needed for diagnosis and repair depends on how reproducible the error is, access to logs, the state of the code and the number of connected systems. A separate support offer describes the possible scope of hourly assistance. Larger problems or additional work require an individual agreement on scope and billing.

How do we verify the completed work?

We tailor acceptance criteria to the agreed scope. For this service, the main checks are:

  • The reported scenario has been repeated and produces the correct result.
  • Relevant cases related to the repair have been checked, rather than only confirming that the message has disappeared.
  • It is clear what was changed and whether any remaining dependencies require action by another provider.

Support after completion, subsequent changes and updates are covered by the terms agreed in the offer for each project.

Questions before getting started

Is sending an error screenshot enough?

A screenshot helps, but it is worth adding the page URL, the steps taken and the time of the incident. If the error is intermittent, these details help match the event to log entries.

Can you fix a problem left by another developer?

We can start by diagnosing the existing solution. Whether and how it can be repaired depends on access to the code, documentation and the store's condition — the work cannot be estimated reliably without a review.

Does technical support include continuous monitoring?

Monitoring is not automatically included in fixing an individual issue. Ongoing maintenance, availability hours and any monitoring arrangements need to be agreed separately.

Let's talk about your store

Tell us what you need help with and the result you want to achieve. You do not need to know the technical solution — let's start with what you need.

Describe the problem with your store