Skip to content
ERP ⇄ E-commerce

Dynamics 365 Business Central to Shopware integration — real-time, two-way sync

Keep Dynamics 365 Business Central 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 Business Central and Shopware

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

Shopware runs the storefront and takes the orders; Dynamics 365 Business Central 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 Order Deliveries, Order Transactions, Sales Channels, Media in Shopware with Items, Sales Orders, Sales Invoices, Purchase Orders in Dynamics 365 Business Central field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Dynamics 365 Business Central, order and customer detail from Shopware — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Write tracking numbers and delivery state onto `order_delivery` from a 3PL or WMS so storefront order status reflects fulfillment.
  • 02 Consolidate orders and customers from multiple `sales_channel` storefronts into one Postgres database for cross-channel analysis.
  • 03 Create sales orders in Business Central automatically from e-commerce or CRM order records, and sync fulfillment status back.
  • 04 Mirror items and inventory levels into external channels so stock data stays current outside the ERP.

Common sync patterns

New orders reach the back office

An order captured in Shopware creates the matching record in Dynamics 365 Business Central 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 Dynamics 365 Business Central, tracking and status flow back to Shopware so buyers see accurate updates.

What you can sync between Dynamics 365 Business Central 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 Business Central objects Shopware objects How this pairing syncs
Customers Core master data synced with CRMs so sales and finance share one customer list. 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.
General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. General Ledger Entries is specific to Dynamics 365 Business Central and Media to Shopware — each maps to any object or custom field on the other side.
Journals Staging records for financial postings created by integrations before posting. 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. Journals is specific to Dynamics 365 Business Central and Products to Shopware — each maps to any object or custom field on the other side.
Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. Dimensions is specific to Dynamics 365 Business Central and Categories to Shopware — each maps to any object or custom field on the other side.
Payments Customer and vendor payment records reconciled against invoices. Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. Payments is specific to Dynamics 365 Business Central and Orders to Shopware — each maps to any object or custom field on the other side.
Vendors Supplier master data synced with procurement and AP automation tools. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Vendors is specific to Dynamics 365 Business Central and Order Line Items to Shopware — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 Business Central 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 Business Central Shopware Sub-second propagation

DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.

DeliveryEach detected change is written to Shopware through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • 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 Business Central ⇄ Shopware

Connect Dynamics 365 Business Central and Shopware for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Dynamics 365 Business Central 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 Business Central 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 Business Central or Shopware record.

Observability

Monitoring

Track your Dynamics 365 Business Central ⇄ 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 Business Central and Shopware.

How the Dynamics 365 Business Central and Shopware connectors work

Dynamics 365 Business Central

Integration surface
REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
Capabilities
read · write · webhooks

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 Business Central 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 Business Central 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 Business Central connected
    Shopware connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dynamics 365 Business Central 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 Business Central ⇄ 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 Business Central Shopware
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Dynamics 365 Business Central 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.

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:

Coworkers laughing in front of a laptop in a casual office setting

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