Skip to content
E-commerce ⇄ Database

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

Keep Akeneo and Citus 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 Citus

Give your engineers Akeneo's products, orders, and customers in Citus: 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 Reference entities and records, Assets, Channels and locales, Media files from Akeneo into Citus 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 Citus, 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 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
  • 02 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
  • 03 Push enriched Products and their Assets into an ecommerce storefront or commerce database when product.created and product.updated webhooks fire.
  • 04 Write Categories, Families, and Attributes from an ERP or supplier feed into Akeneo to build and maintain catalog structure.

Common sync patterns

React to store changes

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

What you can sync between Akeneo and Citus

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 Citus 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. Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Product models is specific to Akeneo and Local tables to Citus — 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. Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Categories is specific to Akeneo and Schemas to Citus — 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. Views Curated projections over distributed data, often used as read-only sync sources. Attributes is specific to Akeneo and Views to Citus — 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. Sequences Key generators that matter when external writes must not collide with application inserts. Families and family variants is specific to Akeneo and Sequences to Citus — 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. Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Reference entities and records is specific to Akeneo and Distributed tables to Citus — 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. Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Assets is specific to Akeneo and Reference tables to Citus — each maps to any object or custom field on the other side.

How changes propagate between Akeneo and Citus

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 Citus 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 Citus as a row-level write, with types converted between the two schemas.

Citus Akeneo Sub-second propagation

DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.

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 ⇄ Citus

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Akeneo ⇄ Citus 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 Citus.

How the Akeneo and Citus 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.

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC
How it works

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

    Choose tables

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

Akeneo and Citus 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 390 integrations available for Akeneo and Citus.

Popular · 7 of 390
All Akeneo integrations All Citus 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