Code written into the theme
Logic written into templates is lost when the theme changes or the shop is upgraded, and cannot move to another webshop.
Custom logic, a bespoke checkout step, an admin screen or automation. Built to PrestaShop standards, so the next upgrade does not take it away.
Logic written into templates is lost when the theme changes or the shop is upgraded, and cannot move to another webshop.
Two overrides on the same class run in an unpredictable order. In a module that problem does not exist.
Without documentation the next developer rewrites it. A module gets a description, a settings screen and a version.
We go through what it has to do, where it appears, and who will use it.
A written specification with screens and edge cases. Price and deadline come from it.
The module follows PrestaShop standards: hooks, a settings screen, translatable strings.
The feature is tried on a copy of your webshop, with real data.
A description of what it does, how to set it up, and what to know at upgrade time.
After release we keep fixing it and adapting it to new PrestaShop versions.
We discuss the requirement and write a specification. Price and deadline follow from it.
The module is built and tried on a copy of your webshop.
We install it on the live webshop, configure it and hand it over with the documentation.
Send the webshop address and what the problem is. We look at it and reply within two working days with what we suggest and what it costs.