Epicor Kinetic and Cin7 integration

What moves between them

The main flow runs from Epicor into Cin7. Vendors and purchase orders from Epicor sync into Cin7 Suppliers and Purchases on a configurable schedule. Sales and purchase records from Cin7 can be read and mapped back into Epicor GL accounts for financial reconciliation. The chart of accounts in Cin7 is read-only, so ml-connector does not write GL entries back to Cin7. Vendor master and GL account dimensions are aligned first so purchases land on valid accounts.

How ml-connector handles it

ml-connector stores both credential sets encrypted and sends the custom Cin7 API key headers on every request. On the Epicor side it accepts the full tenant URL and company name, since Epicor requires both in the path, and polls using OData date filters to retrieve records changed since the last sync. The API Key header in Epicor is sent alongside OAuth2 or Basic Auth credentials as required. Cin7's chart of accounts is queried once to build the GL dimension map, then sales and purchase amounts are allocated to matching Epicor GL accounts. Epicor tokens expire within an hour, so ml-connector implements refresh logic on 401 responses. Cin7 rate limits are enforced per API key, so ml-connector backs off on 429 responses. Every vendor, purchase, and GL posting carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized distribution company runs Epicor Kinetic for procure-to-pay and general ledger, and uses Cin7 Core for inventory and order fulfillment across multiple warehouses. Before the integration, the procurement team exported vendor and purchase order reports from Epicor weekly and re-entered them into Cin7 by hand, while the accounting team manually coded purchases from Cin7 into Epicor GL accounts for month-end close. With Epicor and Cin7 connected, vendors created in Epicor flow into Cin7 automatically, purchase orders sync in both directions, and sales and purchases from Cin7 are mapped to the correct GL accounts without re-entry. Reconciliation time shrinks from days to hours.

What you can do

• •Sync vendors and supplier master data from Epicor Kinetic into Cin7 Core on a configurable schedule.
• •Move purchase orders from Epicor into Cin7 Purchases and read return receipts back to Epicor for matching.
• •Map sales and purchase records from Cin7 to Epicor GL accounts for accurate financial posting.
• •Authenticate Epicor with OData API Key and OAuth2, and Cin7 with custom API key headers, on every request.
• •Poll Epicor on a schedule with OData date filters and handle token refresh, with retries and full audit trails on every record.

Questions

Which direction does data move between Epicor Kinetic and Cin7 Core?

Vendors and purchase orders flow from Epicor into Cin7. Sales and purchase records from Cin7 are read and mapped to Epicor GL accounts. Cin7's chart of accounts is read-only, so ml-connector does not write GL entries back to Cin7. Reference data such as vendors and GL accounts is synchronized to keep both systems aligned.

How does the integration handle Epicor's polling-only API and different auth schemes?

ml-connector uses Epicor's OData v4 API with date filters on fields like UpdatedOn to retrieve records changed since the last sync, combined with offset pagination. It sends the required API Key header alongside OAuth2 or Basic Auth credentials as configured. Tokens are refreshed on 401 responses, and the full tenant URL and company segment are accepted per customer instance.

Does Cin7's read-only chart of accounts limit the integration?

Yes. Cin7's GL chart is read-only via API, so ml-connector reads GL dimensions from Cin7 once and uses them to allocate incoming purchases to matching Epicor GL accounts. New GL accounts must be created in both systems outside the integration, then the sync uses them for mapping.