Real-time
Two-way sync
Changes in Blue Yonder WMS or Recurly instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Accounting and finance
Blue Yonder WMS to Recurly integration — real-time, two-way sync
Keep Blue Yonder WMS 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 Blue Yonder WMS and Recurly
Keep Recurly and Blue Yonder WMS 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 Plans, Invoices, Transactions, Line Items in Recurly with Items / SKUs, Inventory balances, Inbound shipments (ASNs), Purchase orders in Blue Yonder WMS 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 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
- 02 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
- 03 Mirror WMS inventory balances into a warehouse or ERP so planning and finance see the same on-hand numbers.
- 04 Keep the item master aligned between the ERP and the WMS so new SKUs are receivable on day one.
Common sync patterns
Subsidiary to headquarters
Where Recurly serves a business unit and Blue Yonder WMS is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
Where Recurly handles billing: invoices land in Blue Yonder WMS
Invoices and payment activity from the billing side post through to the enterprise system automatically.
Migration without a hard cutover
When one system is replacing the other, run both in parallel with records matching until the switch is complete.
What you can sync between Blue Yonder WMS 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.
| Blue Yonder WMS objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Items / SKUs Product master records that must match the ERP item master for warehouse operations to reconcile. | 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. | Items / SKUs is specific to Blue Yonder WMS and Accounts to Recurly — each maps to any object or custom field on the other side. | |
| Inventory balances On-hand quantities by location and lot, synced outward for availability and planning. | 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. | Inventory balances is specific to Blue Yonder WMS and Subscriptions to Recurly — each maps to any object or custom field on the other side. | |
| Inbound shipments (ASNs) Advance ship notices created from purchase orders to drive receiving. | Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Inbound shipments (ASNs) is specific to Blue Yonder WMS and Plans to Recurly — each maps to any object or custom field on the other side. | |
| Purchase orders Expected receipts pushed from the ERP so the warehouse can plan inbound work. | Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Purchase orders is specific to Blue Yonder WMS and Invoices to Recurly — each maps to any object or custom field on the other side. | |
| Outbound orders Pick, pack, and ship instructions created from sales orders in the ERP or OMS. | Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Outbound orders is specific to Blue Yonder WMS and Transactions to Recurly — each maps to any object or custom field on the other side. | |
| Shipments and shipment confirmations Completed outbound events synced back to update order status and trigger invoicing. | Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Shipments and shipment confirmations is specific to Blue Yonder WMS and Line Items to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Blue Yonder WMS 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.
Blue Yonder WMS Recurly Interval-based propagation
DetectionStacksync polls Blue Yonder WMS for changes on an incremental schedule, reading only records changed since the previous pass. Polling and scheduled extracts.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Blue Yonder WMS 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 Blue Yonder WMS through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Blue Yonder WMS: Subject to the platform's API rate limits, which vary by contract and hosting model.
- 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 Blue Yonder WMS ⇄ Recurly
Connect Blue Yonder WMS and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Blue Yonder WMS–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Blue Yonder WMS 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 Blue Yonder WMS or Recurly record.
Observability
Monitoring
Track your Blue Yonder WMS ⇄ Recurly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Blue Yonder WMS and Recurly.
How the Blue Yonder WMS and Recurly connectors work
Blue Yonder WMS
- Integration surface
- REST APIs on Blue Yonder's cloud platform (formerly branded Luminate); long-standing WMS deployments also expose MOCA-based integration interfaces
- Authentication
- Token-based authentication; specifics vary by deployment and platform edition
- Change detection
- Polling and scheduled extracts; event-style feeds depend on the deployment
- Capabilities
- read · write
- Rate limits
- Subject to the platform's API rate limits, which vary by contract and hosting model
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 Blue Yonder WMS 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 Blue Yonder WMS 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.
Blue Yonder WMS
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Blue Yonder WMS 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 · Blue Yonder WMS ⇄ 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.
Blue Yonder WMS RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Blue Yonder WMS and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Blue Yonder WMS and Recurly: authenticate both systems, choose the objects to sync (such as Blue Yonder WMS's Items / SKUs and Inventory balances), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Blue Yonder WMS and Recurly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Blue Yonder WMS–Recurly integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Blue Yonder WMS and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Blue Yonder WMS: Polling and scheduled extracts; event-style feeds depend on the deployment. 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.
-
On the Recurly side: Plans, Invoices, Transactions, Line Items, plus custom fields where Recurly exposes them. On the Blue Yonder WMS side: Items / SKUs, Inventory balances, Inbound shipments (ASNs), Purchase orders. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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 396 integrations available for Blue Yonder WMS and Recurly.
Popular · 4 of 396
-
Blue Yonder WMS ⇄ Anaplan -
Recurly ⇄ Epicor ERP -
Recurly ⇄ Extensiv (3PL Central) -
Recurly ⇄ Fishbowl Manufacturing
No integrations match .
