Skip to content
E-commerce

Connect Akeneo to any app with two-way sync.

Two-way sync Akeneo across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Object catalog

What Stacksync syncs in Akeneo.

These objects sync between Akeneo and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Akeneo exposes them.

Products
Core catalog records addressed by UUID (recommended) or identifier/SKU; synced two-way with databases, ERPs, and storefronts. Values are scoped per channel and locale.
Product models
Parent records for configurable products; hold shared attribute values that cascade to their variant products, synced alongside Products.
Categories
The category tree used to classify products; read out for storefront navigation or written in from an ERP to seed catalog structure.
Attributes
Attribute definitions plus attribute options and groups; describe the shape of product data, usually mastered in Akeneo and read downstream.
Families and family variants
Templates defining which attributes a product carries and how variants axis out; synced to keep catalog structure consistent across systems.
Reference entities and records
Structured lookups like brands, manufacturers, or ingredients with their own records (Enterprise Edition); synced two-way or read into a warehouse for reporting.
Assets
Asset-family media (images, documents) managed in Akeneo's DAM; linked to products and synced to storefronts and commerce systems.
Channels and locales
Target-market settings that scope attribute values; read to resolve which localized or channel-specific value to map on each side of a sync.
Media files
Product images and files uploaded via the media endpoint; referenced by products and pushed to downstream commerce and content systems.
API surface

How Stacksync connects to Akeneo.

The connector runs on Akeneo's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
REST API (plus a GraphQL API) and an Events API for webhooks
Authentication
OAuth2 password grant: client_id/secret plus an API user's username/password exchanged at /api/oauth/v1/token for a bearer access_token and refresh_token; Apps use the OAuth2 authorization-code flow
Change detection
Events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents; product.updated.delta carries old and new values); falls back to polling the 'updated' datetime search filter where the Events API is unavailable
Rate limits
REST protection triggers above roughly 100 requests/second per PIM instance (HTTP 429 with Retry-After); the Events API caps at 4000 requests/hour with a 500ms webhook ack timeout.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
What ships with Akeneo

Connect Akeneo for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every connection.

Real-time

Two-way sync

Changes in Akeneo instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Akeneo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Akeneo record.

Observability

Monitoring

Track your Akeneo sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Akeneo connector.

Akeneo is the product-information (PIM) system of record for ecommerce, catalog, and merchandising teams, typically owned by PIM managers and product-data operations. It holds the enriched catalog: Products and product models, Families and family variants, Categories, Attributes, Reference entities, and Assets, with values scoped per channel and locale. It feeds storefronts, marketplaces, and print, so retail and manufacturing teams read enriched data out of it and write structured catalog data back in.

  • PIM managers
  • Ecommerce and catalog managers
  • Product data operations
  • Merchandising teams
  • Integration engineers

  1. Two-way sync Products and product models with an operational Postgres database or ERP so SKUs, prices, and localized descriptions stay aligned across systems.

  2. Push enriched Products and their Assets into an ecommerce storefront or commerce database when product.created and product.updated webhooks fire.

  3. Write Categories, Families, and Attributes from an ERP or supplier feed into Akeneo to build and maintain catalog structure.

  4. Read Reference entities records such as brands and manufacturers into a data warehouse for cross-catalog reporting.

  5. Mirror Products and completeness data into a warehouse to track enrichment progress by channel and locale without manual CSV exports.

  6. Two-way sync Products and product models between Akeneo and an operational Postgres or ERP so SKUs, prices, and localized descriptions stay aligned; edits in either system propagate on product.updated events.

All Akeneo integrations

Pick the system you need to keep in sync with Akeneo. Each page covers the sync setup, field mapping, and common workflows for that pair.

CRM · 45

ERP · 38

Database · 50

Data warehouse · 29

Accounting and finance · 17

How it works

Set up Akeneo in minutes, without APIs.

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Akeneo with its native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Akeneo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Akeneo objects to sync — Stacksync auto-detects the schema, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Akeneo
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Akeneo database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Akeneo connector FAQ

What can I sync with the Akeneo connector?

Akeneo's core objects — Products, Product models, Categories, Attributes and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Akeneo?

Via REST API (plus a GraphQL API) and an Events API for webhooks, authenticated with OAuth2 password grant: client_id/secret plus an API user's username/password exchanged at /api/oauth/v1/token for a bearer access_token and refresh_token; Apps use the OAuth2 authorization-code flow. Changes are detected as follows — events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents; product.updated.delta carries old and new values); falls back to polling the 'updated' datetime search filter where the Events API is unavailable. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Akeneo connector two-way?

Yes. Changes made in Akeneo propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does an Akeneo integration take to set up?

Most Akeneo integrations go live in minutes: authenticate Akeneo and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Akeneo data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Akeneo data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own