Oracle JD Edwards and Mailchimp integration

What moves between them

Customer and vendor records flow from Oracle JD Edwards into Mailchimp on a polling schedule set by your refresh cadence. The F03012 Customer Master and F0101 Address Book (both customers and vendors) are mapped to Mailchimp List Members and E-commerce Customers respectively. Fields such as company name, email, phone, and billing address are synchronized to match the Mailchimp contact record structure. Mailchimp has no GL or procurement entities, so only customer and contact data are in scope; invoices, purchase orders, and financial transactions remain in Oracle JD Edwards. The sync is unidirectional (Oracle JD Edwards into Mailchimp) because Mailchimp is a marketing platform with no purchase or financial data to return.

How ml-connector handles it

ml-connector manages the Oracle JD Edwards AIS Server session token lifecycle by obtaining a fresh token via the /jderest/v2/tokenrequest endpoint before each polling cycle and re-authenticating if a token expires (HTTP 444 response). It extracts the Mailchimp data center prefix from the API key (the final segment after the last hyphen) and routes all Mailchimp calls to the correct regional endpoint. Since Oracle JD Edwards has no webhooks, ml-connector polls at a configured interval using the UPMJ date filter to retrieve only changed records since the last sync. Customer and vendor names, email addresses, phone numbers, and address fields are mapped to the appropriate Mailchimp List Member and E-commerce Customer fields. Mailchimp API rate limits are respected with exponential backoff, and the full audit trail tracks every record pulled from Oracle JD Edwards, every value mapped, and every contact created or updated in Mailchimp so changes can be replayed if a downstream sync fails.

A real-world example

A mid-market B2B distributor runs Oracle JD Edwards EnterpriseOne on premises for inventory, procurement, and customer invoicing. The marketing team manually exports the customer list from Oracle JD Edwards into a CSV every quarter and uploads it to Mailchimp, creating duplicate work and inconsistencies when new customers are added between exports. Customer records are often incomplete or stale in Mailchimp because address changes and phone number corrections made in the ERP do not flow to the marketing platform. With Oracle JD Edwards and Mailchimp connected, every new customer added to the F03012 Customer Master automatically populates Mailchimp within the sync interval, and address or email changes in Oracle JD Edwards immediately update the corresponding contact in Mailchimp. The marketing team can confidently segment by region or customer type because the source data is always current, and quarterly list maintenance becomes automatic.

What you can do

• •Sync new customers and vendors from Oracle JD Edwards F03012 and F0101 records into Mailchimp lists and e-commerce customer records.
• •Keep customer email, phone, billing address, and company name synchronized between Oracle JD Edwards and Mailchimp so marketing segments reflect current data.
• •Manage Oracle JD Edwards AIS Server session token lifecycle and re-authentication when tokens expire.
• •Poll Oracle JD Edwards on a customizable schedule with date-based filtering to retrieve only changed records since the last sync.
• •Maintain a full audit trail of every customer record pulled from Oracle JD Edwards, mapped, and written to Mailchimp so changes can be replayed on failure.

Questions

Which direction does data flow between Oracle JD Edwards and Mailchimp?

Data flows from Oracle JD Edwards into Mailchimp only. Customer masters (F03012) and address book records (F0101) sync to Mailchimp List Members and E-commerce Customers. Mailchimp has no ERP entities like purchase orders or GL accounts, so financial data remains in Oracle JD Edwards and does not sync to Mailchimp.

How does ml-connector handle the Oracle JD Edwards AIS Server session token?

ml-connector obtains a session token via POST to the customer's AIS Server /jderest/v2/tokenrequest endpoint using the configured username and password. The token is refreshed before each polling cycle, and if a request returns HTTP 444 (token invalid), ml-connector immediately re-authenticates and retries the failed request without data loss.

Since Oracle JD Edwards has no webhooks, how does the sync stay current?

ml-connector polls the Oracle JD Edwards data service tables on a configurable schedule using the UPMJ (date updated) field to retrieve only records changed since the last sync. The polling interval can be tuned to your business needs, and the full audit trail lets you see exactly when each customer was last checked and synced to Mailchimp.