Skip to content
Data warehouse ⇄ E-commerce

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

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

Make Exasol the analytics and enrichment layer behind Shopware: orders, products, and customers stay current in both directions.

Exasol is the analytical store where the business joins, models, and reports on its data; Shopware runs the storefront, catalog, and transactions that generate most of it. The overlap is every record that has to be counted and enriched on one side and acted on the other — and when the bridge is a nightly export, the warehouse reports on yesterday while the store operates without the segments and metrics the warehouse just computed.

Stacksync syncs Users and roles, Schemas, Tables, Views in Exasol with Media, Products, Categories, Customers in Shopware field by field, in real time, and in both directions. Transactional records land in the warehouse as they change, computed attributes and cleaned catalog data flow back to the store, and you decide which system owns which fields so Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Keep dimension tables such as customers and products aligned with the systems of record.
  • 02 Load CRM and ERP records into Exasol tables on a schedule so analysts query fresh operational data.
  • 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

One product catalog

Where both systems hold product or catalog data, cleaned and enriched attributes stay aligned so the store and the warehouse describe the same items.

Inventory and order status reconciled

Stock levels and order or fulfillment status move between Exasol and Shopware so counts and states agree across reporting and operations.

One customer master

Where both systems keep customer records, corrections in either propagate to the other so analytics and the storefront share one identity.

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

Exasol objects Shopware objects How this pairing syncs
Views Read-only query surfaces often used as curated sources for reverse ETL. Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. Views is specific to Exasol and Categories to Shopware — each maps to any object or custom field on the other side.
Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Virtual schemas is specific to Exasol and Customers to Shopware — each maps to any object or custom field on the other side.
UDF scripts In-database functions that can transform synced data after load. Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. UDF scripts is specific to Exasol and Orders to Shopware — each maps to any object or custom field on the other side.
Users and roles Grant read/write access for the dedicated integration account. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Users and roles is specific to Exasol and Order Line Items to Shopware — each maps to any object or custom field on the other side.
Schemas Namespaces that group the tables a sync reads from or writes into. Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. Schemas is specific to Exasol and Order Deliveries to Shopware — each maps to any object or custom field on the other side.
Tables Primary sync target; columnar relational tables written with standard SQL. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Tables is specific to Exasol and Order Transactions to Shopware — each maps to any object or custom field on the other side.

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

Exasol Shopware Interval-based propagation

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

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

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

Rate-limit considerations

  • Exasol: No API quota; concurrency is bounded by cluster resources and session 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 Exasol ⇄ Shopware

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Exasol and Shopware connectors work

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session limits

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

    Choose tables

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

Exasol 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 Exasol and Shopware.

Popular · 7 of 390
All Exasol 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