Luca Cavallini

PrestaShop development

PrestaShop development: themes & modules

Custom PrestaShop shops, themes and modules on 1.6 through 9. Hooks over overrides, clean code, and decisions that survive the next version upgrade.

Work with me → See the work →

Most PrestaShop pain comes from code that was quick to write and impossible to maintain: override soup, themes that fight every update, modules that conflict. I build the opposite — clean, hook-based, upgrade-aware development by someone who’s lived through every version since 1.5.

I’ve written and maintained twenty production modules and run shops with over a million products. That experience shows up in the details: code that’s light, secure, documented, and that you (or the next developer) can still work with in two years.

Scope

What’s included

  • Custom modulesBespoke functionality built the PrestaShop way — hooks, services, clean install/uninstall, multi-shop aware.
  • Themes & front-endCustom and child themes, template work, responsive front-end that doesn’t fight core updates.
  • Versions 1.6 → 9Deep familiarity with every major version — and the quirks that bite when you move between them.
  • IntegrationsPayment gateways, management software, marketplaces and APIs wired into the shop.
  • Upgrade-safe by designHooks over overrides, no core hacks — so the next version doesn’t undo your work.
  • Maintained, not abandonedYou reach the developer who wrote it. No ticket queue, no silent abandonware.
Proof

Related work

Migration PrestaShop migration & upgrade From 1.6/1.7 to 8 or 9 — data, SEO and modules intact. Staged and reversible. Performance PrestaShop performance Slow shops made fast — measured, not guessed. Big catalogues a specialty.
FAQ

Questions, answered

Can you take over a project another developer started?
Yes — a lot of my work is rescuing and continuing existing shops. I’ll audit what’s there, tell you honestly what’s salvageable, and take it from there.
Do you build for the latest PrestaShop 9?
Yes, and for everything back to 1.6. I’ll recommend the right target version for your case rather than defaulting to the newest.
Will the code be maintainable by someone else later?
That’s a design goal, not an afterthought: hooks over overrides, clear structure, documentation. You’re never locked to me.

Tell me what’s not working — or not talking to what.

New build, a system that needs rescuing, an integration, the June 2026 deadline. One developer who builds it and stays to run it. Reply usually within 1–2 business days.