Skip to content
Accounting and finance ⇄ E-commerce

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

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

Turn every Shopware order into clean revenue: Rillet and Shopware keep customers, orders, and payment status aligned in real time, in both directions.

Shopware runs the storefront — the catalog, the orders, and the buyers placing them. Rillet records the money behind those orders — invoices, revenue, payments, and the ledger the business closes on. The overlap is every customer, order, and product both sides need to agree on, and when that overlap is bridged by CSV export or an overnight batch, finance reconciles against stale numbers while the store quotes prices or stock the books no longer recognize.

Stacksync syncs Charge, Reimbursement, Custom Field, Account in Rillet with Order Deliveries, Order Transactions, Sales Channels, Media in Shopware field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Shopware, its paid-or-overdue state from Rillet — and Stacksync keeps every copy consistent and resolves conflicts by the rules you set.

The result is one shared record of who bought what and whether it has been paid, so the storefront, support, and the finance team all read from the same current data instead of re-keying it between systems.

Common use cases

  • 01 Sync AR and collection status back to customer success tools ahead of renewals.
  • 02 Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
  • 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 customer master

Where both systems keep customer or buyer records, an edit in either propagates to the other, ending duplicate accounts and mismatched contact details.

Catalog and pricing stay aligned

Products, SKUs, and prices maintained on one side propagate to the other, so what the store sells and what the ledger books stay in step.

Refunds and credits reconcile

Refunds, cancellations, and credit notes raised in either system update the corresponding record in the other, keeping balances honest on both sides.

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

Rillet objects Shopware objects How this pairing syncs
Customer Synced with incremental and full sync per the Stacksync docs. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Invoice Payment Synced with incremental and full sync per the Stacksync docs. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Invoice Payment is specific to Rillet and Order Line Items to Shopware — each maps to any object or custom field on the other side.
Charge Synced with incremental and full sync per the Stacksync docs. Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. Charge is specific to Rillet and Order Deliveries to Shopware — each maps to any object or custom field on the other side.
Reimbursement Synced with incremental and full sync per the Stacksync docs. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Reimbursement is specific to Rillet and Order Transactions to Shopware — each maps to any object or custom field on the other side.
Custom Field Synced with incremental and full sync per the Stacksync docs. Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Custom Field is specific to Rillet and Sales Channels to Shopware — each maps to any object or custom field on the other side.
Account Synced with incremental and full sync per the Stacksync docs. Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. Account is specific to Rillet and Media to Shopware — each maps to any object or custom field on the other side.

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

Rillet Shopware Sub-second propagation

DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.

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

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

Rate-limit considerations

  • Rillet: Subject to the platform's 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 Rillet ⇄ Shopware

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Rillet and Shopware connectors work

Rillet

Integration surface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
Change detection
Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
Capabilities
read · write · CDC · webhooks
Rate limits
Subject to the platform's API rate limits.
Rillet setup guide

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

    Choose tables

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

Rillet 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 385 integrations available for Rillet and Shopware.

Popular · 7 of 385
All Rillet 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