IFS Cloud and Mailchimp integration

What moves between them

Customer records and sales orders flow from IFS Cloud into Mailchimp. IFS Cloud customers are synced as Mailchimp e-commerce customers. IFS Cloud sales orders and order lines are synced as Mailchimp e-commerce orders with financial status (pending, paid) and line-item totals. Sync runs on a polling schedule tied to your business calendar (weekly, daily, or after high-volume periods). The flow is primarily IFS Cloud into Mailchimp; Mailchimp email engagement and unsubscribe data can flow back into IFS Cloud as contact notes or flags if needed, but the core motion is outbound from the ERP to the marketing platform.

How ml-connector handles it

ml-connector stores both the IFS Cloud OAuth client credentials and the Mailchimp API key encrypted. It polls IFS Cloud on your schedule using OData $filter on the created/modified timestamp fields to capture new and changed customers and sales orders. For each customer, it reads the full record, captures the ETag response header, and sends it as the If-Match header on any subsequent update to satisfy IFS Cloud's optimistic concurrency requirement. Customer records are then uperted into Mailchimp as e-commerce customers, and sales orders are created as e-commerce orders with line-item detail and financial_status set to pending or paid depending on the IFS Cloud order state. ml-connector respects IFS Cloud's 1000-request-per-minute rate limit and result set size constraints, breaking large queries into batches and backing off on 429 responses. Every sync record, mapping decision, and API call is logged to the audit trail and can be replayed if a downstream update fails.

A real-world example

A mid-sized manufacturing and distribution company runs IFS Cloud for procurement, supply chain, and order-to-cash. They use Mailchimp for product marketing campaigns and quarterly newsletters to their customer base. Before the integration, the marketing team manually exported customer lists from IFS Cloud to a spreadsheet monthly, uploaded them to Mailchimp, and launched campaigns with outdated customer data missing recent orders. With IFS Cloud and Mailchimp connected, each new customer or significant order in IFS Cloud flows automatically into Mailchimp audiences within hours. Marketing campaigns now target the right customers with current order context, and the manual export-import cycle is eliminated.

What you can do

• •Sync IFS Cloud customers into Mailchimp as e-commerce customers so your email lists reflect your current customer base.
• •Sync IFS Cloud sales orders and line items into Mailchimp e-commerce orders with financial status and order totals.
• •Poll IFS Cloud on your schedule with timestamp filters to capture new and changed customer and order records.
• •Enforce OData ETag concurrency controls and handle IFS Cloud's 1000-request-per-minute rate limit with backoff and retry.
• •Track every customer and order sync in a full audit trail and replay any record if a downstream update fails.

Questions

Which direction does data move between IFS Cloud and Mailchimp?

The primary flow is IFS Cloud into Mailchimp. Customers and sales orders are synced from IFS Cloud into Mailchimp as e-commerce customers and orders so your marketing campaigns have current customer and order data. Mailchimp email engagement events and unsubscribe activity can optionally flow back into IFS Cloud as contact notes, but the core motion is outbound from the ERP.

How does ml-connector handle IFS Cloud's OData ETag requirement and rate limits?

ml-connector reads each customer or order record, captures the ETag response header, and includes it as the If-Match header on any subsequent update, satisfying IFS Cloud's optimistic concurrency requirement. For rate limits, ml-connector respects IFS Cloud's 1000-request-per-minute cap, breaks large result sets into batches under 5000 elements, and backs off exponentially on HTTP 429 responses.

Does ml-connector need to configure IFS Cloud Event Actions or webhooks?

No. IFS Cloud Event Actions require manual per-tenant configuration in the IFS admin UI and are not self-registerable via API. ml-connector uses a pull-based polling approach instead, filtering on created and modified timestamps to capture new and changed records on a schedule you control.