Can you integrate Körber WMS with Microsoft Dynamics 365 Sales?

Explore a Körber WMS and Microsoft Dynamics 365 Sales integration with a Stacksync engineer. Stacksync support for Körber WMS and Microsoft Dynamics 365 Sales is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

Can Körber WMS and Microsoft Dynamics 365 Sales sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

What should be ready before the Körber WMS and Microsoft Dynamics 365 Sales initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Körber WMS account, edition, environment, and business objects the integration must access. Identify the Microsoft Dynamics 365 Sales account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Körber WMS to Microsoft Dynamics 365 Sales sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map Körber WMS fields to Microsoft Dynamics 365 Sales?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

Which records should the Körber WMS and Microsoft Dynamics 365 Sales pilot start with?

Start by reviewing Orders in Körber WMS and Opportunities in Microsoft Dynamics 365 Sales. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

ERP / CRM · Two-way sync platform

Körber WMS and Microsoft Dynamics 365 Sales integration

Q: What does a Körber WMS and Microsoft Dynamics 365 Sales integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Plan how Körber WMS and Microsoft Dynamics 365 Sales should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Set this up from Claude or ChatGPT

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

Körber WMS

Microsoft Dynamics 365 Sales

Review the integration scope

Built for teams where self-serve, reliability and scale matter

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

Proposed workflow

Deal or opportunity process handoff

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving Körber WMS Orders or Microsoft Dynamics 365 Sales Opportunities needs a defined result in the other system.

Start with Körber WMS Orders and Microsoft Dynamics 365 Sales Opportunities. Use the record-matching and field-ownership rules from your mapping worksheet.
Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyRepeat the approved handoff and verify that it locates the existing order; test a reopened deal without silently cancelling fulfillment.

Review records and field ownership

AI assistant

Set up Körber WMS and Microsoft Dynamics 365 Sales 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

Open Customize → Connectors, select + Add, then Add custom connector.
Name it Stacksync and enter https://mcp.stacksync.com/mcp.
Select Connect, sign in to Stacksync and choose your workspace.

In ChatGPT

Open Settings → Apps → Advanced settings and turn on Developer mode.
Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
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.

2. Ask your assistant

Create a sync between my Körber WMS and Microsoft Dynamics 365 Sales.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use Körber WMS and Microsoft Dynamics 365 Sales. 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 Microsoft Dynamics 365 Sales 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 first, then sign in from your assistant.

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between Körber WMS and Microsoft Dynamics 365 Sales
Körber WMS record	Microsoft Dynamics 365 Sales record	Record matching	Field ownership
OrdersProposed record; confirm Stacksync object support.Business process handoff	OpportunitiesProposed record; confirm Stacksync object support.	Link the originating deal ID to a newly assigned order ID; do not reuse the deal ID as an order number.	Define the approval event and the customer/product data required to create an order. A sales stage alone must not authorize every order.
OrdersProposed record; confirm Stacksync object support.Business process handoff	InvoicesProposed record; confirm Stacksync object support.	Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.	Finance owns invoice posting; the order system supplies the approved commercial context.
ShipmentsProposed record; confirm Stacksync object support.Business process handoff	OrdersProposed record; confirm Stacksync object support.	Link the order and selected line IDs to separate fulfillment IDs; allow split shipments.	The fulfillment owner decides when an approved order can ship and how cancellations are handled.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

Körber WMS

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Items Inventory Receipts / ASNs Orders Shipments Locations	Confirm support for this record type and the direction you need.

Discuss Körber WMS requirements

Microsoft Dynamics 365 Sales

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Accounts Contacts Leads Opportunities Quotes Orders	Confirm support for this record type and the direction you need.

Discuss Microsoft Dynamics 365 Sales requirements

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits

Connection requirement	Körber WMS	Microsoft Dynamics 365 Sales
Integration interface	Varies by deployment; typically host-interface messages, file exchange, or vendor APIs via middleware	Dataverse Web API (OData v4 REST)
Authentication	Confirm the credentials, API plan, and permissions required for Körber WMS.	Confirm the credentials, API plan, and permissions required for Microsoft Dynamics 365 Sales.
Change detection	Confirm how Stacksync detects changes for this connector and the objects you need.	Confirm how Stacksync detects changes for this connector and the objects you need.
Read access	Confirm with Stacksync	Confirm with Stacksync
Write access	Confirm with Stacksync	Confirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

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

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:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

Körber WMS

Integration interface: Varies by deployment; typically host-interface messages, file exchange, or vendor APIs via middleware
Authentication: Confirm the credentials, API plan, and permissions required for Körber WMS.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

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.

Limitations to check

Confirm Stacksync support for Körber WMS and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Microsoft Dynamics 365 Sales

Integration interface: Dataverse Web API (OData v4 REST)
Authentication: Confirm the credentials, API plan, and permissions required for Microsoft Dynamics 365 Sales.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the Microsoft Dynamics 365 Sales account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Microsoft Dynamics 365 Sales, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for Microsoft Dynamics 365 Sales and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare Körber WMS and Microsoft Dynamics 365 Sales access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

Körber WMS setup checklist

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.

Microsoft Dynamics 365 Sales setup checklist

Identify the Microsoft Dynamics 365 Sales account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Microsoft Dynamics 365 Sales, including read/write support, authentication, and initial-load limits.

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the Körber WMS and Microsoft Dynamics 365 Sales planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Business process

Orders / Opportunities

Approved sales handoff: Microsoft Dynamics 365 Sales Opportunities provides context for Körber WMS Orders. These are related records, not equivalent entities.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Körber WMS: Object support to establish
Microsoft Dynamics 365 Sales: Object support to establish
Record identity: Link the originating deal ID to a newly assigned order ID; do not reuse the deal ID as an order number.
Field ownership: Define the approval event and the customer/product data required to create an order. A sales stage alone must not authorize every order.

Fields to include

Source record reference
Destination record reference
Approved handoff state
Duplicate-detection key

Record dependencies: Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Validation: Repeat the approved handoff and verify that it locates the existing order; test a reopened deal without silently cancelling fulfillment.
Recovery: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

Business process

Orders / Invoices

Order-to-invoice handoff: Körber WMS Orders provides context for Microsoft Dynamics 365 Sales Invoices. These are related records, not equivalent entities.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Körber WMS: Object support to establish
Microsoft Dynamics 365 Sales: Object support to establish
Record identity: Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.
Field ownership: Finance owns invoice posting; the order system supplies the approved commercial context.

Fields to include

Source record reference
Destination record reference
Approved handoff state
Duplicate-detection key

Record dependencies: Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation: Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Recovery: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Business process

Shipments / Orders

Order-to-fulfillment handoff: Microsoft Dynamics 365 Sales Orders provides context for Körber WMS Shipments. These are related records, not equivalent entities.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Körber WMS: Object support to establish
Microsoft Dynamics 365 Sales: Object support to establish
Record identity: Link the order and selected line IDs to separate fulfillment IDs; allow split shipments.
Field ownership: The fulfillment owner decides when an approved order can ship and how cancellations are handled.

Fields to include

Source record reference
Destination record reference
Approved handoff state
Duplicate-detection key

Record dependencies: Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation: Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.
Recovery: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Record matching

Orders / Orders

Compare whether Körber WMS Orders and Microsoft Dynamics 365 Sales Orders describe the same sales order in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Körber WMS: Object support to establish
Microsoft Dynamics 365 Sales: Object support to establish
Record identity: Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
Field ownership: Decide which system approves the order and which can cancel or amend it after fulfillment begins.

Fields to include

Source order ID
Customer reference
Line references and quantities
Order status
Currency

Record dependencies: Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation: Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Recovery: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Orders / Opportunities to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Link the originating deal ID to a newly assigned order ID; do not reuse the deal ID as an order number. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your Körber WMS and Microsoft Dynamics 365 Sales record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Orders / Opportunities, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider explicit orchestration for the Orders / Opportunities handoff.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit: Consider for a one-time Körber WMS / Microsoft Dynamics 365 Sales migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Deal or opportunity process handoff

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Orders or Opportunities record needs a defined result in the other system.

Start with Körber WMS Orders and Microsoft Dynamics 365 Sales Opportunities. Use the record-matching and field-ownership rules from your mapping worksheet.
Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Repeat the approved handoff and verify that it locates the existing order; test a reopened deal without silently cancelling fulfillment.

If it fails: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

Sales order process handoff

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Orders or Invoices record needs a defined result in the other system.

Start with Körber WMS Orders and Microsoft Dynamics 365 Sales Invoices. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.

If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Sales order process handoff

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Shipments or Orders record needs a defined result in the other system.

Start with Körber WMS Shipments and Microsoft Dynamics 365 Sales Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.

If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Reconcile Körber WMS business records with Microsoft Dynamics 365 Sales

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A finance-owned record in Körber WMS needs operational visibility through Accounts or Contacts.

Select Items or Inventory with the correct legal entity, period, and currency.
Define a reporting relationship in Microsoft Dynamics 365 Sales; do not equate customer records, ledger accounts, and posted transactions.
Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated deal or opportunity change

Investigate

Inspect Körber WMS Orders and Microsoft Dynamics 365 Sales Opportunities, their IDs, and the destination error.

Next action

Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

Rejected or repeated sales order change

Investigate

Inspect Körber WMS Orders and Microsoft Dynamics 365 Sales Invoices, their IDs, and the destination error.

Next action

Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Rejected or repeated sales order change

Investigate

Inspect Körber WMS Shipments and Microsoft Dynamics 365 Sales Orders, their IDs, and the destination error.

Next action

Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

A record type or update is unavailable

Investigate

Check the Körber WMS and Microsoft Dynamics 365 Sales connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between Körber WMS and Microsoft Dynamics 365 Sales

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Körber WMS Microsoft Dynamics 365 Sales Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Microsoft Dynamics 365 Sales.

Microsoft Dynamics 365 Sales Körber WMS Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Körber WMS.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Review write-back, deletion handling, update timing, and account limits with the integration team.
Review write-back, deletion handling, update timing, and account limits with the integration team.

FAQ