Real-time
Two-way sync
Changes in Linnworks or Shopware instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ E-commerce
Linnworks to Shopware integration — real-time, two-way sync
Keep Linnworks and Shopware 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 Shopware
Keep the storefront in step with the back office: Shopware and Linnworks share products, inventory, and orders in real time, in both directions.
Shopware runs the storefront and takes the orders; Linnworks owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.
Stacksync syncs Order Deliveries, Order Transactions, Sales Channels, Media in Shopware with Locations, Purchase Orders, Suppliers, Channel Listings in Linnworks field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Linnworks, order and customer detail from Shopware — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Sync `customer` records two-way with a CRM so support and marketing see order history while reps write updates back onto the account.
- 02 Write tracking numbers and delivery state onto `order_delivery` from a 3PL or WMS so storefront order status reflects fulfillment.
- 03 Sync product and listing data with a PIM so channel listings stay aligned with the catalog
- 04 Push customer and order data to a CRM or marketing platform for post-purchase campaigns
Common sync patterns
One product catalog
Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
Fulfillment and shipment status close the loop
As orders are picked, shipped, or invoiced in Linnworks, tracking and status flow back to Shopware so buyers see accurate updates.
One customer master
Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.
What you can sync between Linnworks and Shopware
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 | Shopware objects | How this pairing syncs | |
|---|---|---|---|
| Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. | Processed Orders is specific to Linnworks and Sales Channels to Shopware — each maps to any object or custom field on the other side. | |
| Stock Items SKU records keep product data aligned with ERPs and PIMs. | Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. | Stock Items is specific to Linnworks and Media to Shopware — 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. | Products The product catalog (`product`), including parent/child variants, per-currency nested price arrays, and stock; synced two-way with ERP, PIM, or a database. | Stock Levels is specific to Linnworks and Products to Shopware — each maps to any object or custom field on the other side. | |
| Locations Warehouse and fulfillment location records scope stock data during mapping. | Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. | Locations is specific to Linnworks and Categories to Shopware — each maps to any object or custom field on the other side. | |
| Purchase Orders Replenishment POs sync with suppliers and accounting systems. | Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. | Purchase Orders is specific to Linnworks and Customers to Shopware — each maps to any object or custom field on the other side. | |
| Suppliers Vendor records keep procurement data consistent across tools. | Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. | Suppliers is specific to Linnworks and Orders to Shopware — each maps to any object or custom field on the other side. |
How changes propagate between Linnworks and Shopware
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 Shopware 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 Shopware through its API, with automatic retries and rate-limit backoff.
Shopware Linnworks Sub-second propagation
DetectionShopware notifies Stacksync of record changes through webhook events. App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field.
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.
- Shopware: No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores.
What ships with Linnworks ⇄ Shopware
Connect Linnworks and Shopware for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Linnworks–Shopware connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Linnworks or Shopware 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 Shopware record.
Observability
Monitoring
Track your Linnworks ⇄ Shopware 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 Shopware.
How the Linnworks and Shopware 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
Shopware
- Integration surface
- Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint
- Authentication
- OAuth 2.0 — client-credentials grant using an Integration's Access Key ID + Secret Access Key, or resource-owner password grant for a user; access tokens expire after 10 minutes
- Change detection
- App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field names; otherwise poll on the updatedAt / createdAt fields
- Capabilities
- read · write · webhooks
- Rate limits
- No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores
How it works
How to connect Linnworks to Shopware — 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 Shopware 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
Shopware
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Linnworks and Shopware 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 ⇄ ShopwareCustomers 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 ShopwareCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Linnworks and Shopware integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Linnworks and Shopware: authenticate both systems, choose the objects to sync (such as Linnworks's Processed Orders and Stock Items), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Linnworks: Polling on order and stock endpoints. On Shopware: App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field names; otherwise poll on the updatedAt / createdAt fields. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Shopware side: Order Deliveries, Order Transactions, Sales Channels, Media, plus custom fields where Shopware exposes them. On the Linnworks side: Locations, Purchase Orders, Suppliers, Channel Listings. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Linnworks and Shopware: One product catalog; Fulfillment and shipment status close the loop; One customer master. Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
-
Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Shopware: Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint. Authentication: OAuth 2.0 — client-credentials grant using an Integration's Access Key ID + Secret Access Key, or resource-owner password grant for a user; access tokens expire after 10 minutes. Stacksync manages authentication, retries, and rate limits on both sides.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 462 integrations available for Linnworks and Shopware.
Popular · 5 of 462
-
Linnworks ⇄ Nuorder -
Linnworks ⇄ Shipwire -
Linnworks ⇄ Akeneo -
Linnworks ⇄ Bigcommerce -
Shopware ⇄ Infor WMS
No integrations match .
