Real-time
Two-way sync
Changes in Körber WMS or Salesforce instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ CRM
Körber WMS to Salesforce integration — real-time, two-way sync
Keep Körber WMS and Salesforce 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 Salesforce
Close the gap between front office and back office: Salesforce and Körber WMS share customers and status in real time, in both directions.
Salesforce 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 Cases, Campaigns, Tasks and Events, Products and Price Books in Salesforce with Shipments, Locations, Tasks, Returns 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 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
- 02 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
- 03 Sync inventory positions from Körber WMS to an OMS or e-commerce platform so sellable stock reflects the warehouse
- 04 Push orders from the ERP into the WMS for fulfillment and return shipment confirmations automatically
Common sync patterns
One customer master
Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
Where Körber WMS manages people and org data: keep Salesforce aligned
Owners, territories, and org structure informed by Körber WMS stay current in Salesforce.
Where Körber WMS handles order-to-cash: closed-won flows through
A deal won in Salesforce creates or updates the customer in Körber WMS with clean data, so fulfillment and invoicing start without re-entry.
What you can sync between Körber WMS and Salesforce
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 | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| Orders Outbound orders arrive from the ERP or OMS for allocation and fulfillment. | Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. | Orders is specific to Körber WMS and Tasks and Events to Salesforce — each maps to any object or custom field on the other side. | |
| Shipments Ship confirmations and tracking references return to the order source system. | Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. | Shipments is specific to Körber WMS and Products and Price Books to Salesforce — each maps to any object or custom field on the other side. | |
| Locations Bin and zone definitions scope inventory data during mapping. | Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | Locations is specific to Körber WMS and Custom Objects to Salesforce — each maps to any object or custom field on the other side. | |
| Tasks Warehouse task data supports labor and throughput reporting. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | Tasks is specific to Körber WMS and Accounts to Salesforce — each maps to any object or custom field on the other side. | |
| Returns Return receipts flow back to commerce and ERP systems for refunds and restocking. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Returns is specific to Körber WMS and Contacts to Salesforce — each maps to any object or custom field on the other side. | |
| Items Item definitions keep the WMS aligned with the ERP item master. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Items is specific to Körber WMS and Leads to Salesforce — each maps to any object or custom field on the other side. |
How changes propagate between Körber WMS and Salesforce
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 Salesforce 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 Salesforce through its API, with automatic retries and rate-limit backoff.
Salesforce Körber WMS Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
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.
- Salesforce: Daily API request allocations vary by edition and license count.
What ships with Körber WMS ⇄ Salesforce
Connect Körber WMS and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Körber WMS–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Körber WMS or Salesforce 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 Salesforce record.
Observability
Monitoring
Track your Körber WMS ⇄ Salesforce 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 Salesforce.
How the Körber WMS and Salesforce 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
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect Körber WMS to Salesforce — 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 Salesforce 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
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Körber WMS and Salesforce 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 ⇄ SalesforceCustomers 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 SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Körber WMS and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Körber WMS and Salesforce: authenticate both systems, choose the objects to sync (such as Körber WMS's Orders and Shipments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Salesforce 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 Salesforce connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Körber WMS–Salesforce integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Körber WMS and Salesforce. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Körber WMS: Polling or message/file-based export from the WMS host interface. On Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Salesforce side: Cases, Campaigns, Tasks and Events, Products and Price Books, plus custom fields where Salesforce exposes them. On the Körber WMS side: Shipments, Locations, Tasks, Returns. Stacksync auto-detects both schemas and converts types between the two systems.
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 310 integrations available for Körber WMS and Salesforce.
Popular · 5 of 310
-
Körber WMS ⇄ Close -
Salesforce ⇄ Global Shop Solutions -
Salesforce ⇄ Infor CloudSuite - Salesforce ⇄ Infor LN
- Salesforce ⇄ Infor M3
No integrations match .
