Custom module

The module your store is missing,
written for it.

The PrestaShop marketplace holds thousands of modules, and yet sometimes none does exactly what your business needs: a pricing rule specific to your trade, an export to your logistics provider, a checkout adapted to your B2B customers. That is when I build a custom module — a real module, with its hooks and its settings, not a patch buried in the theme.

5,0/5 · 66 verified reviews 50+ projects shipped 10 years of experience
In detail

A custom module starts with an honest question: does it already exist? I spend half a day checking PrestaShop's native features and the maintained marketplace modules before proposing any code. When the answer is no, I scope the need with you on a single page — what the module does, what it doesn't, which data it relies on — and I quote on that basis, not by the hour.

Read more

Development happens on a copy of your store, on your exact PrestaShop version, with your real products and your real VAT rules. The module follows the expected architecture: hooks rather than overrides, prefixed tables, settings in the back office, clean uninstall. That is what lets it survive your future updates and be taken over by any other PrestaShop developer.

Delivery includes the code, its documentation and acceptance testing on your real cases — then a three-month warranty on what was delivered.

Features

What you get.

01

Native first

Half a day checking that PrestaShop or a maintained module doesn't already do it. If it does, I say so: configuration costs less than development.

02

Scoped on one page

What the module does, what it doesn't, the data it touches. The quote is based on that page, and it doubles as the acceptance checklist.

03

Hooks, no overrides

An isolated, deactivatable module with its own tables and settings. Nothing in the core, nothing buried in the theme: your updates don't break it.

04

Tested on your copy

Built and tested on a copy of your store — your exact version, your products, your VAT rules. Going live is not the first time it runs.

05

Ready for what comes next

Written for the version you have, with the next upgrade in mind: a well-built module goes from 1.7 to 8 without a rewrite.

06

Typical cases

Business pricing and discount rules, accounting and logistics exports, specific product fields, B2B checkout, ERP or till connector, back-office automations.

07

You own it

The code is yours, documented, with no licence or subscription. Another PrestaShop developer can take it over tomorrow.

08

Three-month warranty

Any defect within the delivered scope is fixed at no charge for three months after go-live.

Method

How we proceed.

01

Need check

Native features first, then the marketplace. If a maintained module does the job, I tell you and the quote stops there.

half a day
02

Scoping and quote

A one-page scope agreed together, a fixed price on it. No time-and-materials billing.

48h
03

Development

On a copy of your store. You see the module running before it touches production.

1 to 4 weeks
04

Acceptance

You test on your real cases, with the scope page as the checklist.

a few days
05

Go-live and warranty

Installed on the store, documentation handed over, and three months of fixes included on the delivered scope.

3 months
Real cases

A few examples.

01

Per-customer B2B price grid

Negotiated prices per customer group, applied in the cart and on the invoice, imported from the ERP nightly.

02

Automatic logistics export

Orders exported in the carrier's format as soon as they're paid, tracking number pulled back and sent to the customer.

FAQ

Frequent questions

How much does a custom module cost?
Most fall between €900 and €4,000 excl. VAT: a specific product field or an export sits at the low end, an ERP connector or a B2B checkout at the high end. The price is fixed, set on the scope page.
Why not an override, it's faster?
Faster to write, costlier to live with: an override replaces a core class and is usually rediscovered on update day, when it breaks. A module can be switched off in one click and updated separately.
Will the module survive a version upgrade?
If it is written with the intended hooks and API, yes in the vast majority of cases; a major upgrade (1.7 to 8) may need an adaptation, quoted separately and far shorter than a rewrite.
Can someone else maintain it?
Yes. The code is yours, documented and PrestaShop-compliant, precisely so another developer can take it over without me.
Do you also build for WooCommerce or Shopify?
Yes: a WooCommerce extension or a Shopify app, with the same method — native check, one-page scope, fixed price. PrestaShop remains the core of my work.
Let's start

Ready for your project?

Free quote within 48h. Response within 24h. No commitment.