Skip to content
E-commerce ⇄ Accounting and finance

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

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

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

Channelengine 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 Line Items, Coupons and Redemptions, Billing Info, Measured Units and Usage in Recurly with Returns, Cancellations, Backorders, Order documents in Channelengine field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Channelengine, 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 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
  • 02 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.
  • 03 Load Orders and Returns into Postgres or a warehouse for marketplace sales, fulfillment, and margin reporting without manual CSV exports.
  • 04 Push product content from a PIM, ERP, or database into ChannelEngine's Products endpoint so listings stay current across every connected marketplace.

Common sync patterns

Where Recurly is the money system of record: payment status on the order

Paid, overdue, and refunded state from Recurly lands on the order or account in Channelengine, so the store and support see what has actually been collected.

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.

What you can sync between Channelengine and Recurly

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.

Channelengine objects Recurly objects How this pairing syncs
Order documents Invoices and other order documents; retrieved as a paginated, filterable list via GET /v2/orders/documents for finance and archiving systems. Read-only. Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Order documents is specific to Channelengine and Plans to Recurly — each maps to any object or custom field on the other side.
Orders Marketplace and merchant-fulfilled orders; read via GET /v2/orders and GET /v2/orders/new (status NEW), then acknowledged with POST /v2/orders/acknowledge so later shipment, return, and cancellation calls can reference them. Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Orders is specific to Channelengine and Invoices to Recurly — each maps to any object or custom field on the other side.
Products (product content) Catalog records created and updated via POST /v2/products and deactivated via DELETE; use a parent/child variant model where the parent is a non-purchasable blueprint. Written into ChannelEngine from a PIM, ERP, or database. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Products (product content) is specific to Channelengine and Transactions to Recurly — each maps to any object or custom field on the other side.
Offers (price and stock) Price and stock updates via PUT /v2/offer/stock and the offers endpoints; separate from product content so fast-changing stock can be pushed often, and supports bulk updates across stock locations. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Offers (price and stock) is specific to Channelengine and Line Items to Recurly — each maps to any object or custom field on the other side.
Shipments Fulfillment records; write with POST /v2/shipments to mark an order shipped with tracking, read with GET /v2/shipments. Pushed back from a warehouse or ERP so marketplaces update the buyer. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Shipments is specific to Channelengine and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.
Returns Marketplace- and merchant-initiated returns; read via GET /v2/returns and created with POST /v2/returns. Synced two-way so customer-service and finance systems reconcile with the ERP. 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). Returns is specific to Channelengine and Billing Info to Recurly — each maps to any object or custom field on the other side.

How changes propagate between Channelengine and Recurly

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.

Channelengine Recurly Sub-second propagation

DetectionChannelengine notifies Stacksync of record changes through webhook events. Webhooks fire on order creation and on return and shipment/cancellation changes.

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

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

Rate-limit considerations

  • Channelengine: Rate limits are per endpoint and returned in headers: x-rate-limit-limit (interval length in minutes), x-rate-limit-remaining, and retry-after (seconds to wait); e.g. POST /v2/supportorder allows 3 calls per minute.
  • 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.
What ships with Channelengine ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Channelengine and Recurly connectors work

Channelengine

Integration surface
REST API (Merchant API v2); per-tenant base URL https://{tenant}.channelengine.net/api
Authentication
API key passed as the 'apikey' parameter; ChannelEngine recommends sending it in a request header rather than the URL because some webservers log full URLs
Change detection
Webhooks fire on order creation and on return and shipment/cancellation changes; product content and offers use change-tracking endpoints (GET /v2/products/data and /v2/products/offers) with an acknowledge pattern that returns only changed records, plus polling GET /v2/orders/new
Capabilities
read · write · webhooks
Rate limits
Rate limits are per endpoint and returned in headers: x-rate-limit-limit (interval length in minutes), x-rate-limit-remaining, and retry-after (seconds to wait); e.g. POST /v2/supportorder allows 3 calls per minute.

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.
How it works

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

    Choose tables

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

Channelengine and Recurly 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 364 integrations available for Channelengine and Recurly.

Popular · 8 of 364
All Channelengine integrations All Recurly 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