Real-time
Two-way sync
Changes in Akeneo or Recurly instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ Accounting and finance
Akeneo to Recurly integration — real-time, two-way sync
Keep Akeneo 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 Akeneo and Recurly
Turn every Akeneo order into clean revenue: Recurly and Akeneo keep customers, orders, and payment status aligned in real time, in both directions.
Akeneo 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 Measured Units and Usage, Accounts, Subscriptions, Plans in Recurly with Families and family variants, Reference entities and records, Assets, Channels and locales in Akeneo field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Akeneo, 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 Write Categories, Families, and Attributes from an ERP or supplier feed into Akeneo to build and maintain catalog structure.
- 04 Read Reference entities records such as brands and manufacturers into a data warehouse for cross-catalog reporting.
Common sync patterns
Where Akeneo originates orders: sales flow into the books
A new or updated order in Akeneo 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 Akeneo, 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.
What you can sync between Akeneo 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.
| Akeneo objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Attributes Attribute definitions plus attribute options and groups; describe the shape of product data, usually mastered in Akeneo and read downstream. | 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. | Attributes is specific to Akeneo and Subscriptions to Recurly — each maps to any object or custom field on the other side. | |
| Families and family variants Templates defining which attributes a product carries and how variants axis out; synced to keep catalog structure consistent across systems. | Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Families and family variants is specific to Akeneo and Plans to Recurly — each maps to any object or custom field on the other side. | |
| Reference entities and records Structured lookups like brands, manufacturers, or ingredients with their own records (Enterprise Edition); synced two-way or read into a warehouse for reporting. | Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Reference entities and records is specific to Akeneo and Invoices to Recurly — each maps to any object or custom field on the other side. | |
| Assets Asset-family media (images, documents) managed in Akeneo's DAM; linked to products and synced to storefronts and commerce systems. | Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Assets is specific to Akeneo and Transactions to Recurly — each maps to any object or custom field on the other side. | |
| Channels and locales Target-market settings that scope attribute values; read to resolve which localized or channel-specific value to map on each side of a sync. | Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Channels and locales is specific to Akeneo and Line Items to Recurly — each maps to any object or custom field on the other side. | |
| Media files Product images and files uploaded via the media endpoint; referenced by products and pushed to downstream commerce and content systems. | Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Media files is specific to Akeneo and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Akeneo 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.
Akeneo Recurly Sub-second propagation
DetectionAkeneo notifies Stacksync of record changes through webhook events. Events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Akeneo 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 Akeneo through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Akeneo: REST protection triggers above roughly 100 requests/second per PIM instance (HTTP 429 with Retry-After); the Events API caps at 4000 requests/hour with a 500ms webhook ack timeout.
- 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 Akeneo ⇄ Recurly
Connect Akeneo and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Akeneo–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Akeneo 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 Akeneo or Recurly record.
Observability
Monitoring
Track your Akeneo ⇄ Recurly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Akeneo and Recurly.
How the Akeneo and Recurly connectors work
Akeneo
- Integration surface
- REST API (plus a GraphQL API) and an Events API for webhooks
- Authentication
- OAuth2 password grant: client_id/secret plus an API user's username/password exchanged at /api/oauth/v1/token for a bearer access_token and refresh_token; Apps use the OAuth2 authorization-code flow
- Change detection
- Events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents; product.updated.delta carries old and new values); falls back to polling the 'updated' datetime search filter where the Events API is unavailable
- Capabilities
- read · write · webhooks
- Rate limits
- REST protection triggers above roughly 100 requests/second per PIM instance (HTTP 429 with Retry-After); the Events API caps at 4000 requests/hour with a 500ms webhook ack timeout.
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 Akeneo 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 Akeneo 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.
Akeneo
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Akeneo 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 · Akeneo ⇄ 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.
Akeneo RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Akeneo and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Akeneo and Recurly: authenticate both systems, choose the objects to sync (such as Akeneo's Attributes and Families and family variants), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Akeneo and Recurly records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Akeneo and Recurly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Akeneo–Recurly integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Akeneo and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Akeneo: Events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents; product.updated.delta carries old and new values); falls back to polling the 'updated' datetime search filter where the Events API is unavailable. 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: Measured Units and Usage, Accounts, Subscriptions, Plans, plus custom fields where Recurly exposes them. On the Akeneo side: Families and family variants, Reference entities and records, Assets, Channels and locales. Stacksync auto-detects both schemas and converts types between the two systems.
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 Akeneo and Recurly.
Popular · 8 of 459
-
Akeneo ⇄ Logisense -
Akeneo ⇄ Bill -
Akeneo ⇄ Braintree -
Akeneo ⇄ Navan -
Recurly ⇄ Magento -
Recurly ⇄ Nuorder -
Recurly ⇄ Shipwire -
Recurly ⇄ Shopware
No integrations match .
