Skip to content
E-commerce ⇄ Database

Akeneo to Azure Cosmos DB integration — real-time, two-way sync

Keep Akeneo and Azure Cosmos DB 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 Azure Cosmos DB

Give your engineers Akeneo's products, orders, and customers in Azure Cosmos DB: 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 Product models, Categories, Attributes, Families and family variants from Akeneo into Azure Cosmos DB 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 Azure Cosmos DB, 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 Consolidate documents from multiple containers into a single reporting store.
  • 02 Stream operational documents from Cosmos DB into a SQL warehouse via the change feed for analytics without hitting request-unit budgets with full scans.
  • 03 Write Categories, Families, and Attributes from an ERP or supplier feed into Akeneo to build and maintain catalog structure.
  • 04 Read Reference entities records such as brands and manufacturers into a data warehouse for cross-catalog reporting.

Common sync patterns

React to store changes

Updates in Akeneo arrive as row changes in Azure Cosmos DB, 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 Azure Cosmos DB 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 Azure Cosmos DB for routing, fulfillment, and reporting, without polling the platform.

What you can sync between Akeneo and Azure Cosmos DB

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 Azure Cosmos DB objects How this pairing syncs
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. Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. Channels and locales is specific to Akeneo and Items (JSON documents) to Azure Cosmos DB — each maps to any object or custom field on the other side.
Media files Product images and files uploaded via the media endpoint; referenced by products and pushed to downstream commerce and content systems. Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. Media files is specific to Akeneo and Partition keys to Azure Cosmos DB — each maps to any object or custom field on the other side.
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. Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. Products is specific to Akeneo and Change feed entries to Azure Cosmos DB — each maps to any object or custom field on the other side.
Product models Parent records for configurable products; hold shared attribute values that cascade to their variant products, synced alongside Products. Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. Product models is specific to Akeneo and Stored procedures and triggers to Azure Cosmos DB — 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. Databases Top-level namespaces that scope containers and throughput provisioning. Categories is specific to Akeneo and Databases to Azure Cosmos DB — 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. Containers The unit of partitioning and throughput; each container maps to a synced collection. Attributes is specific to Akeneo and Containers to Azure Cosmos DB — each maps to any object or custom field on the other side.

How changes propagate between Akeneo and Azure Cosmos DB

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 Azure Cosmos DB 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 applied to Azure Cosmos DB as a row-level write, with types converted between the two schemas.

Azure Cosmos DB Akeneo Sub-second propagation

DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.

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.
What ships with Akeneo ⇄ Azure Cosmos DB

Connect Akeneo and Azure Cosmos DB for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Akeneo ⇄ Azure Cosmos DB 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 Azure Cosmos DB.

How the Akeneo and Azure Cosmos DB 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.

Azure Cosmos DB

Integration surface
REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
Authentication
Account keys, resource tokens, or Microsoft Entra ID role-based access
Change detection
Built-in change feed exposing inserts and updates in order within each partition key range
Capabilities
read · write · CDC
How it works

How to connect Akeneo to Azure Cosmos DB — 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 Azure Cosmos DB 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
    Azure Cosmos DB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Akeneo and Azure Cosmos DB 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 ⇄ Azure Cosmos DB
    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 Azure Cosmos DB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Akeneo and Azure Cosmos DB 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 396 integrations available for Akeneo and Azure Cosmos DB.

Popular · 7 of 396
All Akeneo integrations All Azure Cosmos DB 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