Two-way sync
Changes in Dynamics 365 Business Central or Shopware instantly reflect in both systems. No stale data, no manual imports.
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.
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.
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.
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 Business Central, tracking and status flow back to Shopware 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.
| 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. |
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.
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.
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.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Shopware connection.
Changes in Dynamics 365 Business Central or Shopware instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dynamics 365 Business Central or Shopware data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Dynamics 365 Business Central or Shopware record.
Track your Dynamics 365 Business Central ⇄ Shopware sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and Shopware.
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 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.
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.
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 Dynamics 365 Business Central and Shopware: authenticate both systems, choose the objects to sync (such as Dynamics 365 Business Central's Customers and General Ledger Entries), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Dynamics 365 Business Central and Shopware: New orders reach the back office; One product catalog; Fulfillment and shipment status close the loop. 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.
Dynamics 365 Business Central: 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. Shopware: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Shopware: Prices are stored per currency as a nested price array with net and gross values, and products model variants as parent/child rows, so field mappings must handle nested structures. Dynamics 365 Business Central: Posted documents such as posted invoices and GL entries are immutable by design; corrections happen through new postings, which shapes how bi-directional syncs handle financial data. Stacksync's field mapping accounts for these differences between Dynamics 365 Business Central and Shopware without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Dynamics 365 Business Central and Shopware records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dynamics 365 Business Central and Shopware connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dynamics 365 Business Central–Shopware integration in-house.
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 467 integrations available for Dynamics 365 Business Central and Shopware.