Skip to content
ERP

Körber WMS to Odoo integration — real-time, two-way sync

Keep Körber WMS 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 Körber WMS and Odoo

Two ERPs, one set of facts: Stacksync keeps Körber WMS and Odoo consistent in real time, whether they split the business or one is replacing the other.

Companies run two ERPs for structural reasons: a two-tier setup with subsidiaries on lighter systems, an acquisition that brought its own stack, a split by function or region, or a migration that will take quarters. In all of these, some of the same organizations, people, and transactions exist in both systems, and keeping them aligned by hand is a standing tax on the back office.

Stacksync syncs Shipments, Locations, Tasks, Returns in Körber WMS with Invoices (account.move), Products (product.template / product.product), CRM Leads (crm.lead), Purchase Orders (purchase.order) in Odoo bi-directionally and in real time, with field-level mapping across the two data models and conflict rules you define. A record changed in either system is reflected in the other within seconds, not at the next interface run.

Common use cases

  • Mirror receiving and ASN data into procurement systems for inbound visibility
  • Consolidate warehouse task and throughput data into a BI warehouse for operations reporting
  • Mirror invoices and journal entries into a warehouse for consolidated financial reporting across entities.
  • Keep product and price list data aligned between Odoo and storefronts or marketplaces.

Shared master data

Where both systems keep records of the same customers, suppliers, or organizations, a correction in either updates the other.

Split by function

Where one system is the people or finance suite and the other runs operations, the records both sides depend on, such as organizations, cost centers, and reference data, stay in agreement.

Two-tier roll-up

Where subsidiaries run one system and headquarters runs the other, shared records and transactions flow up continuously, so consolidation starts from live data.

What you can sync between Körber WMS 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.

Körber WMS objects Odoo objects
Inventory On-hand quantities by location feed availability in order-taking systems. Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools.
Receipts / ASNs Inbound notices and receipt confirmations sync with procurement systems. CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems.
Orders Outbound orders arrive from the ERP or OMS for allocation and fulfillment. Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems.
Shipments Ship confirmations and tracking references return to the order source system. Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility.
Locations Bin and zone definitions scope inventory data during mapping. Employees (hr.employee) HR records read for directory and provisioning syncs.
Tasks Warehouse task data supports labor and throughput reporting. Projects and Tasks (project.project / project.task) Work items synced with external project tools.
What ships with Körber WMS ⇄ Odoo

Connect Körber WMS and Odoo for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Körber WMS–Odoo connection.

Real-time

Two-way sync

Changes in Körber WMS or Odoo instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Körber WMS 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 Körber WMS or Odoo record.

Observability

Monitoring

Track your Körber WMS ⇄ Odoo sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Körber WMS and Odoo.

How the Körber WMS and Odoo connectors work

Körber WMS

Integration surface
Varies by deployment; typically host-interface messages, file exchange, or vendor APIs via middleware
Authentication
Credentials issued per deployment
Change detection
Polling or message/file-based export from the WMS host interface
Capabilities
read · write
Rate limits
Constrained by deployment architecture rather than published API rate limits

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

    Choose tables

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

Körber WMS and Odoo integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for Körber WMS and Odoo.

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

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