For manufacturers running Epicor Kinetic
Kinetic has one of the best integration surfaces in mid-market ERP. Most shops use almost none of it. We build the layer that turns your BAQs and REST endpoints into things your people actually use.
We do not replace Epicor. We build on the REST API, and everything runs in your accounts.
The gap
The API is good. That is not usually the bottleneck.
Somebody built the queries. They live in the client, they get run by hand, and the results get pasted into a spreadsheet. The data is already shaped. It just never became a dashboard.
Work already done, sitting unused
Application Studio layers, BPMs, and functions built by whoever was here in 2021. They work, mostly. Nobody currently on payroll wants to touch them, so nothing new gets built.
Every new request stalls at "who knows Epicor"
Kinetic holds the truth, and the business runs off exports. Scheduling, quoting, and margin tracking happen in files, then somebody keys the decisions back in.
The ERP is a system of record, not a system of work
What we do
Six things, in whatever order helps you most. Most manufacturers start with two.
MCP is the standard that lets AI assistants talk to real systems. We build one over your Kinetic REST endpoints and BAQs, so Claude, ChatGPT, or Copilot answer from live Epicor data.
In practice
Someone asks "which jobs shipped late last month, and what did they have in common." The assistant runs the right BAQ through the MCP server and answers with real records. Read only by default, and it inherits the API Key plus user identity Kinetic already requires, so permissions are not something we reinvent.
Shop floor tablets, scanning, quoting tools, customer and rep portals. Built for one job and wired into Kinetic through the REST API instead of another client license.
In practice
An operator clocks a job and flags a scrap part on a tablet. It posts through the Kinetic REST API, so the transaction lands the same way it would from the client, with your BPMs and functions still running.
A chatbot grounded in your Epicor data and your own documents. Travelers, work instructions, spec sheets, customer history. It answers from your reality.
In practice
Inside sales asks what a customer ordered last time, what it shipped at, and what is on the floor now. One answer, in seconds, with links back to the Epicor records behind it.
Backlog, throughput, on-time delivery, and margin by job on a wall screen and a phone. Built on the BAQs you already have, refreshing on their own.
In practice
We take the BAQs someone already wrote, expose them as REST endpoints, and publish one dashboard everyone shares. No new client licenses, no Friday rebuild.
Kinetic connected to CRM, EDI, ecommerce, shipping, and accounting. Data entered once, showing up everywhere it should.
In practice
A web order becomes a Kinetic sales order through the REST API, the shipment posts back, the customer gets tracking, and nobody typed anything twice.
Anywhere someone copies a number into or out of Epicor by hand, we automate it. Quotes, POs, confirmations, invoices, price updates.
In practice
Emailed purchase orders get read, matched against Kinetic, and posted as sales orders through an Epicor Function. Anything ambiguous goes to a person with the reason attached.
Not sure which of these matters most for your company? That is what the first call is for.
Under the hood
Through the API Epicor built for exactly this. Nothing bolted on the side.
2 to 4 weeks
from first call to something live in your business
20 to 40+ hrs
of monthly re-keying removed in a typical engagement
0
new Epicor client licenses needed for the apps we build
Questions
No. Kinetic stays your system of record. If you are on a version with the REST API, and most supported versions are, we have what we need. We will tell you honestly if an upgrade would make a specific build easier, but it is not a prerequisite for starting.
Through the Kinetic REST API, which exposes OData v4 endpoints for business objects, processes, reports, BAQs, and Epicor Functions. We browse your instance's own Swagger help first, so everything we build is tested against your configuration rather than a generic one.
It should not. We work through the API rather than modifying Application Studio layers or BPMs, so what we build sits outside your customization stack. Writes go through the API, which means your existing BPMs and validation still fire exactly as they do from the client.
Yes, and that is usually where we start. A BAQ someone already built is data that has already been shaped and validated. Exposing it as a REST endpoint turns a query somebody runs by hand into a dashboard that updates itself.
MCP is the open standard for letting an AI assistant use a real system safely. An MCP server for Epicor means your team asks questions in plain English and gets answers from live Kinetic data, with every request scoped and logged. It is the difference between an AI that guesses about your business and one that reads your actual order book.
Usually only briefly, to confirm API access and licensing. We are not competing with your Epicor partner for the ERP work. We take the projects that sit outside what a partner typically builds.
Two to four weeks for the first working piece. Kinetic's API is good enough that we spend our time on what to build rather than how to get at the data. The worst re-keying is usually gone inside the first two weeks.
Let's talk
Thirty minutes. You show us how Kinetic is set up and where people gave up and went back to Excel. We tell you straight what we would build first, and what it would take.
Read next
Other systems we build on
SYSPRO ERP
MCP servers, custom apps, AI chatbots, and live dashboards built on SYSPRO e.net and OData. We keep SYSPRO as your system of record.
Global Shop Solutions
MCP servers, custom apps, AI chatbots, and live dashboards built on Global Shop Solutions through GAB, the database, and its Web API.
Made2Manage
MCP servers, custom apps, AI chatbots, and live dashboards built on Made2Manage through its Web API, SQL Server, and SSRS.
abas ERP
MCP servers, custom apps, AI chatbots, and live dashboards built on top of abas ERP. We keep abas as your system of record.
All ERP work