Shopware integration.

Assign product content, variants, prices, customer identity, stock, and order state to explicit owners. A catalog update and a fulfillment command need different permissions and acceptance tests. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Write-back support is not established for this connection. Review the Shopware records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

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.

Resolve person or company type, legal entity, business role, and any billing account before transactions.

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact. A multi-line purchase retains the correct variant and customer references, while repeated delivery leaves one intended order and fulfillment state.

Estimate the number of Customers, Products and Orders records, the history to load, ongoing changes, and required environments. Include API access, the integration service, destination storage or processing, and the work to maintain mappings and recover from errors. Review current provider pricing against that workload, including any account or API upgrades.