SAP S/4HANA and Mailchimp integration

What moves between them

Email subscribers and contacts flow from Mailchimp into SAP S/4HANA as new business partners and customers. E-commerce orders from Mailchimp are mapped to SAP customer records and inbound order documents. Contact profile changes and list events update the matching SAP business partner records. Unsubscribe events can flag inactive customers in SAP. The flow is primarily Mailchimp to SAP, since SAP is read-only for GL accounts and cost centers. Updates run on a schedule tied to your email campaign and order-processing cadence.

How ml-connector handles it

ml-connector extracts the data center prefix from the Mailchimp API key and routes all calls to the correct regional endpoint. It polls Mailchimp for list subscriber changes and e-commerce order events since the last run, then maps each email address to an existing SAP business partner or creates a new one using the Mailchimp contact name and email. E-commerce orders are matched to SAP customers by email and inserted as order headers with line items, or appended to existing orders. SAP side uses OAuth 2.0 Client Credentials to request a bearer token from the tenant-specific endpoint, validates the token lifespan, and refreshes it before expiry to prevent timeouts. Mailchimp webhooks are optional: if enabled, ml-connector can accept real-time subscribe and order events instead of polling alone. Because Mailchimp webhooks have no signature verification, all data updates are logged in the audit trail and can be replayed if needed.

A real-world example

A mid-sized e-commerce retailer runs SAP S/4HANA for order-to-cash and accounting, and uses Mailchimp for email marketing and customer engagement across a subscriber base of 50,000 contacts. Without the integration, the marketing team manages customer lists offline and the sales team manually enters new orders from Mailchimp into SAP, leading to duplicate business partners and missing order records. With SAP S/4HANA and Mailchimp connected, each new subscriber is automatically added to SAP as a business partner, e-commerce orders flow directly into SAP order entry, and unsubscribe events mark the customer as inactive in SAP. The sales team can now query SAP for all subscriber-driven orders and the finance team has a complete order-to-cash record without re-keying.

What you can do

• •Sync Mailchimp email subscribers into SAP S/4HANA as new business partner and customer records, eliminating manual list uploads.
• •Map e-commerce orders from Mailchimp to SAP customers and insert them as order documents with line items and totals.
• •Keep customer contact records aligned between Mailchimp and SAP when emails change or profiles are updated.
• •Handle OAuth 2.0 authentication for both systems, manage token expiry, and route Mailchimp calls to the correct regional API endpoint.
• •Track every subscriber and order sync in a full audit trail so changes can be reviewed, queried, and replayed if needed.

Questions

Which direction does data move between SAP S/4HANA and Mailchimp?

The primary flow is from Mailchimp into SAP S/4HANA. Email subscribers become business partners, e-commerce orders are inserted as customer orders, and contact profile changes update the SAP records. SAP data does not flow back to Mailchimp, since SAP GL accounts and cost centers are read-only and Mailchimp has no invoice or purchase order support.

How does ml-connector handle Mailchimp API key routing to the correct data center?

Mailchimp API keys include a data center prefix (such as us6 or us19) as the final segment after the last hyphen. ml-connector extracts that prefix from the key and routes all calls to the corresponding regional endpoint, so no manual configuration of the data center URL is needed.

Can ml-connector use Mailchimp webhooks instead of polling for subscriber and order changes?

Yes. If Mailchimp webhooks are enabled on your account, ml-connector can accept real-time subscribe, unsubscribe, and e-commerce order events instead of polling on a schedule. Webhook events are also logged in the audit trail for full traceability.