You have PrestaShop clients. They ask you for support, maintenance or sometimes a recovery after an incident. You don’t want to recruit a dedicated resource yet. White‑label PrestaShop fills that gap — provided you frame it as a concrete working mode.
The question is not whether to outsource, but how to operate the offer daily: who speaks to the client, how tickets are raised, which accesses to open, what to include in your package, what to exclude, and how to keep a margin without promising unrealistic response times.
By the end of this article you’ll have a simple protocol to launch a white‑label PrestaShop support or maintenance offer with a pilot client, with no ambiguity on confidentiality, GDPR, billing or handover.
White‑label PrestaShop must be framed as an operational mode, not as official support
First point to set internally and in your quotes: white‑label is not a legal status. It’s a commercial and operational arrangement. You sell the service to your client. The technical partner executes all or part of the work under predefined rules.
Another useful point: on 17 November 2026, the PrestaShop open source project is provided “as is”, without warranty or dedicated support. You therefore cannot present your offer as official support included by default. You sell agency support, structured by your own process.
Who keeps the client relationship and who handles the technical work
In white‑label, the agency retains the client relationship. This is the clearest arrangement. The client talks to you. You qualify the request. The technical partner works backstage, with or without direct access to tools, depending on what was agreed.
Put in writing, explicitly:
- who receives the initial request;
- who restates the technical need;
- who asks the client for additional information;
- who approves production deployment;
- who sends the final report.
A common mistake is leaving these points implicit. At the first urgent incident you lose time and responsibility becomes blurred.
What an agency can include without confusing maintenance and migration
Your offer should separate three blocks: routine maintenance, incident support and migration projects. Routine maintenance covers checks, small fixes, controlled updates and minor evolutions. Incident support deals with a bug, an inaccessible back office or blocked payments. Migration is a larger undertaking: versions, compatibilities, modules, theme, testing and regression risks.
The official documentation also reminds that PrestaShop updates can be risky if done without a method. This helps you avoid selling simple maintenance when the shop actually needs a bigger project, or even a fix for a failed PrestaShop migration.
Define a ticket workflow your agency can run without friction
A white‑label offer stands or falls by its request workflow. If that workflow is clean, you can absorb more requests without hiring too early. If it’s fuzzy, every ticket becomes a mini investigation.
Set a single entry point for all requests
Choose a single entry point: support mailbox, ticketing tool or a unique agency channel. Avoid parallel requests by email, phone and messaging. You won’t be able to prioritise or trace them properly.
Each ticket should contain at least:
- the shop concerned;
- the urgency level;
- the observed symptom;
- the time it appeared;
- what changed just before;
- the affected scope: front, payment, cart, back office or emails.
The earlier this qualification is done, the less time you waste on internal back‑and‑forth.
Separate blocking incidents, scheduled maintenance and small evolutions
Don’t mix everything in the same queue. Create at least three categories: blocking incident, scheduled maintenance and small evolution. The rule is simple: a customer cannot place an order, admin access is lost or the site is offline? That’s an incident. Preparing an update, a monthly check or a non‑urgent fix? That’s maintenance. A functional change requested by the client? That’s an evolution.
This separation allows you to sell the right level of service and to steer, if needed, towards on‑demand or monthly PrestaShop support with a clear scope.
Specify who approves production deployment and who restates the request to the client
Two approvals must be planned: approval of the need and approval of the production deployment. In an agency model, the simplest is for the agency to remain decision‑maker on what goes to production, even if the technical partner advises.
The post‑intervention report should always come back to the agency with three items: probable cause, action taken and points to watch. This document lets you reply cleanly to the client, justify billing and avoid the same bug being retried twice.
Frame access, confidentiality and GDPR before the first incident
Signing an NDA is not enough. If the partner accesses systems or customer data, you also need a subcontracting framework. The CNIL reminds that processing carried out by a subcontractor must be contractually defined, with clauses on purpose, duration, confidentiality, security, assistance and end of the relationship: see the model contractual clauses between controller and processor.
Why an NDA alone is not enough
An NDA protects confidentiality. It doesn’t say enough about accesses, incident handling, data destruction, logging or the allocation of GDPR roles. These are the points that cause issues when an urgent ticket requires server or back‑office access.
At minimum, provide for:
- each party’s role in processing;
- the types of access authorised;
- a prohibition on reusing data for the subcontractor’s own purposes without written permission;
- notification rules in case of an incident;
- conditions for returning or deleting data at the end of the engagement.
This avoids a discreet but operationally weak agreement.
Which accesses to open, for how long, and how to close them
CNIL recommends framing maintenance operations and opening remote access only on request, for a defined duration, then closing it at the end: see its recommendations on maintenance framing.
Practically, open named accesses limited to the strict minimum, with expiry where possible. Don’t keep a permanent admin account for convenience. For subcontractor remote access, CNIL also recommends a VPN, multi‑factor authentication and strict limits on bulk downloads.
The common mistake is sharing an agency identifier or using an old account left active after a project. It’s convenient at first, then becomes unmanageable.
What traces to keep after each intervention
Keep a simple log: date, operator, shop, accesses used, operation performed, data possibly handled and access closure. This traceability supports governance, GDPR compliance and reversibility.
The minimum useful level is not complicated. A timestamped ticket history, an intervention note and an inventory of opened accounts already prevent many grey areas.
Choose a billing model that protects your margin and your client promise
White‑label offers rarely fail for technical reasons. They more often fail because the economic model is not sustainable: package too broad, unframed emergencies, many small requests accumulating, slow approvals and unbilled time.
Time spent, ticket bundles or subscription: which to sell for your portfolio
Few shops and irregular requests? Time‑and‑materials is easiest. A small portfolio with recurring needs? Ticket bundles work better. Multiple active shops needing ongoing oversight? A maintenance subscription is simpler to sell and manage.
The choice isn’t only commercial. It mainly depends on the real frequency of requests, your agency’s autonomy and the type of portfolio. If you already sell monthly PrestaShop maintenance, formalise what’s included, what triggers a separate quote and what is considered an emergency.
How to handle out‑of‑scope work, emergencies and hour approvals
To protect your margin, cover three points in the quote:
- what is included in the package;
- what is out‑of‑scope;
- who approves extra hours.
Add a simple rule for emergencies: a blocking incident follows a different path than a comfort evolution. Until the scope is defined, don’t sell an ambiguous SLA. Sell an acceptance, an escalation method and agency approval.
If you work with KLN‑WEB, the hourly rate is published in advance at €70 excl. VAT. That gives a clear base to build your resale price and margin, instead of recalculating each ticket case by case.
Prepare shop takeover and reversibility from day one
Most agencies don’t start with a brand new shop. They take over an existing build by another provider, sometimes poorly documented. An entry audit avoids nasty surprises.
Minimum intake audit before accepting a shop in white‑label
Before taking a shop into your offer, check at minimum: back‑office access, hosting access, backups, current PrestaShop version, critical modules, payment methods, transactional emails, presence of a staging environment and recent incident history.
If you industrialise this phase, rely on a PrestaShop maintenance checklist to industrialise. The aim is not to audit everything at the same depth, but to know whether you’re entering routine maintenance or a risky takeover requiring a separate quote.
Handover in reverse when you hire or change organisation
Reversibility must be planned from the start, not when you internalise. Specify what will be returned: inventory of accesses, ticket history, minimal documentation, list of sensitive modules and status of ongoing actions.
The CNIL guide 2024 also stresses conditions for data return and deletion, and regular review of security measures. This discipline prevents a sudden departure with forgotten accounts or interventions impossible to resume.
The mistake to avoid is making the whole operation depend on a single person or an undocumented channel.
Launch your white‑label PrestaShop offer with a simple protocol
To start, don’t build an overly heavy device. Test your offer with a pilot client and a short protocol. The objective is to verify that your commercial circuit, technical qualification and validation model hold up on real tickets.
Minimum kit to start with a first pilot client
Here’s the minimum kit:
- a written offer that separates maintenance, incident and migration;
- a single entry point for tickets;
- a request qualification template;
- a confidentiality clause and an adapted subcontracting framework;
- a rule for opening and closing accesses;
- a post‑intervention report template;
- a rule for approving production deployments and out‑of‑scope hours.
With this in place you can sell properly without recruiting too early.
The 7 items to lock down before announcing your offer
Before announcing the offer, check these seven items:
- who speaks to the end client;
- who qualifies urgency;
- what real response time you can sell according to scope;
- which accesses are authorised;
- who approves production;
- how you re‑bill out‑of‑scope work;
- how you organise the exit if you internalise later.
If you want to test this setup with a first client, rely on a certified PrestaShop expert able to work white‑label. KLN‑WEB works backstage, the agency keeps the client relationship, with a free diagnosis, replies within 24 h, quotes within 24 working hours and a published rate of €70 excl. VAT per hour.
Frequently asked questions
Do you provide white‑label PrestaShop maintenance for agencies?
Yes. KLN‑WEB can work white‑label for web agencies that want to sell PrestaShop support or maintenance without hiring immediately. The principle is simple: the agency keeps the client relationship, and the technical intervention is framed in advance on scope, accesses, confidentiality and handover.
Does the provider speak to the end client or stay backstage?
The clearest arrangement in white‑label is for the agency to remain the client’s contact. The technical partner works backstage and reports findings to the agency. If direct contact is needed for a specific point, it’s better to plan it from the start to avoid role confusion and deployment approvals.
How does maintenance for a PrestaShop shop start in white‑label?
A clean start requires a framed takeover: inventory of accesses, verification of backups, identification of critical modules, check of payment methods, presence of a staging environment and clarification of the sold scope. This step distinguishes routine maintenance from a risky takeover that needs a separate quote.
How much does PrestaShop maintenance cost?
There is no single price that fits all shops. Cost depends mainly on the sold scope, request volume, presence of emergencies and the level of takeover work on the existing site. At KLN‑WEB, the hourly rate is published at €70 excl. VAT, which lets an agency build its resale margin.
How quickly do you intervene in case of a failure?
The right approach is to talk about acceptance rather than promising one identical response time for everything. A blocking incident, scheduled maintenance and a small evolution do not follow the same path. With KLN‑WEB you can expect a free diagnosis, a reply within 24 h and a quote within 24 working hours.
What’s the difference between maintenance and migration for PrestaShop?
Maintenance covers routine upkeep, checks, targeted fixes and controlled updates. Migration is a different scale: compatibilities, modules, theme, testing and regression risks. If a shop must undergo a major step or recover from a poorly prepared update, treat it as a distinct project, not a simple maintenance ticket.