Loading…
Epicor Kinetic (formerly Epicor ERP 10) is a manufacturing-focused ERP used by discrete and mixed-mode manufacturers and distributors for quoting, job management, MRP, inventory, and finance. Manufacturers integrate Kinetic with CRMs, customer portals, shop-floor systems, EDI, and analytics tools so that quotes, orders, jobs, and shipments do not need re-keying. AIONDATA builds Epicor integrations using the Kinetic REST API (v1 and v2), Business Activity Queries (BAQs) exposed as REST endpoints, Epicor Functions, and BPMs for event-driven triggers.
Kinetic exposes business objects through REST services (v1 and v2) for records such as Customer, Part, SalesOrder, and Job, secured with API keys and either basic or Entra ID authentication. For reads we often use BAQs published as REST endpoints, and for custom logic we use Epicor Functions or BPMs that call out when data changes.
Yes. The REST API is the same across on-premise Kinetic and Epicor's public cloud, with the main difference being network access and how API keys and access scopes are managed. For older Epicor 9 or 10.0 environments we assess the available services before committing to an approach.
Yes. AIONDATA can build a custom MCP server that wraps Epicor REST services and BAQs as tools, letting an AI agent answer questions such as "when will job 12345 ship?" or "how many of this part are on hand?" and create records only where your approval rules allow. Access is scoped through a dedicated Epicor user and API key.
We map to your custom UD fields, extended tables, and BAQs rather than assuming a vanilla install. Where EDI is involved we can integrate alongside Epicor's EDI demand management or replace point solutions with an API-based flow, depending on trading partner requirements.
Tell us the other system and what needs to flow between them. You'll get an honest scope and timeline.