Linnworks to MySQL Integration

How Datrise loads Linnworks into MySQL

Datrise syncs Linnworks's orders, stock items, channels, shipments, suppliers, and inventory levels into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Linnworks: Multichannel order and inventory management.

MySQL: Widely used OSS relational engine (InnoDB).

How Linnworks entities map to MySQL

Linnworks entity	MySQL object	Notes
orders	`linnworks_orders`	id PK · custom fields → JSON columns
stock items	`linnworks_stock_items`	id PK · linked to linnworks_orders
channels	`linnworks_channels`	id PK · linked to linnworks_orders
shipments	`linnworks_shipments`	id PK · linked to linnworks_orders

FAQ

How does Datrise handle Linnworks's custom fields in MySQL?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.

How does the Linnworks to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Linnworks to MySQL the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.