Skip to content
E-commerce ⇄ ERP

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

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

Keep the storefront in step with the back office: Akeneo and Odoo share products, inventory, and orders in real time, in both directions.

Akeneo runs the storefront and takes the orders; Odoo owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.

Stacksync syncs Assets, Channels and locales, Media files, Products in Akeneo with Contacts (res.partner), Sales Orders (sale.order), Invoices (account.move), Products (product.template / product.product) in Odoo field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Odoo, order and customer detail from Akeneo — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Two-way sync Products and product models with an operational Postgres database or ERP so SKUs, prices, and localized descriptions stay aligned across systems.
  • 02 Push enriched Products and their Assets into an ecommerce storefront or commerce database when product.created and product.updated webhooks fire.
  • 03 Mirror invoices and journal entries into a warehouse for consolidated financial reporting across entities.
  • 04 Keep product and price list data aligned between Odoo and storefronts or marketplaces.

Common sync patterns

One customer master

Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.

Where Odoo is the inventory system of record: stock stays accurate

Available quantities from Odoo publish to Akeneo, so the store shows what can actually ship and stops overselling.

New orders reach the back office

An order captured in Akeneo creates the matching record in Odoo with customer, line items, and totals, so fulfillment and invoicing start without re-entry.

What you can sync between Akeneo and Odoo

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 Odoo objects How this pairing syncs
Families and family variants Templates defining which attributes a product carries and how variants axis out; synced to keep catalog structure consistent across systems. Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. Families and family variants is specific to Akeneo and Inventory Transfers (stock.picking) to Odoo — 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. Employees (hr.employee) HR records read for directory and provisioning syncs. Reference entities and records is specific to Akeneo and Employees (hr.employee) to Odoo — 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. Projects and Tasks (project.project / project.task) Work items synced with external project tools. Assets is specific to Akeneo and Projects and Tasks (project.project / project.task) to Odoo — each maps to any object or custom field on the other side.
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. Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. Channels and locales is specific to Akeneo and Contacts (res.partner) to Odoo — 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. Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. Media files is specific to Akeneo and Sales Orders (sale.order) to Odoo — 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. Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. Products is specific to Akeneo and Invoices (account.move) to Odoo — each maps to any object or custom field on the other side.

How changes propagate between Akeneo and Odoo

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 Odoo 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 Odoo through its API, with automatic retries and rate-limit backoff.

Odoo Akeneo Sub-second propagation

DetectionOdoo notifies Stacksync of record changes through webhook events. Polling on the write_date timestamp every record carries.

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.
  • Odoo: Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits.
What ships with Akeneo ⇄ Odoo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Odoo

Integration surface
XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink)
Authentication
Database user credentials or per-user API keys
Change detection
Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules
Capabilities
read · write · webhooks
Rate limits
Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits
How it works

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

    Choose tables

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

Akeneo and Odoo 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 Odoo.

Popular · 7 of 478
All Akeneo integrations All Odoo 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