Skip to content
E-commerce ⇄ CRM

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

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

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

Vitally 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 Account, User, Organization, Task in Vitally to Sales Channels, Media, Products, Categories 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 Sync account health scores and lifecycle stages from Vitally into a CRM so sales sees churn risk before renewals.
  • 02 Mirror product-usage traits and NPS responses into a warehouse for retention and expansion reporting.
  • 03 Consolidate orders and customers from multiple `sales_channel` storefronts into one Postgres database for cross-channel analysis.
  • 04 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.

Common sync patterns

New buyers become CRM records

A customer created in Shopware creates or updates the matching contact or account in Vitally, 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 Vitally segments customers: status travels to the store record

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

What you can sync between Shopware and Vitally

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 Vitally objects How this pairing syncs
Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Conversation Customer conversations logged in Vitally; activity objects include parent object details in the payload. Order Line Items is specific to Shopware and Conversation to Vitally — 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. NPS Response NPS survey responses for account-health reporting. Order Deliveries is specific to Shopware and NPS Response to Vitally — each maps to any object or custom field on the other side.
Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Custom Trait Custom account and user traits for segmentation. Order Transactions is specific to Shopware and Custom Trait to Vitally — each maps to any object or custom field on the other side.
Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Account Core customer account records with health scores and lifecycle traits; created, updated, retrieved, and listed via the REST API. Sales Channels is specific to Shopware and Account to Vitally — each maps to any object or custom field on the other side.
Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. User End users tied to accounts, including activity and custom traits. Media is specific to Shopware and User to Vitally — each maps to any object or custom field on the other side.
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. Organization Parent organizations for hierarchical B2B account structures. Products is specific to Shopware and Organization to Vitally — each maps to any object or custom field on the other side.

How changes propagate between Shopware and Vitally

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

Vitally Shopware Sub-second propagation

DetectionVitally notifies Stacksync of record changes through webhook events. Incremental polling on updatedAt cursors.

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.
  • Vitally: Default rate limit of 1,000 requests/min (token bucket); write operations consume more budget, headers expose remaining quota.
What ships with Shopware ⇄ Vitally

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Shopware ⇄ Vitally 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 Vitally.

How the Shopware and Vitally 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

Vitally

Integration surface
REST API with cursor-based pagination (sortable by createdAt/updatedAt)
Authentication
API key via Basic Auth; keys created in Settings -> Integrations -> REST API and individually revocable
Change detection
Incremental polling on updatedAt cursors; playbook-triggered webhooks can push events for near real-time updates
Capabilities
read · write · webhooks
Rate limits
Default rate limit of 1,000 requests/min (token bucket); write operations consume more budget, headers expose remaining quota.
How it works

How to connect Shopware to Vitally — 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 Shopware and Vitally 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
    Shopware connected
    Vitally connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Shopware and Vitally 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 369 integrations available for Shopware and Vitally.

Popular · 7 of 369
All Shopware integrations All Vitally 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