Real-time
Real-time sync
Changes in E2 Shop System or Körber WMS instantly reflect in both systems. No stale data, no manual imports.
ERP
E2 Shop System to Körber WMS integration — real-time data sync
Keep E2 Shop System 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 E2 Shop System and Körber WMS
Two ERPs, one set of facts: Stacksync keeps E2 Shop System and Körber WMS consistent in real time, whether they split the business or one is replacing the other.
E2 Shop System is a read-only source: Stacksync reads its data in real time and delivers it into Körber WMS, so Körber WMS always reflects the current state of E2 Shop System — without exports, scripts, or schedulers.
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.
Common use cases
- 01 Sync customer and invoice data to accounting or CRM so the front office is not re-keying from the ERP.
- 02 Land quote, job cost, and time-ticket data in a warehouse for margin analysis across jobs.
- 03 Mirror receiving and ASN data into procurement systems for inbound visibility
- 04 Consolidate warehouse task and throughput data into a BI warehouse for operations reporting
Common sync patterns
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.
Migration in parallel
When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.
Shared master data
Where both systems keep records of the same customers, suppliers, or organizations, a correction in either updates the other.
What you can sync between E2 Shop System 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.
| E2 Shop System objects | Körber WMS objects | How this pairing syncs | |
|---|---|---|---|
| Jobs / Work orders Released work with routings and status; the record shop-floor dashboards track. | Returns Return receipts flow back to commerce and ERP systems for refunds and restocking. | Jobs / Work orders is specific to E2 Shop System and Returns to Körber WMS — each maps to any object or custom field on the other side. | |
| Customers Buyer records synced to CRM or accounting counterparts. | Items Item definitions keep the WMS aligned with the ERP item master. | Customers is specific to E2 Shop System and Items to Körber WMS — each maps to any object or custom field on the other side. | |
| Vendors Supplier records referenced on purchasing documents. | Inventory On-hand quantities by location feed availability in order-taking systems. | Vendors is specific to E2 Shop System and Inventory to Körber WMS — each maps to any object or custom field on the other side. | |
| Parts Part masters with routings and material definitions specific to each shop. | Receipts / ASNs Inbound notices and receipt confirmations sync with procurement systems. | Parts is specific to E2 Shop System and Receipts / ASNs to Körber WMS — each maps to any object or custom field on the other side. | |
| Routings / Operations Per-part operation sequences that carry estimated and actual times. | Orders Outbound orders arrive from the ERP or OMS for allocation and fulfillment. | Routings / Operations is specific to E2 Shop System and Orders to Körber WMS — each maps to any object or custom field on the other side. | |
| Purchase orders Outside material and service purchases tied to jobs. | Shipments Ship confirmations and tracking references return to the order source system. | Purchase orders is specific to E2 Shop System and Shipments to Körber WMS — each maps to any object or custom field on the other side. |
How changes propagate between E2 Shop System 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.
E2 Shop System Körber WMS Interval-based propagation
DetectionStacksync polls E2 Shop System for changes on an incremental schedule, reading only records changed since the previous pass. Polling database tables or scheduled exports.
DeliveryEach detected change is written to Körber WMS through its API, with automatic retries and rate-limit backoff.
Körber WMS E2 Shop System 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.
DeliveryE2 Shop System does not accept inbound record writes, so this direction carries requests rather than records: E2 Shop System's output flows back as field updates on the originating Körber WMS records.
Rate-limit considerations
- E2 Shop System: Not API-bound; constrained by on-premises database access windows.
- Körber WMS: Constrained by deployment architecture rather than published API rate limits.
What ships with E2 Shop System ⇄ Körber WMS
Connect E2 Shop System and Körber WMS for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every E2 Shop System–Körber WMS connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever E2 Shop System 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 E2 Shop System or Körber WMS record.
Observability
Monitoring
Track your E2 Shop System ⇄ 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 E2 Shop System and Körber WMS.
How the E2 Shop System and Körber WMS connectors work
E2 Shop System
- Integration surface
- No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment
- Authentication
- Database credentials or application-level export access on the on-premises installation
- Change detection
- Polling database tables or scheduled exports
- Capabilities
- read
- Rate limits
- Not API-bound; constrained by on-premises database access windows
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 E2 Shop System 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 E2 Shop System 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.
E2 Shop System
connected
Körber WMS
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the E2 Shop System 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 · E2 Shop System ⇄ 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.
E2 Shop System Körber WMSCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
E2 Shop System and Körber WMS integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between E2 Shop System and Körber WMS — E2 Shop System is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Change detection on E2 Shop System: Polling database tables or scheduled exports. 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 E2 Shop System side: Time tickets, Invoices, Quotes / Estimates, Jobs / Work orders, plus custom fields where E2 Shop System exposes them. On the Körber WMS side: Inventory, Receipts / ASNs, Orders, Shipments. Stacksync auto-detects both schemas and converts types between the two systems.
-
E2 Shop System is a read-only source, so this integration runs one-way: Stacksync reads from E2 Shop System in real time and delivers into Körber WMS. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for E2 Shop System and Körber WMS: Two-tier roll-up; Migration in parallel; Shared master data. Where subsidiaries run one system and headquarters runs the other, shared records and transactions flow up continuously, so consolidation starts from live data.
-
E2 Shop System: No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment. Authentication: Database credentials or application-level export access on the on-premises installation. 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.
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 36 integrations available for E2 Shop System and Körber WMS.
Popular · 1 of 36
No integrations match .
