When a marketplace module doesn't do what you need, we build it. 27+ modules in production, six functional domains covered, PrestaShop 1.7 to 8.2+ compatibility. Our signature: su_*. Our promise: code delivered, not rented.
A custom PrestaShop module is an extension developed specifically for your store, your catalog, your business logic. It does exactly what you need, with no useless options and no technical debt imposed by a third-party vendor.
The PrestaShop marketplace offers thousands of modules. That covers 70% of standard needs. The remaining 30% is where we step in: business rules specific to your activity, custom integrations, payment constraints not handled by existing addons, back-office customizations requested by your field team.
Six functional domains covered, more than 27 modules in production at our clients. Here's a snapshot of what we've already built. Your project will probably have its own domain or its own modules. The pattern stays the same.
Non-standard payment flows, custom methods, fine-grained billing management.
su_sepa_paiement
su_po_paiement
su_preventdoublepayment
su_multibilling
su_split_vat
Payment and shipping changes after validation. A rare workflow, technically tricky, essential in automotive and premium B2B.
su_order_payment_edit
su_order_shipping_edit
su_ordereditedonpayment
su_ordereditedonshipping
su_onorder
su_bo_shipping_override
Custom attributes, fine combinations, stock alerts, product references, image per combination, B2B management.
su_feature_od
su_productcolorname
su_unique_product_reference
su_img_attribute_fix
su_stock_alert
su_oosflag
su_hideproposedprice
Advanced menus, category hero, home filters, user micro-interactions.
su_dualmenu
su_categoryhero
su_homefilter
su_passwordaccordion
Back-office tweaks for your field teams: custom labels, zones, assets, at-dealer management.
su_change_labels_bo
su_atdealer
su_customzones
su_frontassets
su_bo_shipping_override
PrestaShop REST API extension for ERP integration. AI module for product content generation and translation.
su_ws_extend
su_aicontent
Measure, fix, stabilize. Applied to module development, that gives three clean steps.
Understanding your real need, not your surface request. Identifying what belongs in a module and what deserves something better.
Isolated module, clean code, functional tests, internal documentation. No wild core overrides.
Code delivery, training for your team, follow-up for the first weeks, fast adjustments.
At the end of the process, you have a module that does its job, you understand what it does, and you can evolve it with us or with another team tomorrow.
On PrestaShop, there are two ways to add a feature: create a module, or do an override (of the core or an existing module). Overrides are tempting because they're faster to code. They're also a trap.
Overrides are only used as a last resort, when no PrestaShop hook can deliver the intended behavior. And always documented.
PrestaShop evolves. So do our modules. Here are the concrete commitments behind our su_* signature.
When you take over an older module (yours or from another provider), we offer an audit: version upgrade, refactor if needed, clean-up. You know upfront whether patching is viable or whether rebuilding is wiser.
When the need goes beyond standard, a marketplace module isn't enough. Either it covers only 60% of what you need, or it adds a thousand useless options that pollute your back-office. A custom module does exactly what you need, with no technical debt, with code you own.
Yes. Our su_* signature is compatible with PrestaShop 1.7.7 to 8.2 and above. We test on stable releases and adapt when the core evolves.
No. Our custom modules stay in your name inside your installation. No license to renew, no encryption, no dependency on a third-party marketplace. If a module ever becomes relevant as standard for several clients, we discuss it, but that's not the default.
A module is isolated from the PrestaShop core: it can be disabled, updated, or removed cleanly. An override directly modifies the core or a theme file: it's faster to code, but breaks on every update. We always favor the module. Overrides are used only as a last resort, with explicit documentation.
Yes. We take over modules built by others: code audit, clean-up if needed, feature additions, version upgrade. If the code is too messy and rebuilding costs less than patching, we'll tell you.
Security by default: CSRF protection, prepared statements, input validation, fine-grained permissions, no plain-text storage of sensitive data. Auditable by your team or a third party, the code stays readable.
All our modules follow GDPR principles: explicit cookie consent, right of access and erasure, documented processing registry. No data is sent outside of your installation.
Describe it to Synapse, our AI advisor. Ten minutes to frame what you really need, and an email recap to share internally. Our team comes back to you with a real proposal.