Skip to content
E-commerce ⇄ Database

Akeneo to Elasticsearch integration — real-time, two-way sync

Keep Akeneo and Elasticsearch in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • 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
Why teams connect Akeneo and Elasticsearch

Give your engineers Akeneo's products, orders, and customers in Elasticsearch: read them with normal queries, write inventory and prices back through the sync, and skip the storefront API.

E-commerce data sits behind an API built for the storefront, not for your internal systems. Teams that need those records, for order routing, inventory logic, reporting, or back-office tools, end up writing integration code against a rate-limited API and maintaining it through every catalog change and platform upgrade.

Stacksync mirrors Families and family variants, Reference entities and records, Assets, Channels and locales from Akeneo into Elasticsearch and keeps both sides consistent in real time. Whatever Akeneo holds, whether products, orders, customers, or inventory, those records become rows your code can query, and changes written in Elasticsearch, such as new prices, stock levels, or fulfillment status, sync back into Akeneo with its validations respected.

Merchandising and operations keep working in the storefront, engineers keep working in the database, and neither side has to reconcile against a nightly export.

Common use cases

  • 01 Sync CRM accounts and contacts into an Elasticsearch index to power internal search across customer records.
  • 02 Push product catalog data from an ERP or commerce database into Elasticsearch for storefront search.
  • 03 Mirror Products and completeness data into a warehouse to track enrichment progress by channel and locale without manual CSV exports.
  • 04 Two-way sync Products and product models with an operational Postgres database or ERP so SKUs, prices, and localized descriptions stay aligned across systems.

Common sync patterns

React to store changes

Updates in Akeneo arrive as row changes in Elasticsearch, so jobs and triggers can respond the moment an order, price, or stock level changes.

Keep catalog and inventory current

Prices, stock levels, or product details maintained in Elasticsearch sync back onto Akeneo, so the storefront shows what your systems treat as true.

Order data where your code can use it

Orders and their status become rows in Elasticsearch for routing, fulfillment, and reporting, without polling the platform.

What you can sync between Akeneo and Elasticsearch

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Akeneo objects Elasticsearch objects How this pairing syncs
Product models Parent records for configurable products; hold shared attribute values that cascade to their variant products, synced alongside Products. Aliases Stable read/write names that let a sync cut over between index versions without downtime. Product models is specific to Akeneo and Aliases to Elasticsearch — each maps to any object or custom field on the other side.
Categories The category tree used to classify products; read out for storefront navigation or written in from an ERP to seed catalog structure. Data streams Append-only targets for time-series or event data pushed from source systems. Categories is specific to Akeneo and Data streams to Elasticsearch — each maps to any object or custom field on the other side.
Attributes Attribute definitions plus attribute options and groups; describe the shape of product data, usually mastered in Akeneo and read downstream. Ingest pipelines Server-side transforms applied to documents as a sync writes them. Attributes is specific to Akeneo and Ingest pipelines to Elasticsearch — each maps to any object or custom field on the other side.
Families and family variants Templates defining which attributes a product carries and how variants axis out; synced to keep catalog structure consistent across systems. Index templates Reusable settings and mappings applied automatically to new indices a sync creates. Families and family variants is specific to Akeneo and Index templates to Elasticsearch — each maps to any object or custom field on the other side.
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. Indices Target containers for synced records; each holds a table-like collection of JSON documents. Reference entities and records is specific to Akeneo and Indices to Elasticsearch — each maps to any object or custom field on the other side.
Assets Asset-family media (images, documents) managed in Akeneo's DAM; linked to products and synced to storefronts and commerce systems. Documents The unit of sync; JSON records created, updated, and deleted by _id. Assets is specific to Akeneo and Documents to Elasticsearch — each maps to any object or custom field on the other side.

How changes propagate between Akeneo and Elasticsearch

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Akeneo Elasticsearch Sub-second propagation

DetectionAkeneo notifies Stacksync of record changes through webhook events. Events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents.

DeliveryEach detected change is written to Elasticsearch through its API, with automatic retries and rate-limit backoff.

Elasticsearch Akeneo Interval-based propagation

DetectionStacksync polls Elasticsearch for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or sequence fields.

DeliveryEach detected change is written to Akeneo through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Akeneo: 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.
  • Elasticsearch: No fixed request quota; throughput is bounded by cluster sizing, thread pools, and bulk queue capacity.
What ships with Akeneo ⇄ Elasticsearch

Connect Akeneo and Elasticsearch for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Akeneo or Elasticsearch instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Akeneo or Elasticsearch 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 or Elasticsearch record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Akeneo and Elasticsearch.

How the Akeneo and Elasticsearch connectors work

Akeneo

Integration surface
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
Capabilities
read · write · webhooks
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.

Elasticsearch

Integration surface
REST API (JSON over HTTP)
Authentication
API keys or basic authentication; Elastic Cloud also issues service account tokens
Change detection
Polling on timestamp or sequence fields; Elasticsearch does not expose a native change feed or webhooks
Capabilities
read · write
Rate limits
No fixed request quota; throughput is bounded by cluster sizing, thread pools, and bulk queue capacity
How it works

How to connect Akeneo to Elasticsearch — three steps, no code

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 and Elasticsearch with each platform's 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
    Elasticsearch connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Akeneo and Elasticsearch objects to sync — Stacksync auto-detects both schemas, 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 ⇄ Elasticsearch
    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 Elasticsearch
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Akeneo and Elasticsearch integration FAQ

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

Related integrations

Every pair below is a real-time, two-way sync. Search all 478 integrations available for Akeneo and Elasticsearch.

Popular · 8 of 478
All Akeneo integrations All Elasticsearch integrations Browse all integrations
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