Real-time
Two-way sync
Changes in Shopware or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ CRM
Shopware to Twenty CRM integration — real-time, two-way sync
Keep Shopware and Twenty CRM 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 Shopware and Twenty CRM
Keep the customers and orders that Twenty CRM and Shopware share aligned in real time, so sales works from live purchase history and the store works from current account details.
Twenty CRM holds the customer relationship: the contacts, accounts, and deals a go-to-market team works. Shopware runs the buying side: who placed which order, what they bought, and where it ships. The two describe the same people and companies, and when they are connected only by exports, sales answers questions without recent orders in front of them while the store works from account details that changed weeks ago.
Stacksync links Custom Objects, Attachments, Workspace Members, People in Twenty CRM to Customers, Orders, Order Line Items, Order Deliveries in Shopware with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.
The shared entity is the customer, matched on email or an external ID, so both systems agree on who the buyer is and the order history sits next to the relationship instead of in a separate tab.
Common use cases
- 01 Two-way sync of People and Companies between Twenty and a production Postgres database so engineers can query CRM data with SQL.
- 02 Push product usage or billing data from a warehouse into Twenty custom fields to give reps account context.
- 03 Two-way sync of the `product` catalog — titles, nested price arrays, and stock — between Shopware and an ERP or PIM so pricing and inventory stay aligned.
- 04 Stream new `order` records with their `order_line_item`, `order_delivery`, and `order_transaction` rows into a warehouse or accounting system for revenue and fulfillment reporting.
Common sync patterns
Where Shopware records orders: purchase history on the account
Orders and their status from Shopware appear on the matching contact or account in Twenty CRM, so reps see what a customer has bought and what is in flight before the next conversation.
New buyers become CRM records
A customer created in Shopware creates or updates the matching contact or account in Twenty CRM, so first-time and repeat buyers land in the relationship system without a manual import.
Contact and address details stay consistent
An email, phone, or shipping and billing address corrected in either system updates the other, so the next order and the next outreach both use current information.
What you can sync between Shopware and Twenty CRM
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.
| Shopware objects | Twenty CRM objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Tasks To-dos linked to people, companies, or deals. | Products is specific to Shopware and Tasks to Twenty CRM — each maps to any object or custom field on the other side. | |
| Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. | Notes Free-form notes attached to records, useful for mirroring activity from other tools. | Categories is specific to Shopware and Notes to Twenty CRM — each maps to any object or custom field on the other side. | |
| Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. | Custom Objects User-defined objects created in Twenty's data model settings, addressable through the same APIs as standard objects. | Customers is specific to Shopware and Custom Objects to Twenty CRM — each maps to any object or custom field on the other side. | |
| Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. | Attachments Files linked to records. | Orders is specific to Shopware and Attachments to Twenty CRM — each maps to any object or custom field on the other side. | |
| Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. | Workspace Members User accounts used for record ownership and assignment mapping. | Order Line Items is specific to Shopware and Workspace Members to Twenty CRM — each maps to any object or custom field on the other side. | |
| Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. | People Individual contact records with emails, phones, and company links; a core target for contact syncs. | Order Deliveries is specific to Shopware and People to Twenty CRM — each maps to any object or custom field on the other side. |
How changes propagate between Shopware and Twenty CRM
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.
Shopware Twenty CRM 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 Twenty CRM through its API, with automatic retries and rate-limit backoff.
Twenty CRM Shopware Sub-second propagation
DetectionTwenty CRM notifies Stacksync of record changes through webhook events. Webhooks on record create, update, and delete events, or polling on record update timestamps.
DeliveryEach detected change is written to Shopware through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- 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.
- Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
What ships with Shopware ⇄ Twenty CRM
Connect Shopware and Twenty CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Shopware–Twenty CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Shopware or Twenty CRM 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 Shopware or Twenty CRM record.
Observability
Monitoring
Track your Shopware ⇄ Twenty CRM sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Shopware and Twenty CRM.
How the Shopware and Twenty CRM connectors work
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
Twenty CRM
- Integration surface
- GraphQL and REST APIs
- Authentication
- API key
- Change detection
- Webhooks on record create, update, and delete events, or polling on record update timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits; self-hosted deployments control their own limits.
How it works
How to connect Shopware to Twenty CRM — 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 Shopware and Twenty CRM with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Shopware
connected
Twenty CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Shopware and Twenty CRM 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 · Shopware ⇄ Twenty CRMCustomers 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.
Shopware Twenty CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Shopware and Twenty CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Shopware and Twenty CRM: authenticate both systems, choose the objects to sync (such as Shopware's Products and Categories), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Twenty CRM side: Custom Objects, Attachments, Workspace Members, People, plus custom fields where Twenty CRM exposes them. On the Shopware side: Customers, Orders, Order Line Items, Order Deliveries. 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 Shopware and Twenty CRM: Where Shopware records orders: purchase history on the account; New buyers become CRM records; Contact and address details stay consistent. Orders and their status from Shopware appear on the matching contact or account in Twenty CRM, so reps see what a customer has bought and what is in flight before the next conversation.
-
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. Twenty CRM: GraphQL and REST APIs. Authentication: API key. Stacksync manages authentication, retries, and rate limits on both sides.
-
Twenty CRM: Both GraphQL and REST APIs are generated from the workspace's object schema, so custom objects get the same API surface as standard ones. Shopware: Prices are stored per currency as a nested price array with net and gross values, and products model variants as parent/child rows, so field mappings must handle nested structures. Stacksync's field mapping accounts for these differences between Shopware and Twenty CRM without custom code.
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 393 integrations available for Shopware and Twenty CRM.
Popular · 7 of 393
-
Shopware ⇄ Infor CRM -
Shopware ⇄ Insightly -
Shopware ⇄ Intercom -
Shopware ⇄ Kommo -
Twenty CRM ⇄ Shipwire -
Twenty CRM ⇄ Akeneo -
Twenty CRM ⇄ Bigcommerce
No integrations match .
