Skip to content
ERP

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

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

Two ERPs, one set of facts: Stacksync keeps Cin7 and Linnworks 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 Sales orders, Purchase orders, Contacts, Branches / locations in Cin7 with Shipping Services, Open Orders, Processed Orders, Stock Items in Linnworks 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

  • Keep customer records aligned between Cin7 and the CRM to remove duplicate account entry.
  • Write purchase orders created in a planning tool back into Cin7 for receiving.
  • Sync product and listing data with a PIM so channel listings stay aligned with the catalog
  • Push customer and order data to a CRM or marketing platform for post-purchase campaigns

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 Cin7 and Linnworks

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.

Cin7 objects Linnworks objects
Branches / locations Warehouse entities that scope every stock movement and order allocation. Returns & Refunds Post-sale records flow to finance and support systems.
Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. Shipping Services Carrier and service definitions support label and tracking data in order syncs.
Credit notes / returns Return documents synced so finance and support see the same refund state. Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems.
Products SKU records with options and pricing, synced with storefront and marketplace catalogs. Processed Orders Completed orders feed accounting and warehouse-based margin reporting.
Inventory levels Stock on hand by branch or location, published outward for availability. Stock Items SKU records keep product data aligned with ERPs and PIMs.
Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability.
What ships with Cin7 ⇄ Linnworks

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Cin7 ⇄ Linnworks sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Cin7 and Linnworks.

How the Cin7 and Linnworks connectors work

Cin7

Integration surface
REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
Authentication
API key credentials (paired with a username or account ID, depending on the product)
Change detection
Polling on modified-date filters; webhook support exists on some editions for order and stock events
Capabilities
read · write · webhooks
Rate limits
Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core

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
How it works

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

    Choose tables

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

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

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.