There’s a moment that plays out the same way in almost every order-automation demo a distributor sits through. The pitch is good. The screenshots are clean. Then you say the words “we’re on the AS/400” — or iSeries, or System i, depending on which decade you started — and you can feel the room change. The rep nods slowly. “Got it. So, ah, we’d have to look into that one.” You never hear back with a real plan.
If that’s happened to you more than once, it’s not a coincidence and it’s not your fault. The market quietly sorted AS/400 shops into the “too hard” pile years ago. The irony is that those are exactly the shops with the most manual order entry left to eliminate. Here’s what’s actually going on behind that awkward pause — and why running your business on a green screen is no reason to keep retyping orders by hand.
What people mean when they say “AS/400”
First, a quick translation, because the name is a moving target. AS/400 was IBM’s midrange system launched in 1988. It became the iSeries, then System i, then IBM i running on Power servers. Most distributors use the names interchangeably, and so will this post. The hardware underneath is modern and supported; what people are really pointing at is the application layer — order entry that runs through 5250 green-screen programs, business logic written in RPG, and decades of customizations that make each install one of a kind.
That stack is rock-solid. It’s been entering orders correctly since before most SaaS vendors were founded. The problem isn’t reliability. It’s that it doesn’t look like what modern automation tools were built to plug into.
Why automation vendors skip it
Most AI order-entry startups grew up integrating against cloud ERPs with clean REST APIs — connect once with an OAuth token and a webhook, and the same connector works for every customer on that platform. That economics is the whole business model. AS/400 breaks it in three ways:
- No off-the-shelf API to call. Order entry often lives behind 5250 screens, RPG programs, or flat-file and EDI handoffs — not a documented JSON endpoint a developer can hit in an afternoon. Getting an order in means meeting the system the way it actually accepts orders.
- Every install is a snowflake. Two distributors on the “same” AS/400 setup have years of custom order types, custom pricing logic, and custom validation rules layered on top. There’s no single connector that works everywhere, so the vendor’s connect-once math falls apart.
- The stakes are high and the buyers know it. This system is the business and has been for thirty years. No competent ops leader is going to let a half-tested integration write bad orders into the system of record. So the vendor would have to earn real trust — and that’s slower than chasing the next cloud-ERP logo.
So they do the rational startup thing: they smile, say “we’d have to look into that,” and go sell to someone on NetSuite instead. The AS/400 lane gets left uncontested — which is backwards, because that’s where the manual keying is heaviest.
”Just migrate off it” is advice, not a solution
The other thing AS/400 shops get told is to modernize: rip out the iSeries, move to something cloud-native, then automate. For most distributors that’s a multi-year, seven-figure project that risks the one system the business genuinely cannot afford to break — all to fix a problem that was never about the ERP.
Because the ERP isn’t the bottleneck. The bottleneck is the human translation layer sitting in front of it: someone reading an emailed PDF, a faxed PO, or a handwritten note and retyping it, line by line, into the order screen. That work is identical whether the screen behind it is green or cloud-blue. Replacing a system that works in order to delete the retyping is like buying a new house because you don’t like doing the dishes.
What it actually takes to automate order entry on AS/400
The skill that matters isn’t calling a modern API. It’s meeting the system where it lives. On an AS/400 it comes down to three things:
- Read any format the customer sends. Emails, PDF purchase orders, faxes, scanned documents, handwritten notes — all turned into structured line items with quantities, part numbers, and pricing.
- Validate against your catalog before anything posts. Match customer part numbers to your SKUs, check pricing and quantities, and surface anything that doesn’t line up — instead of keying a wrong order and creating a return three days later.
- Write into the system the way the system accepts orders. For an AS/400 that can mean the order-entry program, a structured import, an EDI or flat-file handoff, or an integration touchpoint the install already exposes. The job is to fit the existing path, not force a new one.
None of that requires replacing the iSeries, retraining your team on new software, or asking your customers to change how they send orders. The customer keeps emailing the same PDF. The order desk keeps owning the relationship. The retyping is what disappears.
Flag, don’t guess
AS/400 teams are right to be cautious, because a bad automated order is worse than a slow manual one. So the rule has to be flag, don’t guess. When everything is clean — a clear PDF, parts that match, pricing that checks out — the order flows through. When something’s ambiguous — a smudged fax, a part number that won’t resolve, a quantity that looks off — it routes to a person to confirm instead of getting guessed at and posted.
That’s the difference between automation a thirty-year-old system can actually trust and automation that just invents a new category of errors. Your team stops keying every order and starts reviewing the handful that genuinely need a human.
This is the lane Ordermatic chose on purpose
Ordermatic turns the emails, PDFs, faxes, and handwritten POs your customers already send into clean, validated ERP entries — automatically — and we built for the systems most automation vendors won’t touch, including AS/400, IBM iSeries, and Infor M3/M4 and Epicor Prophet 21.
We do it in production today with GenFit (Generational Fittings), an industrial fittings distributor running a legacy stack. Ordermatic now processes $1.5M+ in orders for them with 65% of orders fully automated — no migration, no change to how their customers order, and their team focused on exceptions and relationships instead of the keyboard.
No rip-and-replace. No new software for your team to learn. No asking customers to change anything. It runs on top of the system you already trust.
Put a number on the green screen
Before you accept that AS/400 means stuck, it’s worth knowing what the manual keying is costing. We built a free set of calculators — cost-per-order, manual-vs-automated, and a hiring-vs-automating projection — that run the math on your real volumes, with no email wall to see the numbers. For most iSeries distributors the figure climbs past six figures faster than expected, precisely because the manual load is heaviest where automation was hardest to get.
The AS/400 lane was abandoned because it was hard, not because it didn’t matter. If you’re on the iSeries, run the calculators, then book a 30-minute demo and we’ll walk through your order flow on your actual system — green screen and all.
