Skip to content
ERP ⇄ E-commerce

SAP S/4HANA to Shopware integration — real-time, two-way sync

Keep SAP S/4HANA 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 SAP S/4HANA and Shopware

Keep the storefront in step with the back office: Shopware and SAP S/4HANA share products, inventory, and orders in real time, in both directions.

Shopware runs the storefront and takes the orders; SAP S/4HANA 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 Orders, Order Line Items, Order Deliveries, Order Transactions in Shopware with Business Partners, Sales Orders, Purchase Orders, Products / Materials in SAP S/4HANA field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from SAP S/4HANA, order and customer detail from Shopware — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Write tracking numbers and delivery state onto `order_delivery` from a 3PL or WMS so storefront order status reflects fulfillment.
  • 02 Consolidate orders and customers from multiple `sales_channel` storefronts into one Postgres database for cross-channel analysis.
  • 03 Surface invoice and payment status from S/4HANA inside the CRM so account teams see open balances.
  • 04 Replicate material master and pricing data to e-commerce and quoting tools.

Common sync patterns

New orders reach the back office

An order captured in Shopware creates the matching record in SAP S/4HANA 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 SAP S/4HANA, tracking and status flow back to Shopware so buyers see accurate updates.

What you can sync between SAP S/4HANA 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.

SAP S/4HANA objects Shopware objects How this pairing syncs
Purchase Orders Procurement documents shared with supplier portals and spend-management tools. Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. Purchase Orders is specific to SAP S/4HANA and Categories to Shopware — each maps to any object or custom field on the other side.
Products / Materials Material master data distributed to e-commerce, PIM, and CRM catalogs. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Products / Materials is specific to SAP S/4HANA and Customers to Shopware — each maps to any object or custom field on the other side.
Billing Documents (Invoices) Invoice data pushed to CRMs and payment or collections tools for finance visibility. Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. Billing Documents (Invoices) is specific to SAP S/4HANA and Orders to Shopware — each maps to any object or custom field on the other side.
Deliveries Outbound delivery status synced to customer-facing systems for order tracking. Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. Deliveries is specific to SAP S/4HANA and Order Line Items to Shopware — each maps to any object or custom field on the other side.
Journal Entries Financial postings read into warehouses and consolidation tools for reporting. Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. Journal Entries is specific to SAP S/4HANA and Order Deliveries to Shopware — each maps to any object or custom field on the other side.
Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Customer / Supplier Roles is specific to SAP S/4HANA and Order Transactions to Shopware — each maps to any object or custom field on the other side.

How changes propagate between SAP S/4HANA 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.

SAP S/4HANA Shopware Interval-based propagation

DetectionStacksync polls SAP S/4HANA for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change timestamps exposed by the OData services.

DeliveryEach detected change is written to Shopware through its API, with automatic retries and rate-limit backoff.

Shopware SAP S/4HANA 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 SAP S/4HANA through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
  • 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 SAP S/4HANA ⇄ Shopware

Connect SAP S/4HANA and Shopware for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every SAP S/4HANA–Shopware connection.

Real-time

Two-way sync

Changes in SAP S/4HANA or Shopware instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever SAP S/4HANA 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 SAP S/4HANA or Shopware record.

Observability

Monitoring

Track your SAP S/4HANA ⇄ Shopware sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between SAP S/4HANA and Shopware.

How the SAP S/4HANA and Shopware connectors work

SAP S/4HANA

Integration surface
OData REST APIs (v2/v4), with SOAP, BAPI/RFC, and IDoc interfaces on on-premise editions
Authentication
OAuth 2.0 with communication arrangements on cloud editions; basic auth or certificate-based on-premise
Change detection
Polling on change timestamps exposed by the OData services; business events can be emitted through SAP's event infrastructure on cloud editions
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits, which vary by edition and communication arrangement

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 SAP S/4HANA 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.

  1. 01

    Connect your apps

    Authenticate SAP S/4HANA 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    SAP S/4HANA connected
    Shopware connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the SAP S/4HANA 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · SAP S/4HANA ⇄ Shopware
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    SAP S/4HANA Shopware
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

SAP S/4HANA and Shopware integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 467 integrations available for SAP S/4HANA and Shopware.

Popular · 8 of 467
All SAP S/4HANA integrations All Shopware integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own