PrestaShop
New custom modules
Create one new module for a defined customer workflow, Back Office tool, checkout or order behaviour, regulatory function, or bounded integration.
Module-level ownershipOpen route →Loading content
Custom development / decision
Custom development on Addons means one new module or plugin for a specific operational requirement. The users, inputs, outputs, platform versions and acceptance scenarios are agreed before build. Repairs, upgrades, migrations, retainers and store maintenance remain at psdevs.com.
A bounded addon starts with acceptance criteria and ends with code, testing evidence and a clear handover.
A scope starts with
01One affected workflow02Known inputs and outputs03Data and failure boundaries04Acceptance and maintenance criteriaDiscovery
PrestaShop
Create one new module for a defined customer workflow, Back Office tool, checkout or order behaviour, regulatory function, or bounded integration.
Module-level ownershipOpen route →WooCommerce
A secondary P2 path for one new plugin with an agreed WooCommerce data and compatibility boundary.
Plugin-level ownershipOpen route →Broad project
When discovery expands beyond one addon or integration, the project belongs at PsDevs.
Explicit host boundaryOpen route →Intake
Useful intake names the business requirement, users, current process, desired outcome, PrestaShop or WooCommerce and PHP versions, dependencies, data categories, UI surfaces, edge cases and acceptance scenarios.
Do not send credentials, database dumps, customer records or production tokens through a first-contact brief.
Boundary
A scoped addon defines its interfaces, stored data, failure handling, update assumptions and operational owner.
If the work becomes a redesign, migration, multi-team program or ongoing maintenance contract, the brief moves to psdevs.com rather than duplicating agency intent here.
Decision path
Confirm that no documented PsDevs product already fits.
Agree one workflow, its inputs, outputs and exclusions.
Implement the agreed addon against supported extension points.
Verify acceptance, failure and compatibility paths in staging.
Hand over code, operating notes and the maintenance boundary.
Fit
One customer or operator journey with named actors, triggers, data and completion criteria.
One defined data exchange with authentication, retry, failure and ownership rules.
An installable add-on, agreed documentation, known limits and acceptance evidence—not an open-ended retainer.
Broken modules, upgrades, performance work, store errors and ongoing support belong at psdevs.com.