Skip to content
CRM ⇄ E-commerce

Kommo to Shopware integration — real-time, two-way sync

Keep Kommo 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 Kommo and Shopware

Keep the customers and orders that Kommo and Shopware share aligned in real time, so sales works from live purchase history and the store works from current account details.

Kommo 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 Users, Chats, Leads, Contacts in Kommo to Media, Products, Categories, Customers 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 Keep customer records consistent between Kommo and invoicing or ERP systems
  • 02 Mirror pipeline stage changes into BI tools for forecasting
  • 03 Write tracking numbers and delivery state onto `order_delivery` from a 3PL or WMS so storefront order status reflects fulfillment.
  • 04 Consolidate orders and customers from multiple `sales_channel` storefronts into one Postgres database for cross-channel analysis.

Common sync patterns

Where both keep product records: catalog and CRM products aligned

Where Kommo tracks products or line items and Shopware holds the catalog, shared items are matched on SKU so quotes, deals, and orders reference the same products.

One customer identity across sales and store

A person who exists as a contact in Kommo and a buyer in Shopware is kept as a single, deduplicated record, so both teams work from the same customer instead of two partial copies.

Where Shopware records orders: purchase history on the account

Orders and their status from Shopware appear on the matching contact or account in Kommo, so reps see what a customer has bought and what is in flight before the next conversation.

What you can sync between Kommo 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.

Kommo objects Shopware objects How this pairing syncs
Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. Chats is specific to Kommo and Media to Shopware — each maps to any object or custom field on the other side.
Leads The central pipeline record; external signups and form fills sync in as leads. 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. Leads is specific to Kommo and Products to Shopware — each maps to any object or custom field on the other side.
Contacts Person records sync with other CRMs and databases for a shared contact file. Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. Contacts is specific to Kommo and Categories to Shopware — each maps to any object or custom field on the other side.
Companies Organization records map to accounts in ERPs and invoicing tools. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Companies is specific to Kommo and Customers to Shopware — each maps to any object or custom field on the other side.
Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. Pipelines & Statuses is specific to Kommo and Orders to Shopware — each maps to any object or custom field on the other side.
Tasks Follow-up records keep rep activity consistent across systems. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Tasks is specific to Kommo and Order Line Items to Shopware — each maps to any object or custom field on the other side.

How changes propagate between Kommo 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.

Kommo Shopware Sub-second propagation

DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.

DeliveryEach detected change is written to Shopware through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • Kommo: Subject to per-account request rate limits.
  • 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 Kommo ⇄ Shopware

Connect Kommo and Shopware for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Kommo or Shopware instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Kommo 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 Kommo or Shopware record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Kommo and Shopware.

How the Kommo and Shopware connectors work

Kommo

Integration surface
REST API
Authentication
OAuth 2.0 with refresh tokens
Change detection
Webhooks on record add and update events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to per-account request rate limits

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 Kommo 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.

  1. 01

    Connect your apps

    Authenticate Kommo 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Kommo connected
    Shopware connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Kommo 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Kommo ⇄ Shopware
    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
    Kommo Shopware
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Kommo and Shopware 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 476 integrations available for Kommo and Shopware.

Popular · 8 of 476
All Kommo integrations All Shopware 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