Epicor Kinetic and Orderful integration

What moves between them

The primary flow is outbound: Epicor purchase orders are polled by OData UpdatedOn filter and posted to Orderful's /v4 endpoint as 850 documents with the supplier's ISA identifier. Orderful translates and delivers them to the supplier's preferred channel. Inbound 855 (acknowledgments) and 810 (invoices) arrive via Orderful webhooks or polling and are mapped back into Epicor as PurchaseOrderChangeAcknowledgments and APInvoices. Vendor and part master records are synced once during initial setup so ISA identifiers and line-item details are consistent end-to-end.

How ml-connector handles it

ml-connector queries Epicor's PurchaseOrders entity on a schedule you define, filtering by UpdatedOn to retrieve only records changed since the last sync. It extracts the vendor ISA identifier from your vendor master mapping, assembles the 850 document structure, and POSTs it to Orderful's /v4 endpoint with your API Key. Orderful returns a transaction ID for audit tracking. On the inbound side, ml-connector either webhooks incoming 855 and 810 documents directly into a handler you expose, or polls Orderful's /v3/polling-buckets endpoint every 5 to 10 minutes. Each inbound document is mapped to the matching Epicor PO via line references, and the data is inserted into the appropriate Epicor entity (PurchaseOrderChangeAcknowledgment or APInvoice). EDI validation errors and mapping failures are logged with full context for investigation. All transactions carry a complete audit trail, linking Epicor PO numbers to Orderful transaction IDs and EDI document versions.

A real-world example

A mid-sized electronics distributor runs Epicor Kinetic for procurement and inventory. They supply 40 manufacturers across North America, each expecting EDI 850 purchase orders and able to send back 855 acknowledgments and 810 invoices. Before the integration, the procurement team exported POs from Epicor each morning, manually formatted them as X12, and uploaded them to each supplier's VAN or SFTP site, then manually downloaded incoming EDI and re-entered invoices into Epicor. With Epicor and Orderful connected, each new PO in Epicor automatically translates to EDI and routes to the correct supplier, inbound acknowledgments update the PO status in Epicor same-day, and invoices are received and matched to the original PO without human intervention. The procurement team spends three hours per day on other work, and invoice discrepancies fall to near zero.

What you can do

• •Translate Epicor purchase orders to EDI 850 documents and route them to suppliers via Orderful's AS2, SFTP, or HTTP channels.
• •Receive and map inbound 855 purchase order acknowledgments from suppliers back into Epicor as PurchaseOrderChangeAcknowledgments.
• •Receive and map inbound 810 invoices from suppliers into Epicor as APInvoices, linked to the original PO for three-way matching.
• •Poll Epicor POs on a schedule you control using OData UpdatedOn filtering, and receive Orderful documents via webhooks or polling.
• •Maintain a complete audit trail linking every Epicor PO to its Orderful transaction ID and EDI document versions, with full error logging for EDI validation failures.

Questions

How does ml-connector know which ISA identifier to use when sending an Epicor PO to Orderful?

You map each vendor in Epicor to their ISA identifier during setup, storing the mapping in ml-connector's configuration. When a PO is polled from Epicor, ml-connector looks up the vendor ID, retrieves the ISA identifier, and includes it as the receiver.isaId in the Orderful 850 request. If the mapping is missing, the transaction is flagged as an error for investigation.

Does ml-connector support both 856 (ship notice) and 810 (invoice) inbound from Orderful?

Yes. Orderful webhooks both 856 and 810 documents, and ml-connector can process both. Inbound 856 ship notices map to Epicor's receiving records, and 810 invoices map to APInvoices. The Orderful transaction ID and original EDI sender are stored in each Epicor record for full traceability.

What happens if a supplier sends an EDI document that does not match any open PO in Epicor?

ml-connector logs the mismatch with the supplier ISA ID, EDI document type, and line details so your procurement team can investigate. The document is flagged but not discarded, allowing you to manually match it or correct the PO data if needed. All unmatched transactions appear in the ml-connector audit log for review.