Dynamics 365 Business Central
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
ERP / E-commerce · Two-way sync platform
Dynamics 365 Business Central and Shopware integration
Plan how Dynamics 365 Business Central and Shopware should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.
- Scope your workflow with an integration engineer
- Review the systems, records, and updates you need
Integration planning
stacksync.com Built for teams where self-serve, reliability and scale matter
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
Proposed workflow
Sales order process handoff
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving Dynamics 365 Business Central Sales Invoices or Shopware Orders needs a defined result in the other system.
Start with Dynamics 365 Business Central Sales Invoices and Shopware Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Review records and field ownershipProposed record relationships
Records to connect
Use these examples to define record matching and field ownership for your technical review.
Download the mapping worksheetCSV · No email required
| Dynamics 365 Business Central record | Shopware record | Record matching | Field ownership |
|---|---|---|---|
| Sales InvoicesProposed record; confirm Stacksync object support.Business process handoff | OrdersProposed record; confirm Stacksync object support. | Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order. | Finance owns invoice posting; the order system supplies the approved commercial context. |
| CustomersProposed record; confirm Stacksync object support.Record matching | CustomersProposed record; confirm Stacksync object support. | Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. | Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company. |
| Sales OrdersProposed record; confirm Stacksync object support.Record matching | OrdersProposed record; confirm Stacksync object support. | Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. | Decide which system approves the order and which can cancel or amend it after fulfillment begins. |
These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.
Record coverage to review
Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.
Shopware
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
Connection essentials
Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.
View setup requirements and limits| Connection requirement | Dynamics 365 Business Central | Shopware |
|---|---|---|
| Integration interface | REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL | Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint |
| Authentication | Confirm the credentials, API plan, and permissions required for Dynamics 365 Business Central. | Confirm the credentials, API plan, and permissions required for Shopware. |
| Change detection | Confirm how Stacksync detects changes for this connector and the objects you need. | Confirm how Stacksync detects changes for this connector and the objects you need. |
| Read access | Confirm with Stacksync | Confirm with Stacksync |
| Write access | Confirm with Stacksync | Confirm with Stacksync |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance and data transfers
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
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:
Record-level recovery
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
Dynamics 365 Business Central
- Integration interface
- REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
- Authentication
- Confirm the credentials, API plan, and permissions required for Dynamics 365 Business Central.
- Change detection
- Confirm how Stacksync detects changes for this connector and the objects you need.
- Read access
- Confirm with Stacksync
- Write access
- Confirm with Stacksync
Setup requirements
- Identify the Dynamics 365 Business Central account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Dynamics 365 Business Central, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Dynamics 365 Business Central and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Shopware
- Integration interface
- Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint
- Authentication
- Confirm the credentials, API plan, and permissions required for Shopware.
- Change detection
- Confirm how Stacksync detects changes for this connector and the objects you need.
- Read access
- Confirm with Stacksync
- Write access
- Confirm with Stacksync
Setup requirements
- Identify the Shopware account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Shopware, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Shopware and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Prepare Dynamics 365 Business Central and Shopware access
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Dynamics 365 Business Central setup checklist
- Identify the Dynamics 365 Business Central account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Dynamics 365 Business Central, including read/write support, authentication, and initial-load limits.
Shopware setup checklist
- Identify the Shopware account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Shopware, including read/write support, authentication, and initial-load limits.
Prepare to go live
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the Dynamics 365 Business Central and Shopware planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Record identity and field ownership
Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.
Download the mapping worksheet · CSV, no email required
Business process
Sales Invoices / Orders
Order-to-invoice handoff: Shopware Orders provides context for Dynamics 365 Business Central Sales Invoices. These are related records, not equivalent entities.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Dynamics 365 Business Central
- Object support to establish
- Shopware
- Object support to establish
- Record identity
- Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.
- Field ownership
- Finance owns invoice posting; the order system supplies the approved commercial context.
Fields to include
- Source record reference
- Destination record reference
- Approved handoff state
- Duplicate-detection key
- Record dependencies
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Validation
- Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
- Recovery
- Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Record matching
Customers / Customers
Compare whether Dynamics 365 Business Central Customers and Shopware Customers describe the same customer in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Dynamics 365 Business Central
- Object support to establish
- Shopware
- Object support to establish
- Record identity
- Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
- Field ownership
- Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Fields to include
- Source customer ID
- Person/company classification
- Legal entity or business unit
- Destination identity reference
- Record dependencies
- Resolve person or company type, legal entity, business role, and any billing account before transactions.
- Validation
- Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
- Recovery
- Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Record matching
Sales Orders / Orders
Compare whether Dynamics 365 Business Central Sales Orders and Shopware Orders describe the same sales order in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Dynamics 365 Business Central
- Object support to establish
- Shopware
- Object support to establish
- Record identity
- Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
- Field ownership
- Decide which system approves the order and which can cancel or amend it after fulfillment begins.
Fields to include
- Source order ID
- Customer reference
- Line references and quantities
- Order status
- Currency
- Record dependencies
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Validation
- Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
- Recovery
- Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Record matching
Items / Products
Compare whether Dynamics 365 Business Central Items and Shopware Products describe the same product or catalog item in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Dynamics 365 Business Central
- Object support to establish
- Shopware
- Object support to establish
- Record identity
- Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
- Field ownership
- Assign ownership for catalog content, price, and stock separately.
Fields to include
- Source product ID
- SKU or variant reference
- Description
- Unit of measure
- Price-list reference
- Record dependencies
- Resolve units, variants, categories, and applicable price lists before order lines.
- Validation
- Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
- Recovery
- Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Sales Invoices / Orders to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Stacksync managed sync
- Best fit
- Review compatibility with a Stacksync engineer using an example of the records and updates you need.
- Operating responsibility
- Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
- Before you choose
- Check record matching: Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order. Verify field coverage, deletion handling, and how changes are detected.
Native vendor integration
- Best fit
- A vendor-built integration may fit if it supports your Dynamics 365 Business Central and Shopware record types.
- Operating responsibility
- Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
- Before you choose
- First check whether either vendor offers this integration. If available, verify Sales Invoices / Orders, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider explicit orchestration for the Sales Invoices / Orders handoff.
- Operating responsibility
- Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
- Before you choose
- Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.
File or scheduled snapshot
- Best fit
- Consider for a one-time Dynamics 365 Business Central / Shopware migration or a reporting need with an explicit freshness window.
- Operating responsibility
- Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
- Before you choose
- Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow scenarios and expected results
Sales order process handoff
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Sales Invoices or Orders record needs a defined result in the other system.
- Start with Dynamics 365 Business Central Sales Invoices and Shopware Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Customer sync test
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Customers or Customers record needs a defined result in the other system.
- Start with Dynamics 365 Business Central Customers and Shopware Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve person or company type, legal entity, business role, and any billing account before transactions.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Sales order sync test
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Sales Orders or Orders record needs a defined result in the other system.
- Start with Dynamics 365 Business Central Sales Orders and Shopware Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Reconcile Dynamics 365 Business Central business records with Shopware
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A finance-owned record in Dynamics 365 Business Central needs operational visibility through Products or Customers.
- Select Customers or Vendors with the correct legal entity, period, and currency.
- Define a reporting relationship in Shopware; do not equate customer records, ledger accounts, and posted transactions.
- Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Initial load and acceptance testing
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Sales Invoices / Orders
Test case
Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Customers / Customers
Test case
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Expected result
The expected customer relationship is preserved with no duplicate action or unintended write.
Sales Orders / Orders
Test case
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Items / Products
Test case
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
Expected result
The expected product or catalog item relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.
Expected result
Only an approved, supported direction and permitted fields are written.
Freshness and reconciliation
Test case
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failed updates, retries and recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Rejected or repeated sales order change
Investigate
Inspect Dynamics 365 Business Central Sales Invoices and Shopware Orders, their IDs, and the destination error.
Next action
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Rejected or repeated customer change
Investigate
Inspect Dynamics 365 Business Central Customers and Shopware Customers, their IDs, and the destination error.
Next action
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Rejected or repeated sales order change
Investigate
Inspect Dynamics 365 Business Central Sales Orders and Shopware Orders, their IDs, and the destination error.
Next action
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
A record type or update is unavailable
Investigate
Check the Dynamics 365 Business Central and Shopware connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
Change detection and update delivery
How updates move between Dynamics 365 Business Central and Shopware
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Dynamics 365 Business Central Shopware Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in Shopware.
Shopware Dynamics 365 Business Central Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in Dynamics 365 Business Central.
Update timing and record limits
- Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
FAQ
Dynamics 365 Business Central and Shopware integration FAQ
-
Explore a Dynamics 365 Business Central and Shopware integration with a Stacksync engineer. Stacksync support for Dynamics 365 Business Central and Shopware is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.
-
Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Dynamics 365 Business Central account, edition, environment, and business objects the integration must access. Identify the Shopware account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
-
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
-
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
-
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
-
Start by reviewing Sales Invoices in Dynamics 365 Business Central and Orders in Shopware. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
-
Choose a method around one example record and the update your business needs. Use Sales Invoices / Orders to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 467 integrations listed for Dynamics 365 Business Central and Shopware.
Popular · 8 of 467
-
Dynamics 365 Business Central and Akeneo -
Dynamics 365 Business Central and BigCommerce -
Dynamics 365 Business Central and ChannelEngine -
Dynamics 365 Business Central and EasyPost -
Shopware and Microsoft Dynamics NAV -
Shopware and Plex ERP -
Shopware and QAD ERP -
Shopware and Rootstock ERP
No integrations match .
Next step
Plan your integration with an engineer
Walk through your Dynamics 365 Business Central and Shopware records, field mappings, and requirements with an integration engineer.
