By Clarus Content Team · Published 19 november 2026
An AS400 warehouse management system is a WMS that runs on IBM i, the operating system IBM sells for its IBM Power hardware. The platform is current and supported, so the real question for most UK operators is not whether the system works. It is whether the application built on it still suits the way the warehouse runs, and whether enough people understand it to change it safely.
IBM announced the AS/400 in 1988, and the name has changed several times since, as the AS/400 article records. Its operating system became IBM i in 2008, and IBM still lists it as a current product on its IBM i product page. Many UK warehouses and 3PLs still run a WMS on it. This guide explains why, where the real risks sit, and how to plan a move to a modern cloud system if you decide to make one.
What is an AS400 warehouse management system?
An AS400 warehouse management system is lagerhanteringsmjukvara written for, and run on, IBM i. Staff usually work in it through 5250 terminal screens, the block-mode “green screen” interface described on the IBM 5250 page, or through radio frequency (RF) handheld scanners that show the same screens. Most of that code is written in RPG, the language common to IBM i business software.
Is AS400 the same as IBM i and iSeries?
Mostly, yes. AS400 is the older name for the platform. iSeries and System i were later names for the same family, and IBM i is the current operating system name. Anyone asking for “the AS400” is almost always talking about an IBM i system.
| Name | What it refers to |
|---|---|
| AS/400 or AS400 | The original IBM midrange system, announced in 1988 |
| iSeries or eServer iSeries | The name used from 2000 for the same family |
| System i | The name used from 2006 |
| IBM i | The operating system name used since 2008 |
Why do so many warehouses still run a WMS on AS400?
Usually because it works. The platform has a long record of stability, and the AS/400 design let programs move to new processors without being recompiled. That helps explain how application code written many years ago is still running live operations today.
The strengths are real, and they are the reason many operators hesitate:
- Stability. A system that has run for years has known failure modes, and the team knows how to work around them.
- Fit. The screens follow the process because the process was built around them. Changing that is a change-management job as much as a software one.
- Uptime. Operators who have run IBM i for a long time often value how little time it spends down. That record is hard to dismiss.
None of this is a reason to ignore the risks. It is a reason to be clear about what you would be replacing.
What are the real risks of keeping a green-screen WMS?
The risks rarely sit in the platform itself. They sit in the application, in the few people who know it, and in the way it connects to everything around it. The table below sets out where they usually show up on the floor and the question to ask now.
| Risk | What it looks like on the floor | Question to ask now |
|---|---|---|
| Skills | Changes wait on one or two people who know the RPG code | Who maintains the code, and what happens if they leave? |
| Integration | Flat files and FTP transfers that someone checks by hand | Which files do we send and receive, and who owns each one? |
| Scanning | RF guns driven by 5250 screens, with few app-style prompts | Which tasks need a scan step the current screens cannot offer? |
| Rapportering | Reports held as spool files and exported to Excel | Which reports do managers and clients actually use each week? |
| Client visibility | Stock queries answered by phone and email | How many stock queries arrive each week, and from whom? |
| Plattform | IBM i releases move through IBM’s support stages | Which release do we run, and when does its support change? |
The skills point is the one that surprises people most. Ask your IT team who maintains the code and what would happen if those people left within the next year. The answer is rarely a number, but it usually tells you how urgent the decision is.
Which IBM i release are you running?
IBM publishes release dates and support stages on its release life cycle page. IBM i 7.3 standard support ended on 30 September 2023, with an extension to 30 September 2028. IBM i 7.4 reaches its change in service level on 30 September 2026, with a paid Service Extension to 30 September 2029. IBM i 7.6 became generally available on 18 April 2025. Check these dates against the page before you plan, because IBM updates them.
How do scanning and reporting work on an AS400 WMS?
Can an AS400 WMS work with handheld scanners?
Yes, usually over RF devices that drive 5250 screens. That covers receiving, put away and picking for most sites. It is harder to add a new scan step or prompt without a code change, and the device is only as useful as the screen behind it.
Scanning also does not replace floor discipline. Scanning a location, a pallet and a product still lets a picker take the wrong carton from the pallet beside it, because the system can only check what it is shown.
How do you get reports out of an AS400 WMS?
Most teams run queries or print spool files, then move the results into Excel or PDF by hand. It works, but every report becomes someone’s regular job, and the figures are only as current as the last export.
Where should you move: keep, modernise or replace?
Three paths are realistic. You can keep and maintain the system, modernise it in place by adding web front ends or integrations around the core, or replace it with a cloud WMS. Keeping works while the skills and release dates hold. Modernising buys time but adds more to a base you still have to support. Replacing moves the application onto a vendor-maintained product, but it needs a proper migration plan.
- Keep and maintain. The lowest disruption today. It only stays low-risk if the skills, the support dates and the hardware refresh are covered for the years ahead.
- Modernise in place. Useful when the core process is right but the edges, such as scanning, reporting or customer access, are failing. The core still needs skilled support.
- Replace with a cloud WMS. The application moves to software as a service, so you no longer run the server yourself. The migration becomes the main piece of work.
For a wider view of where an AS400 system sits beside on-premise, ERP-module and cloud options, read our guide to typer av lagerhanteringssystem.
Before you assume that keeping the system is cheap, add up the hardware, licence and support costs. Our article on why an on-premises WMS costs more than you think sets out the usual lines to check.
Clarus WMS is a cloud-native system built for 3PLs. There are no servers for you to maintain, and contracts run on a monthly rolling basis from £1,000 a month with no long-term lock-in. Mathew Buttar, Head of Solutions at Clarus, makes the case for cloud on uptime and updates. He says cloud gives significantly better uptime, and because it is software as a service, any update the vendor develops is available to every customer. On-premise systems, by contrast, are limited by server life, server size, manual updates and the downtime needed to apply them.
Security is the usual objection, and it deserves a proper answer. The NCSC cloud security guidance is a sensible checklist to take into any supplier conversation.
How do you migrate from a legacy WMS to the cloud?
Moving off an AS400 WMS is mostly a data and process project with a software installation at the end. A legacy system is one that still runs the operation but was built around older tools and assumptions. The steps below follow the order that usually saves the most pain.
Clean the data before anything moves
Products, locations, stock and customer records all need checking before migration. Duplicate product codes, location codes that no longer match the floor and stock records that have drifted from the counted quantity all become errors on day one. The data migration work is usually bigger than the software configuration. Start the audit early, agree who signs off each data set, and decide how much history you need.
Map every interface
AS400 WMS systems often exchange data with carriers, customers and an ERP through EDI, flat files and FTP. List every feed: what it carries, who sends it, how often, and what comes back to confirm it. Our guide to WMS ERP integration covers what to connect and how to test it.
Where an ERP offers an API, Clarus can connect to it that way. Where it does not, Clarus can remap interface files into its own format to create a sales order or receipt, then send a file back to confirm it. Either way, the mapping needs to be written down, field by field, before build starts.
Decide which custom logic you actually need
Bespoke rules often began as a workaround for one customer and then became standard practice. For each rule, ask whether it is a customer requirement, a legal or safety requirement, or simply habit. Habit is the one to challenge first. Keep the rules that protect stock or a contract, and drop the ones that only reproduce an old screen.
Big bang or parallel running?
Mathew Buttar, Head of Solutions at Clarus, puts the decision bluntly: “A big bang is fine if you have time for UAT. Don’t do the big bang if you haven’t done a full UAT schedule where you are confident that each of your processes, goods in, stock control, goods out, interfaces, has been listed, checked, tested and signed off by all parties involved including the customer.”
Parallel running keeps the old system live while the new one takes real work. It gives you a fallback, but it means transactions and stock are handled twice, and someone has to reconcile the two systems every day. It suits operations that have the people to manage that double running. A big bang is quicker, but it only works if your testing is complete.
Run UAT with super users and plan the cut-over
Name at least two super users early. Clarus’s approach is to identify them at the start of a project, so they run UAT and become the go-to people on site. Clarus’s UAT is manual, and it includes interface files. The customer tests the feeds too, not just the screens.
Plan the cut-over weekend with a full stock count, agree how open orders move across, and set a sign-off point for each process. Once the new system is live, keep the IBM i read-only so historical records stay available for queries without anyone editing them.
On timing, Clarus aims to go live in around 12 weeks on a standard project, with the right support on both sides. That assumes an off-the-shelf set-up with no development. Complex projects with many features and high volumes can take much longer, and the most demanding can run to two years. Our warehouse management system implementation guide sets out the wider method.
What should you ask a cloud WMS supplier?
- How will you take our data feeds, by API, interface file or SFTP, and what do you need from us to start?
- What does your UAT look like, and who signs it off?
- Which parts of the standard product do you configure, and which would need development?
- How many super users will you ask us to name, and what will they do?
- What go-live date would you commit to for our scope, and what would move it?
- How do you support us after go-live, and how do you release updates without long downtime?
Tala med en lagerarbetare
Om du håller på att utvärdera dina alternativ och vill se hur ett specialutvecklat lagerhanteringssystem (WMS) fungerar i praktiken, är Clarus värt att ta en pratstund med. Vi samarbetar med 3PL-företag och distributörer över hela Storbritannien för att implementera lagerhanteringsprogramvara som anpassas efter just er verksamhet – inte tvärtom.
Kom i kontakt med vårt team att diskutera dina krav.