Two-way sync
Changes in Akeneo or Dynamics 365 F&O instantly reflect in both systems. No stale data, no manual imports.
Keep Akeneo and Dynamics 365 F&O in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Akeneo runs the storefront and takes the orders; Dynamics 365 F&O 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 Products, Product models, Categories, Attributes in Akeneo with Released Products, Sales Orders, Purchase Orders, Customer Invoices in Dynamics 365 F&O field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Dynamics 365 F&O, order and customer detail from Akeneo — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
An order captured in Akeneo creates the matching record in Dynamics 365 F&O with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
As orders are picked, shipped, or invoiced in Dynamics 365 F&O, tracking and status flow back to Akeneo so buyers see accurate updates.
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 | Dynamics 365 F&O objects | How this pairing syncs | |
|---|---|---|---|
| Categories The category tree used to classify products; read out for storefront navigation or written in from an ERP to seed catalog structure. | Vendors Supplier master records; synced with procurement and AP tools. | Categories is specific to Akeneo and Vendors to Dynamics 365 F&O — 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. | Released Products Sellable product master; read out to commerce channels and CRM catalogs. | Attributes is specific to Akeneo and Released Products to Dynamics 365 F&O — 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. | Sales Orders Order transactions; written in from storefronts or CRM and tracked through fulfillment. | Families and family variants is specific to Akeneo and Sales Orders to Dynamics 365 F&O — 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 Procurement transactions; extracted for spend and supply chain reporting. | Reference entities and records is specific to Akeneo and Purchase Orders to Dynamics 365 F&O — 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. | Customer Invoices AR billing documents; status synced back to CRM and customer success tools. | Assets is specific to Akeneo and Customer Invoices to Dynamics 365 F&O — 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. | Vendor Invoices AP documents; synced with invoice automation systems. | Channels and locales is specific to Akeneo and Vendor Invoices to Dynamics 365 F&O — each maps to any object or custom field on the other side. |
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.
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 Dynamics 365 F&O through its API, with automatic retries and rate-limit backoff.
DetectionDynamics 365 F&O pushes changes as they happen — webhook events backed by change data capture. Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity.
DeliveryEach detected change is written to Akeneo through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Akeneo–Dynamics 365 F&O connection.
Changes in Akeneo or Dynamics 365 F&O instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Akeneo or Dynamics 365 F&O data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Akeneo or Dynamics 365 F&O record.
Track your Akeneo ⇄ Dynamics 365 F&O sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Akeneo and Dynamics 365 F&O.
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.
Authenticate Akeneo and Dynamics 365 F&O with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Akeneo and Dynamics 365 F&O 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Akeneo and Dynamics 365 F&O: authenticate both systems, choose the objects to sync (such as Akeneo's Categories and Attributes), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Dynamics 365 F&O: Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Akeneo side: Products, Product models, Categories, Attributes, plus custom fields where Akeneo exposes them. On the Dynamics 365 F&O side: Released Products, Sales Orders, Purchase Orders, Customer Invoices. 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 Dynamics 365 F&O: 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 Dynamics 365 F&O with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
Akeneo: 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. Dynamics 365 F&O: OData REST endpoint over data entities, plus the Data Management Framework for batch. Authentication: OAuth via Microsoft sign-in: provide the D365 F&O environment URL, sign in with Microsoft credentials, and grant the Stacksync app consent (admin consent may be required — "Need admin approval for this app"). Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 372 integrations available for Akeneo and Dynamics 365 F&O.