Presentation of PrestaShop Enterprise for internal use

This report synthesizes all the key information that support and sales representatives can convey to merchants regarding PrestaShop Enterprise, with an emphasis on access to demo versions and the technical aspects related to the installation of modules or imported libraries.

1. General presentation of PrestaShop Enterprise

PrestaShop Enterprise is distinguished by its performance, stability, and the ability to offer sustainable and secure customization. The main advantages to highlight to merchants include:

• Optimized performance: ultra-fast loading times, better management of SQL queries.
• Controlled customization: verified and fully compatible modules are available on the marketplace, ensuring security and stability.
• Regular and transparent updates: enhanced security, facilitated migration.
• Total control: the merchant retains ownership of their store and their data.
• Scalability: the solution automatically supports the growth of the business, from launch to large volumes.
• Dedicated support: a team of experts and resources are available to assist merchants.

Key features to highlight.

• Managed hosting (scalable, optimized, maintained)
• Boosted performance (+90% of requests processed, reduced TTFB)
• Automatic updates (core, native modules, security)
• Monitoring 24/7 (supervision proactive)
• Integrated CDN (loading acceleration)
• Dedicated expert support (email & phone)
• Agency compatibility (API, web services, facilitated integration)
• Classic back-office (no retraining required)
• Compliance with open-core (no lock-in, migration possible)

Access and use of demonstration environments

Access to demos

Support and sales teams may offer agencies access to demonstration environments to explore the features of Enterprise, subject to funding. Several environments are available: development, staging, and production. It is recommended to use the staging environment to simulate the experience of a merchant.

For merchants, demos can be offered, but without providing access to the environment.

• Link to demo instructions for agencies: https://www.notion.so/prestashopcorp/Enterprise-Demo-Environment-for-Certified-Agencies-2105d6cf071f803cbf6be8ee109522b8
• Link to access the environment management dashboard: https://enterprise.prestashop.com/dashboard
• Direct access to a demo store (back office): Example of a link to access a demo back office.

What the demo allows to showcase.

• Filtered marketplace with certified modules.
• Visualization of subscription consumption.
• Dedicated performance page (coming online soon).
• Demonstration of quality controls during the installation of modules (examples of modules generating PHP errors, others without errors, or generating override errors).
• Access to developer tools (SDK, technical guidelines).

Supplementary resources.

• SDK Documentation: https://prestashopcorp.github.io/prestashop-docs/prestashop_enterprise/software-developer-kit/
• Enterprise Guidelines: https://prestashopcorp.github.io/prestashop-docs/prestashop_enterprise/guidelines/enterprise_guidelines/

• Enterprise Landing Page (official site)

  Detailed presentation of the offer, benefits, included modules, customer testimonials.

  https://prestashop.com/prestashop-offers/enterprise/

3. Installation of imported modules and libraries

General principles

• Certified modules: Only modules validated for Enterprise are guaranteed to be compatible. A selection of 116 modules has been made based on the most common needs of merchants, best sellers, and security/performance criteria. These modules are directly accessible from the back-office marketplace.
• Custom modules: It is possible to install custom modules or those purchased outside of the selection, but they should preferably comply with Enterprise compatibility standards.

Installation procedure

• The standard installation is carried out via the administration interface, under the "Modules" tab. The module must be provided in ZIP format and install without manual file manipulation.
• The module configuration must offer a clear page, allowing the merchant to enter their credentials or create an account if necessary.
• Any external dependency (PHP library, extension) must be declared and verified during installation. If a required PHP extension is not present, the module must notify the merchant and not proceed with the installation.

Technical constraints and limitations

• No modification of the Core: It is strictly prohibited to modify the PrestaShop core files, under penalty of making any future updates impossible and exiting the Enterprise scope.
• Management of libraries (vendor): In the event of dependency conflicts (for example, two modules using different versions of the same library), it is recommended to use PHP-Scoper to isolate the dependencies in a namespace specific to the module. Refer to the official documentation for managing the vendor folder.
• Hooks: All hooks used must be declared in the theme to ensure the proper functioning of the modules. It is preferable to use hooks rather than overrides when possible.
• Testing and validation: Before any production deployment, it is advisable to use a staging environment to test the installation and compatibility of the modules.
• PHP and server compatibility: The modules must check for the presence of the necessary PHP extensions and adhere to the recommended memory/execution time limits (32 M minimum for memory, 30 s for execution time).
• Security: Prioritize the use of PrestaShop validation tools and refer to the guidelines to avoid common vulnerabilities (permission management, file protection, etc.).

Points of attention for imported libraries

• Dependency collisions: The shared PHP environment among modules can generate errors if two modules use incompatible versions of the same library. Isolation via PHP-Scoper is the recommended solution, but it complicates development and may increase the size/memory of the module.
• Absence of centralized management: PrestaShop does not impose centralized management of dependencies via Composer for modules, which can complicate maintenance during updates.
• Risks associated with evolution: Unupdated modules may become incompatible, and migrating to a more stringent ecosystem may incur additional costs for merchants.

Support and resources for merchants

• Dedicated technical support: Merchants benefit from assistance for the validation and installation of custom modules, as well as for resolving compatibility issues.
• Centralized knowledge base: FAQs, technical documentation, and onboarding guides are regularly updated to address recurring questions and share best practices.
• Diagnostic tools: CLI tools, SDKs, and development and staging environments are made available to facilitate testing prior to any production deployment.

5. Advice to convey to merchants

• Always prioritize the installation of validated Enterprise modules to ensure the stability and longevity of the store.
• In the event of a need for specific modules not listed, seek the assistance of an agency or support to validate compatibility.
• Never modify the PrestaShop core or use overrides without prior validation by PrestaShop.
• Systematically test any new installation in a staging environment before moving to production.
• Refer to the guidelines and official documentation for any technical questions or advanced customization projects.

Responses to common objections

• "I can keep the open-source version"

  Open-source remains possible but requires more management, budget, and technical expertise. Enterprise offers better performance, scalability, security, and ongoing maintenance.

• "It is too expensive."

  The cost is offset by the reduction in breakdowns, slowdowns, and technical interventions. The ROI is measurable: increased conversions, reduced friction. Numerous tools and exclusive modules are made available in the Enterprise package to ensure these benefits.

• "I already have an agency"

  Enterprise integrates with your current partner, enhances security and performance, and allows everyone to focus on added value.

• "Little traffic"

  The important factor is profitability per visitor: speed, stability, and improved search engine optimization enhance conversion.

• "Closed solution?"

  No: code and data remain accessible. No proprietary lock-in.

• "I want to be able to leave."

  Migration is possible at any time, as with any PrestaShop instance.

• "I have a good developer."

  He will be able to focus on creating value, not on maintenance or patches.

In summary, the support and sales teams must emphasize security, compatibility, ease of evolution, and the quality of support offered by PrestaShop Enterprise, while raising merchants' awareness of best practices for the installation of imported modules and libraries, and providing them with access to demonstration environments to validate the suitability of the solution for their needs.