Skip to content
E-commerce ⇄ ERP

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

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

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

Magento 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 Orders, Customers, Inventory source items (MSI), Invoices in Magento with Products (product.template / product.product), CRM Leads (crm.lead), Purchase Orders (purchase.order), Inventory Transfers (stock.picking) 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 Magento — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Read new Orders to trigger provisioning, accounting, or 3PL fulfillment in an operational database as they are placed.
  • 02 Sync Orders, invoices, and shipments from Magento into Postgres or a warehouse for revenue, margin, and fulfillment-SLA reporting.
  • 03 Keep product and price list data aligned between Odoo and storefronts or marketplaces.
  • 04 Sync employee records from an HR system of record into Odoo for expense and timesheet workflows.

Common sync patterns

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

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

New orders reach the back office

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

One product catalog

Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.

What you can sync between Magento 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.

Magento objects Odoo objects How this pairing syncs
Inventory source items (MSI) Per-source stock quantities under Multi-Source Inventory; written from a WMS/ERP so storefront stock matches the warehouse. Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. Inventory source items (MSI) is specific to Magento and Invoices (account.move) to Odoo — each maps to any object or custom field on the other side.
Invoices Invoice documents tied to orders; read out for finance and revenue recognition, or created via the sales API when billing downstream. Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools. Invoices is specific to Magento and Products (product.template / product.product) to Odoo — each maps to any object or custom field on the other side.
Shipments Shipment and tracking records against orders; created or read to drive fulfillment status between Magento and a 3PL/WMS. CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems. Shipments is specific to Magento and CRM Leads (crm.lead) to Odoo — each maps to any object or custom field on the other side.
Carts / quotes Active and guest carts (quotes) with items and totals; read for abandoned-cart analysis (not available on the Cloud Service subset). Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems. Carts / quotes is specific to Magento and Purchase Orders (purchase.order) to Odoo — each maps to any object or custom field on the other side.
Products Catalog items keyed by SKU; carry created_at/updated_at for incremental polling and are written two-way from a PIM or ERP into the storefront. Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. Products is specific to Magento and Inventory Transfers (stock.picking) to Odoo — each maps to any object or custom field on the other side.
Configurable / variant products Parent configurable products link to simple product variants by attribute; synced so size/color SKUs and their prices stay aligned with source systems. Employees (hr.employee) HR records read for directory and provisioning syncs. Configurable / variant products is specific to Magento and Employees (hr.employee) to Odoo — each maps to any object or custom field on the other side.

How changes propagate between Magento 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.

Magento Odoo Sub-second propagation

DetectionMagento notifies Stacksync of record changes through webhook events. Polling with searchCriteria filters on updated_at (catalog, sales, and customer entities carry created_at/updated_at).

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

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

Rate-limit considerations

  • Magento: No fixed request-per-minute cap on PaaS/on-prem; responses page via searchCriteria pageSize/currentPage under a default maximum page size of 300 (Web API Input Limits), with /async/bulk endpoints for large writes.
  • Odoo: Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits.
What ships with Magento ⇄ Odoo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Magento and Odoo.

How the Magento and Odoo connectors work

Magento

Integration surface
REST and GraphQL Web APIs (SOAP also available)
Authentication
Token-based OAuth: an integration's access token (consumer key/secret + access token/secret) or a Bearer admin token (default 4-hour expiry); Adobe Commerce as a Cloud Service authenticates via Adobe IMS (OAuth 2)
Change detection
Polling with searchCriteria filters on updated_at (catalog, sales, and customer entities carry created_at/updated_at); optional near-real-time via the Adobe Commerce Webhooks / Adobe I/O Events modules (order/created, product/updated, customer/created)
Capabilities
read · write · webhooks
Rate limits
No fixed request-per-minute cap on PaaS/on-prem; responses page via searchCriteria pageSize/currentPage under a default maximum page size of 300 (Web API Input Limits), with /async/bulk endpoints for large writes.

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 Magento 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 Magento 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
    Magento connected
    Odoo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

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

Popular · 7 of 478
All Magento 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