Real-time
Two-way sync
Changes in Körber WMS or Linnworks instantly reflect in both systems. No stale data, no manual imports.
ERP
Körber WMS to Linnworks integration — real-time, two-way sync
Keep Körber WMS and Linnworks 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 Linnworks
Two ERPs, one set of facts: Stacksync keeps Körber WMS and Linnworks 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 Receipts / ASNs, Orders, Shipments, Locations in Körber WMS with Suppliers, Channel Listings, Returns & Refunds, Shipping Services in Linnworks 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
- 01 Push orders from the ERP into the WMS for fulfillment and return shipment confirmations automatically
- 02 Mirror receiving and ASN data into procurement systems for inbound visibility
- 03 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels
- 04 Sync product and listing data with a PIM so channel listings stay aligned with the catalog
Common sync patterns
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 Linnworks
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 | Linnworks objects | How this pairing syncs | |
|---|---|---|---|
| Locations Bin and zone definitions scope inventory data during mapping. | Locations Warehouse and fulfillment location records scope stock data during mapping. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Inventory On-hand quantities by location feed availability in order-taking systems. | Stock Items SKU records keep product data aligned with ERPs and PIMs. | Inventory is specific to Körber WMS and Stock Items to Linnworks — each maps to any object or custom field on the other side. | |
| Receipts / ASNs Inbound notices and receipt confirmations sync with procurement systems. | Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Receipts / ASNs is specific to Körber WMS and Stock Levels to Linnworks — each maps to any object or custom field on the other side. | |
| Orders Outbound orders arrive from the ERP or OMS for allocation and fulfillment. | Purchase Orders Replenishment POs sync with suppliers and accounting systems. | Orders is specific to Körber WMS and Purchase Orders to Linnworks — each maps to any object or custom field on the other side. | |
| Shipments Ship confirmations and tracking references return to the order source system. | Suppliers Vendor records keep procurement data consistent across tools. | Shipments is specific to Körber WMS and Suppliers to Linnworks — each maps to any object or custom field on the other side. | |
| Tasks Warehouse task data supports labor and throughput reporting. | Channel Listings Marketplace and webstore listing mappings tie channel products to internal SKUs. | Tasks is specific to Körber WMS and Channel Listings to Linnworks — each maps to any object or custom field on the other side. |
How changes propagate between Körber WMS and Linnworks
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.
Körber WMS Linnworks 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 Linnworks through its API, with automatic retries and rate-limit backoff.
Linnworks Körber WMS Interval-based propagation
DetectionStacksync polls Linnworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling on order and stock endpoints.
DeliveryEach detected change is written to Körber WMS through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Körber WMS: Constrained by deployment architecture rather than published API rate limits.
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Körber WMS ⇄ Linnworks
Connect Körber WMS and Linnworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Körber WMS–Linnworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Körber WMS or Linnworks 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 Linnworks record.
Observability
Monitoring
Track your Körber WMS ⇄ Linnworks 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 Linnworks.
How the Körber WMS and Linnworks 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
Linnworks
- Integration surface
- REST API
- Authentication
- Application credentials and an install token exchanged for a session token
- Change detection
- Polling on order and stock endpoints
- Capabilities
- read · write
- Rate limits
- Per-endpoint rate limits apply on the Linnworks API
How it works
How to connect Körber WMS to Linnworks — 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 Körber WMS and Linnworks with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Körber WMS
connected
Linnworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Körber WMS and Linnworks 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 · Körber WMS ⇄ LinnworksCustomers 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.
Körber WMS LinnworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Körber WMS and Linnworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Körber WMS and Linnworks: authenticate both systems, choose the objects to sync (such as Körber WMS's Locations and Inventory), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Körber WMS and Linnworks: Shared master data; Split by function; Two-tier roll-up. Where both systems keep records of the same customers, suppliers, or organizations, a correction in either updates the other.
-
Körber WMS: Varies by deployment; typically host-interface messages, file exchange, or vendor APIs via middleware. Authentication: Credentials issued per deployment. Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Stacksync manages authentication, retries, and rate limits on both sides.
-
Körber WMS: As is typical for large-scale WMS deployments, integration with ERP hosts is usually implemented through defined host interfaces and middleware rather than a single public SaaS API, so the integration surface varies by deployment. Linnworks: Stock is tracked per location, and channel listings are mapped to internal SKUs, which is the join integrations rely on when reconciling marketplace data. Stacksync's field mapping accounts for these differences between Körber WMS and Linnworks without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Körber WMS and Linnworks records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Körber WMS and Linnworks connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Körber WMS–Linnworks integration in-house.
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 279 integrations available for Körber WMS and Linnworks.
Popular · 4 of 279
No integrations match .
