Microsoft Dynamics NAV
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
Microsoft Dynamics NAV and Shipwire integration
Plan how Microsoft Dynamics NAV and Shipwire 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
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 Microsoft Dynamics NAV Sales Orders & Invoices or Shipwire Orders needs a defined result in the other system.
Start with Microsoft Dynamics NAV Sales Orders & Invoices and Shipwire 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
| Microsoft Dynamics NAV record | Shipwire record | Record matching | Field ownership |
|---|---|---|---|
| Sales Orders & 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. |
| ItemsProposed record; confirm Stacksync object support.Record matching | ProductsProposed record; confirm Stacksync object support. | Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. | Assign ownership for catalog content, price, and stock separately. |
| Purchase OrdersProposed record; confirm Stacksync object support.Record matching | Purchase OrdersProposed record; confirm Stacksync object support. | Retain purchase-order and line IDs together with the supplier and legal-entity context. | Keep procurement approval separate from receipt and payment states. |
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.
Shipwire
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 | Microsoft Dynamics NAV | Shipwire |
|---|---|---|
| Integration interface | SOAP and OData web services published from NAV pages and codeunits; direct SQL Server access on-premises | REST API (v3) |
| Authentication | Confirm the credentials, API plan, and permissions required for Microsoft Dynamics NAV. | Confirm the credentials, API plan, and permissions required for Shipwire. |
| 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
Microsoft Dynamics NAV
- Integration interface
- SOAP and OData web services published from NAV pages and codeunits; direct SQL Server access on-premises
- Authentication
- Confirm the credentials, API plan, and permissions required for Microsoft Dynamics NAV.
- 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 Microsoft Dynamics NAV account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Microsoft Dynamics NAV, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Microsoft Dynamics NAV and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Shipwire
- Integration interface
- REST API (v3)
- Authentication
- Confirm the credentials, API plan, and permissions required for Shipwire.
- 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 Shipwire account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Shipwire, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Shipwire and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Prepare Microsoft Dynamics NAV and Shipwire 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.
Microsoft Dynamics NAV setup checklist
- Identify the Microsoft Dynamics NAV account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Microsoft Dynamics NAV, including read/write support, authentication, and initial-load limits.
Shipwire setup checklist
- Identify the Shipwire account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Shipwire, 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 Microsoft Dynamics NAV and Shipwire 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 Orders & Invoices / Orders
Order-to-invoice handoff: Shipwire Orders provides context for Microsoft Dynamics NAV Sales Orders & Invoices. These are related records, not equivalent entities.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Microsoft Dynamics NAV
- Object support to establish
- Shipwire
- 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
Items / Products
Compare whether Microsoft Dynamics NAV Items and Shipwire 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.
- Microsoft Dynamics NAV
- Object support to establish
- Shipwire
- 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.
Record matching
Purchase Orders / Purchase Orders
Compare whether Microsoft Dynamics NAV Purchase Orders and Shipwire Purchase Orders describe the same purchase order in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Microsoft Dynamics NAV
- Object support to establish
- Shipwire
- Object support to establish
- Record identity
- Retain purchase-order and line IDs together with the supplier and legal-entity context.
- Field ownership
- Keep procurement approval separate from receipt and payment states.
Fields to include
- Source purchase-order ID
- Supplier reference
- Line references
- Quantity
- Approval status
- Record dependencies
- Resolve supplier, product, business unit, and delivery-location references before lines.
- Validation
- Test a partially received purchase order and an amendment after approval.
- Recovery
- Reconcile receipts already recorded before resubmitting an amended order.
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Sales Orders & 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 Microsoft Dynamics NAV and Shipwire 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 Orders & Invoices / Orders, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider explicit orchestration for the Sales Orders & 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 Microsoft Dynamics NAV / Shipwire 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 Orders & Invoices or Orders record needs a defined result in the other system.
- Start with Microsoft Dynamics NAV Sales Orders & Invoices and Shipwire 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.
Product or catalog item sync test
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Items or Products record needs a defined result in the other system.
- Start with Microsoft Dynamics NAV Items and Shipwire Products. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve units, variants, categories, and applicable price lists before order lines.
- 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 two variants of one product, a changed SKU, and a price that applies to only one market or currency.
If it fails: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Purchase 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 Purchase Orders or Purchase Orders record needs a defined result in the other system.
- Start with Microsoft Dynamics NAV Purchase Orders and Shipwire Purchase Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve supplier, product, business unit, and delivery-location references before lines.
- 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 received purchase order and an amendment after approval.
If it fails: Reconcile receipts already recorded before resubmitting an amended order.
Reconcile Microsoft Dynamics NAV business records with Shipwire
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A finance-owned record in Microsoft Dynamics NAV needs operational visibility through Orders or Products.
- Select Customers or Vendors with the correct legal entity, period, and currency.
- Define a reporting relationship in Shipwire; 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 Orders & 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.
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.
Purchase Orders / Purchase Orders
Test case
Test a partially received purchase order and an amendment after approval.
Expected result
The expected purchase order 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 Microsoft Dynamics NAV Sales Orders & Invoices and Shipwire 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 product or catalog item change
Investigate
Inspect Microsoft Dynamics NAV Items and Shipwire Products, their IDs, and the destination error.
Next action
Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Rejected or repeated purchase order change
Investigate
Inspect Microsoft Dynamics NAV Purchase Orders and Shipwire Purchase Orders, their IDs, and the destination error.
Next action
Reconcile receipts already recorded before resubmitting an amended order.
A record type or update is unavailable
Investigate
Check the Microsoft Dynamics NAV and Shipwire 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 Microsoft Dynamics NAV and Shipwire
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Microsoft Dynamics NAV Shipwire 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 Shipwire.
Shipwire Microsoft Dynamics NAV 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 Microsoft Dynamics NAV.
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
Microsoft Dynamics NAV and Shipwire integration FAQ
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 462 integrations listed for Microsoft Dynamics NAV and Shipwire.
Next step
Plan your integration with an engineer
Walk through your Microsoft Dynamics NAV and Shipwire records, field mappings, and requirements with an integration engineer.
