Skip to content
ERP ⇄ E-commerce

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

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

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

Shopware 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 Media, Products, Categories, Customers in Shopware with Purchase Orders (purchase.order), Inventory Transfers (stock.picking), Employees (hr.employee), Projects and Tasks (project.project / project.task) 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 Shopware — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Stream new `order` records with their `order_line_item`, `order_delivery`, and `order_transaction` rows into a warehouse or accounting system for revenue and fulfillment reporting.
  • 02 Sync `customer` records two-way with a CRM so support and marketing see order history while reps write updates back onto the account.
  • 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 Shopware, so the store shows what can actually ship and stops overselling.

New orders reach the back office

An order captured in Shopware 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 Odoo and Shopware

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.

Odoo objects Shopware objects How this pairing syncs
Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. Products The product catalog (`product`), including parent/child variants, per-currency nested price arrays, and stock; synced two-way with ERP, PIM, or a database. Sales Orders (sale.order) is specific to Odoo and Products to Shopware — each maps to any object or custom field on the other side.
Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. Invoices (account.move) is specific to Odoo and Categories to Shopware — each maps to any object or custom field on the other side.
Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Products (product.template / product.product) is specific to Odoo and Customers to Shopware — each maps to any object or custom field on the other side.
CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems. Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. CRM Leads (crm.lead) is specific to Odoo and Orders to Shopware — each maps to any object or custom field on the other side.
Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Purchase Orders (purchase.order) is specific to Odoo and Order Line Items to Shopware — each maps to any object or custom field on the other side.
Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. Inventory Transfers (stock.picking) is specific to Odoo and Order Deliveries to Shopware — each maps to any object or custom field on the other side.

How changes propagate between Odoo and Shopware

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.

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

Shopware Odoo Sub-second propagation

DetectionShopware notifies Stacksync of record changes through webhook events. App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field.

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

Rate-limit considerations

  • Odoo: Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits.
  • Shopware: No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores.
What ships with Odoo ⇄ Shopware

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Odoo and Shopware connectors work

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

Shopware

Integration surface
Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint
Authentication
OAuth 2.0 — client-credentials grant using an Integration's Access Key ID + Secret Access Key, or resource-owner password grant for a user; access tokens expire after 10 minutes
Change detection
App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field names; otherwise poll on the updatedAt / createdAt fields
Capabilities
read · write · webhooks
Rate limits
No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores
How it works

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

    Choose tables

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

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

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:

Related integrations

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

Popular · 8 of 478
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.