Real-time
Two-way sync
Changes in Linnworks or Recurly instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Accounting and finance
Linnworks to Recurly integration — real-time, two-way sync
Keep Linnworks 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 Linnworks and Recurly
Keep Recurly and Linnworks agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.
A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.
Stacksync syncs Billing Info, Measured Units and Usage, Accounts, Subscriptions in Recurly with Shipping Services, Open Orders, Processed Orders, Stock Items in Linnworks in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.
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 Push customer and order data to a CRM or marketing platform for post-purchase campaigns
- 04 Sync orders from Linnworks into an ERP or accounting system as they are processed, without CSV exports
Common sync patterns
One customer and vendor master
Where both systems keep records of the same organizations, corrections made in either propagate to the other.
Subsidiary to headquarters
Where Recurly serves a business unit and Linnworks is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
Where Recurly handles billing: invoices land in Linnworks
Invoices and payment activity from the billing side post through to the enterprise system automatically.
What you can sync between Linnworks 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.
| Linnworks objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Shipping Services Carrier and service definitions support label and tracking data in order syncs. | 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). | Shipping Services is specific to Linnworks and Billing Info to Recurly — each maps to any object or custom field on the other side. | |
| Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | Open Orders is specific to Linnworks and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side. | |
| Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | 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. | Processed Orders is specific to Linnworks and Accounts to Recurly — each maps to any object or custom field on the other side. | |
| Stock Items SKU records keep product data aligned with ERPs and PIMs. | 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. | Stock Items is specific to Linnworks and Subscriptions to Recurly — each maps to any object or custom field on the other side. | |
| Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Stock Levels is specific to Linnworks and Plans to Recurly — each maps to any object or custom field on the other side. | |
| Locations Warehouse and fulfillment location records scope stock data during mapping. | Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Locations is specific to Linnworks and Invoices to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Linnworks 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.
Linnworks Recurly Interval-based propagation
DetectionStacksync polls Linnworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling on order and stock endpoints.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Linnworks 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 Linnworks through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
- 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 Linnworks ⇄ Recurly
Connect Linnworks and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Linnworks–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Linnworks 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 Linnworks or Recurly record.
Observability
Monitoring
Track your Linnworks ⇄ Recurly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Linnworks and Recurly.
How the Linnworks and Recurly connectors work
Linnworks
- Integration surface
- REST API
- Authentication
- Application credentials and an install token exchanged for a session token
- Change detection
- Polling on order and stock endpoints
- Capabilities
- read · write
- Rate limits
- Per-endpoint rate limits apply on the Linnworks API
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 Linnworks 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.
- 01
Connect your apps
Authenticate Linnworks 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.
Linnworks
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Linnworks 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.
objects · Linnworks ⇄ RecurlyCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Linnworks RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Linnworks and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Linnworks and Recurly: authenticate both systems, choose the objects to sync (such as Linnworks's Shipping Services and Open Orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Recurly: Records carry both opaque IDs and human-readable codes (account_code, plan_code); lookups can use either, which helps map to external keys. Linnworks: The Linnworks API uses a token-exchange model: application credentials plus a per-account install token are exchanged for a session token that authorizes subsequent calls. Stacksync's field mapping accounts for these differences between Linnworks and Recurly without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Linnworks and Recurly records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Linnworks and Recurly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Linnworks–Recurly integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Linnworks and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Linnworks: Polling on order and stock endpoints. On Recurly: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 499 integrations available for Linnworks and Recurly.
Popular · 8 of 499
-
Linnworks ⇄ Ramp -
Linnworks ⇄ Rillet -
Linnworks ⇄ Workday -
Linnworks ⇄ Anaplan -
Recurly ⇄ Acumatica -
Recurly ⇄ SAP S/4HANA -
Recurly ⇄ Odoo -
Recurly ⇄ Blue Yonder WMS
No integrations match .
