--- title: "Körber WMS connector: setup and compatibility | Stacksync" description: "Körber WMS integration guide: plan Items and Inventory, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/korber-wms last_modified: 2026-09-15 --- ERP · Two-way sync platform # Körber WMS integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your Körber WMS workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Items, Inventory and Orders. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Items** - **Inventory** - **Receipts / ASNs** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=korber-wms) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Körber WMS records to discuss. These Körber WMS record examples help scope a technical review. They are not a list of verified Stacksync operations. Items Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. Inventory Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient. Receipts / ASNs Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Orders Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. Shipments Retain shipment/fulfillment and line IDs, order reference, and carrier context. Locations Identify this record type and the operation you need to review with Stacksync. Connection setup ## Körber WMS connection requirements. Review Körber WMS access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Körber WMS account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Körber WMS, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Körber WMS integration. Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Körber WMS **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. Load related records in the right order Resolve units, variants, categories, and applicable price lists before order lines. ### Mapping checks by record type #### Items Confirm object support with Stacksync Identity Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. Fields to consider Source product ID · SKU or variant reference · Description · Unit of measure · Price-list reference Related records to resolve first Resolve units, variants, categories, and applicable price lists before order lines. Test before going live Test two variants of one product, a changed SKU, and a price that applies to only one market or currency. #### Inventory Confirm object support with Stacksync Identity Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient. Fields to consider Product reference · Location reference · Quantity type · Quantity · As-of time Related records to resolve first Resolve product, unit, warehouse/location, and lot/serial references. Test before going live Test the same SKU in two locations, a reservation, and an older snapshot arriving late. #### Orders Confirm object support with Stacksync Identity Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. Fields to consider Source order ID · Customer reference · Line references and quantities · Order status · Currency Related records to resolve first Create or locate the customer and products first; resolve taxes, currency, and fulfillment references. Test before going live Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header. #### Shipments Confirm object support with Stacksync Identity Retain shipment/fulfillment and line IDs, order reference, and carrier context. Fields to consider Source shipment ID · Order/line references · Carrier · Tracking reference · Fulfillment status Related records to resolve first Resolve order lines, delivery address, carrier, and any partial-fulfillment references. Test before going live Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order. #### Tasks Confirm object support with Stacksync Identity Use a stable task/work-item ID and preserve its project or parent-ticket reference. Fields to consider Source task ID · Parent reference · Assignee · Status · Due date Related records to resolve first Resolve project, user, and parent-item references before the task. Test before going live Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Körber WMS integration in four steps. Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice. ### View the four setup tests and expected results 1. ### Verify Körber WMS credentials and resource scope After confirming an implementation path, validate the selected access method with the intended account, region or workspace, and resource scope. Record the credential owner and renewal procedure, then demonstrate access to one selected object. **Expected result:** The selected resource is accessible through the approved credential, with the renewal and revocation procedure assigned to an owner. 2. ### Test record matching for Items Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test two variants of one product, a changed SKU, and a price that applies to only one market or currency. **Expected result:** Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice. 3. ### Test the operation your workflow needs Review one Körber WMS record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Körber WMS integration. ### Diagnose record matching, delayed changes, and rejected operations A Körber WMS record appears under the wrong destination record Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. Resolve units, variants, categories, and applicable price lists before order lines. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Körber WMS implementation’s change-detection method for Items, Inventory and Orders. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Körber WMS object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Körber WMS workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=korber-wms) ## Körber WMS integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## Körber WMS connector FAQ ### How should I plan an integration with Körber WMS? Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Körber WMS connector write changes back? Write-back support is not established for this connection. Review the Körber WMS records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Körber WMS data? Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. ### Which related records should I load first for Körber WMS? Resolve units, variants, categories, and applicable price lists before order lines. ### How do I validate Körber WMS changes after the initial load? Test two variants of one product, a changed SKU, and a price that applies to only one market or currency. Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice. ### What will we cover in a Körber WMS integration demo? Start with one workflow and a sample record from Items, Inventory and Orders. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. AI assistant ## Set up Körber WMS from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Körber WMS and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Körber WMS. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Körber WMS record changes.” - “Create a Genie that answers questions about our Körber WMS data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Körber WMS connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Infor M3 and Körber WMS](https://www.stacksync.com/integrations/infor-m3-and-korber-wms) - [Körber WMS and MySQL](https://www.stacksync.com/integrations/korber-wms-and-mysql) - [Körber WMS and Shopify](https://www.stacksync.com/integrations/korber-wms-and-shopify) - [Körber WMS and Snowflake](https://www.stacksync.com/integrations/korber-wms-and-snowflake) - [Körber WMS and Materialize](https://www.stacksync.com/integrations/korber-wms-and-materialize) - [Körber WMS and Unleashed Software](https://www.stacksync.com/integrations/korber-wms-and-unleashed-software) - [Körber WMS and Salesmate](https://www.stacksync.com/integrations/korber-wms-and-salesmate) - [Körber WMS and Manhattan Associates WMS](https://www.stacksync.com/integrations/korber-wms-and-manhattan-associates-wms) ### CRM · 8 - [Körber WMS and Close](https://www.stacksync.com/integrations/close-and-korber-wms) - [Körber WMS and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-korber-wms) - [Körber WMS and HubSpot](https://www.stacksync.com/integrations/hubspot-and-korber-wms) - [Körber WMS and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/korber-wms-and-microsoft-dynamics-365-sales) - [Körber WMS and Salesforce](https://www.stacksync.com/integrations/korber-wms-and-salesforce) - [Körber WMS and Salesmate](https://www.stacksync.com/integrations/korber-wms-and-salesmate) - [Körber WMS and Shopify](https://www.stacksync.com/integrations/korber-wms-and-shopify) - [Körber WMS and Zoho CRM](https://www.stacksync.com/integrations/korber-wms-and-zoho-crm) ### ERP · 7 - [Körber WMS and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-korber-wms) - [Körber WMS and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-korber-wms) - [Körber WMS and IQMS (DELMIAworks)](https://www.stacksync.com/integrations/iqms-delmiaworks-and-korber-wms) - [Körber WMS and Manhattan Associates WMS](https://www.stacksync.com/integrations/korber-wms-and-manhattan-associates-wms) - [Körber WMS and NetSuite](https://www.stacksync.com/integrations/korber-wms-and-netsuite) - [Körber WMS and SAP](https://www.stacksync.com/integrations/korber-wms-and-sap) - [Körber WMS and Unleashed Software](https://www.stacksync.com/integrations/korber-wms-and-unleashed-software) ### Database · 4 - [Körber WMS and MySQL](https://www.stacksync.com/integrations/korber-wms-and-mysql) - [Körber WMS and Redis Enterprise](https://www.stacksync.com/integrations/korber-wms-and-redis-enterprise) - [Körber WMS and SingleStore](https://www.stacksync.com/integrations/korber-wms-and-singlestore) - [Körber WMS and Supabase](https://www.stacksync.com/integrations/korber-wms-and-supabase) ### Data warehouse · 4 - [Körber WMS and Databricks](https://www.stacksync.com/integrations/databricks-and-korber-wms) - [Körber WMS and Materialize](https://www.stacksync.com/integrations/korber-wms-and-materialize) - [Körber WMS and Rockset](https://www.stacksync.com/integrations/korber-wms-and-rockset) - [Körber WMS and Snowflake](https://www.stacksync.com/integrations/korber-wms-and-snowflake) ### Business productivity · 4 - [Körber WMS and Lemlist](https://www.stacksync.com/integrations/korber-wms-and-lemlist) - [Körber WMS and ServiceNow](https://www.stacksync.com/integrations/korber-wms-and-servicenow) - [Körber WMS and Slack](https://www.stacksync.com/integrations/korber-wms-and-slack) - [Körber WMS and Zendesk](https://www.stacksync.com/integrations/korber-wms-and-zendesk) 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. [Learn more about security](https://www.stacksync.com/security) | | | | --- | --- | | | 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: [OAuth 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)