Real-time
Two-way sync
Changes in Linnworks or Salesforce instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ CRM
Linnworks to Salesforce integration — real-time, two-way sync
Keep Linnworks and Salesforce 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 Salesforce
Close the gap between front office and back office: Salesforce and Linnworks share customers and status in real time, in both directions.
Salesforce holds the customer relationship; Linnworks runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Cases, Campaigns, Tasks and Events, Products and Price Books in Salesforce with Open Orders, Processed Orders, Stock Items, Stock Levels in Linnworks field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
- Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
- Sync orders from Linnworks into an ERP or accounting system as they are processed, without CSV exports
- Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
Where Linnworks handles order-to-cash: closed-won flows through
A deal won in Salesforce creates or updates the customer in Linnworks with clean data, so fulfillment and invoicing start without re-entry.
Where Linnworks is the finance system of record: money status on the account
Invoice and payment state from Linnworks shows on the account in Salesforce, so reps see balances before promising the next order.
One customer master
Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
What you can sync between Linnworks and Salesforce
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 | Salesforce objects | |
|---|---|---|
| Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | Cases Support records; synced with help desk tools or internal databases for escalation workflows. | |
| Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | |
| Stock Items SKU records keep product data aligned with ERPs and PIMs. | Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. | |
| Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. | |
| Locations Warehouse and fulfillment location records scope stock data during mapping. | Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | |
| Purchase Orders Replenishment POs sync with suppliers and accounting systems. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. |
What ships with Linnworks ⇄ Salesforce
Connect Linnworks and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Linnworks–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Linnworks or Salesforce 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 Salesforce record.
Observability
Monitoring
Track your Linnworks ⇄ Salesforce 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 Salesforce.
How the Linnworks and Salesforce 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
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect Linnworks to Salesforce — 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 Salesforce 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
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Linnworks and Salesforce 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 ⇄ SalesforceCustomers 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 SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Linnworks and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Linnworks and Salesforce: authenticate both systems, choose the objects to sync (such as Linnworks's Open Orders and Processed Orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Linnworks and Salesforce: Where Linnworks handles order-to-cash: closed-won flows through; Where Linnworks is the finance system of record: money status on the account; One customer master. A deal won in Salesforce creates or updates the customer in Linnworks with clean data, so fulfillment and invoicing start without re-entry.
-
Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Salesforce: REST, SOAP, and Bulk APIs. Authentication: OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode. Stacksync manages authentication, retries, and rate limits on both sides.
-
Salesforce: Non-writable objects, non-triggerable objects (trigger mode), and tables without a last_modified_data column (polling mode) cannot be synced yet. Linnworks: Orders are modeled in two populations, open orders and processed orders, and syncs typically treat processing as the state transition that moves a record between them. Stacksync's field mapping accounts for these differences between Linnworks and Salesforce without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Linnworks and Salesforce records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Linnworks and Salesforce connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Linnworks–Salesforce integration in-house.
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 Salesforce.
Popular · 8 of 386
-
Linnworks ⇄ Kommo -
Linnworks ⇄ Kustomer -
Linnworks ⇄ Nimble -
Linnworks ⇄ Nutshell -
Salesforce ⇄ QAD ERP -
Salesforce ⇄ Rootstock ERP -
Salesforce ⇄ Sage 100 - Salesforce ⇄ Sage 300
No integrations match .
