prestashop-module-development

PrestaShop Module Development

When to use

Use this skill for PrestaShop module development tasks such as:

• Creating new modules with modern architecture (Symfony controllers, services, entities)
• Refactoring legacy modules to use modern PrestaShop patterns
• Implementing hooks, actions, and event listeners
• Adding configuration pages (modern Symfony-form approach)
• Creating front office features and widgets
• Setting up database entities and migrations
• Implementing security measures (CSRF, input validation, SQL injection prevention)
• Adding multilingual support and translations
• Converting legacy code patterns (HelperForm, jQuery UI sortable, ObjectModel) to modern equivalents
• Building list pages with the PrestaShop Grid system (filters, pagination, toggle, drag-and-drop position)
• Creating and managing PrestaShop cart rules (vouchers, discount codes, promotional codes)
• Implementing Symfony console commands for background tasks and batch operations

Inputs required

• PrestaShop version (target 8.x/9.x for modern development)
• Module scope and functionality requirements
• Existing module path (if updating legacy code)
• Database schema requirements (if applicable)
• Front office integration needs (hooks, widgets, pages)
• Configuration requirements (settings, admin interface)
• Multilingual requirements and supported languages

Procedure

0) Project structure & namespace naming

Read: references/module-structure.md

Key rules:

• Derive PSR-4 namespace from the module name prefix — never use PrestaShop\Module\
• Use the PrestaShop Module Generator to scaffold new modules

1) Main module class & installer

Read: references/module-class-and-installer.md

MANDATORY patterns:

• install() method: ALWAYS if (!parent::install()) { return false; } FIRST, THEN delegate to installer
• uninstall() method: ALWAYS installer FIRST, THEN parent::uninstall() with && chaining: return $installer->uninstall() && parent::uninstall();
• Hooks: Define as class property array private array $hooks = [...] in Installer, use $module->registerHook($this->hooks) to register
• Tabs: Define as class property array private array $tabs = [...] with structured data: name, class_name, label, parent_class_name, visible
• Parent group tab: Auto-check if exists, if not, prepend to tabs array with array_unshift($this->tabs, $parentTab)
• No getTabs(): NEVER add getTabs() method to module class — all tab management in Installer only