Skip to content
ERP ⇄ Analytics

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

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

Put Linnworks's records into Treasuredata as live data for reporting and dashboards, without nightly exports, and send the segments and metrics Treasuredata computes back where Linnworks can use them.

ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether Linnworks carries financials, operations, workforce data, or all three, those numbers belong in Treasuredata, next to the product, behavioral, and web data the team already measures.

Stacksync syncs Stock Levels, Locations, Purchase Orders, Suppliers from Linnworks into Treasuredata continuously, handling API limits and schema drift as it goes, so each record type arrives as Scheduled Queries, Query Jobs, Databases, Tables ready to report on. The connection is bi-directional, so segments, scores, and metrics computed in Treasuredata can be written back to fields in Linnworks where that is useful.

Common use cases

  • 01 Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.
  • 02 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
  • 03 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels
  • 04 Sync product and listing data with a PIM so channel listings stay aligned with the catalog

Common sync patterns

Where Linnworks runs order-to-cash: customer and account analytics

Orders, invoices, and account records from Linnworks join the behavioral and usage data Treasuredata already tracks, so customer analysis spans activity and dollars in one view.

Where Linnworks runs operations: inventory and fulfillment metrics

Operational records from Linnworks become measurable in Treasuredata, joinable with the rest of what the company tracks for supply and fulfillment reporting.

Where Linnworks is the HR system of record: workforce and cost analysis

Worker and organization data from Linnworks syncs into Treasuredata for headcount, cost, and utilization reporting alongside other company data.

What you can sync between Linnworks and Treasuredata

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 Treasuredata objects How this pairing syncs
Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. Databases Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables. Open Orders is specific to Linnworks and Databases to Treasuredata — each maps to any object or custom field on the other side.
Processed Orders Completed orders feed accounting and warehouse-based margin reporting. Tables Columnar log tables in TD's Plazma storage; every row carries a mandatory `time` column (Unix epoch) that Stacksync uses as the incremental watermark and partition key. Synced two-way with warehouse or database tables. Processed Orders is specific to Linnworks and Tables to Treasuredata — each maps to any object or custom field on the other side.
Stock Items SKU records keep product data aligned with ERPs and PIMs. Master (Parent) Segments Unified customer profiles assembled from multiple source tables in Audience Studio; read out to push enriched attributes onto CRM or warehouse records. Stock Items is specific to Linnworks and Master (Parent) Segments to Treasuredata — each maps to any object or custom field on the other side.
Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. Stock Levels is specific to Linnworks and Segments to Treasuredata — each maps to any object or custom field on the other side.
Locations Warehouse and fulfillment location records scope stock data during mapping. Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. Locations is specific to Linnworks and Journeys to Treasuredata — each maps to any object or custom field on the other side.
Purchase Orders Replenishment POs sync with suppliers and accounting systems. Predictive Segments AI/ML-scored segments; propensity scores read out and written onto customer records in a CRM or database for prioritization. Purchase Orders is specific to Linnworks and Predictive Segments to Treasuredata — each maps to any object or custom field on the other side.

How changes propagate between Linnworks and Treasuredata

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 Treasuredata 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 written to Treasuredata through its API, with automatic retries and rate-limit backoff.

Treasuredata Linnworks Interval-based propagation

DetectionStacksync polls Treasuredata for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column.

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.
  • Treasuredata: TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs.
What ships with Linnworks ⇄ Treasuredata

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Treasuredata

Integration surface
TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys
Authentication
API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints)
Change detection
Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark
Capabilities
read · write
Rate limits
TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs
How it works

How to connect Linnworks to Treasuredata — 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 Treasuredata 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
    Treasuredata connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Linnworks and Treasuredata 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 ⇄ Treasuredata
    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 Treasuredata
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Linnworks and Treasuredata 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 378 integrations available for Linnworks and Treasuredata.

Popular · 6 of 378
All Linnworks integrations All Treasuredata integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own