Real-time
Two-way sync
Changes in Akeneo or Linnworks instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ ERP
Akeneo to Linnworks integration — real-time, two-way sync
Keep Akeneo and Linnworks 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 Linnworks
Keep the storefront in step with the back office: Akeneo and Linnworks share products, inventory, and orders in real time, in both directions.
Akeneo runs the storefront and takes the orders; Linnworks owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.
Stacksync syncs Media files, Products, Product models, Categories in Akeneo with Stock Levels, Locations, Purchase Orders, Suppliers in Linnworks field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Linnworks, order and customer detail from Akeneo — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Mirror Products and completeness data into a warehouse to track enrichment progress by channel and locale without manual CSV exports.
- 02 Two-way sync Products and product models with an operational Postgres database or ERP so SKUs, prices, and localized descriptions stay aligned across systems.
- 03 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels
- 04 Sync product and listing data with a PIM so channel listings stay aligned with the catalog
Common sync patterns
New orders reach the back office
An order captured in Akeneo creates the matching record in Linnworks with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
One product catalog
Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
Fulfillment and shipment status close the loop
As orders are picked, shipped, or invoiced in Linnworks, tracking and status flow back to Akeneo so buyers see accurate updates.
What you can sync between Akeneo and Linnworks
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 | Linnworks objects | How this pairing syncs | |
|---|---|---|---|
| Product models Parent records for configurable products; hold shared attribute values that cascade to their variant products, synced alongside Products. | Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Product models is specific to Akeneo and Processed Orders to Linnworks — each maps to any object or custom field on the other side. | |
| Categories The category tree used to classify products; read out for storefront navigation or written in from an ERP to seed catalog structure. | Stock Items SKU records keep product data aligned with ERPs and PIMs. | Categories is specific to Akeneo and Stock Items to Linnworks — each maps to any object or custom field on the other side. | |
| Attributes Attribute definitions plus attribute options and groups; describe the shape of product data, usually mastered in Akeneo and read downstream. | Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Attributes is specific to Akeneo and Stock Levels to Linnworks — 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. | Locations Warehouse and fulfillment location records scope stock data during mapping. | Families and family variants is specific to Akeneo and Locations to Linnworks — 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. | Purchase Orders Replenishment POs sync with suppliers and accounting systems. | Reference entities and records is specific to Akeneo and Purchase Orders to Linnworks — 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. | Suppliers Vendor records keep procurement data consistent across tools. | Assets is specific to Akeneo and Suppliers to Linnworks — each maps to any object or custom field on the other side. |
How changes propagate between Akeneo and Linnworks
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 Linnworks 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 Linnworks through its API, with automatic retries and rate-limit backoff.
Linnworks Akeneo 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 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.
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Akeneo ⇄ Linnworks
Connect Akeneo and Linnworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Akeneo–Linnworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Akeneo or Linnworks 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 Linnworks record.
Observability
Monitoring
Track your Akeneo ⇄ Linnworks 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 Linnworks.
How the Akeneo and Linnworks 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.
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
How it works
How to connect Akeneo to Linnworks — 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 Linnworks 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
Linnworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Akeneo and Linnworks 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 ⇄ LinnworksCustomers 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 LinnworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Akeneo and Linnworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Akeneo and Linnworks: authenticate both systems, choose the objects to sync (such as Akeneo's Product models and Categories), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Akeneo and Linnworks. 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 Linnworks: Polling on order and stock endpoints. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Akeneo side: Media files, Products, Product models, Categories, plus custom fields where Akeneo exposes them. On the Linnworks side: Stock Levels, Locations, Purchase Orders, Suppliers. 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.
-
Common patterns for Akeneo and Linnworks: New orders reach the back office; One product catalog; Fulfillment and shipment status close the loop. An order captured in Akeneo creates the matching record in Linnworks with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
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 462 integrations available for Akeneo and Linnworks.
Popular · 8 of 462
-
Akeneo ⇄ SAP Business ByDesign -
Akeneo ⇄ SAP Business One -
Akeneo ⇄ Oracle Fusion ERP -
Akeneo ⇄ Acumatica -
Linnworks ⇄ Nuorder -
Linnworks ⇄ Shipwire -
Linnworks ⇄ Shopware -
Linnworks ⇄ Bigcommerce
No integrations match .
