What we build

Websites

Company websites and B2B platforms on WordPress or custom builds, with design, audits and speed optimisation.

Website development →

What we run

SEO

Visibility in Google and in language models. One team looks after search, your business profile and what ChatGPT and Gemini say about your brand.

Search engine optimisation →

What we run

Advertising and campaigns

Campaigns judged on net profit after returns and cost of goods, not on the ROAS in the ad platform. Creative is made in-house, so it never waits for a third supplier.

Digital marketing agency →

What we run

Analytics and data

Measurement first, decisions second. Ad, store and warehouse data in one place, so a budget conversation takes fifteen minutes, not three meetings.

Web analytics for e-commerce →
Home/Services/E-commerce//Post-launch care

PrestaShop maintenance and developer support

PrestaShop store maintenance is ongoing care for what's already selling: updates, backups, monitoring and technical support. On top of that, a pool of development hours and a response time written into the contract. Unused hours don't carry over to the next month, so we size the package to your real pace of work and adjust it as we go.

Store care: monitoring, updates, backups PrestaShop Expert ★★★ 24/7 uptime monitoring
Trusted by
Technology partners
Starting point

What happens to a store after launch, once nobody's watching it?

Three situations where store owners call JustIdea for the first time. In each one, the store loses time first: catching up on a year of backlog takes 2-4 weeks before you can even get back to actual development.

Updates put off for later

The PrestaShop core, modules and PHP version drift apart over a year to the point where updating stops being a click and becomes a project. The longer you wait, the more the same move costs.

A ticket with nowhere to go

The store stops accepting payments on a Saturday, and the contractor who built it doesn't answer, because the project ended a year ago. Finding someone who knows that code costs more than the fix itself.

A budget spent only on putting out fires

Money for the store goes on outages, and the list of changes that would grow sales slips another quarter. After a year the store still works and hasn't moved an inch.

Definition

What is developer care and technical support for a PrestaShop store?

Post-launch care is an agreement covering two things at once: technical maintenance of what already works, and a pool of hours for what needs to change. Maintenance covers updates, backups, monitoring and a response time to outages written in as an SLA. You spend the development hours where you decide, not wherever the ticket queue happens to put them.

Maintenance and updates

PrestaShop core and module updates, backups with recovery tested in practice, uptime and response-time monitoring.

SLA, meaning a contracted response time

An outage stopping sales has a different priority from a typo in a product description. That distinction sits in the contract, so it's never up for negotiation on the day something breaks.

A pool of hours for development

Hours you spend on changes that grow sales. You see the usage in the monthly summary, and unused hours don't carry over, so we size the package to your pace of work.

Scope

Hour packages, updates and SLA

  • ✓ Package 5H: 1h maintenance plus 4h development, €320 net a month
  • ✓ Package 10H: maintenance plus 9h development, Custom quote
  • ✓ Package 20H: weekly store checks plus 16h development, Custom quote
  • ✓ Package 30H: weekly store checks plus 26h development, Custom quote
  • ✓ A developer version of the PrestaShop store and a shared ActiveCollab project
How it works, step by step

From taking over the store to ongoing technical support

Five stages. The first four happen once, the fifth runs for as long as the store keeps selling.

  1. 1

    Handover and stock-take

    1-2 weeks

    Access, backups, an inventory of PrestaShop modules and modifications, a risk assessment. Ends with a list of things that need fixing before we start developing anything.

  2. 2

    Setting up the development environment

    a few days

    We set up a developer version of the store, a copy where every change and update is checked before it reaches production. You have access to it, so you see a change before it goes live, not after.

  3. 3

    Connecting monitoring tools

    a few days

    On the 20H and 30H packages, we connect the store to tools that watch uptime, errors and response time. An alert about a problem reaches us before a customer notices it in the basket.

  4. 4

    Clearing the backlog

    2-4 weeks

    Updates tested on the developer version, and backups with a trial restore. This phase ends with a store where you know exactly what happens after an outage.

  5. 5

    A steady monthly rhythm

    ongoing work

    Maintenance plus a development hours pool, billed monthly. You set the priorities, and you see unused hours in the summary.

Service boundaries

How is post-launch care different from an audit and from hosting?

Short answer

Care is a standing pool of hours for fixes, updates and development, with a response time in the contract. An audit is a one-off diagnosis, and hosting is server upkeep at a provider. Care carries out what the audit listed, on the server that hosting maintains.

The package can change along the way, and notice is two months. Unused hours don't carry over, which is why we size the package to your real pace of work and adjust it when that pace changes.

A standing pool of hours with a contracted response time, between a one-off audit and server upkeep

This is the right service

  • The store is alive: promotions, new modules, updates, integrations.
  • You don't have a developer who knows PrestaShop, or you only have one.
  • You want a response time to tickets written into the contract.

Start somewhere else

  • You want a one-off diagnosis with no commitment: that's a technical audit.
  • The problem is the server, not the code: that's PrestaShop hosting.
  • You have a large build to deliver: that's a dedicated solution, quoted separately.
What happens without a ticket

What you're paying for in a month with no tickets

The most common complaint about a retainer is: you didn't do anything, though. A large part of PrestaShop store maintenance happens with no ticket filed, and its absence only shows on the day something breaks. Below are four things that run in the background.

A test environment stands ready the whole time

A copy of the PrestaShop store where we check every change before it goes live. It's what keeps a module update from being an experiment on a live basket, and it costs the same regardless of how many tickets come in.

Keeping the core and modules current

PrestaShop and module releases don't arrive when you happen to have time for them. We check what's come out, what's a security patch and what needs testing first, and tell you what's worth deploying now.

Regular store checks

A review of error logs, response times and integrations that have started throwing exceptions. Most outages start quietly weeks earlier, and that's the point where catching them is cheapest.

Access to someone who knows your store

A ticket goes to the team that built these integrations, not into a queue. The difference is the time you don't spend bringing someone up to speed on the project before anyone can even start fixing it.

What's covered by the retainer and what's billed separately

Included: work on your store

Tickets, fixes, small development work, updates tested on a copy first, and a regular review of errors and performance. All counted in hours from your chosen pool. Tickets go through a task system, so you see in real time how many hours have gone where.

Included: a test environment

A copy of the store where we check changes before production stands ready the whole time and is maintained from the package. It's what keeps a module update from being an experiment on a live basket. Setting it up at the start of the engagement is sometimes a separate, one-off line item.

Not included: hosting and licences

The server and paid modules are your own agreements with providers, and you pay them directly. We do this deliberately: access stays on your side, and changing agency doesn't mean moving the store. Configuring and maintaining these things is covered by the package hours.

Not included: new builds

A new integration, a basket rebuild, a custom module. These are projects with their own scope and their own quote, because trying to squeeze them into a retainer ends either in blown hours or a deadline that keeps slipping. We quote them after a brief, as fixed-scope work.

How the SLA and response time work

We respond to a ticket within 24 hours on working days, and that's a commitment, not a statement of good intentions. Outages blocking sales take priority over everything else, and we respond faster to those. If you need a guaranteed response outside working hours, we set that separately in the contract.

Included: performance optimisation and new features

Development hours go on whatever you decide: new panel features, purchase-path fixes, PrestaShop store performance optimisation measured by load time and Core Web Vitals, or implementing technical SEO recommendations from an audit. For every change we say whether it touches conversion, and report it in the monthly summary. That's how the development pool doesn't just disappear into fixes alone.

Included: ERP integrations and version updates

A PrestaShop store rarely runs alone: it talks to an ERP system, to base., to carriers and to a payment gateway. Keeping those connections running is covered by the package, because that's where a critical error shows up after a change on someone else's side, needing a same-day response. We plan migrations to a new PrestaShop release ahead of time and test them on a copy. An update within the same version fits inside the package hours, while moving to a new release that requires rewriting modules is quoted as a separate project.

The other side

Security, performance and integrations: what breaks when nobody's watching

A store without care doesn't break suddenly. It breaks slowly, over a year or more, and the bill arrives all at once.

„The platform version stops being supported”

Every skipped release raises the cost of the one you'll have to install eventually anyway. After two or three years, an update stops being an update and becomes a build project, because modules and changes made along the way need rewriting too.

„Known holes stay open”

Module vulnerabilities get published so they can be patched, but the same publication is a set of instructions for bots hunting for stores without the patch. A compromised store usually doesn't vanish: it gets a redirect visible only to search engines, so the problem only surfaces once rankings drop.

„Integrations go quiet one by one”

Providers change their interfaces, and an unmaintained integration stops answering some requests without flagging it anywhere. The gap surfaces at stocktaking or during a complaint, meaning it's already a commercial problem, not a technical one.

„There's no backup you can actually restore from”

Backups usually exist, nobody's ever tried restoring the store from them. Checking takes one afternoon, and not checking costs a full day of downtime on the day the file turns out incomplete or too old.

Other services

Neighbouring services: audit, hosting and builds

A store is several layers at once: catalogue, technology, visibility and measurement. Post-launch care touches one of them, so below are the neighbouring pages, in case the problem sits a floor further along.

PrestaShop technical audit

A PrestaShop store technical audit: server, modules, code, performance and security.

View ›

PrestaShop hosting

PrestaShop doesn't charge a platform subscription, but it still needs somewhere to run.

View ›

Dedicated solutions

Dedicated e-commerce solutions for an online store: ERP and CRM integrations, custom modules and online sales automation built around your process.

View ›
Reviews of working with us

What clients whose PrestaShop stores we run say

Ars Longa has standing care and feature development with us, exactly this service. CENTROBUD and BioOrganika work with us on the same platform.

„
JustIdea is a company that always finds a solution to a problem.
Daniel TurkowiakArs Longa, publishing and online sales
„
If you're after the lowest price, you'll probably find it cheaper elsewhere, but here it's simply solid. I've been working with them for over 1.5 years and have no plans to change that.
Dominik GrochCENTROBUD, building materials and installations
„
JustIdea agency built us an online store that not only fully met our expectations but is also a benchmark for our competitors.
Adrian KomenderskiBioOrganika, natural cosmetics
Client reviews

Ratings for the agency you're trusting with your store for months at a time

A monthly retainer has the property that it's easy to tick the box and have nobody notice for half a year. Before you sign, see how clients rate working with JustIdea as a whole.

4.96 / 5

weighted average of 224 reviews across three platforms. Clients gave them, and each site below links to the profile with the full text of every review.

Read the reviews
Certifications and partnerships

Statuses that shorten the route to PrestaShop's maker

A retainer only makes sense if there's somewhere to ask when something goes wrong. Below are the statuses that decide how quickly we find out whether a fix is ours to make or the platform's.

PrestaShop Expert ★★★

PrestaShop, agency programme

The top tier of the agency programme gives us a route to report core bugs and knowledge of upcoming release requirements. That stops a store update from being a leap into the dark once a quarter.

Top E-commerce Developers Kraków 2026

Clutch, e-commerce developer ranking

A ranking of e-commerce developers. Care is the service clients judge after months, not after a week, and Clutch verifies every review with a call to the author.

base. (BaseLinker)

BaseLinker, integration partnership

Maintenance tickets are most often about integrations, since that's where something changes on someone else's side. This integration partnership gives us support on base.'s side, instead of waiting in a general queue.

Doubts before you commit

Four doubts we hear before signing

Each one is about money or time, and each is answered by the contract, not a promise.

„We're paying for hours we won't use”

Unused hours don't carry over to the next month, and we say so before you sign. That's why we size the package to your real pace of work, and you can scale it down along the way if it turns out too big.

„We already have our own developer”

Great, then care is backup for holidays, outages and PrestaShop updates that one person can't safely do alone. Some clients take the smallest package specifically as that safety net, not as a substitute for a hire.

„An outage on a Friday evening and nobody picks up”

On working days we respond within 24 hours, and for an outage blocking sales we react the same day. Coverage outside working hours is set in the contract, instead of promising an on-call rota we couldn't actually keep.

„We are wary of a long commitment”

The notice period is two months, and the package can change along the way. You stay because the tickets get handled, not because the contract says so.

FAQ

PrestaShop developer care: questions before you decide

How much does PrestaShop store maintenance cost?

Packages start from €320 net a month for 5 hours. Larger packages, up to 30 hours with weekly store checks, get a custom quote once we know your real pace of changes, since size follows from how often the store changes, not from its turnover.

Do unused hours carry over to the next month?

No, and we say so plainly instead of burying it in the terms. That's why we size the package to your real pace of work, and it can be adjusted along the way if it turns out too big or too small.

How do tickets get logged, and what's the response time?

Through a shared ActiveCollab project, where you see the status and time spent on every task. On working days we respond within 24 hours, that's our SLA in the contract, and the 20H and 30H packages add a weekly store check.

What happens if more hours are used in a month than the package covers?

The overage is billed at a rate tied to your package, and it's lower the larger the package. We flag an overage before it happens, so the decision to keep going is yours, not the invoice's.

Can I change the package along the way?

Yes, it can move in either direction and doesn't require rewriting the whole contract. A sensible order is to start smaller, watch real hour usage for two or three months, and only then pick the right size.

What's the notice period for care?

Two months, counted to the end of a calendar month. Access, code and documentation are yours throughout the engagement, so leaving doesn't mean recovering or buying anything back.

Let's size the package to how fast your store changes

On the call we work out how many changes you genuinely make in a month and what needs tidying up at the start. That gives us the package size, which you can change later if it turns out too big or too small.

A technical audit report with recommendations ordered by priority and a three-year store TCO calculation
Book a call about care 2-month notice, counted to the end of the month.
Contact

A conversation about your numbers: 30 minutes

The call is led by a new business specialist. When we get into the details of an account, the specialist for that channel joins in. We reply within one business day.

A quick review of your tracking and campaignsThree priorities for the next quarterA written summary that stays with you

Before the meeting we review your website, your visibility and what your campaigns show from the outside. We will not open with “so, what does your company do?”.

4.96 224 reviews
By sending the form you agree to the processing of your data in line with our Privacy Policy.

What happens after you send it
01
within 1 business day

We reply to your email

The reply comes from the same new business specialist who will run the call. No qualification form and no call from an unknown number.

02
this week

A 30-minute conversation

We go through your numbers and your questions. If it turns out we are not the right fit, we will tell you straight away.