Commerce engineering / PrestaShop
PrestaShop development.
Modules, multistore and the systems behind a sale.
Self-hosted commerce scope for merchants and agencies: custom modules, storefront themes, catalogue combinations, languages, currencies, payments, carriers and ERP or PIM connections. Start with the exact release and shop context before extending the store.
Discuss PrestaShop requirements โContents ยท PrestaShop
Make modules, catalogue rules and shop context explicit.
A PrestaShop project can be a new store, module, theme, multistore setup, takeover or version upgrade. Name the product catalogue, combinations, customer groups, prices, stock, tax, languages and fulfilment before selecting modules. Payment, carrier and tax compatibility should be reviewed against the chosen release before custom work depends on them.
Keep a protected staging environment with representative catalogue data and production-like runtime, services and cache configuration. Record installed modules, overrides, themes, core changes and external accounts. Use reviewed modules and supported hooks or services rather than hiding business rules in templates or editing core files. Modular code still needs compatibility tests and maintained dependencies.
- Storefront: discovery, combinations, customer accounts, cart and checkout in the intended languages and currencies.
- Back office: catalogue, orders, customers, carriers, tax, shop settings and module-specific operator screens.
- Integrations: payment, shipping, ERP, PIM, stock and feeds with clear authoritative fields and failure handling.
- Delivery: version control, code review, static analysis, module tests, staging and authorised release.
- Operation: hosting, scheduled work, backups/restores, updates, monitoring and receiving-team handover.
A separate ready-made marketplace is not a PrestaShop module or proof of a live store. Choose based on demonstrated buying and operating workflows, not a geographic popularity claim or an arbitrary catalogue-size threshold.
Custom-code rights and third-party licences are separate.
Agree the custom modules, theme work, repositories/history, configuration, schema changes, deployment scripts, documentation and approved accounts to be delivered. Distinguish custom-code rights from platform licensing, purchased modules, themes, media and external services. An open-source platform does not transfer every commercial module or service account.
Record confidentiality, white-label branding, source access, licence inventory, updates, support, exit and receiving-team responsibilities in writing. Keep passwords, payment keys and database secrets out of ordinary source archives and use an approved secure handover route. Source access alone does not guarantee another team can operate the store immediately.
Name owners of hosting, domains, back-office roles, merchant/carrier accounts and business data. Prove handover through setup, deployment and restore tasks. Agree confidentiality, custom and third-party rights, access transfer, support and exit responsibilities in writing.
Compare actual buying and operating requirements.
Compare PrestaShop, WooCommerce, Magento, OpenCart and hosted alternatives using the same catalogue, combinations, customer groups, editorial needs, currencies, tax, integrations and staff tasks. Avoid high/medium/low cost labels, install-speed rankings, regional stereotypes and product-count cutoffs.
- Store model: demonstrate shop groups, separate domains, stock/customer sharing, price settings and operator permissions.
- Hosting: verify supported runtime, database, services and responsibility for patches, backups and incidents.
- Catalogue workload: benchmark representative combinations, faceted filters, search, imports and concurrent purchase journeys.
- Ecosystem: inspect current module/theme licences, compatibility, maintenance, operating cost and supported replacement paths.
- Control: distinguish custom code, platform terms, exports, account ownership and third-party constraints.
An existing WordPress editorial workflow can prompt a WooCommerce comparison. Complex company buying can prompt a Magento assessment. Compare OpenCart or a hosted service such as Shopify or BigCommerce when their demonstrated constraints fit. Neither the platform name nor catalogue size establishes suitability.
Seven decisions before a PrestaShop engagement.
What does development cover?
Scope custom pricing/configurator/B2B modules, themes, multistore, payment/carrier methods, marketplace logic and ERP/PIM integration separately. The catalogue, checkout and back office are a starting point, not proof that the intended order workflow is ready. Define acceptance for each custom rule and external dependency.
Review front-office Smarty and the templates/services used by the actual back-office page. Evaluate a child theme where supported and test module-template overrides, responsive behaviour and the selected release. A theme that inherits templates is not automatically compatible with every update.
How should a slow store be investigated?
Profile production-like staging rather than drawing conclusions from debug mode. Review PHP OPcache, worker/memory capacity, Smarty compile/cache settings, CCC, database queries, combinations, faceted search, module hooks and external calls. Change one measured bottleneck at a time and verify correctness after each change.
APC/APCu-labelled options and Memcached depend on the installed release, PHP extensions and host. A single-server memory cache is not automatically shared between web nodes. Confirm the actual adapter instead of copying an old cache recipe. Test multi-front synchronisation and invalidation.
How should an older store move to a newer version?
Inventory core changes, modules, overrides, theme, PHP/database versions and integration contracts. Check the current supported source/target path and the Update Assistant options for that store. Rehearse backup, update and restore on staging and reconcile orders, customers, catalogue relationships and URLs.
Source release-calendar claims and support status can age. Use current release information and the exact compatibility chart, not an assumption that all 9.x or all 8.x releases accept the same PHP version. The inspected chart differentiates9.0 and 9.1, so a generic PHP8 label is not enough.
What does selling across countries require?
Define languages, translated content/URLs, currencies, customer groups, tax display, country tax rules, invoice numbering and carrier coverage. Review VAT/OSS, business-tax identifiers, privacy, consumer duties and payment authentication with the responsible adviser and providers. A localisation or tax module does not establish regulatory compliance.
Test each intended country/language/currency checkout and its resulting invoice and payment record. Do not assume every language needs a separate shop: choose languages within a shop or separate shops based on catalogue, domain, stock and operational requirements.
Which platform fits?
Compare the same buying, content and operating tasks across self-hosted and hosted options. Ask which modules are required, who maintains them and what happens when an upgrade changes a dependency. Do not select a platform through a geographic preference, module-count claim or catalogue threshold.
Can the store include chat or a support chatbot?
Treat a hosted widget or custom assistant as a separately approved integration. Review provider data processing, tracking, consent, performance, customer identity and access to catalogue/order data. Where opt-in is required, do not load the third-party script before consent. Loading after page render alone does not make a widget privacy-safe or free of performance cost.
A logged-in session must not automatically disclose cart, order history or personal data to a chat service. Define minimum fields and verify ownership and authorisation for order lookups. Protect Webservice/Admin API credentials server-side and prevent cross-customer or cross-shop access. Test the complete chatbot, data-access and provider integration before enabling it for customers.
What determines cost and team shape?
Catalogue combinations, shops, languages/currencies, tax, migrations, modules, theme work, marketplace rules, ERP/PIM and operations drive scope. Separate one-time work from hosting, paid modules/themes, processing and maintenance. Obtain an itemised current quote rather than source sample amounts or durations.
A contained carrier change and a multistore upgrade need different skills. Name module/theme/integration/QA/infrastructure reviewers, continuity and incident ownership. Agree milestones, support and confidentiality in writing; a team label is not evidence of delivery quality.
Modules, hooks and durable integration work.
Feature modules and lifecycle
Keep business services separate from hooks and controllers where practical. Use module-owned tables and versioned setup changes rather than undocumented core schema edits. Document dependencies, translations, permissions, configuration, shop association and any back-office screens.
Test install, enable/disable, reset, upgrade and uninstall. The source suggested removing tables on uninstall as a standard; decide retention explicitly instead. Business orders, integration history and audit records should not be accidentally erased by a module removal. A module boundary alone does not isolate every side effect.
Hooks, Symfony services and overrides
Use a documented hook or supported service decoration/extension when it fits the target release. Inspect event timing and parameters, not just its name. For migrated Symfony areas, check the real service/controller boundary. Avoid direct core edits.
Official guidance describes class/controller overrides as exclusive and risky: another module cannot predictably override the same behaviour. It discourages distributing override-based modules and suggests hooks, inheritance or service decoration where suitable. Document an unavoidable local override, its conflicts and removal/upgrade tests. No hook-based implementation is automatically upgrade-proof.
The paid-status ERP example needs transaction and replay design
The source registers actionOrderStatusPostUpdate and inserts an order ID when the new state is marked paid. Official documentation describes notification after status changes and supplies old/new states, order ID and shop context. That is an integration trigger, not a complete fulfilment or exactly-once guarantee.
- Define the business condition and authoritative payment/order state, including cancellation, refunds and partial fulfilment.
- Coordinate committed state with a durable work record; test insert failure, rollback and a worker seeing incomplete work.
- Persist an idempotency/reconciliation identity for each intended external effect and handle duplicate/concurrent status events.
- Implement and operate the worker, locking, retry/backoff, failed-work visibility and controlled replay.
- Carry the correct shop and external identifiers through ERP/PIM stock and order updates.
- Reconcile ambiguous upstream acceptance after timeouts before creating another external order.
The snippet omits install SQL, queue schema, worker and recovery policy. It is therefore replaced by explicit requirements rather than presented as production code. Moving ERP requests out of a web call can reduce coupling, but database/enqueue work and shared resources still affect the order path.
Webservice and Admin API are different contracts
The legacy Webservice exposes CRUD resources and can be extended through modules. The newer PrestaShop 9 Admin API uses OAuth2 clients, access tokens and scopes. Verify endpoint/field coverage for the intended release and workflow rather than treating the APIs as interchangeable or a complete ready-made mobile backend.
Use least-privilege credentials, HTTPS, server-side storage, validation and appropriate resource ownership checks. Custom endpoints and webhook delivery need explicit authentication, retry, idempotency and reconciliation design; they are not automatically supplied by a REST label.
Shop groups and API context shape every change.
PrestaShop multistore enables several shops and shop groups within one installation. Each shop belongs to a group, and the back-office context selects all shops, a group or a single shop. Plan shared or separate customers, stock, catalogue, prices, domains and settings before importing data. Official guidance warns not all features/modules support multistore.
- Change a product, combination, price and stock record in each intended context and inspect the resulting storefronts.
- Verify module configuration, employee permissions, orders, exports and reports do not cross intended boundaries.
- Test domain/URL generation, translations, currency/tax persistence, callbacks and cache keys per shop.
- Reconcile shared inventory and external ERP/PIM identifiers with the authoritative system.
- Test changes made in all-shops context as well as an individual shop, with explicit approval for broad effects.
The inspected Admin API multishop documentation labels its support experimental behind admin_api_multistore. It requires explicit request context when multistore is enabled and distinguishes request scope from a resource's shop associations. Verify the selected release and flag before relying on it; do not assume a missing shop parameter safely picks the intended shop.
Separate stores are not automatically independent tenants or legal entities. Plan access, financial reporting, customer data and failure impact according to the business, not only the administration dropdown.
Three engagement shapes with separate operating terms.
- Separate marketplace product: assess its actual stack, vendor workflow, apps, licences and acceptance rather than calling it PrestaShop.
- Custom store or upgrade: specify theme, extensions, integrations, data work, supported release and handover evidence.
- Ongoing store work: define feature changes, patching, updates, seasonal preparation, monitoring and release responsibility under agreed capacity and terms.
Agree review cadence, milestones, billing, cancellation, defect boundaries and support scope. No fixed team size, guaranteed sprint output, first-commit deadline, launch date or included support period is assumed.
Six acceptance areas before handover.
- Review: custom code, permissions, input/output handling, hook signatures, overrides and dependency compatibility.
- Tests: model logic, module installation, catalogue, account, cart, checkout, each selected payment/carrier route and failure handling.
- Performance: representative data, cache modes, concurrent journeys and background jobs with measurement conditions recorded.
- Handover: repository history, extension/theme licence inventory, setup guide, configuration, APIs, releases and recovery runbook.
- Payments: approved test-mode charges/refunds, callback authenticity, amount/currency checks, duplicate delivery, ambiguous outcomes and provider-dashboard reconciliation.
- Operation: errors, slow queries, failed callbacks, scheduled work, backups/restores, patch ownership and escalation under written terms.
Hosted payment fields or checkout can reduce some card-data exposure, but inspect the actual integration and the merchant/provider PCI DSS responsibilities. Do not certify compliance or assume every payment method keeps card data away from the store. Live activation and real charges require separate authority.
Include agreed desktop/mobile browsers and accessibility checks. Analytics and external error monitoring need a data/privacy and consent review before activation. Obtain approval for the actual account, collection and recipient configuration before activation.
Choose technologies for the release and shop workflow.
An option inventory, not an installed bundle or a claim that every listed service is included.
- PrestaShop 8/9: verify exact release, maintenance status and compatible modules/themes.
- PHP/MySQL/MariaDB: follow the release-specific support matrix, required extensions and backup/restore needs.
- Symfony: use the supported services and migrated back-office boundaries for the selected version.
- Smarty/Twig: distinguish storefront/theme and actual back-office/module rendering paths.
- Composer: dependencies, autoloading, licences and repeatable builds.
- OPcache/APC or APCu-labelled adapter/Memcached: separate bytecode, template and object-cache responsibilities and actual host support.
- Webservice/Admin API/custom REST/webhooks: endpoint coverage, authentication, scopes and reconciliation.
- Stripe/PayPal/Mollie or selected payment modules: current business/country eligibility, callbacks, refunds and authentication.
- Cloudflare or another CDN: static delivery, origin/cache rules and personal-data boundaries.
- GitHub Actions/PHPUnit/PHPStan: release-compatible checks, representative module tests and staging.
- Sentry or another monitor: sensitive-data filtering, access, alert and incident ownership.
- Docker/AWS or another hosting option: workload, persistent storage, scheduled tasks, releases and recovery.
The inspected current 9.x chart distinguishes supported PHP versions for 9.0 and 9.1. The 9.0 release announcement is a historical release description, not a compatibility promise for every later minor version. Some optimisation documentation also contains older PHP/database examples; do not copy those into a new deployment without current validation.
Rehearse update, restoration and business continuity.
Audit source version, core/theme changes, installed modules, overrides, dependencies, custom tables and external accounts. Confirm the exact target and compatible replacements. A PrestaShop 1.6 migration and a supported update from a later release can require different tooling and redevelopment; verify each supported path rather than assume a single universal route.
The Update Assistant, formerly 1-Click Upgrade and technically Autoupgrade, offers backup/update/restore steps. Its recommended and latest channels can differ and are adapted to the store/PHP state. Check all blocking errors and warnings. Options to disable non-native modules or overrides and regenerate emails can change behaviour or overwrite customisations, so review them with the receiving team.
Maintain an independently verified files/database backup and rehearse restoration, not only the assistant's success screen. Map products/combinations, categories, translations, media, customers, groups, orders, invoices, coupons, stock, shop associations and external references. Reconcile representative relationships and custom-module data as well as totals.
Test payment authorisations, callbacks/refunds, carrier labels, ERP/PIM, accounts, translated URLs, canonicals and redirects. Agree final sync, authorised maintenance/cutover, rollback and post-update reconciliation. No search-ranking, zero-downtime, complete-data or automatic upgrade guarantee is offered. Production changes and live financial operations remain separately authorised.
From product brief to an operated release.
- Brief: products, stores, customers, payment/carrier accounts, current hosting, data and confidentiality.
- Scope: supported release, theme/modules, integration ownership, migration and acceptance evidence.
- Build: protected environments, versioned extension work, named review and representative test data.
- QA: checkout, store boundaries, callbacks, workload, backups and failure recovery.
- Release/handover: owner-approved cutover, reconciled data, verified account access, documentation and receiving-team operation.
Merchant onboarding, content, provider eligibility and owner review can affect the plan. Agree dependencies, milestones and change control in writing. No fixed duration, same-day agreement, guaranteed first commit or automatic live-gateway switch is offered.
What changes the PrestaShop estimate?
- Catalogue structure, options, media, historical data and custom extension tables.
- Stores, themes, languages, currencies and country-specific requirements.
- Custom pricing, configurators, wholesale/quote or marketplace workflows.
- Payment and carrier modules, current licences, eligibility and recovery work.
- ERP, accounting, feeds and authoritative stock/order reconciliation.
- Runtime/hosting, search, cache, backups, monitoring and workload.
- Upgrade replacements, tests, documentation, training and maintenance.
Ask for separate implementation, recurring hosting, paid extensions/themes, payment processing and ongoing operation lines. No source sample price, project range, delivery duration or retainer/cancellation figure is treated as a current offer. A written scope and itemised quote should state assumptions and exclusions.
An illustrative multilingual accessories store.
Consider an accessories brand moving an older commerce installation while revising its catalogue, international checkout and editorial design. This is a requirements scenario, not a Paris client result, proven migration, deadline or page-speed outcome.
- Plan the intended French, English and German experience without assuming one shop per language; demonstrate the chosen shop/language/domain model.
- Reconcile products, combinations, images, customers and historical orders with scripted transformations where needed.
- Evaluate a Smarty child theme against the actual release, module hooks and mobile purchase journeys.
- Review Stripe/PayPal or selected payments, carrier coverage, taxes and provider-supported authentication for the intended countries.
- Design durable order/stock work and ERP/PIM reconciliation using the selected Webservice/Admin API boundaries.
- Trial the migration, redirects, final sync, restore and receiving-team operation on protected staging.
- Measure real category/search/checkout workload and review applicable privacy, tax and payment duties with responsible experts.
The source mixes illustrative framing with asserted delivery details and targets. Those figures are not adopted as evidence. The useful material is a testable catalogue, language, payment, carrier, tax, migration and operating scope.
PrestaShop delivery review and handover.
Agree the implementation boundary, deliverables and acceptance checks in the project scope. Include the source and configuration to be handed over, third-party dependencies, account ownership and the receiving owner's installation and operating walkthrough. Review the selected work at the agreed milestones, with unresolved items recorded before release.
The delivery review can cover a reproducible module build, theme compatibility, shop-context tests, checkout/callback reconciliation, measured workload, upgrade/restore rehearsal and receiving-team handover. Confirm contracting identity, current credentials if claimed, commercial terms and support/source obligations directly. No project counts, ratings, named testimonials or guaranteed response times are reproduced as verified evidence.
Turn sector labels into catalogue and order rules.
- Healthcare/wellness: permitted goods, prescription checks, repeats and sensitive-data boundaries with expert review.
- Telemedicine: care packages, appointments and subscriptions need separately assessed clinical and payment workflows.
- Fintech-related commerce: provider eligibility, fraud, wallets/pay-later, refunds and disputes.
- Retail: catalogue, promotions, stock, sale workload, fulfilment and returns.
- Media: subscriptions, merchandise, digital downloads and entitlement handling.
- Creators: shops, paid communities, collaboration rights and permissions.
- Transportation: parts, fleet supplies, booking deposits and cancellation.
- Food/beverage: menus, availability, delivery zones, cutoffs, loyalty and operator handling.
Questions to settle before PrestaShop work.
Can one installation run several stores?
Yes, multistore is documented, but plan shop groups, domains, shared data and module compatibility first. Verify each intended setting and workflow in all-shops/group/shop context. Multiple languages alone do not require a separate shop for every language.
Can the catalogue scale?
Measure combinations, filters, search, imports, cache behaviour and concurrent purchasing on representative infrastructure. Product totals alone do not establish capacity or a point where another platform must be used.
What back-office access and source are included?
List products/combinations, orders, customers/groups, carriers, tax, multistore, reports and custom-module screens by employee role. Agree repositories/history, custom module/theme code, configuration, licences and documentation. Test setup and recovery instead of promising universal IP transfer or immediate independence.
Who manages hosting and payment activation?
Name runtime, cache, database, backups, TLS, patch and incident owners. Test provider modules, authentication, callbacks/refunds and reconciliation in approved test mode. Live activation, DNS changes and real charges need their own authority; hosted fields do not certify the complete store.
Can an existing store be taken over?
Begin with module/override/core/theme/dependency and account audits. Rehearse supported updates and replacements on staging, then agree prioritised fixes. Review source 9.x support/version claims against current official information rather than repeating a release calendar.
How are support, confidentiality and international work agreed?
Record confidentiality, custom-code rights, scope, milestones, support/defect boundaries, monitoring, contact hours and escalation in writing. Test the intended languages, currencies, tax and shipping with the responsible experts. Agree the actual contact hours, response expectations, quote and support period for the engagement.
Platform references used for technical checks.
Official documentation checked on 17 November 2026. Verify the exact version, module/theme support, API coverage and provider terms before implementation. A historical release announcement or old optimisation example is not a current deployment recipe.
- Release-specific system and PHP compatibility chart
- Admin API OAuth2, scopes and HTTPS
- Experimental multishop API flag and explicit context
- Shop groups, back-office context and compatibility caveat
- Module separation and owned data
- Profiling and optimisation with older-example caveat
- Smarty, CCC and cache controls
- Update Assistant channels, backup, update and restore
- Historical 9.0 framework and API changes
- Order-status hook parameters and shop context
- Exclusive override risks and alternatives
- Legacy Webservice resources and module extension
Bring the product rule, store or integration that needs to change.
Describe the current store, its products, customer groups, markets and operational problem. Keep the release, hosting, theme, extensions, external systems and receiving-team responsibilities visible, then agree scope and evidence before committing to implementation.
Discuss your PrestaShop scope โ