Skip to content
Marketing ⇄ ERP

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

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

Feed the real customer, order, and revenue records from SAP S/4HANA into Iterable so campaigns run on who actually bought what, and let contact and consent changes flow back in real time.

Marketing runs on lists of people, but the list rarely knows which of those people are paying customers, what they ordered, or what they are worth. SAP S/4HANA holds exactly that: Sales Orders, Purchase Orders, Products / Materials, Billing Documents (Invoices) that record who the customer is, what they bought, and what they owe. When the two are joined only by a periodic export, campaigns go out against stale audiences, existing customers get prospecting emails, high-value accounts look the same as cold leads, and a canceled order still counts toward a segment.

Stacksync syncs Sales Orders, Purchase Orders, Products / Materials, Billing Documents (Invoices) in SAP S/4HANA with Catalogs, Commerce / Purchases, Export data, Users in Iterable in real time, and where both sides accept writes, in both directions. Customer, order, and invoice data maps field by field onto the contacts, audiences, or accounts Iterable works with, so segmentation and personalization run on current purchase history instead of a month-old snapshot. Contact details and consent changes that originate in Iterable flow back onto the record in SAP S/4HANA.

The strongest bridge between the two is identity and purchase history, who the customer is and what they have bought, so that is where most of the value sits. Because the sync is field-level, each system keeps the attributes the other has no use for; only the shared records are held in agreement.

Common use cases

  • 01 Keep supplier records aligned between S/4HANA procurement and third-party spend platforms.
  • 02 Push closed-won CRM opportunities into S/4HANA as sales orders without manual re-keying.
  • 03 Track product and revenue Events (custom events, trackPurchase, updateCart) into Iterable from an app or database so journeys trigger on live behavior.
  • 04 Export Iterable engagement data (emailSend, emailOpen, emailClick, emailBounce, purchase) into a warehouse for deliverability and campaign reporting.

Common sync patterns

Purchase history drives segmentation

Orders, invoices, and revenue totals from SAP S/4HANA land on the matching contact or account in Iterable, so audiences are built from what customers actually bought and spent rather than from guesses.

Suppress or target existing customers

Because SAP S/4HANA knows who is already a paying customer, Iterable can exclude them from acquisition campaigns or single them out for renewal and cross-sell.

One customer identity across both systems

A person or company's contact details corrected in either system update the other, so marketing and the back office stop maintaining separate versions of the same record.

What you can sync between Iterable 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.

Iterable objects SAP S/4HANA objects How this pairing syncs
Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. Billing Documents (Invoices) Invoice data pushed to CRMs and payment or collections tools for finance visibility. Templates is specific to Iterable and Billing Documents (Invoices) to SAP S/4HANA — each maps to any object or custom field on the other side.
Lists Static subscriber lists; read via GET /api/lists and /api/lists/getUsers, with users added or removed via /api/lists/subscribe and /api/lists/unsubscribe to control who receives a send. Deliveries Outbound delivery status synced to customer-facing systems for order tracking. Lists is specific to Iterable and Deliveries to SAP S/4HANA — each maps to any object or custom field on the other side.
Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. Journal Entries Financial postings read into warehouses and consolidation tools for reporting. Catalogs is specific to Iterable and Journal Entries to SAP S/4HANA — each maps to any object or custom field on the other side.
Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. Commerce / Purchases is specific to Iterable and Customer / Supplier Roles to SAP S/4HANA — each maps to any object or custom field on the other side.
Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. Production Orders Manufacturing order status surfaced in planning and operations tools. Export data is specific to Iterable and Production Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. Business Partners Unified customer and supplier master records, the anchor entity for CRM-to-ERP account syncs. Users is specific to Iterable and Business Partners to SAP S/4HANA — each maps to any object or custom field on the other side.

How changes propagate between Iterable 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.

Iterable SAP S/4HANA Sub-second propagation

DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.

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

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

Rate-limit considerations

  • Iterable: Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
What ships with Iterable ⇄ SAP S/4HANA

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

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

Real-time

Two-way sync

Changes in Iterable 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 Iterable 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 Iterable or SAP S/4HANA record.

Observability

Monitoring

Track your Iterable ⇄ 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 Iterable and SAP S/4HANA.

How the Iterable and SAP S/4HANA connectors work

Iterable

Integration surface
Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data
Authentication
API key sent in the Api-Key HTTP header (also accepted as Api_Key; the name is case-insensitive). Keys are scoped by type - Server-side, JavaScript (Web SDK), or Mobile - with optional JWT-enabled keys. US projects use api.iterable.com; EU projects use api.eu.iterable.com.
Change detection
System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range.
Capabilities
read · write · webhooks
Rate limits
Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.

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 Iterable 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 Iterable 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
    Iterable connected
    SAP S/4HANA connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Iterable 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 469 integrations available for Iterable and SAP S/4HANA.

Popular · 7 of 469
All Iterable 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