Skip to content
Database ⇄ ERP

Azure Cosmos DB to Körber WMS integration — real-time, two-way sync

Keep Azure Cosmos DB and Körber WMS 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 Azure Cosmos DB and Körber WMS

Give your engineers Körber WMS's data in Azure Cosmos DB: read it with normal queries, write back through the sync, and skip the ERP API entirely.

ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.

Stacksync mirrors Tasks, Returns, Items, Inventory from Körber WMS into Azure Cosmos DB and keeps both sides consistent in real time. Whatever Körber WMS is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Azure Cosmos DB sync back into Körber WMS with its validations respected.

Common use cases

  • Stream operational documents from Cosmos DB into a SQL warehouse via the change feed for analytics without hitting request-unit budgets with full scans.
  • Sync CRM or ERP records into a Cosmos DB container that backs a customer-facing application.
  • Push orders from the ERP into the WMS for fulfillment and return shipment confirmations automatically
  • Mirror receiving and ASN data into procurement systems for inbound visibility

Controlled write-back

Choose exactly which tables and fields may flow from Azure Cosmos DB back into Körber WMS, keeping the ERP authoritative.

Read ERP records with a query

Records from Körber WMS live in Azure Cosmos DB as ordinary tables or collections, joinable with the rest of your data.

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the Körber WMS interface, limits, and retries.

What you can sync between Azure Cosmos DB and Körber WMS

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.

Azure Cosmos DB objects Körber WMS objects
Containers The unit of partitioning and throughput; each container maps to a synced collection. Returns Return receipts flow back to commerce and ERP systems for refunds and restocking.
Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. Items Item definitions keep the WMS aligned with the ERP item master.
Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. Inventory On-hand quantities by location feed availability in order-taking systems.
Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. Receipts / ASNs Inbound notices and receipt confirmations sync with procurement systems.
Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. Orders Outbound orders arrive from the ERP or OMS for allocation and fulfillment.
Databases Top-level namespaces that scope containers and throughput provisioning. Shipments Ship confirmations and tracking references return to the order source system.
What ships with Azure Cosmos DB ⇄ Körber WMS

Connect Azure Cosmos DB and Körber WMS for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Körber WMS.

How the Azure Cosmos DB and Körber WMS connectors work

Azure Cosmos DB

Integration surface
REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
Authentication
Account keys, resource tokens, or Microsoft Entra ID role-based access
Change detection
Built-in change feed exposing inserts and updates in order within each partition key range
Capabilities
read · write · CDC

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
How it works

How to connect Azure Cosmos DB to Körber WMS — 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 Azure Cosmos DB and Körber WMS 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
    Azure Cosmos DB connected
    Körber WMS connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Azure Cosmos DB and Körber WMS 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 Azure Cosmos DB and Körber WMS.

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.