Skip to content
E-commerce ⇄ ERP

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

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

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

Akeneo 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 Assets, Channels and locales, Media files, Products in Akeneo with Production Orders, Business Partners, Sales Orders, Purchase Orders 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 Akeneo — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Push enriched Products and their Assets into an ecommerce storefront or commerce database when product.created and product.updated webhooks fire.
  • 02 Write Categories, Families, and Attributes from an ERP or supplier feed into Akeneo to build and maintain catalog structure.
  • 03 Feed S/4HANA financial and logistics documents into a data warehouse for reporting without custom ABAP extracts.
  • 04 Keep supplier records aligned between S/4HANA procurement and third-party spend platforms.

Common sync patterns

Fulfillment and shipment status close the loop

As orders are picked, shipped, or invoiced in SAP S/4HANA, tracking and status flow back to Akeneo 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 SAP S/4HANA is the inventory system of record: stock stays accurate

Available quantities from SAP S/4HANA publish to Akeneo, so the store shows what can actually ship and stops overselling.

What you can sync between Akeneo and SAP S/4HANA

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.

Akeneo objects SAP S/4HANA objects How this pairing syncs
Assets Asset-family media (images, documents) managed in Akeneo's DAM; linked to products and synced to storefronts and commerce systems. Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. Assets is specific to Akeneo and Customer / Supplier Roles to SAP S/4HANA — each maps to any object or custom field on the other side.
Channels and locales Target-market settings that scope attribute values; read to resolve which localized or channel-specific value to map on each side of a sync. Production Orders Manufacturing order status surfaced in planning and operations tools. Channels and locales is specific to Akeneo and Production Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Media files Product images and files uploaded via the media endpoint; referenced by products and pushed to downstream commerce and content systems. Business Partners Unified customer and supplier master records, the anchor entity for CRM-to-ERP account syncs. Media files is specific to Akeneo and Business Partners to SAP S/4HANA — each maps to any object or custom field on the other side.
Products Core catalog records addressed by UUID (recommended) or identifier/SKU; synced two-way with databases, ERPs, and storefronts. Values are scoped per channel and locale. Sales Orders Order headers and line items synced to CRMs and fulfillment systems as they are created or amended. Products is specific to Akeneo and Sales Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Product models Parent records for configurable products; hold shared attribute values that cascade to their variant products, synced alongside Products. Purchase Orders Procurement documents shared with supplier portals and spend-management tools. Product models is specific to Akeneo and Purchase Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Categories The category tree used to classify products; read out for storefront navigation or written in from an ERP to seed catalog structure. Products / Materials Material master data distributed to e-commerce, PIM, and CRM catalogs. Categories is specific to Akeneo and Products / Materials to SAP S/4HANA — each maps to any object or custom field on the other side.

How changes propagate between Akeneo and SAP S/4HANA

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.

Akeneo SAP S/4HANA Sub-second propagation

DetectionAkeneo notifies Stacksync of record changes through webhook events. Events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents.

DeliveryEach detected change is written to SAP S/4HANA through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • Akeneo: REST protection triggers above roughly 100 requests/second per PIM instance (HTTP 429 with Retry-After); the Events API caps at 4000 requests/hour with a 500ms webhook ack timeout.
  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
What ships with Akeneo ⇄ SAP S/4HANA

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Akeneo and SAP S/4HANA connectors work

Akeneo

Integration surface
REST API (plus a GraphQL API) and an Events API for webhooks
Authentication
OAuth2 password grant: client_id/secret plus an API user's username/password exchanged at /api/oauth/v1/token for a bearer access_token and refresh_token; Apps use the OAuth2 authorization-code flow
Change detection
Events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents; product.updated.delta carries old and new values); falls back to polling the 'updated' datetime search filter where the Events API is unavailable
Capabilities
read · write · webhooks
Rate limits
REST protection triggers above roughly 100 requests/second per PIM instance (HTTP 429 with Retry-After); the Events API caps at 4000 requests/hour with a 500ms webhook ack timeout.

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
How it works

How to connect Akeneo to SAP S/4HANA — 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 Akeneo and SAP S/4HANA 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
    Akeneo connected
    SAP S/4HANA connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Akeneo and SAP S/4HANA 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 · Akeneo ⇄ SAP S/4HANA
    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
    Akeneo SAP S/4HANA
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

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

Popular · 8 of 467
All Akeneo integrations All SAP S/4HANA 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