Per-customer B2B price grid
Negotiated prices per customer group, applied in the cart and on the invoice, imported nightly from the company's management software (ERP).
Módulo a medida
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 partner, an ordering flow suited to your business customers. That is when I build a custom module: a real module, with its own settings, not a patch buried in the theme.
5,0/5 · 66 reseñas verificadas
50+ proyectos entregados
10 años de experiencia
En detalle
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.
Leer más
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, the attachment points PrestaShop provides, rather than overrides, those files that replace a part of the software; its own tables; its settings in the admin; a 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, checking together that everything does what was agreed, then a three-month warranty on what was delivered.
Características
Lo que obtienes.
Método
Cómo procedemos.
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 billing by the hour.
48h
03
Development
On a copy of your store. You see the module running before it touches the live site.
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 what was delivered.
3 months
Casos reales
Algunos ejemplos.
Automatic logistics export
Orders exported in the carrier's format as soon as they are paid, tracking number pulled back and sent to the customer.
FAQ
Preguntas frecuentes
How much does a custom module cost?
Most fall between €900 and €4,000 excl. VAT: a specific product field or an export at the low end; a connection to your management software (ERP) or a checkout for professional buyers 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 — a file that replaces part of the original software — is usually rediscovered on update day, when it breaks. A module, by contrast, can be switched off in one click and updated separately.
Will the module survive a version upgrade?
Yes in the vast majority of cases, if it relies on PrestaShop's official attachment points (the 'hooks'). 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.
Ver también
Páginas relacionadas.
Empecemos
¿Listo para tu proyecto?
Presupuesto gratis en 48h. Respuesta en 24h. Sin compromiso.