Two-way sync
Changes in Exasol or Körber WMS instantly reflect in both systems. No stale data, no manual imports.
Keep Exasol 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.
ERP data is some of the most asked-for data in the warehouse and some of the hardest to get: the record types are many, the APIs are strict, and extract jobs are brittle. Whether Körber WMS carries financials, operations, workforce data, or all three, the analysis belongs in Exasol next to everything else the company measures.
Stacksync syncs Items, Inventory, Receipts / ASNs, Orders from Körber WMS into tables in Exasol continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in Exasol can be written back to fields in Körber WMS where that is useful.
Operational records become queryable tables in Exasol, joinable with sales and finance data.
Combine Körber WMS's records with data synced from other systems in Exasol for consolidated views no single system can produce.
Classifications or reference values computed in Exasol sync back onto the corresponding records in 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.
| Exasol objects | Körber WMS objects | |
|---|---|---|
| Schemas Namespaces that group the tables a sync reads from or writes into. | Shipments Ship confirmations and tracking references return to the order source system. | |
| Tables Primary sync target; columnar relational tables written with standard SQL. | Locations Bin and zone definitions scope inventory data during mapping. | |
| Views Read-only query surfaces often used as curated sources for reverse ETL. | Tasks Warehouse task data supports labor and throughput reporting. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | Returns Return receipts flow back to commerce and ERP systems for refunds and restocking. | |
| UDF scripts In-database functions that can transform synced data after load. | Items Item definitions keep the WMS aligned with the ERP item master. | |
| Users and roles Grant read/write access for the dedicated integration account. | Inventory On-hand quantities by location feed availability in order-taking systems. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Körber WMS connection.
Changes in Exasol or Körber WMS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Exasol or Körber WMS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Exasol or Körber WMS record.
Track your Exasol ⇄ Körber WMS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Exasol and Körber WMS.
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.
Authenticate Exasol 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.
Pick the Exasol 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Exasol and Körber WMS: authenticate both systems, choose the objects to sync (such as Exasol's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Exasol and Körber WMS. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Exasol: Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients. On Körber WMS: Polling or message/file-based export from the WMS host interface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Exasol side: Tables, Views, Virtual schemas, UDF scripts, plus custom fields where Exasol exposes them. On the Körber WMS side: Items, Inventory, Receipts / ASNs, Orders. 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 Exasol and Körber WMS: Where Körber WMS runs operations: order and supply analysis; Group reporting across systems; Write-back where Körber WMS exposes writable fields. Operational records become queryable tables in Exasol, joinable with sales and finance data.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Exasol and Körber WMS.