Skip to content
Database ⇄ E-commerce

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

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

Give your engineers Shopware's products, orders, and customers in Reltio: 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 Reltio 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 Reltio, 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 Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
  • 02 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.
  • 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

Order data where your code can use it

Orders and their status become rows in Reltio for routing, fulfillment, and reporting, without polling the platform.

Controlled write-back

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

Read the store's data with a query

Records from Shopware, whether products, orders, customers, or inventory, live in Reltio as ordinary tables or collections, joinable with the rest of your data.

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

Reltio objects Shopware objects How this pairing syncs
Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Relations is specific to Reltio and Customers to Shopware — each maps to any object or custom field on the other side.
Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. Crosswalks is specific to Reltio and Orders to Shopware — each maps to any object or custom field on the other side.
Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Interactions is specific to Reltio and Order Line Items to Shopware — each maps to any object or custom field on the other side.
Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. Matches (Potential Matches) is specific to Reltio and Order Deliveries to Shopware — each maps to any object or custom field on the other side.
Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Activity Log is specific to Reltio and Order Transactions to Shopware — each maps to any object or custom field on the other side.
Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Data Change Requests (DCR) is specific to Reltio and Sales Channels to Shopware — each maps to any object or custom field on the other side.

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

Reltio Shopware Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

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

Shopware Reltio 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 written to Reltio through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
  • 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 Reltio ⇄ Shopware

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Reltio and Shopware connectors work

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.

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

    Choose tables

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

Reltio 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 389 integrations available for Reltio and Shopware.

Popular · 6 of 389
All Reltio 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