Real-time
Two-way sync
Changes in Kommo or Körber WMS instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ ERP
Kommo to Körber WMS integration — real-time, two-way sync
Keep Kommo 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 Kommo and Körber WMS
Close the gap between front office and back office: Kommo and Körber WMS share customers and status in real time, in both directions.
Kommo holds the customer relationship; Körber WMS runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Chats, Leads, Contacts, Companies in Kommo with Returns, Items, Inventory, Receipts / ASNs in Körber WMS field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Keep customer records consistent between Kommo and invoicing or ERP systems
- 02 Mirror pipeline stage changes into BI tools for forecasting
- 03 Consolidate warehouse task and throughput data into a BI warehouse for operations reporting
- 04 Sync inventory positions from Körber WMS to an OMS or e-commerce platform so sellable stock reflects the warehouse
Common sync patterns
Where Körber WMS manages people and org data: keep Kommo aligned
Owners, territories, and org structure informed by Körber WMS stay current in Kommo.
Where Körber WMS handles order-to-cash: closed-won flows through
A deal won in Kommo creates or updates the customer in Körber WMS with clean data, so fulfillment and invoicing start without re-entry.
Where Körber WMS is the finance system of record: money status on the account
Invoice and payment state from Körber WMS shows on the account in Kommo, so reps see balances before promising the next order.
What you can sync between Kommo 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.
| Kommo objects | Körber WMS objects | How this pairing syncs | |
|---|---|---|---|
| Tasks Follow-up records keep rep activity consistent across systems. | Tasks Warehouse task data supports labor and throughput reporting. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. | Orders Outbound orders arrive from the ERP or OMS for allocation and fulfillment. | Chats is specific to Kommo and Orders to Körber WMS — each maps to any object or custom field on the other side. | |
| Leads The central pipeline record; external signups and form fills sync in as leads. | Shipments Ship confirmations and tracking references return to the order source system. | Leads is specific to Kommo and Shipments to Körber WMS — each maps to any object or custom field on the other side. | |
| Contacts Person records sync with other CRMs and databases for a shared contact file. | Locations Bin and zone definitions scope inventory data during mapping. | Contacts is specific to Kommo and Locations to Körber WMS — each maps to any object or custom field on the other side. | |
| Companies Organization records map to accounts in ERPs and invoicing tools. | Returns Return receipts flow back to commerce and ERP systems for refunds and restocking. | Companies is specific to Kommo and Returns to Körber WMS — each maps to any object or custom field on the other side. | |
| Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. | Items Item definitions keep the WMS aligned with the ERP item master. | Pipelines & Statuses is specific to Kommo and Items to Körber WMS — each maps to any object or custom field on the other side. |
How changes propagate between Kommo and Körber WMS
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.
Kommo Körber WMS Sub-second propagation
DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.
DeliveryEach detected change is written to Körber WMS through its API, with automatic retries and rate-limit backoff.
Körber WMS Kommo Interval-based propagation
DetectionStacksync polls Körber WMS for changes on an incremental schedule, reading only records changed since the previous pass. Polling or message/file-based export from the WMS host interface.
DeliveryEach detected change is written to Kommo through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Kommo: Subject to per-account request rate limits.
- Körber WMS: Constrained by deployment architecture rather than published API rate limits.
What ships with Kommo ⇄ Körber WMS
Connect Kommo and Körber WMS for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kommo–Körber WMS connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Kommo 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 Kommo or Körber WMS record.
Observability
Monitoring
Track your Kommo ⇄ 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 Kommo and Körber WMS.
How the Kommo and Körber WMS connectors work
Kommo
- Integration surface
- REST API
- Authentication
- OAuth 2.0 with refresh tokens
- Change detection
- Webhooks on record add and update events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account request rate limits
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 Kommo 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.
- 01
Connect your apps
Authenticate Kommo 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.
Kommo
connected
Körber WMS
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Kommo 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.
objects · Kommo ⇄ Körber WMSCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Kommo Körber WMSCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Kommo and Körber WMS integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Kommo and Körber WMS: authenticate both systems, choose the objects to sync (such as Kommo's Tasks and Chats), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Kommo side: Chats, Leads, Contacts, Companies, plus custom fields where Kommo exposes them. On the Körber WMS side: Returns, Items, Inventory, Receipts / ASNs. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Kommo and Körber WMS: Where Körber WMS manages people and org data: keep Kommo aligned; Where Körber WMS handles order-to-cash: closed-won flows through; Where Körber WMS is the finance system of record: money status on the account. Owners, territories, and org structure informed by Körber WMS stay current in Kommo.
-
Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Körber WMS: Varies by deployment; typically host-interface messages, file exchange, or vendor APIs via middleware. Authentication: Credentials issued per deployment. Stacksync manages authentication, retries, and rate limits on both sides.
-
Kommo: The API uses OAuth 2.0 with short-lived access tokens refreshed via refresh tokens, and supports webhooks on record lifecycle events. Körber WMS: Körber's warehouse management portfolio grew in part from its acquisition of HighJump, and the product line is positioned as modular software for complex, multi-site warehouse operations. Stacksync's field mapping accounts for these differences between Kommo and Körber WMS without custom code.
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 293 integrations available for Kommo and Körber WMS.
Popular · 4 of 293
No integrations match .
