Real-time
Two-way sync
Changes in Linnworks or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
ERP
Linnworks to Microsoft Dynamics NAV integration — real-time, two-way sync
Keep Linnworks and Microsoft Dynamics NAV 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 Linnworks and Microsoft Dynamics NAV
Two ERPs, one set of facts: Stacksync keeps Linnworks and Microsoft Dynamics NAV 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 Stock Items, Stock Levels, Locations, Purchase Orders in Linnworks with Vendors, Items, Sales Orders & Invoices, Purchase Orders in Microsoft Dynamics NAV 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 Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
- 02 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels
- 03 Sync customers, items, and orders between NAV and a CRM in both directions.
- 04 Push ecommerce orders into NAV sales orders through published page services.
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 Linnworks and Microsoft Dynamics NAV
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.
| Linnworks objects | Microsoft Dynamics NAV objects | How this pairing syncs | |
|---|---|---|---|
| Purchase Orders Replenishment POs sync with suppliers and accounting systems. | Purchase Orders Purchasing documents reconciled with receiving and vendor systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Returns & Refunds Post-sale records flow to finance and support systems. | Vendors Vendor cards aligned with procurement and AP tools. | Returns & Refunds is specific to Linnworks and Vendors to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Shipping Services Carrier and service definitions support label and tracking data in order syncs. | Items Item cards and availability mirrored to ecommerce and planning systems. | Shipping Services is specific to Linnworks and Items to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | Sales Orders & Invoices Sales documents created from external orders and read back for posting status. | Open Orders is specific to Linnworks and Sales Orders & Invoices to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | G/L Entries Posted ledger entries replicated to warehouses for finance reporting. | Processed Orders is specific to Linnworks and G/L Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Stock Items SKU records keep product data aligned with ERPs and PIMs. | Item Ledger Entries Inventory movement history read for stock and costing analytics. | Stock Items is specific to Linnworks and Item Ledger Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. |
How changes propagate between Linnworks and Microsoft Dynamics NAV
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.
Linnworks Microsoft Dynamics NAV 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 applied to Microsoft Dynamics NAV as a row-level write, with types converted between the two schemas.
Microsoft Dynamics NAV Linnworks Sub-second propagation
DetectionChanges in Microsoft Dynamics NAV are captured at the source via change data capture — no polling loop against its API. Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases.
DeliveryEach detected change is written to Linnworks through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Linnworks ⇄ Microsoft Dynamics NAV
Connect Linnworks and Microsoft Dynamics NAV for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Linnworks–Microsoft Dynamics NAV connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Linnworks or Microsoft Dynamics NAV 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 Linnworks or Microsoft Dynamics NAV record.
Observability
Monitoring
Track your Linnworks ⇄ Microsoft Dynamics NAV sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Linnworks and Microsoft Dynamics NAV.
How the Linnworks and Microsoft Dynamics NAV connectors work
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
Microsoft Dynamics NAV
- Integration surface
- SOAP and OData web services published from NAV pages and codeunits; direct SQL Server access on-premises
- Authentication
- Windows authentication or NavUserPassword credentials
- Change detection
- Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases; no native webhooks
- Capabilities
- read · write · CDC
How it works
How to connect Linnworks to Microsoft Dynamics NAV — 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 Linnworks and Microsoft Dynamics NAV with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Linnworks
connected
Microsoft Dynamics NAV
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Linnworks and Microsoft Dynamics NAV 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 · Linnworks ⇄ Microsoft Dynamics NAVCustomers 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.
Linnworks Microsoft Dynamics NAVCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Linnworks and Microsoft Dynamics NAV integration FAQ
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 502 integrations available for Linnworks and Microsoft Dynamics NAV.
Popular · 8 of 502
-
Linnworks ⇄ Plex ERP -
Linnworks ⇄ QAD ERP -
Linnworks ⇄ Rootstock ERP -
Linnworks ⇄ Sage 100 -
Microsoft Dynamics NAV ⇄ Manhattan Associates WMS - Microsoft Dynamics NAV ⇄ Microsoft Dynamics GP
- Microsoft Dynamics NAV ⇄ Plex ERP
- Microsoft Dynamics NAV ⇄ QAD ERP
No integrations match .
