Can you integrate Dynamics 365 F&O with Linnworks?

Explore a Dynamics 365 F&O and Linnworks integration with a Stacksync engineer. Stacksync support for Linnworks 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 Dynamics 365 F&O and Linnworks 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 Dynamics 365 F&O and Linnworks initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Provide the Dynamics environment URL and authorize the Stacksync app with Microsoft sign-in; arrange administrator consent if required. Identify the Linnworks account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Dynamics 365 F&O to Linnworks 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 Dynamics 365 F&O fields to Linnworks?

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.

What does a Dynamics 365 F&O and Linnworks 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.

Which records should the Dynamics 365 F&O and Linnworks pilot start with?

Start by reviewing Vendors in Dynamics 365 F&O and Suppliers in Linnworks. 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 · Two-way sync platform

Dynamics 365 F&O and Linnworks integration

Plan how Dynamics 365 F&O and Linnworks should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

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

Integration planning

stacksync.com

Dynamics 365 F&O

Linnworks

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

Supplier or vendor sync test

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

Starting eventA change involving Dynamics 365 F&O Vendors or Linnworks Suppliers needs a defined result in the other system.

Start with Dynamics 365 F&O Vendors and Linnworks Suppliers. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve business-unit and payment-term references before purchasing transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.

Review records and field ownership

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 Dynamics 365 F&O and Linnworks
Dynamics 365 F&O record	Linnworks record	Record matching	Field ownership
VendorsProposed record; confirm Stacksync object support.Record matching	SuppliersProposed record; confirm Stacksync object support.	Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.	Assign responsibility for approved supplier details; restrict changes to payment instructions to the business approval process.
Purchase OrdersProposed record; confirm Stacksync object support.Record matching	Purchase OrdersProposed record; confirm Stacksync object support.	Retain purchase-order and line IDs together with the supplier and legal-entity context.	Keep procurement approval separate from receipt and payment states.

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.

Dynamics 365 F&O

Read and write support varies by record

Record types covered in the setup guide

Record types	Coverage and requirements
Standard entities	Requires account access and compatible change tracking. Confirm field permissions and sync direction.
Custom entities	Requires API exposure and compatible change tracking. Confirm field permissions and sync direction.

Read the Dynamics 365 F&O connector guide

Linnworks

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Open Orders Processed Orders Stock Items Stock Levels Locations Purchase Orders	Confirm support for this record type and the direction you need.

Discuss Linnworks 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	Dynamics 365 F&O	Linnworks
Integration interface	OData REST endpoint over data entities, plus the Data Management Framework for batch	REST API
Authentication	OAuth via Microsoft sign-in	Confirm the credentials, API plan, and permissions required for Linnworks.
Change detection	Full and incremental syncs use Dynamics change tracking where available; enable tracking on the selected entities.	Confirm how Stacksync detects changes for this connector and the objects you need.
Read access	Available for supported records	Confirm with Stacksync
Write access	Available for supported records	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

Dynamics 365 F&O

Integration interface: OData REST endpoint over data entities, plus the Data Management Framework for batch
Authentication: OAuth via Microsoft sign-in: provide the D365 F&O environment URL, sign in with Microsoft credentials, and grant the Stacksync app consent (admin consent may be required — "Need admin approval for this app")
Change detection: Full and incremental syncs use Dynamics change tracking where available; enable tracking on the selected entities.
Read access: Available for supported records
Write access: Available for supported records

Setup requirements

Provide the Dynamics environment URL and authorize the Stacksync app with Microsoft sign-in; arrange administrator consent if required.
Enable change tracking for each selected entity and check whether changes in child tables are included.

Limitations to check

Some complex entities cannot enable change tracking. Primary-table tracking does not capture changes in child tables.

Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Dynamics 365 F&O setup guide

Linnworks

Integration interface: REST API
Authentication: Confirm the credentials, API plan, and permissions required for Linnworks.
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 Linnworks account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Linnworks, including read/write support, authentication, and initial-load limits.

Limitations to check

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

Prepare Dynamics 365 F&O and Linnworks 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.

Dynamics 365 F&O setup checklist

Provide the Dynamics environment URL and authorize the Stacksync app with Microsoft sign-in; arrange administrator consent if required.
Enable change tracking for each selected entity and check whether changes in child tables are included.

Setup guides: Authorize Dynamics 365 F\&O

Linnworks setup checklist

Identify the Linnworks account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Linnworks, 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 Dynamics 365 F&O and Linnworks 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

Record matching

Vendors / Suppliers

Compare whether Dynamics 365 F&O Vendors and Linnworks Suppliers describe the same supplier or vendor in your business.

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

Dynamics 365 F&O: Object support to establish
Linnworks: Object support to establish
Record identity: Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
Field ownership: Assign responsibility for approved supplier details; restrict changes to payment instructions to the business approval process.

Fields to include

Source supplier ID
Legal name
Entity reference
Payment terms
Active status

Record dependencies: Resolve business-unit and payment-term references before purchasing transactions.
Validation: Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
Recovery: Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.

References: Dynamics 365 F&O: Vendors documentation

Record matching

Purchase Orders / Purchase Orders

Compare whether Dynamics 365 F&O Purchase Orders and Linnworks Purchase Orders describe the same purchase order in your business.

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

Dynamics 365 F&O: Object support to establish
Linnworks: Object support to establish
Record identity: Retain purchase-order and line IDs together with the supplier and legal-entity context.
Field ownership: Keep procurement approval separate from receipt and payment states.

Fields to include

Source purchase-order ID
Supplier reference
Line references
Quantity
Approval status

Record dependencies: Resolve supplier, product, business unit, and delivery-location references before lines.
Validation: Test a partially received purchase order and an amendment after approval.
Recovery: Reconcile receipts already recorded before resubmitting an amended order.

References: Dynamics 365 F&O: Purchase Orders documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Vendors / Suppliers 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: Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries. 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 Dynamics 365 F&O and Linnworks 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 Vendors / Suppliers, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider when Dynamics 365 F&O and Linnworks need a transformation, approval, or action outside a direct record sync.
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 Dynamics 365 F&O / Linnworks 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

Supplier or vendor sync test

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

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

Start with Dynamics 365 F&O Vendors and Linnworks Suppliers. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve business-unit and payment-term references before purchasing transactions.
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 supplier shared across subsidiaries and an inactive supplier referenced by an open bill.

If it fails: Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.

Purchase order sync test

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

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

Start with Dynamics 365 F&O Purchase Orders and Linnworks Purchase Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve supplier, product, business unit, and delivery-location references before lines.
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 received purchase order and an amendment after approval.

If it fails: Reconcile receipts already recorded before resubmitting an amended order.

Reconcile Dynamics 365 F&O business records with Linnworks

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

Starting event: A finance-owned record in Dynamics 365 F&O needs operational visibility through Purchase Orders or Suppliers.

Select Customers or Vendors with the correct legal entity, period, and currency.
Define a reporting relationship in Linnworks; 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 supplier or vendor change

Investigate

Inspect Dynamics 365 F&O Vendors and Linnworks Suppliers, their IDs, and the destination error.

Next action

Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.

Rejected or repeated purchase order change

Investigate

Inspect Dynamics 365 F&O Purchase Orders and Linnworks Purchase Orders, their IDs, and the destination error.

Next action

Reconcile receipts already recorded before resubmitting an amended order.

A record type or update is unavailable

Investigate

Check the Dynamics 365 F&O and Linnworks 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 Dynamics 365 F&O and Linnworks

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

Dynamics 365 F&O Linnworks Direction requires confirmation

Detect changesFull and incremental syncs use Dynamics change tracking where available; enable tracking on the selected entities.

Apply updatesConfirm that Stacksync can create or update the records you need in Linnworks.

Linnworks Dynamics 365 F&O 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 Dynamics 365 F&O.

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.
Some complex entities cannot enable change tracking. Primary-table tracking does not capture changes in child tables.
Review write-back, deletion handling, update timing, and account limits with the integration team.

FAQ