Skip to content
Accounting and finance ⇄ CRM

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

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

Sync customers, invoices, and payment status between Recurly and Shopify in real time, so sales sees the money and finance sees the relationship.

Finance and sales describe the same customers in different systems. Shopify knows the relationship: who the contacts are and what is in motion with the account. Recurly knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.

Stacksync links Coupons and Redemptions, Billing Info, Measured Units and Usage, Accounts in Recurly to Abandoned Checkouts, Products, ProductMedias, ProductVariants in Shopify with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.

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 inventory levels from a WMS or ERP into Shopify locations to keep availability accurate.
  • 04 Mirror the product catalog from a PIM or database into Shopify products, variants, and metafields.

Common sync patterns

Collections with context

Finance sees the account owner and relationship history from Shopify when chasing a balance, and sales sees that the chase is happening.

Where Shopify tracks deals: closed-won creates the finance record

A won opportunity creates or updates the customer in Recurly with the right billing details, so invoicing starts without re-keying.

Payment status on the account

Invoice and payment status from Recurly appears on the account in Shopify, so reps see overdue balances before they promise the next order.

What you can sync between Recurly and Shopify

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 Shopify objects How this pairing syncs
Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Abandoned Checkouts Synced with incremental and full sync per the Stacksync docs. Line Items is specific to Recurly and Abandoned Checkouts to Shopify — 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 Catalog entries; often mastered in a PIM or ERP and written into Shopify. Coupons and Redemptions is specific to Recurly and Products to Shopify — 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). ProductMedias Synced with incremental and full sync per the Stacksync docs. Billing Info is specific to Recurly and ProductMedias to Shopify — 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. ProductVariants Synced with incremental and full sync per the Stacksync docs. Measured Units and Usage is specific to Recurly and ProductVariants to Shopify — each maps to any object or custom field on the other side.
Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. Orders Purchase transactions; pushed to ERPs for fulfillment and billing, and read into databases for reporting. Accounts is specific to Recurly and Orders to Shopify — each maps to any object or custom field on the other side.
Subscriptions Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting. Customers Buyer records; matched to CRM contacts for marketing and lifetime-value analysis. Subscriptions is specific to Recurly and Customers to Shopify — each maps to any object or custom field on the other side.

How changes propagate between Recurly and Shopify

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

Shopify Recurly Sub-second propagation

DetectionShopify notifies Stacksync of record changes through webhook events. Webhook topics per resource, with polling on updated_at as a fallback.

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.
  • Shopify: GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
What ships with Recurly ⇄ Shopify

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Recurly ⇄ Shopify 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 Shopify.

How the Recurly and Shopify 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.

Shopify

Integration surface
GraphQL Admin API (primary) and REST Admin API (legacy)
Authentication
OAuth via a custom Shopify app: admin creates an app in the Shopify Dev Dashboard, enables required API scopes, sets the Stacksync redirect URL, then supplies shop name + Client ID and Client Secret to Stacksync
Change detection
Webhook topics per resource, with polling on updated_at as a fallback
Capabilities
read · write · webhooks
Rate limits
GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
Shopify setup guide
How it works

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

    Choose tables

    Pick the Recurly and Shopify 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 ⇄ Shopify
    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 Shopify
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Recurly and Shopify 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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 527 integrations available for Recurly and Shopify.

Popular · 8 of 527
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.