Azure SQL Database
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. |
Database / E-commerce · Two-way sync platform
Azure SQL Database and Shipwire integration
Plan how Azure SQL Database 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 reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving the proposed sales order table in Azure SQL Database or Shipwire Orders needs a defined result in the other system.
Start with the proposed sales order table in Azure SQL Database 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 multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
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
| Azure SQL Database record | Shipwire record | Record matching | Field ownership |
|---|---|---|---|
| Proposed sales order tableProposed table; choose its name and schema.Reporting dataset | 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. |
| Proposed product or catalog item tableProposed table; choose its name and schema.Reporting dataset | 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. |
| Proposed inventory or stock position tableProposed table; choose its name and schema.Reporting dataset | StockProposed record; confirm Stacksync object support. | Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient. | Choose the stock authority and distinguish available, reserved, and physical quantities. |
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 | Azure SQL Database | Shipwire |
|---|---|---|
| Integration interface | SQL wire protocol (TDS), the same protocol as SQL Server; T-SQL over standard drivers | REST API (v3) |
| Authentication | Confirm the credentials, API plan, and permissions required for Azure SQL Database. | 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
Azure SQL Database
- Integration interface
- SQL wire protocol (TDS), the same protocol as SQL Server; T-SQL over standard drivers
- Authentication
- Confirm the credentials, API plan, and permissions required for Azure SQL Database.
- 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 Azure SQL Database account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Azure SQL Database, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Azure SQL Database 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 Azure SQL Database 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.
Azure SQL Database setup checklist
- Identify the Azure SQL Database account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Azure SQL Database, 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 Azure SQL Database 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
Reporting dataset
Proposed sales order table in Azure SQL Database (choose its name) / Orders
Plan a sales order dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Azure SQL Database
- Your database schema
- Shipwire
- 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.
Reporting dataset
Proposed product or catalog item table in Azure SQL Database (choose its name) / Products
Plan a product or catalog item dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Azure SQL Database
- Your database schema
- 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.
Reporting dataset
Proposed inventory or stock position table in Azure SQL Database (choose its name) / Stock
Plan a inventory or stock position dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Azure SQL Database
- Your database schema
- Shipwire
- Object support to establish
- Record identity
- Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient.
- Field ownership
- Choose the stock authority and distinguish available, reserved, and physical quantities.
Fields to include
- Product reference
- Location reference
- Quantity type
- Quantity
- As-of time
- Record dependencies
- Resolve product, unit, warehouse/location, and lot/serial references.
- Validation
- Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
- Recovery
- Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
Reporting dataset
Proposed purchase order table in Azure SQL Database (choose its name) / Purchase Orders
Plan a purchase order dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Azure SQL Database
- Your database schema
- 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 Proposed sales order table in Azure SQL Database (choose its name) / 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: Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. 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 Azure SQL Database 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 Proposed sales order table in Azure SQL Database (choose its name) / Orders, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when Azure SQL Database and Shipwire need a transformation, approval, or action outside a direct record sync.
- 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.
File or scheduled snapshot
- Best fit
- Consider for a one-time Azure SQL Database / 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 reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed sales order table in Azure SQL Database (choose its name) or Orders record needs a defined result in the other system.
- Start with Azure SQL Database Proposed sales order table in Azure SQL Database (choose its name) 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 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.
Product or catalog item reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed product or catalog item table in Azure SQL Database (choose its name) or Products record needs a defined result in the other system.
- Start with Azure SQL Database Proposed product or catalog item table in Azure SQL Database (choose its name) 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.
Inventory or stock position reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed inventory or stock position table in Azure SQL Database (choose its name) or Stock record needs a defined result in the other system.
- Start with Azure SQL Database Proposed inventory or stock position table in Azure SQL Database (choose its name) and Shipwire Stock. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve product, unit, warehouse/location, and lot/serial 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 the same SKU in two locations, a reservation, and an older snapshot arriving late.
If it fails: Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
Coordinate Shipwire commerce data with Azure SQL Database
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A catalog, order, or fulfillment change in Shipwire matters to a selected destination dataset.
- Choose the commerce entity from Orders or Products; separate products, variants, orders, and fulfillments.
- Preserve order and line references through the Azure SQL Database process. Define many-to-one or one-to-many relationships explicitly.
- Assign separate ownership for commercial approval, inventory, and fulfillment, including partial cancellations or returns.
Expected result: A split fulfillment and repeated request preserve line quantities without duplicate orders or shipments.
If it fails: Look up existing downstream records before retrying creation; reconcile current order and fulfillment states.
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.
Proposed sales order table in Azure SQL Database (choose its name) / 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.
Proposed product or catalog item table in Azure SQL Database (choose its name) / 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.
Proposed inventory or stock position table in Azure SQL Database (choose its name) / Stock
Test case
Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
Expected result
The expected inventory or stock position relationship is preserved with no duplicate action or unintended write.
Proposed purchase order table in Azure SQL Database (choose its name) / 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 Azure SQL Database Proposed sales order table in Azure SQL Database (choose its name) 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 Azure SQL Database Proposed product or catalog item table in Azure SQL Database (choose its name) 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 inventory or stock position change
Investigate
Inspect Azure SQL Database Proposed inventory or stock position table in Azure SQL Database (choose its name) and Shipwire Stock, their IDs, and the destination error.
Next action
Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
A record type or update is unavailable
Investigate
Check the Azure SQL Database 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 Azure SQL Database 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.
Azure SQL Database 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 Azure SQL Database 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 Azure SQL Database.
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
Azure SQL Database and Shipwire integration FAQ
-
Explore a Azure SQL Database and Shipwire integration with a Stacksync engineer. Stacksync support for Azure SQL Database and Shipwire 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 Azure SQL Database account, edition, environment, and business objects the integration must access. Identify the Shipwire 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 Proposed sales order table in Azure SQL Database (choose its name) in Azure SQL Database and Orders in Shipwire. 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 Proposed sales order table in Azure SQL Database (choose its name) / 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 401 integrations listed for Azure SQL Database and Shipwire.
Popular · 7 of 401
-
Azure SQL Database and Shopware -
Azure SQL Database and Akeneo -
Azure SQL Database and BigCommerce -
Shipwire and TimescaleDB -
Shipwire and VoltDB -
Shipwire and YugabyteDB -
Shipwire and Amazon DynamoDB
No integrations match .
Next step
Plan your integration with an engineer
Walk through your Azure SQL Database and Shipwire records, field mappings, and requirements with an integration engineer.
