Skip to content
E-commerce ⇄ Database

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

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

Give your engineers Shopware's products, orders, and customers in SingleStore: read them with normal queries, write inventory and prices back through the sync, and skip the storefront API.

E-commerce data sits behind an API built for the storefront, not for your internal systems. Teams that need those records, for order routing, inventory logic, reporting, or back-office tools, end up writing integration code against a rate-limited API and maintaining it through every catalog change and platform upgrade.

Stacksync mirrors Media, Products, Categories, Customers from Shopware into SingleStore and keeps both sides consistent in real time. Whatever Shopware holds, whether products, orders, customers, or inventory, those records become rows your code can query, and changes written in SingleStore, such as new prices, stock levels, or fulfillment status, sync back into Shopware with its validations respected.

Merchandising and operations keep working in the storefront, engineers keep working in the database, and neither side has to reconcile against a nightly export.

Common use cases

  • 01 Consolidate data from transactional databases and SaaS apps into one store that handles both lookups and scans.
  • 02 Keep reference data consistent between SingleStore and application databases.
  • 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

React to store changes

Updates in Shopware arrive as row changes in SingleStore, so jobs and triggers can respond the moment an order, price, or stock level changes.

Keep catalog and inventory current

Prices, stock levels, or product details maintained in SingleStore sync back onto Shopware, so the storefront shows what your systems treat as true.

Order data where your code can use it

Orders and their status become rows in SingleStore for routing, fulfillment, and reporting, without polling the platform.

What you can sync between Shopware and SingleStore

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 SingleStore objects How this pairing syncs
Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Stored Procedures Existing logic sometimes invoked on write paths. Order Line Items is specific to Shopware and Stored Procedures to SingleStore — 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. Indexes and Shard Keys Determine data distribution and lookup speed for sync match keys. Order Deliveries is specific to Shopware and Indexes and Shard Keys to SingleStore — 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. Databases The connection target containing the tables a sync addresses. Order Transactions is specific to Shopware and Databases to SingleStore — 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. Tables (rowstore and columnstore) Primary read/write target; storage type affects whether a table suits point lookups or scans. Sales Channels is specific to Shopware and Tables (rowstore and columnstore) to SingleStore — 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. Views Read-only projections used as curated sync sources. Media is specific to Shopware and Views to SingleStore — 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. Reference Tables Small tables replicated to every node, often used for dimension data in syncs. Products is specific to Shopware and Reference Tables to SingleStore — each maps to any object or custom field on the other side.

How changes propagate between Shopware and SingleStore

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 SingleStore 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 applied to SingleStore as a row-level write, with types converted between the two schemas.

SingleStore Shopware Interval-based propagation

DetectionStacksync polls SingleStore for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or watermark columns.

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.
  • SingleStore: No API rate limits; throughput is bounded by workspace or cluster size.
What ships with Shopware ⇄ SingleStore

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

SingleStore

Integration surface
SQL over the MySQL wire protocol; an HTTP Data API is also available for SQL over REST
Authentication
Database credentials
Change detection
Polling on timestamp or watermark columns; the platform also provides change-observation features in recent versions
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by workspace or cluster size
How it works

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

    Choose tables

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

Shopware and SingleStore 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 407 integrations available for Shopware and SingleStore.

Popular · 7 of 407
All Shopware integrations All SingleStore 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