Skip to content
CRM ⇄ E-commerce

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

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

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

Clari 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 Opportunity field extensions, Audit Events, Forecast, Quota in Clari 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 Stream Audit Events into a reporting database to monitor forecast-submission changes and user activity for compliance.
  • 02 Pull Activity (Capture) meetings and emails, mapped to their accounts and opportunities, into a database for coverage and engagement analysis.
  • 03 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.
  • 04 Sync `customer` records two-way with a CRM so support and marketing see order history while reps write updates back onto the account.

Common sync patterns

Where Clari segments customers: status travels to the store record

Lifecycle stage, tier, or account owner set in Clari syncs onto the customer record in Shopware, so the buying side can act on how the relationship is classified.

Where both keep product records: catalog and CRM products aligned

Where Clari 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 Clari 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.

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

Clari objects Shopware objects How this pairing syncs
Opportunity field extensions Warehouse-computed fields pushed onto Opportunity records via the ingest API; up to 100 records per request or 10MB bulk files. Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. Opportunity field extensions is specific to Clari and Order Deliveries to Shopware — each maps to any object or custom field on the other side.
Audit Events User edits and system events exported with filtering by actor, session, and date range; read-only feed for change tracking and compliance. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Audit Events is specific to Clari and Order Transactions to Shopware — each maps to any object or custom field on the other side.
Forecast Exported per forecast tab and fiscal period via async jobs; includes submitted forecast calls, updates, manager adjustments, and CRM totals. Read-only. Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Forecast is specific to Clari and Sales Channels to Shopware — each maps to any object or custom field on the other side.
Quota Quota and quota-history values exported alongside forecast data, scoped by fiscal quarter; read-only, useful for warehouse attainment reporting. Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. Quota is specific to Clari and Media to Shopware — each maps to any object or custom field on the other side.
Opportunities Retrieved synchronously by ID from GET /opportunity (up to 100 IDs per call) with Clari CRM scoring and field-change history; read-only, mirroring the CRM opportunity Clari sits on. 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. Opportunities is specific to Clari and Products to Shopware — each maps to any object or custom field on the other side.
Activity (Capture) Meetings, emails, and attachments captured by Clari and mapped to accounts and opportunities; exported read-only via async activity jobs. Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. Activity (Capture) is specific to Clari and Categories to Shopware — each maps to any object or custom field on the other side.

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

Clari Shopware Interval-based propagation

DetectionStacksync polls Clari for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reads run as asynchronous export jobs (submit export, poll job status, download results).

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

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

Rate-limit considerations

  • Clari: Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
  • 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 Clari ⇄ Shopware

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Clari and Shopware connectors work

Clari

Integration surface
REST APIs on api.clari.com - Export API (v4, asynchronous bulk jobs for forecast, quota, activity, and audit) and Ingest API (v2, field extensions); Opportunity reads are synchronous via GET /opportunity
Authentication
API token in the apikey header, generated per user in Settings; ingest/partner endpoints also require a partnerkey header, and Copilot endpoints require X-Api-Key and X-Api-Password
Change detection
Polling — reads run as asynchronous export jobs (submit export, poll job status, download results); the ingest API supports an incremental mode for regular field updates. No webhooks.
Capabilities
read · write
Rate limits
Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.

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 Clari 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 Clari 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
    Clari connected
    Shopware connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Clari 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 · Clari ⇄ 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
    Clari Shopware
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Clari 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 380 integrations available for Clari and Shopware.

Popular · 7 of 380
All Clari 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