Skip to content
E-commerce ⇄ Data warehouse

Shopware to Starburst Enterprise integration — real-time, two-way sync

Keep Shopware and Starburst Enterprise 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 Starburst Enterprise

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

Starburst Enterprise 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 Views, Materialized views, Columns, Catalogs in Starburst Enterprise with Orders, Order Line Items, Order Deliveries, Order Transactions 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 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
  • 02 Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
  • 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

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 Starburst Enterprise 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 Shopware and Starburst Enterprise

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 Starburst Enterprise objects How this pairing syncs
Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Columns Typed per the Trino type system, mapped from each source's native types. Sales Channels is specific to Shopware and Columns to Starburst Enterprise — 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. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Media is specific to Shopware and Catalogs to Starburst Enterprise — 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. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Products is specific to Shopware and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side.
Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. Tables Queryable relations; writes pass through to sources whose connectors support them. Categories is specific to Shopware and Tables to Starburst Enterprise — each maps to any object or custom field on the other side.
Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Views Engine-level SQL views used to shape federated data before syncing it out. Customers is specific to Shopware and Views to Starburst Enterprise — each maps to any object or custom field on the other side.
Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. Materialized views Precomputed results that make repeated sync reads cheaper. Orders is specific to Shopware and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Shopware and Starburst Enterprise

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

Starburst Enterprise Shopware Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

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.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Shopware ⇄ Starburst Enterprise

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

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

    Choose tables

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

Shopware and Starburst Enterprise 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 394 integrations available for Shopware and Starburst Enterprise.

Popular · 7 of 394
All Shopware integrations All Starburst Enterprise 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