diff --git a/_data/sidebars/pbc_all_sidebar.yml b/_data/sidebars/pbc_all_sidebar.yml index fd4675b4f76..16e0832d11d 100644 --- a/_data/sidebars/pbc_all_sidebar.yml +++ b/_data/sidebars/pbc_all_sidebar.yml @@ -987,6 +987,7 @@ entries: include_versions: - "202311.0" - title: Spryker Middleware powered by Alumio + url: /docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/spryker-middleware-powered-by-alumio.html include_versions: - "202311.0" nested: diff --git a/_includes/pbc/all/data-exchange/202311.0/custom-integrations-with-alumio-connectors.md b/_includes/pbc/all/data-exchange/202311.0/custom-integrations-with-alumio-connectors.md new file mode 100644 index 00000000000..ad5bc05735c --- /dev/null +++ b/_includes/pbc/all/data-exchange/202311.0/custom-integrations-with-alumio-connectors.md @@ -0,0 +1,18 @@ +In cases where there are no integration apps for data exchange with the third-party system you need, you can build them yourself using the Alumio platform. Alumio provides a number of built-in API connectors to third-party systems that you can use to build integrations between these systems and Spryker. Check the available connectors for Spryker on the [Alumio website](https://www.alumio.com/platforms/spryker). + +With custom integrations, the data exchange process looks like this: + +
+ + + +We recommend building custom integrations with the existing Alumio connectors in the following cases: +- There is no Spryker Integration App for the system you need to integrate with. However, Alumio offers a connector for this system. +- You require a quick setup of the data exchange process, which should take up to a few days. +- You have a tech-savvy user who can configure the mapping of data for exchange between Spryker and a third-party system. +- For your project, it's important that the data exchange solution allows for the proper data orchestration like dependency management, error handling and logging, entity mapping, integration variable management, .CSV file validation, health monitoring, etc. + +For more details on how to manage integrations and exchange data in the Alumio platform, see the following information provided by Alumio: +- [The Basic Parts Of A Connector Package In Alumio](https://support.alumio.com/support/solutions/articles/80001031213-the-basic-parts-of-a-connector-package-in-alumio) +- [How To Use The Alumio Connector Packages](https://forum.alumio.com/t/how-to-use-the-alumio-connector-packages/219) +- List of Alumio standard Connector Packages: [Latest iPaaS Connector Packages](https://forum.alumio.com/c/ipaas-connector-packages/27) \ No newline at end of file diff --git a/_includes/pbc/all/data-exchange/202311.0/custom-integrations-with-custom-connectors.md b/_includes/pbc/all/data-exchange/202311.0/custom-integrations-with-custom-connectors.md new file mode 100644 index 00000000000..7a6a7446fed --- /dev/null +++ b/_includes/pbc/all/data-exchange/202311.0/custom-integrations-with-custom-connectors.md @@ -0,0 +1,24 @@ +If you have legacy systems or old version systems with which you need to exchange data and for which Alumio doesn't provide a connector, you can still build your own connector to these systems, as Alumio platform includes an Alumio SDK to build connectors. + +{% info_block warningBox "Check before implementation" %} + +Before beginning to implement any custom connector, double check if the connector with the third-party system you want to integrate with is on the list of existing Alumio standard connectors: [Alumio iPaasS Connector Packages](https://forum.alumio.com/c/ipaas-connector-packages/27). This list is continuously updated. +If the system you wish to integrate with isn't on the list, you can submit a request for the implementation of a standard connector. This will give you an opportunity to assess if it aligns with your project timelines. For details on how to submit the request, refer to [How do I request a new connector package?](https://forum.alumio.com/t/how-do-i-request-a-new-connector-package/148). + +{% endinfo_block %} + + +To build a data integration for a legacy system, you need to do the following: + +1. Have a user account on Spryker Middleware powered by Alumio. +2. Build a connector to the legacy system using the Alumio SDK. Building a connector with the Alumio SDK usually takes up to a few weeks. +3. Build the mapping and transformation of data. Initial configuration of data mapping and transformation usually takes up to a few days, and changing them takes up to a few hours. + +With the data integration with custom connectors, the data exchange process looks like this: + +
+ + +We recommend building custom integrations with the connectors created using the Alumio SDK, in cases where Alumio doesn't have the connectors to the system you want to exchange data with. Even though you need a developer to build a connector for such systems, most of the time, this solution is still faster and, in the long term, more cost-efficient than, for example, using the default Data Importers and Data Exporters. + +For information on how to build Alumio connectors with the Alumio SDK, check the Alumio documentation: [Creating Alumio Connector Packages](https://forum.alumio.com/t/creating-alumio-connector-packages/252). \ No newline at end of file diff --git a/_includes/pbc/all/data-exchange/202311.0/spryker-integration-apps.md b/_includes/pbc/all/data-exchange/202311.0/spryker-integration-apps.md new file mode 100644 index 00000000000..9b3f15e3f7d --- /dev/null +++ b/_includes/pbc/all/data-exchange/202311.0/spryker-integration-apps.md @@ -0,0 +1,32 @@ +The Integration Apps let you import data between your Spryker system and third-party systems without any development effort and without the need to configure mapping and transformation of data, as the configurations are preset. + +To exchange data between a Spryker system and a third-party system with an Integration App, you need to do the following: + +- Have a user account on Spryker Middleware powered by Alumio. +- Have the Integration App you need deployed in the Spryker Middleware powered by Alumio platform. +- Make minimum adjustments to the existing mapping and transformation of data. + +Reach out to [Spryker support](https://spryker.com/support/) or to your Customer Success Manager if you need access to the Spryker Middleware powered by Alumio and the Integration Apps. + +We recommend considering Integration Apps for data exchange in the following cases: + +- You require a quick setup of the data exchange process, which should take up to a few hours. +- You need a pre-configured mapping and transformation of data for exchange between Spryker and a third-party system, so you would have to make minimum adjustments. +- For your project, it's important that the data exchange solution allows for the proper data orchestration like dependency management, error handling and logging, entity mapping, health monitoring, etc. + +With the Spryker Integration Apps, the data exchange process looks like this: + +
+ + +Spryker provides Early Access to the [Akeneo PIM Integration App](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/akeneo-pim-integration-app.html). This Integration App allows to import products from Akeneo PIM to Spryker Cloud Commerce OS. The connector between Spryker and Akeneo is set up in a configurable way. Once new objects such as categories, attributes, or products are created or updated in Akeneo, they are transformed in the Alumio platform before the data is transferred to the Spryker Cloud Commerce OS. + +The middleware allows customers to configure data that is to be transferred to Spryker, for example, attributes and super attributes. + +{% info_block infoBox "Cold data handling" %} + +Akeneo handles the so-called “cold data”. Cold data is product information directly linked to the product that describes product properties. The Akeneo PIM Integration App doesn't include the transfer of “hot data” such as stock or pricing. + +{% endinfo_block %} + +For details on how to import data from Akeneo to Spryker, see [Configure the Akeneo PIM Integration App](/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app.html). \ No newline at end of file diff --git a/_includes/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio.md b/_includes/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio.md new file mode 100644 index 00000000000..c9049e58dcd --- /dev/null +++ b/_includes/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio.md @@ -0,0 +1,16 @@ +The Spryker Middleware powered by Alumio is a cloud-based integration Platform as a Service (iPaaS). It lets you exchange data between your Spryker system and third-party systems via a user-friendly interface. +The Spryker Middleware Powered by Alumio isn't a part of SCCOS by default. To obtain it, reach out to [Spryker support](https://spryker.com/support/). To connect the Spryker Middleware powered by Alumio with SCCOS, you need to have the [Data Exchange API feature](/docs/pbc/all/data-exchange/{{page.version}}/install-and-upgrade\install-the-data-exchange-api-inventory-management-feature.html) in your environment. + +{% info_block infoBox "Alumio" %} + +Alumio is a cloud-based iPaaS solution which is the foundation of Spryker Middleware and Spryker Integration Apps. Alumio has integrations or connectors with several solutions in its marketplace allowing to connect Spryker with other systems. + +{% endinfo_block %} + +With the Spryker Middleware powered by Alumio, the data exchange process looks like this: + +1. Transfer of data from the source system via the API connector. The data is transferred in real-time, which ensures that the data is always current across all integrated platforms. +2. Data is fed into Alumio and transformed there. +3. Transfer of data to the target system via the API connector. + +The Spryker Middleware powered by Alumio is the foundation of the Spryker Integration Apps. You can also use it to build [custom integrations](/docs/pbc/all/data-exchange/{{page.version}}/data-exchange.html#custom-integrations-with-alumio-connectors). \ No newline at end of file diff --git a/docs/pbc/all/data-exchange/202311.0/data-exchange.md b/docs/pbc/all/data-exchange/202311.0/data-exchange.md index 115c0ea8eee..5859cd05845 100644 --- a/docs/pbc/all/data-exchange/202311.0/data-exchange.md +++ b/docs/pbc/all/data-exchange/202311.0/data-exchange.md @@ -18,102 +18,19 @@ Spryker offers the following options to import and export data: ## Spryker Middleware powered by Alumio -The Spryker Middleware powered by Alumio is a cloud-based integration Platform as a Service (iPaaS). It lets you exchange data between your Spryker system and third-party systems via a user-friendly interface. -The Spryker Middleware Powered by Alumio isn't a part of SCCOS by default. To obtain it, reach out to [Spryker support](https://spryker.com/support/). - -With the Spryker Middleware powered by Alumio, the data exchange process looks like this: - -1. Transfer of data from the source system via the API connector. The data is transferred in real-time, which ensures that the data is always current across all integrated platforms. -2. Data is fed into Alumio and transformed there. -3. Transfer of data to the target system via the API connector. - - - -The Spryker Middleware powered by Alumio is the foundation of the Spryker Integration Apps. You can also use it to build [custom integrations](#custom-integrations-with-alumio-connectors). +{% include pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio.md %} ### Spryker Integration Apps -The Integration Apps let you import data between your Spryker system and third-party systems without any development effort and without the need to configure mapping and transformation of data, as the configurations are preset. - -To exchange data between a Spryker system and a third-party system with an Integration App, you need to do the following: - -- Have a user account on Spryker Middleware powered by Alumio. -- Have the Integration App you need deployed in the Spryker Middleware powered by Alumio platform. -- Make minimum adjustments to the existing mapping and transformation of data. - -Reach out to [Spryker support](https://spryker.com/support/) or to your Customer Success Manager if you need access to the Spryker Middleware powered by Alumio and the Integration Apps. - -We recommend considering Integration Apps for data exchange in the following cases: - -- You require a quick setup of the data exchange process, which should take up to a few hours. -- You need a pre-configured mapping and transformation of data for exchange between Spryker and a third-party system, so you would have to make minimum adjustments. -- For your project, it's important that the data exchange solution allows for the proper data orchestration like dependency management, error handling and logging, entity mapping, health monitoring, etc. - -With the Spryker Integration Apps, the data exchange process looks like this: - -
- - -Spryker provides Early Access to the Akeneo PIM Integration App. This Integration App allows to import products from Akeneo PIM to Spryker Cloud Commerce OS. The connector between Spryker and Akeneo is set up in a configurable way. Once new objects such as categories, attributes, or products are created or updated in Akeneo, they are transformed in the Alumio platform before the data is transferred to the Spryker Cloud Commerce OS. - -The middleware allows customers to configure data that is to be transferred to Spryker, for example, attributes and super attributes. - -{% info_block infoBox "Cold data handling" %} - -Akeneo handles the so-called “cold data”. Cold data is product information directly linked to the product that describes product properties. The Akeneo PIM Integration App doesn't include the transfer of “hot data” such as stock or pricing. - -{% endinfo_block %} - - +{% include pbc/all/data-exchange/202311.0/spryker-integration-apps.md %} ### Custom integrations with Alumio connectors -In cases where there are no integration apps for data exchange with the third-party system you need, you can build them yourself using the Alumio platform. Alumio provides a number of built-in API connectors to third-party systems that you can use to build integrations between these systems and Spryker. Check the available connectors for Spryker on the [Alumio website](https://www.alumio.com/platforms/spryker). - -With custom integrations, the data exchange process looks like this: - -
- - - -We recommend building custom integrations with the existing Alumio connectors in the following cases: -- There is no Spryker Integration App for the system you need to integrate with. However, Alumio offers a connector for this system. -- You require a quick setup of the data exchange process, which should take up to a few days. -- You have a tech-savvy user who can configure the mapping of data for exchange between Spryker and a third-party system. -- For your project, it's important that the data exchange solution allows for the proper data orchestration like dependency management, error handling and logging, entity mapping, integration variable management, .CSV file validation, health monitoring, etc. - -For more details on how to manage integrations and exchange data in the Alumio platform, see the following information provided by Alumio: -- [The Basic Parts Of A Connector Package In Alumio](https://support.alumio.com/support/solutions/articles/80001031213-the-basic-parts-of-a-connector-package-in-alumio) -- [How To Use The Alumio Connector Packages](https://forum.alumio.com/t/how-to-use-the-alumio-connector-packages/219) -- List of Alumio standard Connector Packages: [Latest iPaaS Connector Packages](https://forum.alumio.com/c/ipaas-connector-packages/27) +{% include pbc/all/data-exchange/202311.0/custom-integrations-with-alumio-connectors.md %} ### Custom integrations with custom connectors -If you have legacy systems or old version systems with which you need to exchange data and for which Alumio doesn't provide a connector, you can still build your own connector to these systems, as Alumio platform includes an Alumio SDK to build connectors. - -{% info_block warningBox "Check before implementation" %} - -Before beginning to implement any custom connector, double check if the connector with the third-party system you want to integrate with is on the list of existing Alumio standard connectors: [Alumio iPaasS Connector Packages](https://forum.alumio.com/c/ipaas-connector-packages/27). This list is continuously updated. -If the system you wish to integrate with isn't on the list, you can submit a request for the implementation of a standard connector. This will give you an opportunity to assess if it aligns with your project timelines. For details on how to submit the request, refer to [How do I request a new connector package?](https://forum.alumio.com/t/how-do-i-request-a-new-connector-package/148). - -{% endinfo_block %} - - -To build a data integration for a legacy system, you need to do the following: - -1. Have a user account on Spryker Middleware powered by Alumio. -2. Build a connector to the legacy system using the Alumio SDK. Building a connector with the Alumio SDK usually takes up to a few weeks. -3. Build the mapping and transformation of data. Initial configuration of data mapping and transformation usually takes up to a few days, and changing them takes up to a few hours. - -With the data integration with custom connectors, the data exchange process looks like this: - -
- - -We recommend building custom integrations with the connectors created using the Alumio SDK, in cases where Alumio doesn't have the connectors to the system you want to exchange data with. Even though you need a developer to build a connector for such systems, most of the time, this solution is still faster and, in the long term, more cost-efficient than, for example, using the default Data Importers and Data Exporters. - -For information on how to build Alumio connectors with the Alumio SDK, check the Alumio documentation: [Creating Alumio Connector Packages](https://forum.alumio.com/t/creating-alumio-connector-packages/252). - +{% include pbc/all/data-exchange/202311.0/custom-integrations-with-custom-connectors.md %} ## Data Exchange API diff --git a/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/akeneo-pim-integration-app.md b/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/akeneo-pim-integration-app.md new file mode 100644 index 00000000000..fb97cf2238a --- /dev/null +++ b/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/akeneo-pim-integration-app.md @@ -0,0 +1,66 @@ +--- +title: Akeneo PIM Integration App +description: Import products from Akeneo to Spryker with Akeneo PIM Integration App +last_updated: August 7, 2023 +template: concept-topic-template +--- + +The Akeneo PIM Integration App lets you import products from Akeneo PIM to your Spryker project. + +You can import the following product data: + +- General product information: Name, description, SKU, locale, stores +- Abstract product information with its variants +- Assets (images) +- Product categories +- Product attributes +- Product super attributes +- Product images +- Product relations +- Product labels +- Price types + +You can specify the product data you want to import from Akeneo when configuring the data mapping between Akeneo and SCCOS in the Spryker Middleware powered by Alumio. +For more information, see [Configure data mapping between Akeneo and SCCOS](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-data-mapping-between-akeneo-and-sccos.html) + +You can initiate the product import manually whenever you need, set up the scheduler to automatically import data on a regular basis, or use webhooks to enable the Akeneo PIM to send data to Alumio in real-time. For details on how to do that, see [Create tasks and import products from Akeneo to SCCOS](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/create-tasks-and-import-products-from-akeneo-to-sccos.html). + +## Prerequisites for the Akeneo PIM Integration App + +To use the Akeneo PIM Integration App, you need to have the Spryker Middleware powered by Alumio. To obtain it, reach out to [Spryker support](https://spryker.com/support/). +The Akeneo PIM Integration App works with B2C and B2B business models of Spryker Cloud Commerce OS (SCCOS). At the moment, it doesn't cover the Marketplace business models. + +## Importing product structure from Akeneo to Spryker + +Akeneo lets you create products with up to 3 levels of enrichment, while Spryker lets you select multiple super attributes to enrich product information and create product variants. + +For example, if you want to create a T-shirt with varying sizes and colors, here is how it is created in Akeneo: +*Root* Product Model = T-shirt +*Level 1* Product Models (created by varying colour) = Yellow T-shirt, red T-shirt +*Level 2* Product Variants (with variant: size) = Yellow T-shirt small, yellow T-shirt large, red T-shirt small, red T-shirt Large + +When importing this data into Spryker, the following applies: +- Level 1 Product Models from Akeneo are imported as abstract products into Spryker. In our example, this means that two abstract products are created in SCCOS: a yellow T-shirt and a red T-shirt. +- Level 2 variants are imported as concrete products of the abstract product. In our example, this means that two concrete products are created per each product abstract in Spryker: +- For the yellow T-shirt abstract product, a yellow T-shirt small and a yellow T-shirt large concrete products +- For the red T-shirt abstract product, a red T-shirt small and a red T-shirt large concrete products + +To identify the Product Model (abstract product) for the different Akeneo products upon import, the parent identifier is saved as the abstract SKU in Spryker. This way, the hierarchy and relationship between the products is preserved after the import. + +The following table represents the high-level mapping of product data between Akeneo and Spryker: + +| Akeneo | Spryker | Note | +|-----------------------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Product Model | Abstract Product | | +| Family | Abstract Product | | +| Product | Concrete Product | | +| Family Variant | Concrete Product | Spryker uses the family variant structure to determine the relationship between the Abstract and Concrete Product | +| Family Variant (axes) | Super Attribute | Spryker uses the family variant axes to identify the super attribute. However, for the sake of accuracy, make sure to specify the super attributes when configuring the [Memo Base to Spryker - Product - Akeneo Preprocessor](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-data-mapping-between-akeneo-and-sccos.html#memo-base-to-spryker---product---akeneo-preprocessor) | +| Category | Category | | +| Attribute | Attribute | | +| Localized Labels | Locales | | + +## Next steps +[Configure the Akeneo PIM Integration App](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app.html) + + diff --git a/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-data-mapping-between-akeneo-and-sccos.md b/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-data-mapping-between-akeneo-and-sccos.md index 9d9379d1ffa..7013eeb5452 100644 --- a/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-data-mapping-between-akeneo-and-sccos.md +++ b/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-data-mapping-between-akeneo-and-sccos.md @@ -88,7 +88,14 @@ If the locale isn't specified in Akeneo, the locale you specify at this step wil ![value-as-sku](https://spryker.s3.eu-central-1.amazonaws.com/docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/3-configure-data-mapping-between-akeneo-and-spryker/value-as-sku.png) 4. In *Name*, either enter the name for your products, or if you want to import it from Akeneo, use the `&{values.name}` as a placeholder. 5. In *Description*, either enter the description for your products, or if you want to import it from Akeneo, use the `&{values.description}` as a placeholder. -6. In *Short description*, either enter the short description for your products or if you want to import it from Akeneo, use the `&{values.short_description}` as a placeholder. + +{% info_block infoBox "Importing product descriptions" %} + +Spryker uses a simple text editor in its product description, however Akeneo enables customers to use rich-text in their product description. If you want to use rich-text on your store you need to extend Spryker to enable the support of rich text on a project-level. + +{% endinfo_block %} + +6. In *Short description*, either enter the short description for your products, or if you want to import it from Akeneo, use the `&{values.short_description}` as a placeholder. 7. Optional: Define the tax set to use for the imported products. Do the following: 1. Go to your Spryker project's Back Office, to **Administration -> Tax Sets** page. 2. On the *Overview of tax sets* page, copy the value from the *Name* column of the tax set you want to use for the products imported from Akeneo PIM. diff --git a/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/integration-apps/integration-apps.md b/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/integration-apps/integration-apps.md new file mode 100644 index 00000000000..f4cec1b7fe6 --- /dev/null +++ b/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/integration-apps/integration-apps.md @@ -0,0 +1,9 @@ +--- +title: Integration Apps +description: General information about the integration apps. +template: concept-topic-template +--- +An Integration App is a flexible end-to-end solution that aims to build data integrations in close to one day. With an Integration App, you have access to the default data mappings, transformers, data validators and other preset configurations for a specific data integration use-case. +Spryker Integration Apps are built using Spryker demoshops data models as a default mapping, that you may use and then adjust the configuration to you specific use-case. +Spryker provides the [Akeneo PIM Integration App](/docs\pbc\all\data-exchange\{{page.version}}spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/akeneo-pim-integration-app.html) that lets you import products from Akeneo PIM to Spryker Cloud Commerce OS. + \ No newline at end of file diff --git a/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/spryker-middleware-powered-by-alumio.md b/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/spryker-middleware-powered-by-alumio.md new file mode 100644 index 00000000000..32580e320ac --- /dev/null +++ b/docs/pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio/spryker-middleware-powered-by-alumio.md @@ -0,0 +1,19 @@ +--- +title: Spryker Middleware powered by Alumio +description: General information about the data exchange options. +template: concept-topic-template +--- + +{% include pbc/all/data-exchange/202311.0/spryker-middleware-powered-by-alumio.md %} + +## Spryker Integration Apps + +{% include pbc/all/data-exchange/202311.0/spryker-integration-apps.md %} + +## Custom integrations with Alumio connectors + +{% include pbc/all/data-exchange/202311.0/custom-integrations-with-alumio-connectors.md %} + +## Custom integrations with custom connectors + +{% include pbc/all/data-exchange/202311.0/custom-integrations-with-custom-connectors.md %} \ No newline at end of file