Skip to content
Database ⇄ E-commerce

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

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

Give your engineers Shopware's products, orders, and customers in MySQL: 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 Orders, Order Line Items, Order Deliveries, Order Transactions from Shopware into MySQL 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 MySQL, 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 Two-way sync between a MySQL application database and a CRM so operational records and sales records stay identical
  • 02 Expose SaaS objects as MySQL tables so legacy internal tools built on MySQL can read live business data
  • 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

Keep catalog and inventory current

Prices, stock levels, or product details maintained in MySQL 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 MySQL for routing, fulfillment, and reporting, without polling the platform.

Controlled write-back

Choose exactly which tables and fields may flow from MySQL back into Shopware, keeping the store authoritative on what it owns.

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

MySQL objects Shopware objects How this pairing syncs
Triggers An alternative change-capture mechanism when binlog access is unavailable. Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. Triggers is specific to MySQL and Orders to Shopware — each maps to any object or custom field on the other side.
Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Databases (Schemas) is specific to MySQL and Order Line Items to Shopware — each maps to any object or custom field on the other side.
Tables The primary sync target; rows map to records in connected systems. Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. Tables is specific to MySQL and Order Deliveries to Shopware — each maps to any object or custom field on the other side.
Views Read-side projections used as outbound sync sources. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Views is specific to MySQL and Order Transactions to Shopware — each maps to any object or custom field on the other side.
Columns Field-level mapping targets with engine-typed values. Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Columns is specific to MySQL and Sales Channels to Shopware — each maps to any object or custom field on the other side.
Primary and Unique Keys Match keys for idempotent upserts and conflict handling. Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. Primary and Unique Keys is specific to MySQL and Media to Shopware — each maps to any object or custom field on the other side.

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

MySQL Shopware Sub-second propagation

DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.

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

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

Rate-limit considerations

  • MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
  • 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 MySQL ⇄ Shopware

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the MySQL and Shopware connectors work

MySQL

Integration surface
SQL wire protocol (MySQL client/server protocol)
Authentication
Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
Change detection
Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by connection limits and server resources
MySQL 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 MySQL 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 MySQL 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
    MySQL connected
    Shopware connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

MySQL 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 504 integrations available for MySQL and Shopware.

Popular · 8 of 504
All MySQL 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