Scope of work
What I can take on
- 01 I diagnose 500 errors, blank pages and problems after a store update.
- 02 I fix order placement, payment confirmation and status changes in the checkout process.
- 03 After a breach I remove the attacker's leftover access, restore operation and secure the store.
- 04 I assess the state of an abandoned project and set out a plan to finish it.
- 05 I look for conflicts between modules and the causes of errors that occur only in specific situations.
- 06 I explain and fix stock discrepancies between the store and the ERP.
From securing data to a repair plan
Before making changes I back up the files and the database. Then I check the logs, recent deployments and the change history. An initial diagnosis usually identifies the cause and estimates the repair effort within a few hours. On that basis we agree on the next steps.
After sales are restored
Once the failure is fixed, I trace its source and prepare recommendations that reduce the risk of it happening again. You get a summary of what was fixed and a list of further changes, if any are needed.
Practical information
Questions about working together
How soon can you start the diagnosis?
When sales have stopped, I usually pick up the report on the same working day. Clients with a maintenance contract get the agreed response time set out in the SLA.
Will you handle a failure outside PrestaShop?
Yes, I also analyse failures and the aftermath of breaches in other systems. I know PrestaShop best, so diagnosis there is usually faster. With an unfamiliar project, time is needed to understand how it is built.
Can you help without the previous contractor?
Yes, as long as you have access to the hosting and the domain. From the code and the database I can establish the state of the store even if no documentation has survived.
How do you estimate the cost of a repair?
I bill the time spent on the work. A diagnosis usually takes 2 to 4 hours. After it I give an estimated repair cost and wait for your decision on the further scope.