Skip to content
Database ⇄ E-commerce

InterSystems IRIS to Shopware integration — real-time, two-way sync

Keep InterSystems IRIS 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 InterSystems IRIS and Shopware

Give your engineers Shopware's products, orders, and customers in InterSystems IRIS: 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 InterSystems IRIS 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 InterSystems IRIS, 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 IRIS data with other databases in an analytics warehouse for cross-system reporting
  • 02 Keep reference data consistent between an IRIS-based clinical or financial application and downstream SaaS tools
  • 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

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the Shopware API, rate limits, and retries.

React to store changes

Updates in Shopware arrive as row changes in InterSystems IRIS, 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 InterSystems IRIS sync back onto Shopware, so the storefront shows what your systems treat as true.

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

InterSystems IRIS objects Shopware objects How this pairing syncs
Namespaces Namespaces partition databases and determine the connection context for integrations. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Namespaces is specific to InterSystems IRIS and Order Line Items to Shopware — each maps to any object or custom field on the other side.
Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. Stored Procedures is specific to InterSystems IRIS and Order Deliveries to Shopware — each maps to any object or custom field on the other side.
Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Tables is specific to InterSystems IRIS and Order Transactions to Shopware — each maps to any object or custom field on the other side.
Views SQL views expose curated slices of data for outbound replication. Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Views is specific to InterSystems IRIS and Sales Channels to Shopware — each maps to any object or custom field on the other side.
Schemas Schema organization scopes which tables a sync connection can see. Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. Schemas is specific to InterSystems IRIS and Media to Shopware — each maps to any object or custom field on the other side.
Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. 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. Persistent Classes is specific to InterSystems IRIS and Products to Shopware — each maps to any object or custom field on the other side.

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

InterSystems IRIS Shopware Interval-based propagation

DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).

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

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

Rate-limit considerations

  • InterSystems IRIS: Constrained by database resources rather than published API rate 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 InterSystems IRIS ⇄ Shopware

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the InterSystems IRIS and Shopware connectors work

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate 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 InterSystems IRIS 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 InterSystems IRIS 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
    InterSystems IRIS connected
    Shopware connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

InterSystems IRIS 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 425 integrations available for InterSystems IRIS and Shopware.

Popular · 7 of 425
All InterSystems IRIS 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