Epicor Kinetic and Zoho CRM integration

What moves between them

The main flow runs from Epicor Kinetic into Zoho CRM. Vendors created or modified in Epicor Kinetic are polled on a schedule and synced into Zoho CRM as Vendor records. Purchase orders from Epicor Kinetic are polled and mapped into Zoho CRM Purchase Orders, with line items translated to match the CRM structure. Reference data such as vendor categories and product codes is aligned to keep purchase order lines valid in both systems. Zoho CRM is read-mostly in this integration; ml-connector does not write vendor or PO changes back to Epicor Kinetic.

How ml-connector handles it

ml-connector stores both credential sets encrypted and uses Basic Auth or OAuth2 bearer tokens to authenticate against Epicor. For Epicor cloud, it accepts the full tenant URL per customer and constructs OData queries with $filter on UpdatedOn to retrieve changed records since the last sync, using $top=100 and $skip offsets for pagination. For Zoho, it refreshes the OAuth2 access token hourly before expiry and uses the api_domain from the token response as the base URL. ml-connector handles the one-day webhook channel expiry by checking channel status on each sync cycle and renewing as needed, though it primarily relies on polling for reliability. Vendors are deduplicated by comparing Epicor source IDs against existing Zoho records to prevent duplicates on re-sync. Purchase order line items require two-step mapping: Epicor PO header data is fetched along with line detail, then mapped to Zoho CRM line items, with GL account references stored in audit metadata for financial reconciliation. Bearer tokens on both sides carry expiry windows, so ml-connector tracks refresh timing to avoid token-expired failures mid-flow. Every record carries audit metadata with the Epicor source ID, sync timestamp, and change delta.

A real-world example

A mid-sized electronics distributor runs Epicor Kinetic for inventory, purchasing, and finance, and uses Zoho CRM for customer relationships and sales opportunity tracking. Before the integration, the sales team manually looked up vendor and PO information in Epicor to answer customer questions about delivery and supply status, losing context between sales cycles. With Epicor Kinetic and Zoho CRM connected, vendors and active purchase orders appear directly in the CRM alongside each customer account, so sales representatives can see supplier lead times, outstanding commitments, and product availability without context switching. Operations can also reference sales pipeline data in Epicor reports without re-keying forecast assumptions.

What you can do

• •Sync vendor master data from Epicor Kinetic into Zoho CRM Vendor records on a configurable schedule, keeping supplier lists aligned.
• •Map Epicor Kinetic purchase orders and line items into Zoho CRM Purchase Orders with reference data for order status tracking.
• •Authenticate Epicor with Basic Auth or OAuth2, and Zoho with OAuth2 client credentials, refreshing tokens before expiry.
• •Poll Epicor on a schedule using OData date-range filters to retrieve only changed records since the last sync, reducing bandwidth and latency.
• •Prevent duplicate vendors and purchase orders by cross-referencing Epicor source IDs and maintaining a full audit trail on every record.

Questions

Which direction does data move between Epicor Kinetic and Zoho CRM?

The main flow is from Epicor Kinetic into Zoho CRM. Vendors and purchase orders move from Epicor into Zoho CRM so your sales team can see supplier and order information. ml-connector does not write vendor or PO changes back to Epicor Kinetic, so Zoho CRM is treated as a read-mostly mirror of Epicor sourcing data.

How does ml-connector handle Epicor's lack of native webhooks?

Epicor Kinetic has no native outbound webhooks, so ml-connector polls the Epicor REST API on a schedule tied to your purchasing and sales cycle. It uses OData $filter queries on date fields like UpdatedOn to retrieve only records changed since the last sync, reducing unnecessary API calls and keeping both systems current without manual intervention.

Does the integration work with both Epicor cloud and on-premises instances?

Yes. Epicor cloud uses OAuth2 against a tenant-specific SaaS URL, while on-premises instances use Basic Auth or Token Resource Service tokens against a customer-provided host. ml-connector accepts either configuration and handles tenant-specific URLs, company segments, and the API Key header requirement that applies to both cloud and on-premises deployments.