For manufacturers and distributors running SYSPRO
We have run AI against SYSPRO’s own business objects and tables, not a demo dataset. That groundwork is already done, so the custom apps, chatbots, reporting and live dashboards you need get built on top of it instead of starting from scratch.
We do not replace SYSPRO. We build on e.net and OData, and everything runs in your accounts.
Why this is faster with us
Any AI project on an ERP spends its first weeks the same way: working out how the system stores things and what can be trusted. That work is done for SYSPRO.
We built our own tools for SYSPRO and ran them against the real system, over and over. e.net business objects, OData endpoints, and the SQL tables underneath. Where the same fact lives in three places, we know which one to trust.
We put real SYSPRO questions in front of it and checked the answers against the records. Where it was confidently wrong, we fixed the tooling until it was not.
SYSPRO customers are using this now. Your build starts from a foundation that has already survived contact with real data.
The gap
Different manufacturers, same three complaints, every time.
Anything beyond the standard set means SRS and Crystal. That means a designer installed on the right workstation, the right permissions, and somebody who knows Crystal. So most people just export to Excel.
Simple questions turn into a two week ticket
Inventory, sales orders, and job costing each answer for themselves. Stitching them into one number, per job, per customer, per month, is where the analysis stalls out.
The numbers that matter most are the slowest to get
Orders come in by email or portal and get keyed in. Confirmations get keyed out. Every keystroke is a chance to be wrong, and it happens all day.
Hours a day of typing that nobody should be doing
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 against your SYSPRO install so Claude, ChatGPT, or Copilot can answer from live SYSPRO data instead of guessing.
In practice
Someone asks "what is on backorder for our top ten customers, and what is the stock position." The assistant reads SYSPRO through the MCP server and answers with real records. Read only by default. Writes are scoped, logged, and enabled on purpose.
Warehouse scanning, shop floor tablets, customer and rep portals, quoting tools. Built for one job and wired into SYSPRO through e.net business objects.
In practice
A picker scans a bin on a phone and the transaction posts through the e.net business object, so SYSPRO validation, costing, and audit trail all run. No direct table writes, no reconciliation surprises at month end.
A chatbot grounded in your SYSPRO data and your own documents. Price lists, spec sheets, customer history, work instructions. It answers from your reality.
In practice
Customer service asks about a part number: stock on hand, what is on order, what this customer paid last time, and lead time. One answer, in seconds, with links back to the SYSPRO records behind it.
Sales, inventory turns, WIP, on-time delivery, margin by job. Live on a wall screen and on a phone. No Crystal designer, no workstation requirement, no Friday rebuild.
In practice
We read through SYSPRO OData and SQL Server views, then publish one dashboard everyone shares. The Monday meeting starts with numbers nobody argues about.
SYSPRO connected to the rest of the stack. Ecommerce, EDI, CRM, shipping, and the spreadsheets your team will not give up.
In practice
A web order becomes a SYSPRO sales order through e.net, the shipment posts back, the tracking number reaches the customer, and nobody typed anything twice.
Anywhere a person moves a number into or out of SYSPRO by hand, we automate it. Orders, POs, confirmations, invoices, price updates.
In practice
Emailed purchase orders get read, matched against SYSPRO, and posted as sales orders. Anything ambiguous goes to a person with the reason attached. The rest just happens.
Not sure which of these matters most for your company? That is what the first call is for.
Under the hood
Through the interfaces SYSPRO ships. Nothing bolted onto the side, nothing clicking through the UI overnight.
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
direct table writes, every transaction goes through e.net
Questions
No. SYSPRO stays your system of record. We build the layer on top: dashboards, custom apps, AI, and the connections to everything else you run. Most ERP replacement projects overrun and a majority miss their goals. This is deliberately not that.
Through the interfaces SYSPRO ships. e.net business objects for transactions, SYSPRO OData for RESTful reporting reads, and read only SQL Server views for heavy cross module analysis. On SYSPRO 8 that traffic runs through the e.net communications load balancer, the same way SYSPRO own services do.
It is, when the writes go through e.net business objects, which is exactly how we do it. SYSPRO applies its own validation, costing, and audit trail to those transactions. What is not safe is writing straight into SQL tables, and we do not do that.
MCP is the open standard for letting an AI assistant use a real system safely. An MCP server for SYSPRO means your team can ask questions in plain English and get answers from live SYSPRO 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.
For most day to day reporting, yes. Dashboards we build refresh on their own and open in a browser, so nobody needs Crystal Designer installed or the right operator permissions to see a number. Keep SRS for the printed documents and statutory formats it is genuinely good at.
Usually only briefly, to confirm e.net licensing and access. We are not competing with your SYSPRO 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. We move fast because we work from your live SYSPRO data instead of months of interviews. The worst re-keying is usually gone inside the first two weeks.
Let's talk
Thirty minutes. You show us how SYSPRO is set up and which reports people gave up on. We tell you straight what we would build first, and what it would take.
Read next
Other systems we build on
Epicor Kinetic
MCP servers, custom apps, AI chatbots, and live dashboards built on the Epicor Kinetic REST API, BAQs, and Epicor Functions.
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