Real-time
Two-way sync
Changes in Recurly or Shipwire instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ E-commerce
Recurly to Shipwire integration — real-time, two-way sync
Keep Recurly and Shipwire 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 Shipwire
Turn every Shipwire order into clean revenue: Recurly and Shipwire keep customers, orders, and payment status aligned in real time, in both directions.
Shipwire 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, Products, Stock, Receivings in Shipwire field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Shipwire, 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 Push Products, kits, and their dimensions and pricing from a PIM or ERP into the Shipwire catalog and keep SKUs aligned.
- 04 Read Stock levels per warehouse into an operational database or storefront so availability and backorder state reflect real inventory.
Common sync patterns
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.
Where Shipwire originates orders: sales flow into the books
A new or updated order in Shipwire creates or updates the matching invoice or revenue record in Recurly, so billing and reporting start without re-entry.
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 Shipwire, so the store and support see what has actually been collected.
What you can sync between Recurly and Shipwire
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 | Shipwire objects | How this pairing syncs | |
|---|---|---|---|
| Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | Stock Real-time per-warehouse inventory levels; read-only, pulled into a database or storefront so availability reflects on-hand and backordered quantities. | Measured Units and Usage is specific to Recurly and Stock to Shipwire — 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. | Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. | Accounts is specific to Recurly and Receivings to Shipwire — 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. | Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. | Subscriptions is specific to Recurly and Returns to Shipwire — each maps to any object or custom field on the other side. | |
| Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. | Plans is specific to Recurly and Purchase Orders to Shipwire — each maps to any object or custom field on the other side. | |
| Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. | Invoices is specific to Recurly and Trackings to Shipwire — 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. | Rates Shipping cost quotes for a cart or order; read-only, called at checkout time to estimate carrier costs rather than synced as stored records. | Transactions is specific to Recurly and Rates to Shipwire — each maps to any object or custom field on the other side. |
How changes propagate between Recurly and Shipwire
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 Shipwire 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 Shipwire through its API, with automatic retries and rate-limit backoff.
Shipwire Recurly Sub-second propagation
DetectionShipwire notifies Stacksync of record changes through webhook events. Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics.
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.
- Shipwire: No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
What ships with Recurly ⇄ Shipwire
Connect Recurly and Shipwire for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Recurly–Shipwire connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Recurly or Shipwire 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 Shipwire record.
Observability
Monitoring
Track your Recurly ⇄ Shipwire 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 Shipwire.
How the Recurly and Shipwire 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.
Shipwire
- Integration surface
- REST API (v3)
- Authentication
- Bearer token sent as `Authorization: ShipwireKey <token>`; up to two keys are generated per account on the Users and Roles page, refreshable/expirable, over HTTPS only (separate sandbox at api.beta.shipwire.com)
- Change detection
- Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics; polling the list endpoints as a fallback (no CDC/log stream)
- Capabilities
- read · write · webhooks
- Rate limits
- No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
How it works
How to connect Recurly to Shipwire — 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 Recurly and Shipwire with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Recurly
connected
Shipwire
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Recurly and Shipwire 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 · Recurly ⇄ ShipwireCustomers 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.
Recurly ShipwireCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Recurly and Shipwire integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Recurly and Shipwire: authenticate both systems, choose the objects to sync (such as Recurly's Measured Units and Usage and Accounts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Recurly: List endpoints support incremental pulls via sort=updated_at (or created_at) with begin_time/end_time filters, so polling fetches only records changed since the last run. Shipwire: List endpoints and webhook payloads return at most 20 sub-items per resource by default (recommended page max ~200), so orders or receivings with many line items must be traversed via next links. Stacksync's field mapping accounts for these differences between Recurly and Shipwire 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 Recurly and Shipwire records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Recurly and Shipwire connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Recurly–Shipwire integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Recurly and Shipwire. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection 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. On Shipwire: Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics; polling the list endpoints as a fallback (no CDC/log stream). 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
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 459 integrations available for Recurly and Shipwire.
Popular · 8 of 459
-
Recurly ⇄ Bigcommerce -
Recurly ⇄ Channelengine -
Recurly ⇄ Easypost -
Recurly ⇄ Magento -
Shipwire ⇄ Rillet -
Shipwire ⇄ Workday -
Shipwire ⇄ Anaplan -
Shipwire ⇄ Chargebee
No integrations match .
