Skip to content
E-commerce ⇄ Database

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

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

Give your engineers Shopware's products, orders, and customers in TimescaleDB: 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 Order Line Items, Order Deliveries, Order Transactions, Sales Channels from Shopware into TimescaleDB 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 TimescaleDB, 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 Sync product or IoT telemetry stored in TimescaleDB into a CRM so account teams see usage metrics next to the customer record.
  • 02 Replicate subscription and billing events from operational Postgres tables into Timescale hypertables for time-series analysis.
  • 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

Keep catalog and inventory current

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

Controlled write-back

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

What you can sync between Shopware and TimescaleDB

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 TimescaleDB objects How this pairing syncs
Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs. Sales Channels is specific to Shopware and Hypertables to TimescaleDB — 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. Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly. Media is specific to Shopware and Chunks to TimescaleDB — 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. Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems. Products is specific to Shopware and Continuous Aggregates to TimescaleDB — 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. Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data. Categories is specific to Shopware and Regular PostgreSQL Tables to TimescaleDB — 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 Standard SQL views used to shape or filter data for consumers. Customers is specific to Shopware and Views to TimescaleDB — 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. Schemas Postgres namespaces used to separate synced datasets by team or environment. Orders is specific to Shopware and Schemas to TimescaleDB — each maps to any object or custom field on the other side.

How changes propagate between Shopware and TimescaleDB

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

TimescaleDB Shopware Sub-second propagation

DetectionChanges in TimescaleDB are captured at the source via change data capture — no polling loop against its API. Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must.

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.
  • TimescaleDB: No API rate limits; throughput is bounded by database resources and connection limits.
What ships with Shopware ⇄ TimescaleDB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

TimescaleDB

Integration surface
SQL wire protocol (PostgreSQL)
Authentication
Database credentials
Change detection
Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by database resources and connection limits.
How it works

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

    Choose tables

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

Shopware and TimescaleDB 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 387 integrations available for Shopware and TimescaleDB.

Popular · 7 of 387
All Shopware integrations All TimescaleDB 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