Skip to content
CRM ⇄ E-commerce

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

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

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

Attio 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 People, Companies, Users, Deals in Attio to Categories, Customers, Orders, Order Line Items 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 Run a two-way dual-run when migrating to Attio from another CRM.
  • 02 Sync companies, people, and deals with Postgres so ops teams enrich and update CRM records with SQL.
  • 03 Sync `customer` records two-way with a CRM so support and marketing see order history while reps write updates back onto the account.
  • 04 Write tracking numbers and delivery state onto `order_delivery` from a 3PL or WMS so storefront order status reflects fulfillment.

Common sync patterns

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 Attio segments customers: status travels to the store record

Lifecycle stage, tier, or account owner set in Attio 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 Attio 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.

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

Attio objects Shopware objects How this pairing syncs
Workspaces Synced with incremental and full sync per the Stacksync docs. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Workspaces is specific to Attio and Customers to Shopware — each maps to any object or custom field on the other side.
Custom objects Workspace-defined objects that behave like standard ones in the API. Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. Custom objects is specific to Attio and Orders to Shopware — each maps to any object or custom field on the other side.
People Standard person object; synced with marketing tools and warehouse person tables. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. People is specific to Attio and Order Line Items to Shopware — each maps to any object or custom field on the other side.
Companies Standard company object; matched to billing and product accounts in two-way syncs. Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. Companies is specific to Attio and Order Deliveries to Shopware — each maps to any object or custom field on the other side.
Users Synced with incremental and full sync per the Stacksync docs. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Users is specific to Attio and Order Transactions to Shopware — each maps to any object or custom field on the other side.
Deals Pipeline records; read out for revenue reporting and written to from automation. Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Deals is specific to Attio and Sales Channels to Shopware — each maps to any object or custom field on the other side.

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

Attio Shopware Sub-second propagation

DetectionAttio notifies Stacksync of record changes through webhook events. Webhooks on record and list-entry events, with polling as a fallback.

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

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

Rate-limit considerations

  • Attio: Subject to the platform's published API 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 Attio ⇄ Shopware

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Attio and Shopware connectors work

Attio

Integration surface
REST API
Authentication
Guided in-app connection ("Attio CRM" connection created in a few clicks, "without any coding required"); the docs do not name the underlying auth mechanism (OAuth vs API key)
Change detection
Webhooks on record and list-entry events, with polling as a fallback
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's published API rate limits.
Attio setup guide

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

    Choose tables

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

Attio 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 488 integrations available for Attio and Shopware.

Popular · 8 of 488
All Attio 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