Skip to content
Accounting and finance ⇄ E-commerce

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

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

Turn every Shopware order into clean revenue: Recurly 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. Recurly 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 Billing Info, Measured Units and Usage, Accounts, Subscriptions in Recurly with Orders, Order Line Items, Order Deliveries, Order Transactions 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 Recurly — 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 Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
  • 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 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 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 Recurly 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.

Recurly objects Shopware objects How this pairing syncs
Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Invoices is specific to Recurly and Order Transactions to Shopware — each maps to any object or custom field on the other side.
Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Transactions is specific to Recurly and Sales Channels to Shopware — each maps to any object or custom field on the other side.
Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. Line Items is specific to Recurly and Media to Shopware — each maps to any object or custom field on the other side.
Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. 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. Coupons and Redemptions is specific to Recurly and Products to Shopware — each maps to any object or custom field on the other side.
Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. Billing Info is specific to Recurly and Categories to Shopware — each maps to any object or custom field on the other side.
Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Measured Units and Usage is specific to Recurly and Customers to Shopware — each maps to any object or custom field on the other side.

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

Recurly Shopware Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

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

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

Rate-limit considerations

  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
  • 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 Recurly ⇄ Shopware

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Recurly and Shopware connectors work

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.

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

    Choose tables

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

Recurly 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 459 integrations available for Recurly and Shopware.

Popular · 8 of 459
All Recurly 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