Skip to content
ERP ⇄ Data warehouse

Linnworks to MotherDuck integration — real-time, two-way sync

Keep Linnworks and MotherDuck 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 MotherDuck

Put Linnworks's records in MotherDuck as live tables for reporting and analysis, without extract jobs, and write results back where Linnworks can use them.

ERP data is some of the most asked-for data in the warehouse and some of the hardest to get: the record types are many, the APIs are strict, and extract jobs are brittle. Whether Linnworks carries financials, operations, workforce data, or all three, the analysis belongs in MotherDuck next to everything else the company measures.

Stacksync syncs Purchase Orders, Suppliers, Channel Listings, Returns & Refunds from Linnworks into tables in MotherDuck continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in MotherDuck can be written back to fields in Linnworks where that is useful.

Common use cases

  • Share curated, synced datasets with other teams through read-only database shares
  • Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
  • Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
  • Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels

Where Linnworks runs operations: order and supply analysis

Operational records become queryable tables in MotherDuck, joinable with sales and finance data.

Group reporting across systems

Combine Linnworks's records with data synced from other systems in MotherDuck for consolidated views no single system can produce.

Write-back where Linnworks exposes writable fields

Classifications or reference values computed in MotherDuck sync back onto the corresponding records in Linnworks.

What you can sync between Linnworks and MotherDuck

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 MotherDuck objects
Processed Orders Completed orders feed accounting and warehouse-based margin reporting. Views Modeled projections used as outbound sync sources.
Stock Items SKU records keep product data aligned with ERPs and PIMs. Database Shares Read-only copies of a database shared with other users or teams.
Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries.
Locations Warehouse and fulfillment location records scope stock data during mapping. Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes.
Purchase Orders Replenishment POs sync with suppliers and accounting systems. Schemas Namespaces within a database used to organize synced tables.
Suppliers Vendor records keep procurement data consistent across tools. Tables The main landing target for synced records and source for analysis.
What ships with Linnworks ⇄ MotherDuck

Connect Linnworks and MotherDuck for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Linnworks–MotherDuck connection.

Real-time

Two-way sync

Changes in Linnworks or MotherDuck instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Linnworks or MotherDuck 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 MotherDuck record.

Observability

Monitoring

Track your Linnworks ⇄ MotherDuck 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 MotherDuck.

How the Linnworks and MotherDuck 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

MotherDuck

Integration surface
SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
Authentication
Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck setup guide
How it works

How to connect Linnworks to MotherDuck — 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.

  1. 01

    Connect your apps

    Authenticate Linnworks and MotherDuck with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Linnworks connected
    MotherDuck connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Linnworks and MotherDuck 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Linnworks ⇄ MotherDuck
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Linnworks MotherDuck
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Linnworks and MotherDuck integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for Linnworks and MotherDuck.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.