Skip to content
CRM ⇄ E-commerce

6sense to Shopware integration — real-time data sync

Keep 6sense 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 6sense and Shopware

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

6sense is a read-only source: Stacksync reads its data in real time and delivers it into Shopware, so Shopware always reflects the current state of 6sense — without exports, scripts, or schedulers.

6sense 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.

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 Pull segment membership into a marketing automation platform to trigger campaigns when accounts enter a segment.
  • 02 Land account-level intent data in a warehouse to join with pipeline data for ABM reporting.
  • 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

New buyers become CRM records

A customer created in Shopware creates or updates the matching contact or account in 6sense, 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.

Where 6sense segments customers: status travels to the store record

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

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

6sense objects Shopware objects How this pairing syncs
Segments Dynamic account lists built from intent and fit criteria, read out to drive targeting. 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. Segments is specific to 6sense and Products to Shopware — each maps to any object or custom field on the other side.
Buying Stage Scores Model-predicted stage per account, synced onto CRM records for prioritization. Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. Buying Stage Scores is specific to 6sense and Categories to Shopware — each maps to any object or custom field on the other side.
Intent Signals Keyword-level research activity used to flag in-market accounts. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Intent Signals is specific to 6sense and Customers to Shopware — each maps to any object or custom field on the other side.
People / Contacts Persona and contact data surfaced for accounts, used to build outreach lists. Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. People / Contacts is specific to 6sense and Orders to Shopware — each maps to any object or custom field on the other side.
Reach Scores Model scores reflecting the level and recency of outreach to an account or contact, used to prioritize follow-up. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Reach Scores is specific to 6sense and Order Line Items to Shopware — each maps to any object or custom field on the other side.
Accounts Company records enriched with firmographics and intent data, matched to CRM accounts. Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. Accounts is specific to 6sense and Order Deliveries to Shopware — each maps to any object or custom field on the other side.

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

6sense Shopware Interval-based propagation

DetectionStacksync polls 6sense for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

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

Shopware 6sense 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.

Delivery6sense does not accept inbound record writes, so this direction carries requests rather than records: 6sense's output flows back as field updates on the originating Shopware records.

Rate-limit considerations

  • 6sense: Subject to the platform's API rate limits, which vary by contracted API package.
  • 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 6sense ⇄ Shopware

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the 6sense and Shopware connectors work

6sense

Integration surface
REST API
Authentication
API key (token passed in request headers)
Change detection
Polling; scores and segment membership are typically refreshed on the platform's model update cadence
Capabilities
read
Rate limits
Subject to the platform's API rate limits, which vary by contracted API package

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

    Choose tables

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

6sense 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 390 integrations available for 6sense and Shopware.

Popular · 8 of 390
All 6sense 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