Start with a specific incident
"The site is slow" is not enough to define an intervention. Note a page address, when the problem appears, and the actions that make it possible to reproduce it. If the command fails, specify the step and the message displayed, without attaching bank data.
Make a useful inventory
Gather the PrestaShop version, theme, list of modules, known customizations and external connections. Indicate who manages hosting, domain and backups. Accesses will be transmitted via an agreed channel, never in a public comment.
Define what needs to be preserved
Resumption may concern catalogues, orders, accounts receivable or only one module. Identify expected data and behaviours before encrypting a migration. A working copy allows you to prepare the changes without using the public shop as a trial site.
Agree on the recipe
Check together a representative path: product search, choice of variants, addition to the basket, carrier, authorized test payment and confirmation. Add your particularities, such as professional rates or delivery areas.
The estimate must distinguish diagnosis, correction, online posting and follow-up. Also ask for the conditions to go back if the recipe reveals a problem.
To frame this recovery, consult our PrestaShop support and our Freelance PrestaShop expertise.