PrestaShop support: hours pack or monthly maintenance
Technical support for a PrestaShop store is bought in two ways: a pack of hours that is used up when needed or a monthly maintenance fee. We explain what each one includes, what to ask about response times, what access to give and how, and how to work out how many hours you need.
Technical support for a PrestaShop store is bought in two ways: with an hours pack, which you pay for once and which is used up according to what you ask for, or with a monthly maintenance fee, which covers a fixed set of tasks each month. The pack fits when the work is irregular; the fee, when you want someone to do the same thing every month without having to ask.
Who to hire (a freelance developer, an agency) is a separate decision, which we cover in another article on the blog. This one focuses on the model: what you are buying in each case, what should be included, what to ask before signing and how to start working with a developer without giving them more access than necessary.
What support for a PrestaShop store covers
Under one name or another, the work falls into four blocks:
- Errors. A blank page, a 500 error, a checkout step that fails, an email that does not arrive, a module that stops working after an update.
- Changes. Texts, banners, a new carrier, a payment method, a theme adjustment, a module that needs installing and configuring.
- Updates. PrestaShop, the modules, the theme and the server's PHP version. It is the work nobody asks for and the work that prevents the most problems.
- Emergencies. The store down, a checkout that does not take payment or an intrusion. What matters here is how long it takes to get started.
On top of that comes what is not seen: checking that there are backups and that they can be restored, reviewing error logs and measuring speed before and after each change.
Hours pack: how it works
You buy a package of hours and the developer deducts the time spent on each task. The reasonable thing is for there to be an estimate before each job and, afterwards, a report with what was done and the time spent.
- Pros: you pay only for what you use, it works for any type of task, there is no minimum term and, if nothing happens one month, you spend nothing.
- Cons: if nobody asks for anything, nobody checks anything. Updates and preventive reviews have to be agreed, or they do not get done. And you need to look at the reports to know where the time goes.
What to ask: whether the hours expire, whether there is a minimum usage, how time is counted (minimum increments), whether out-of-hours emergencies are deducted at the same rate and what priority you have over someone without a pack.
Monthly maintenance fee: how it works
You pay a fixed amount each month in exchange for a defined set of tasks: normally updates, backups, monitoring and a number of hours for changes or incidents.
- Pros: the cost is predictable, preventive work gets done without you asking and it usually comes with committed response times.
- Cons: you pay for the quiet months too, the included hours do not always roll over and anything outside the fee is invoiced separately. Some fees come with a minimum term.
What to ask: which specific tasks it includes and how often, how many hours it comes with and whether they roll over, what counts as “outside the fee” and at what price, and whether there is a minimum term.
Comparison table
| Hours pack | Monthly fee | |
|---|---|---|
| How you pay | Once, in advance | Every month |
| Months without incidents | Nothing is spent | You pay all the same |
| Preventive tasks | They have to be agreed | Included by definition |
| Type of work | Any | Whatever the contract says; the rest, separately |
| Spending forecast | Variable, depending on what you ask for | Fixed |
| Fits | Stores with irregular needs or specific projects | Stores that want to delegate the routine completely |
There is a middle ground that works well: an hours pack with an agreed periodic review, monthly or quarterly, which is deducted from the pack itself. You get the preventive work without paying for the months in which nothing is done.
Response times: what to ask
“We respond quickly” is not a commitment. What is worth making clear:
- Response is not resolution. How long they take to reply and get started is one thing, and how long they take to fix it is another. Ask about both.
- What counts as an emergency. A store that is down or payments that do not work, yes; a misplaced banner, no. Having the definition in writing avoids arguments.
- Hours. What happens on a Saturday night or in the middle of a sales campaign, and whether it costs more.
- Channel. Where requests are made (email, ticketing system, phone) and who answers.
- Priority. Whether having a pack or a fee puts you ahead of someone calling for the first time.
What access to give and how
A developer needs access to work, but not yours and not for ever:
- Back office: their own employee account, with their name and email address, not your shared user. That way there is a record of who did what and you can disable it when they finish.
- Files: their own SFTP or SSH account, not the main hosting password.
- Database and hosting control panel: only if the task requires it, and with a separate user when the panel allows it.
- How to send them: never just in an email. Use a password manager or a one-time link, and send the username and the password through different channels.
- When the work is finished: disable the accounts or change the passwords. And ask for the same in return: that they tell you what access they still hold.
If the developer is going to see customer data, and in a store that is unavoidable, there must be a data processing agreement in line with the GDPR.
Working on a copy
Changes that could break something (updating PrestaShop or an important module, touching the checkout, changing the PHP version) are tested first on a copy of the store, not on the live one. That copy must be password-protected, not indexed, with email diverted so as not to write to real customers and with payments in test mode. Ask whoever provides your support whether they work this way and who pays for the time to set up the copy. It costs a little more than making changes on the live site, and a good deal less than an afternoon with a broken checkout.
How to work out how many hours you need
- List what is outstanding: known errors, changes you have been meaning to make for months and overdue updates.
- Look at how long it has been since you last updated. An up-to-date store needs little each month; one that has not been touched for two years needs bringing up to date first.
- Count modules and custom code. The more modules and the more changes of your own, the longer each update takes.
- Ask for an estimate per task, not an overall figure. By adding up the estimates you will know which pack makes sense.
- Separate bringing the store up to date from maintenance. The first is a one-off job; the second, the routine that follows.
- Review usage after three months with the reports in hand and adjust.
How to solve it in PrestaShop
At Rekire we work with hours packs, with no monthly fee and no minimum term: PrestaShop maintenance is done with the same pack as fixes and changes. You tell us what you need, or we agree a review every month or every quarter, and we deduct only the time we actually use. The hours do not expire, there is an estimate before we start and a report on every task, and we test first on a copy of your store. We maintain PrestaShop 1.7, 8 and 9.
The price ranges from €38.30 to €50 per hour + VAT depending on the pack. The 20-hour PrestaShop support pack is the entry-level one, with no minimum monthly usage and with priority on incidents over those without a pack; the others are in the PrestaShop technical support section. Telling us what is wrong with the store before it becomes urgent always works out cheaper.
Frequently asked questions
Which is better, an hours pack or a maintenance fee?
It depends on how regular the work is. If you ask for things from time to time, a pack; if you want to delegate the monthly routine completely, a fee. A pack with an agreed periodic review covers both cases.
How much does PrestaShop technical support cost?
It depends on the state of the store and on what you ask for. At Rekire, from €38.30 to €50 per hour + VAT depending on the hours pack you choose.
What access does a PrestaShop developer need?
Normally their own employee account in the back office and an SFTP or SSH account. The database and the hosting control panel, only if the task demands it.
Do the hours in a pack expire?
It depends on who sells it; ask before buying. In Rekire's packs the hours do not expire.