Skip to content
ERP ⇄ E-commerce

Dynamics 365 F&O to Shopware integration — real-time, two-way sync

Keep Dynamics 365 F&O and Shopware 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 Dynamics 365 F&O and Shopware

Keep the storefront in step with the back office: Shopware and Dynamics 365 F&O share products, inventory, and orders in real time, in both directions.

Shopware 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 Media, Products, Categories, Customers in Shopware with Vendors, Released Products, Sales Orders, Purchase Orders 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 Shopware — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync `customer` records two-way with a CRM so support and marketing see order history while reps write updates back onto the account.
  • 02 Write tracking numbers and delivery state onto `order_delivery` from a 3PL or WMS so storefront order status reflects fulfillment.
  • 03 Sync customers, vendors, and released products into an operational database that internal apps read instead of calling OData directly.
  • 04 Push sales orders from e-commerce into F&O and sync fulfillment and invoice status back to the storefront.

Common sync patterns

One customer master

Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.

Where Dynamics 365 F&O is the inventory system of record: stock stays accurate

Available quantities from Dynamics 365 F&O publish to Shopware, so the store shows what can actually ship and stops overselling.

New orders reach the back office

An order captured in Shopware creates the matching record in Dynamics 365 F&O with customer, line items, and totals, so fulfillment and invoicing start without re-entry.

What you can sync between Dynamics 365 F&O and Shopware

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.

Dynamics 365 F&O objects Shopware objects How this pairing syncs
Customers Customer master records; kept aligned with CRM accounts in two-way syncs. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Sales Orders Order transactions; written in from storefronts or CRM and tracked through fulfillment. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Sales Orders is specific to Dynamics 365 F&O and Order Transactions to Shopware — each maps to any object or custom field on the other side.
Purchase Orders Procurement transactions; extracted for spend and supply chain reporting. Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Purchase Orders is specific to Dynamics 365 F&O and Sales Channels to Shopware — each maps to any object or custom field on the other side.
Customer Invoices AR billing documents; status synced back to CRM and customer success tools. Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. Customer Invoices is specific to Dynamics 365 F&O and Media to Shopware — each maps to any object or custom field on the other side.
Vendor Invoices AP documents; synced with invoice automation systems. Products The product catalog (`product`), including parent/child variants, per-currency nested price arrays, and stock; synced two-way with ERP, PIM, or a database. Vendor Invoices is specific to Dynamics 365 F&O and Products to Shopware — each maps to any object or custom field on the other side.
General Journal Entries GL postings; read-only extracts for consolidated finance reporting. Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. General Journal Entries is specific to Dynamics 365 F&O and Categories to Shopware — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 F&O and Shopware

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.

Dynamics 365 F&O Shopware Sub-second propagation

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 Shopware through its API, with automatic retries and rate-limit backoff.

Shopware Dynamics 365 F&O Sub-second propagation

DetectionShopware notifies Stacksync of record changes through webhook events. App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field.

DeliveryEach detected change is written to Dynamics 365 F&O through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Dynamics 365 F&O: OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
  • Shopware: No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores.
What ships with Dynamics 365 F&O ⇄ Shopware

Connect Dynamics 365 F&O and Shopware for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 F&O–Shopware connection.

Real-time

Two-way sync

Changes in Dynamics 365 F&O or Shopware instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamics 365 F&O or Shopware 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 Dynamics 365 F&O or Shopware record.

Observability

Monitoring

Track your Dynamics 365 F&O ⇄ Shopware sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dynamics 365 F&O and Shopware.

How the Dynamics 365 F&O and Shopware connectors work

Dynamics 365 F&O

Integration surface
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")
Change detection
Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable
Capabilities
read · write · CDC · webhooks
Rate limits
OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
Dynamics 365 F&O setup guide

Shopware

Integration surface
Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint
Authentication
OAuth 2.0 — client-credentials grant using an Integration's Access Key ID + Secret Access Key, or resource-owner password grant for a user; access tokens expire after 10 minutes
Change detection
App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field names; otherwise poll on the updatedAt / createdAt fields
Capabilities
read · write · webhooks
Rate limits
No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores
How it works

How to connect Dynamics 365 F&O to Shopware — 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.

  1. 01

    Connect your apps

    Authenticate Dynamics 365 F&O and Shopware with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Dynamics 365 F&O connected
    Shopware connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dynamics 365 F&O and Shopware 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Dynamics 365 F&O ⇄ Shopware
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Dynamics 365 F&O Shopware
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Dynamics 365 F&O and Shopware integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 372 integrations available for Dynamics 365 F&O and Shopware.

Popular · 6 of 372
All Dynamics 365 F&O integrations All Shopware integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own