Connecting an e-commerce platform to D365 F&O: integration options

To connect an e-commerce platform to Dynamics 365 Finance & Operations, you usually combine several integration patterns documented by Microsoft: OData on data entities for real-time single-record exchanges (create an order, read a status), asynchronous data APIs (DMF package, recurring integrations) for volumes (catalogue, prices, stock), custom services for logic that matches no entity (computed availability), and business events to push changes to the platform.

You can also rely on a partner connector or middleware or, depending on scope, on Dynamics 365 Commerce, Microsoft's commerce application.

• Web orders to F&O: OData (single synchronous create) or, at high volume, asynchronous batch import.
• Catalogue and prices to the site: export through a data entity, usually scheduled (DMF package API or recurring integration).
• Available stock: Microsoft cites real-time inventory lookup precisely as a custom service use case. See custom service vs OData action.
• Order status, shipment, invoice: business events to Service Bus, Event Grid or Power Automate, or on-demand OData reads.
• Customers: OData or batch import depending on volume.

Microsoft notes that volumes quoted in its scenarios are for choosing a pattern, not system limits.

• Partner connector: quick to set up for a widespread platform; check covered flows, error handling and ability to include your customisations.
• Middleware (iPaaS, Azure Logic Apps…): decouples systems, centralises transformations and monitoring; requires operations.
• Direct development: relevant for simple, stable flows; requires handling retries, idempotency and logging.

In every case, the quality of the data entities F&O exposes drives the quality of the integration.

• Making single OData calls to sync the whole catalogue: prefer asynchronous APIs.
• Querying F&O on every page view for stock: expensive; plan a cache or a dedicated service.
• Ignoring the API service protection limits (throttling) documented by Microsoft.
• Not planning retries: a lost web order is a lost customer.
• Letting each flow handle its own errors with no common monitoring.

Orders, stock, prices: each flow relies on data entities, services or business events on the F&O side. Skalp AI does not connect the platform: you plug in your interfaces; Skalp can generate the D365 F&O side (data entities, classes, parameters). See ERP e-commerce integration and D365 F&O API interfaces, the bigger picture in building X++ without a consultant in 2026, and the Basic, Pro and Max plans (1 credit, ≈ €400 on Basic, €200 on Pro, consumed only when the code is generated).

See also: EDI DESADV in D365 F&O and AI ticket creation in D365 F&O.

• Microsoft Learn, "Integration between finance and operations apps and third-party services", updated 9 Mar 2026, accessed 18 Oct 2026.
• Microsoft Learn, "Open Data Protocol (OData)", updated 14 Jan 2026, accessed 18 Oct 2026.
• Microsoft Learn, "Business events overview", updated 15 Jan 2026, accessed 18 Oct 2026.