Real-time
Two-way sync
Changes in Sage 100 or Shopware instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ E-commerce
Sage 100 to Shopware integration — real-time, two-way sync
Keep Sage 100 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 Sage 100 and Shopware
Keep the storefront in step with the back office: Shopware and Sage 100 share products, inventory, and orders in real time, in both directions.
Shopware runs the storefront and takes the orders; Sage 100 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 Sales Orders, AR Invoices, Purchase Orders, GL Accounts in Sage 100 field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Sage 100, order and customer detail from Shopware — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Sync `customer` records two-way with a CRM so support and marketing see order history while reps write updates back onto the account.
- 02 Write tracking numbers and delivery state onto `order_delivery` from a 3PL or WMS so storefront order status reflects fulfillment.
- 03 Publish item, pricing, and on-hand inventory to online catalogs on a schedule.
- 04 Replicate GL and sales history to a warehouse or Postgres database for reporting off the on-premise system.
Common sync patterns
New orders reach the back office
An order captured in Shopware creates the matching record in Sage 100 with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
One product catalog
Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
Fulfillment and shipment status close the loop
As orders are picked, shipped, or invoiced in Sage 100, tracking and status flow back to Shopware so buyers see accurate updates.
What you can sync between Sage 100 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.
| Sage 100 objects | Shopware objects | How this pairing syncs | |
|---|---|---|---|
| Customers AR customer master records synced to CRMs for account and credit visibility. | Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Purchase Orders Procurement documents read for spend and receiving workflows. | Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. | Purchase Orders is specific to Sage 100 and Orders to Shopware — each maps to any object or custom field on the other side. | |
| GL Accounts Chart of accounts read for mapping transactions in finance integrations. | Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. | GL Accounts is specific to Sage 100 and Order Line Items to Shopware — each maps to any object or custom field on the other side. | |
| Journal Entries Posted GL activity replicated to warehouses for FP&A. | Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. | Journal Entries is specific to Sage 100 and Order Deliveries to Shopware — each maps to any object or custom field on the other side. | |
| Vendors AP vendor master records synced with procurement and payment tools. | Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. | Vendors is specific to Sage 100 and Order Transactions to Shopware — each maps to any object or custom field on the other side. | |
| Inventory Items Item master with pricing and quantities, synced to e-commerce catalogs. | Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. | Inventory Items is specific to Sage 100 and Sales Channels to Shopware — each maps to any object or custom field on the other side. |
How changes propagate between Sage 100 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.
Sage 100 Shopware Interval-based propagation
DetectionStacksync polls Sage 100 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.
DeliveryEach detected change is written to Shopware through its API, with automatic retries and rate-limit backoff.
Shopware Sage 100 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 applied to Sage 100 as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- 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 Sage 100 ⇄ Shopware
Connect Sage 100 and Shopware for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Sage 100–Shopware connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Sage 100 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 Sage 100 or Shopware record.
Observability
Monitoring
Track your Sage 100 ⇄ Shopware sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Sage 100 and Shopware.
How the Sage 100 and Shopware connectors work
Sage 100
- Integration surface
- ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes
- Authentication
- Sage 100 company and user credentials; ODBC DSN credentials for direct reads
- Change detection
- Scheduled polling; no webhooks or change log on the integration surface
- Capabilities
- read · write
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 Sage 100 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 Sage 100 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.
Sage 100
connected
Shopware
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Sage 100 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 · Sage 100 ⇄ 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.
Sage 100 ShopwareCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Sage 100 and Shopware integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Sage 100 and Shopware: authenticate both systems, choose the objects to sync (such as Sage 100's Customers and Purchase Orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Sage 100: Scheduled polling; no webhooks or change log on the integration surface. On Shopware: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Shopware side: Sales Channels, Media, Products, Categories, plus custom fields where Shopware exposes them. On the Sage 100 side: Sales Orders, AR Invoices, Purchase Orders, GL Accounts. 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 Sage 100 and Shopware: New orders reach the back office; One product catalog; Fulfillment and shipment status close the loop. An order captured in Shopware creates the matching record in Sage 100 with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
-
Sage 100: ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes. Authentication: Sage 100 company and user credentials; ODBC DSN credentials for direct reads. 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.
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 465 integrations available for Sage 100 and Shopware.
Popular · 6 of 465
-
Sage 100 ⇄ Shipwire -
Sage 100 ⇄ Akeneo -
Sage 100 ⇄ Bigcommerce -
Sage 100 ⇄ Channelengine -
Shopware ⇄ DEAR Inventory -
Shopware ⇄ Epicor ERP
No integrations match .
