PrestaShop expert or agency: what to ask before hiring

Before hiring a PrestaShop expert, developer or agency, ask how they make backups, whether they test changes on a copy of the store before touching the live one, whether they build with modules or by modifying the core, who owns the code and the access, how they alert you to errors and how they charge (bundle of hours or a fee). The answers to those questions say more than any portfolio.

It is not about being suspicious, but about knowing how the person or team who will hold the keys to your business works. These are the questions, grouped by topic, and what you would want to hear.

Backups and test environment

How and how often are backups made?

The sensible answer is a daily backup of files and database, stored off the store's server, and another one just before any major change. Also ask when one was last restored: a backup that has never been tested may not work on the day you need it.

Where are changes tested?

The right answer is «on a copy of your store, before taking them to production». PrestaShop updates, new modules, theme changes: everything goes through a test environment with your data first. If the answer is «we do it directly, carefully», your store is the test environment.

Can that copy write to my customers?

A copy with real email configured can send an email to a real customer with a simple order status change. Anyone who works properly diverts all email from copies to a test mailbox and puts the payment gateways in test mode.

How it is built

Modules or overrides?

PrestaShop lets you change its behaviour in two ways: with modules that hook into the intended points (hooks) or with overrides, which replace parts of the core. Overrides have their place, but each one is a piece that can break with the next update and can clash with another module that touches the same thing. Ask how many overrides your store has and why, and whether new changes will be made as a module.

Is the core or the original theme modified?

Editing PrestaShop core files or the original theme's templates is the quickest way to make a change and the most expensive in the medium term: the next update wipes it out or breaks it. The healthy approach is a child theme for the design and modules for the logic.

How is it documented?

Ask for a change log: what was touched, when and why. Without it, the next technician (or the same one, a year from now) has to rediscover the store.

Ownership and access

• Who owns the custom code? Normally, what is developed for your store should be yours or, at least, you should have the right to use and modify it without depending on whoever wrote it.
• In whose name are the domain, hosting and accounts? Domain, hosting, payment gateways, analytics and app store accounts: all in your name. It is fine for the technician to have access; it is not fine for them to be the holder.
• Does each person log in with their own user? In the back office and on the server, individual access, not a shared account. That way you know who did what and can remove someone's access without changing everything.
• What happens if we stop working together? The reassuring answer is: we hand over access, backups and documentation, and remove our own access.

Errors, alerts and response times

How will I find out if something fails?

Ideally, the technician finds out before you do, and certainly before your customers. Ask whether there is monitoring of errors, of the store's availability and of suspicious changes (new employees, modified files), and who receives those alerts.

How long do you take to respond?

Distinguish between an incident that stops sales (the checkout does not work) and an improvement. Ask for times for each type and what happens at weekends or during campaigns.

Will you tell me beforehand how much it will cost?

For any task that is not routine, an estimate in hours beforehand, and afterwards a breakdown of what was done. No surprises on the invoice.

Experience worth checking

A portfolio of attractive stores says little about how they are maintained on the inside. Better to ask about specific situations:

• Updates and migrations carried out. Have they taken stores from 1.6 or 1.7 to current versions? What broke and how did they solve it? Someone who has really done it describes specific problems, not just that «it went well».
• Versions they work with. That they know PrestaShop 8 and 9, with the PHP versions they require, and not only the version they learnt on.
• A serious incident. Ask them to tell you about an outage or a security problem they had to deal with: what they did first, how long it took and what they changed afterwards so it would not happen again.
• Integrations similar to yours. If you have an ERP, marketplaces or a carrier with its own connection, ask whether they have worked with something similar.
• Modules they maintain. Anyone who publishes and updates their own modules has to keep up with every new PrestaShop version, and that shows when maintaining stores.

Bundle of hours or fixed fee

Neither is better in itself. What matters is that, with either one, there is preventive work (updates, backup checks, monitoring) and not just repairs.

Signs you are on the right track

• They explain changes in language you understand and show you what you can do yourself.
• They say no to things that would harm the store, even if you are paying for them.
• They prefer updating often in small steps to doing it all at once every few years.
• They can tell you at any time which version of PrestaShop, PHP and each module you have.
• They warn you about a problem before a customer tells you.

How we work at Rekire

We are a team that develops its own PrestaShop modules and maintains clients' stores; on the about us page we tell you who we are. We work on a copy of your store before touching production, with email from copies diverted and gateways in test mode. For PrestaShop maintenance and PrestaShop support we work with bundles of hours: the 20-hour bundle for incidents and one-off improvements, and the 50-hour bundle for ongoing support on performance, security and improvements. The hours do not expire and have no minimum monthly usage, clients with a bundle go first in the incident queue, we give you an estimate before starting and only the hours worked are deducted, with a breakdown of each task.

Frequently asked questions

Is a freelance developer or a PrestaShop agency better?

It depends on the size of the store. What matters is that there are backups, a test environment, documentation and someone who responds when that person is not available.

What is a PrestaShop expert?

Someone who knows the core, themes and modules, and knows how to update and debug a store without breaking it. Ask them about updates and migrations they have carried out.

How do I change agency without losing the store?

Make sure the domain, hosting and accounts are in your name, ask for a full backup and the change documentation, and change all passwords when you are done.

How many hours of maintenance does a store need?

It depends on the modules, the integrations and the custom code. The practical approach is to measure for a few months and adjust the bundle or the fee to what is really needed.