SaaS approach

Akeneo Activation is a fully managed SaaS product built and maintained by Akeneo. Because Akeneo owns the entire product lifecycle, new features and improvements are delivered continuously — without requiring any action on your part.

What the SaaS model means for you

As a SaaS product, Akeneo Activation delivers the following to every customer:

  • Continuous delivery — Akeneo deploys new versions and enhancements regularly, as with other Akeneo PXM products.
  • Zero downtime deployments — Updates are applied without interrupting your operations.
  • Single, unified access point — You access Akeneo Activation directly from your Akeneo PIM interface.
  • API-based integration — Akeneo Activation connects to your PIM via the Akeneo PIM API and to each retailer or marketplace via API or flat file, depending on what the destination channel supports.
  • Generic features by design — Because Akeneo Activation serves all customers from the same codebase, its features are built to cover the broadest possible set of use cases. The source code is not accessible or customizable.

The Akeneo Activation source code is not accessible. If you need behavior that differs from what the app provides out of the box, contact your Akeneo Customer Success Manager to discuss your requirements.

How Akeneo Activation connects to your data

Akeneo Activation uses two integration layers:

  1. Akeneo PIM API — Activation reads your product data, assets, and catalog structure directly from the PIM using the standard REST API. Catalog selection, product filtering, mapping, and transformation are configured through the Catalogs for Apps functionality, which is accessible in your PIM under Connect > Connected Apps.
  2. Retailer and marketplace APIs (or flat files) — Activation pushes product data to each destination channel using that channel's supported exchange method. When a destination does not offer an API, Activation uses flat file exchange instead.

Because both sides of the integration are API-driven, Activation operates within the limits of the APIs it connects to. It cannot push data structures or volumes that exceed what either the PIM API or the destination channel API allows. See Activation limitations for platform guidelines and channel-specific constraints.

Related