Eco modules

Overview of Eco modules

Eco Modules are essential building blocks for extending the Spryker Commerce OS, enabling businesses to integrate seamlessly with external systems and services.

At their core, Eco modules act as connectors or adapters. They bridge the functionality of Spryker Commerce OS with third-party systems and services, empowering your platform to handle tasks like payment processing, product information management, and system monitoring without needing to reinvent the wheel.

For instance, instead of building a custom payment integration from scratch, you can leverage the Spryker Eco Module for Adyen to handle payments reliably and securely.

Location of Eco modules

Understanding where Eco modules live in your project directory is key to maintaining a clean and organized codebase. You’ll find them under the vendor/spryker-eco/ directory, which distinguishes them from:

• Spryker Core Modules: Located under vendor/spryker/, these are the essential building blocks of the Spryker OS.
• Project Specific Code: Usually found in src/Pyz/, this is where your team implements customizations and business logic tailored to your project.

This clear separation helps developers navigate the project more efficiently and keeps external integrations modular and easy to manage.

Installation of Eco modules

Eco Modules are installed using Composer, just like other dependencies in a PHP project. They follow a consistent naming convention, using the spryker-eco/ prefix in their package names. For example:

• spryker-eco/adyen
• spryker-eco/akeneo-connector

This naming standard makes it easy to identify Eco modules and differentiate them from core packages or other vendor dependencies.

Eco module examples

The functionality of Eco modules is diverse, enabling Spryker applications to harness the power of external partners and services. Common use cases include:

• Payment: Processing payments through providers like Adyen or CrefoPay.
• Product information management: Synchronizing product data with solutions like Akeneo.
• Monitoring: Sending performance data to services like New Relic for tracking and analysis.

These modules simplify the integration of powerful external tools, saving development time and reducing the risk of errors that can come with custom implementations.

Relationship to Spryker core code

Although Eco modules are distributed separately from the Spryker core, they’re designed to integrate seamlessly. They leverage Spryker’s standardized extension mechanisms, including plugins and dependency providers, making them as extensible and customizable as the core modules themselves.

This consistent approach means you can treat Eco modules like any other Spryker module, adapting or extending them to meet your project’s specific needs.

Using Eco modules

In essence, Eco modules provide a standardized and maintainable way to enhance Spryker by connecting it to the broader technology ecosystem. They empower businesses to build tailored, best of breed solutions that combine the strength of Spryker with the capabilities of leading third-party services.

With Eco Modules, you’re not limited by what’s built into the Spryker core – you can tap into a world of possibilities, driving innovation and differentiation in your ecommerce platform.