Epicor Kinetic and TrueCommerce integration

What moves between them

The primary flow moves purchase orders from Epicor Kinetic into TrueCommerce. New or modified purchase orders are polled from Epicor with OData filters on UpdatedOn timestamps, then formatted as X12 850 EDI documents and written to the TrueCommerce SFTP inbox or submitted via the Exchange API. Purchase order acknowledgments (855), invoices (810), and advance ship notices (856) arrive at TrueCommerce from suppliers and are polled back into Epicor at a scheduled cadence (hourly or daily depending on trading partner requirements). The sync is primarily one-way: Epicor pushes orders out; TrueCommerce brings supplier responses back in. Vendor master data and reference tables are synced bidirectionally to keep trading partner details in agreement.

How ml-connector handles it

ml-connector polls Epicor Kinetic with bearer token refresh logic on a one-hour cycle and retrieves purchase orders modified since the last sync using OData $filter on UpdatedOn. It maps Epicor PO line items to X12 850 segments and submits them to TrueCommerce via SFTP or the Exchange API, handling customer-specific file naming conventions. On the return path, it polls TrueCommerce SFTP (hourly or daily per configuration) for inbound EDI documents, deduplicates using ISA control numbers from functional acknowledgments, and parses 855 acknowledgments and 810 invoices back into Epicor via the two-step update pattern (GetNew followed by UpdateMaster). Epicor's bearer tokens expire roughly hourly and are refreshed automatically. TrueCommerce credentials (SFTP username/password or API key) are stored encrypted and rotated per your Merchant ID provisioning. All record metadata carries a full audit trail so supply chain events can be traced back to the source system.

A real-world example

A mid-sized discrete manufacturer produces goods to order and uses Epicor Kinetic for procurement and inventory. Before integration, the procurement team manually exported purchase orders from Epicor, re-keyed them into TrueCommerce for EDI encoding, then watched for supplier acknowledgments and invoices that arrived as EDI files and had to be manually parsed and entered into Epicor to update receipt and invoice status. With Epicor and TrueCommerce connected, each new purchase order flows automatically into the EDI network, supplier responses come back and are matched to open orders in Epicor without re-entry, and invoice receipt status is updated without manual intervention. The team now focuses on supplier performance and risk instead of data entry.

What you can do

• •Poll purchase orders from Epicor Kinetic on a schedule and submit them to TrueCommerce as X12 850 EDI documents ready for supplier delivery.
• •Receive purchase order acknowledgments (855), invoices (810), and advance ship notices (856) from TrueCommerce and post them into Epicor to close purchase orders and trigger receipt flows.
• •Authenticate Epicor with OAuth2 bearer tokens and handle token refresh automatically, and TrueCommerce with SFTP or API key credentials stored encrypted.
• •Map Epicor PO line items to X12 EDI segments and handle per-customer TrueCommerce file naming and integration path conventions.
• •Maintain a full audit trail of every order, acknowledgment, and invoice so supply chain events can be traced and replayed if a downstream call fails.

Questions

Do purchase orders flow from Epicor to TrueCommerce, or the other way around?

Purchase orders flow primarily from Epicor to TrueCommerce. New POs created in Epicor are polled, formatted as X12 850 documents, and submitted to TrueCommerce for EDI encoding and supplier delivery. Supplier responses (acknowledgments, invoices, advance ship notices) flow back from TrueCommerce into Epicor to close the loop and update receipt and invoice status.

How does the integration handle TrueCommerce's customer-specific file naming and API configuration?

TrueCommerce assigns file naming conventions and integration paths per customer during onboarding, and does not publish them as standard APIs. ml-connector stores these conventions per customer credential set and applies them when writing outbound EDI files to SFTP or the Exchange API. Configuration is confirmed during integration setup and stored encrypted alongside the SFTP or API key credential.

Does the integration handle EDI deduplication and Epicor token refresh?

Yes. On the EDI side, TrueCommerce uses ISA control numbers in functional acknowledgments to detect duplicate documents; ml-connector respects this deduplication. On the Epicor side, OAuth2 bearer tokens expire roughly every hour; ml-connector detects 401 responses and refreshes the token automatically before retrying the failed request.