Real-time
Two-way sync
Changes in Cin7 or Shopware instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ E-commerce
Cin7 to Shopware integration — real-time, two-way sync
Keep Cin7 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.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
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
Why teams connect Cin7 and Shopware
Keep the storefront in step with the back office: Shopware and Cin7 share products, inventory, and orders in real time, in both directions.
Shopware runs the storefront and takes the orders; Cin7 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 Sales Channels, Media, Products, Categories in Shopware with Inventory levels, Sales orders, Purchase orders, Contacts in Cin7 field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Cin7, order and customer detail from Shopware — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Two-way sync of the `product` catalog — titles, nested price arrays, and stock — between Shopware and an ERP or PIM so pricing and inventory stay aligned.
- 02 Stream new `order` records with their `order_line_item`, `order_delivery`, and `order_transaction` rows into a warehouse or accounting system for revenue and fulfillment reporting.
- 03 Publish Cin7 inventory levels to storefronts, marketplaces, and a CRM so every channel quotes real availability.
- 04 Sync sales orders from Cin7 into an accounting platform or warehouse for revenue and margin reporting.
Common sync patterns
Fulfillment and shipment status close the loop
As orders are picked, shipped, or invoiced in Cin7, tracking and status flow back to Shopware so buyers see accurate updates.
One customer master
Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.
Where Cin7 is the inventory system of record: stock stays accurate
Available quantities from Cin7 publish to Shopware, so the store shows what can actually ship and stops overselling.
What you can sync between Cin7 and Shopware
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.
| Cin7 objects | Shopware objects | How this pairing syncs | |
|---|---|---|---|
| Products SKU records with options and pricing, synced with storefront and marketplace catalogs. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. | Sales orders is specific to Cin7 and Media to Shopware — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders synced with procurement and accounting workflows. | Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. | Purchase orders is specific to Cin7 and Categories to Shopware — each maps to any object or custom field on the other side. | |
| Contacts Customers and suppliers, matched to CRM records to keep account data consistent. | Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. | Contacts is specific to Cin7 and Customers to Shopware — each maps to any object or custom field on the other side. | |
| Branches / locations Warehouse entities that scope every stock movement and order allocation. | Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. | Branches / locations is specific to Cin7 and Orders to Shopware — each maps to any object or custom field on the other side. | |
| Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. | Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. | Stock adjustments and transfers is specific to Cin7 and Order Line Items to Shopware — each maps to any object or custom field on the other side. |
How changes propagate between Cin7 and Shopware
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.
Cin7 Shopware Sub-second propagation
DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.
DeliveryEach detected change is written to Shopware through its API, with automatic retries and rate-limit backoff.
Shopware Cin7 Sub-second propagation
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 Cin7 through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
- Shopware: No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores.
What ships with Cin7 ⇄ Shopware
Connect Cin7 and Shopware for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Shopware connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Cin7 or Shopware data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Cin7 or Shopware record.
Observability
Monitoring
Track your Cin7 ⇄ Shopware sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Cin7 and Shopware.
How the Cin7 and Shopware connectors work
Cin7
- Integration surface
- REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
- Authentication
- API key credentials (paired with a username or account ID, depending on the product)
- Change detection
- Polling on modified-date filters; webhook support exists on some editions for order and stock events
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core
Shopware
- Integration surface
- 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
- Change detection
- App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field names; otherwise poll on the updatedAt / createdAt fields
- Capabilities
- read · write · webhooks
- Rate limits
- No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores
How it works
How to connect Cin7 to Shopware — three steps, no code
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.
- 01
Connect your apps
Authenticate Cin7 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.
Cin7
connected
Shopware
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Cin7 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.
objects · Cin7 ⇄ ShopwareCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Cin7 ShopwareCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Cin7 and Shopware integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Cin7 and Shopware: authenticate both systems, choose the objects to sync (such as Cin7's Products and Sales orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Shopware side: Sales Channels, Media, Products, Categories, plus custom fields where Shopware exposes them. On the Cin7 side: Inventory levels, Sales orders, Purchase orders, Contacts. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Cin7 and Shopware: Fulfillment and shipment status close the loop; One customer master; Where Cin7 is the inventory system of record: stock stays accurate. As orders are picked, shipped, or invoiced in Cin7, tracking and status flow back to Shopware so buyers see accurate updates.
-
Cin7: REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs. Authentication: API key credentials (paired with a username or account ID, depending on the product). 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. Cin7: Inventory is modeled per branch/location, so availability syncs choose between per-location and aggregated quantities. Stacksync's field mapping accounts for these differences between Cin7 and Shopware without custom code.
SECURITY
Security teams trust Stacksync
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
→ SECURITY WITH BENEFITS
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 458 integrations available for Cin7 and Shopware.
Popular · 7 of 458
-
Cin7 ⇄ Channelengine -
Cin7 ⇄ Easypost -
Cin7 ⇄ Magento -
Cin7 ⇄ Nuorder -
Shopware ⇄ Infor CloudSuite - Shopware ⇄ Infor LN
- Shopware ⇄ Infor M3
No integrations match .
