A lot of conversations about AI in manufacturing start from the wrong assumption: that the ERP is somehow the problem. It almost never is. SAP, Oracle, Epicor, Infor \u2014 these systems exist because they’re genuinely good at what they were built to do, and most manufacturers running one aren’t looking to rip it out.<\/p>\n\n\n\n
The actual problem usually isn’t inside the ERP at all. It’s in the space around it \u2014 the manual work that exists specifically because the ERP doesn’t (and often shouldn’t) handle everything on its own.<\/p>\n\n\n\n
Three gaps show up constantly, across almost every manufacturing operation we’ve looked at.<\/p>\n\n\n\n
The first is communication. ERPs track orders and inventory, but they don’t read a supplier’s email and update themselves. Someone has to open that email, interpret it, and manually enter whatever changed.<\/p>\n\n\n\n
The second is documents. Invoices, packing slips, certificates of compliance \u2014 these arrive as PDFs or scanned images, and getting that information into a structured system still usually means a person reading the document and typing the relevant fields in by hand.<\/p>\n\n\n\n
The third is the in-between state of things in motion. A shipment that’s delayed, a partial delivery that doesn’t match the original PO, an order that’s been split across multiple trucks \u2014 ERPs are built around clean, structured records, and they tend to handle messy, in-progress situations poorly. Someone ends up tracking the messy reality in a spreadsheet on the side, because the ERP’s clean data model doesn’t have a natural place for it yet.<\/p>\n\n\n\n
None of these are ERP failures. They’re just outside the scope of what an ERP is designed to do. That’s exactly the space where an AI agent is actually useful \u2014 not as a replacement, but as the thing that sits in that gap and absorbs the manual translation work.<\/p>\n\n\n\n