Guide
Manufacturing software companies, compared honestly
Most lists of manufacturing software companies are published by someone who sells one of the systems on them. This guide names the vendors the rankings agree on, explains why the rankings disagree, shows how to choose by what you make rather than by rank, and ends where no vendor list does: what you will still run in a spreadsheet afterwards.
Which manufacturing software companies should you shortlist?
Shortlist by what you make and how you make it, not by position on a list. Acumatica, Microsoft Dynamics 365 Business Central, SAP, Oracle NetSuite, Epicor Kinetic, Infor CloudSuite Industrial, Sage and Plex appear across most rankings, and which of them fits depends on whether your work is repetitive, make to order, engineer to order or process.
Search this term and you will find a dozen ranked lists that disagree with each other. That disagreement is not because the question is hard. It is because of who writes the lists, which is the first thing worth understanding before you read any of them, including this page.
What follows is the set of manufacturing software companies that appear across those rankings, what each is consistently reported to suit, how to narrow the field by your production type, what the software actually costs once implementation is counted, and the part no vendor list ends with: what you will still be doing in a spreadsheet after any of them goes live.
Why do all the rankings disagree with each other?
Because most of them are published by companies that sell or implement one of the systems being ranked. The clearest example on this results page is a list that places its own publisher first, citing a self reported hundred percent implementation success rate, while that publisher is an implementation partner for one of the vendors it ranks.
This is worth being specific about, because it changes how you should read every page you have open. Among the pages ranking for this search are two published by an Infor implementation partner. Their lists rank that partner first. The supporting figure is a hundred percent implementation success rate, self reported, with no definition of success and no independent audit. Nothing about that is unlawful or even unusual, and it is exactly why the rankings do not agree with each other.
The rest of the field divides into three. Vendor blogs, which rank their own product highly for reasons that need no explanation. Partner and reseller blogs, which rank whichever product they implement. And comparison sites, which are generally the most neutral of the three but which usually earn through referral fees from the vendors listed, so the set of products that appears is shaped by who pays referral fees.
We are not neutral either, and the useful thing is to say exactly how. We do not sell, resell or implement any ERP. We build the software that sits around one, and we are paid more when a company has gaps a product did not fill. That gives us a reason to emphasise the limits of these systems, which is the bias to read this page against. What it also means is that we have no reason to prefer one vendor over another, and we take no referral fees from any of them.
How to read a ranking. Find who publishes it. Look for a partner or reseller page on the same site. Check whether the number one on the list is also the product that site implements. That takes about thirty seconds and tells you more than the ranking does.
What do these vendors actually sell?
Six different categories that buyers often conflate: ERP for orders and costing, MES for what is happening on the floor, scheduling, quality and compliance, PLM for drawings and revisions, and maintenance. Most rankings compare only ERP, which is why a system can score well and still leave your real problem untouched.
| Category | What it handles | What to know |
|---|---|---|
| ERP | Orders, inventory, purchasing, costing, the general ledger | The system of record. Everything else usually has to agree with it. |
| MES | What is happening on the floor right now, by machine and by job | Where ERP says what should happen, MES says what did. Many mid sized plants run neither and use a whiteboard. |
| Scheduling and planning | Sequencing jobs against capacity, materials and due dates | The function most often done in a spreadsheet beside the ERP, because the ERP's version was too rigid for how the plant actually books work. |
| Quality and compliance | Inspections, non conformances, certificates, traceability | Driven by what your customers audit. Automotive, aerospace and food each want something different. |
| PLM | Drawings, revisions, bills of material through design changes | Matters enormously in engineer to order, barely at all in high volume repetitive work. |
| Maintenance | Asset history, preventive schedules, spares | Usually the last to be bought and the first to pay for itself when downtime is expensive. |
The confusion costs real money. A plant whose actual problem is scheduling buys an ERP, because ERP is what the lists rank, and discovers eighteen months later that the scheduling module was never the strong part and the planner has quietly rebuilt the old spreadsheet. Work out which of these six rows is costing you hours before you read a single comparison, because the comparison is almost certainly about row one.
Which manufacturing software companies appear on most lists?
Acumatica appears on every list reviewed. Microsoft Dynamics 365 Business Central, SAP and Sage appear on most. Oracle NetSuite, Epicor Kinetic and Infor CloudSuite Industrial recur. The descriptions below are what the rankings consistently report rather than independent benchmarking, which nobody on this results page has done either.
| Vendor | How often listed | What the lists consistently say |
|---|---|---|
| Acumatica | Named on every list reviewed | Cloud, aimed at small and mid sized manufacturers. Its resource based licensing, which does not charge per user, is the feature lists mention most. |
| Microsoft Dynamics 365 Business Central | Named on four of five | Commonly recommended where the company already runs Microsoft. Lists note that complex production often needs add ons from partners rather than core functionality. |
| SAP, both S/4HANA and Business One | Named on four of five | S/4HANA for large discrete manufacturers, Business One positioned at smaller ones. Two very different products sharing a brand, which the lists do not always make clear. |
| Oracle NetSuite | Named on three of five | Consistently described as strong on financials and lighter on manufacturing depth, which matters more the more complex your production is. |
| Epicor Kinetic | Named on three of five | Described as manufacturing specific, with particular depth in mid market make to order and engineer to order work. |
| Infor CloudSuite Industrial, formerly SyteLine | Named on two of five | Positioned for discrete manufacturing. Worth noting that several of the lists ranking it are published by Infor implementation partners. |
| Sage, X3 and Intacct | Named on three of five | Two different products again. X3 is the manufacturing oriented one; Intacct is a financial system. |
| Plex | Named on some lists | Associated with plant floor intensive work, particularly automotive and electronics, where shop floor data capture matters as much as the ledger. |
| Others that recur | SYSPRO, IFS Cloud, QAD, DELMIAWorks, Odoo | Each appears on some lists and not others, which is itself informative about how these rankings are assembled. |
Two cautions about reading any table like this one, including this one. First, several of these brands cover more than one product with very different capabilities, and a ranking that says SAP without saying which SAP is not telling you anything actionable. Second, frequency of appearance measures marketing reach, not fit. A product that appears on every list may still be wrong for a thirty person process plant.
We have deliberately not scored or ranked these. Any score we assigned would be as unsupported as the ones we just criticised, and the honest position is that fit depends on variables that no ranking can know about your plant.
How do you choose between manufacturing software companies?
Start from what you make and how you make it. Repetitive, make to order, engineer to order and process manufacturing need different strengths, and a system that is excellent at one is usually adequate at best in the others. Match the production mode first, then compare the shortlist on the two or three functions that actually cost you hours.
| If your work is | Meaning | What the system has to be good at |
|---|---|---|
| Repetitive and high volume | The same things, made many times | Throughput, scheduling against capacity, and shop floor data capture. Deep costing by job matters less when every job is the same. |
| Make to order | Known products, built when ordered | Quoting, capacity planning and promise dates. The system has to tell a salesperson when something can ship without a trip to the floor. |
| Engineer to order | Designed and then built, each one different | Revision control, project costing and the link between the drawing and the bill of material. This is where PLM stops being optional. |
| Process | Mixed, batched, measured, rather than assembled | Formulation, batch records, yield and lot traceability. A discrete ERP forced onto process work is the most expensive mismatch in this table. |
| Mixed mode | More than one of the above under one roof | Honesty about which mode dominates, because most systems are genuinely good at one and adequate at the rest. |
The expensive mismatch in that table is the fourth row. Process manufacturing, where things are mixed, batched and measured rather than assembled from countable parts, breaks assumptions that discrete systems make everywhere. If you make paint, food, chemicals or anything with a formulation and a yield, say so in the first minute of every vendor call and watch what happens.
Then run the demo on your own data. Not the vendor's demo dataset. Take your three most awkward real jobs, the ones with the special pricing, the customer specific certificate and the part that gets re-engineered halfway through, and ask each vendor to walk those through the system. Most of what you need to know surfaces in that hour, and it is the single highest value thing you can do in a selection process.
What does manufacturing software cost?
The licence is the smaller number. Implementation commonly costs one to three times the first year of licensing, depending on how much configuration, data migration and integration the project needs. Comparisons that rank by subscription price are comparing the part of the cost you are least likely to be surprised by.
Three things drive the implementation figure, and none of them appear in a ranking. How far your processes sit from the system's assumptions, because every gap is either configuration, a bolt on product, or a change to how your plant works. How bad your data is, which nobody knows until someone looks at the item master and finds four spellings of the same supplier. And how many other systems have to agree with it, because each integration is a small project with its own testing.
There is a second cost nobody quotes: your own people. A selection and implementation consumes a serious amount of time from the people who understand how the plant actually runs, and those are the same people the plant cannot spare. Budget their hours honestly at the start, because the alternative is a project that stalls while everyone waits for the one person who knows how quoting works.
The number worth asking every vendor for is not the licence cost. It is the total first year cost including implementation, data migration, integration and training, and the typical range for a company of your size and complexity. A vendor who will not give a range is telling you something.
Does Dynamics GP end of support force a decision now?
Dynamics GP end of support sets a dated deadline rather than an immediate requirement. Microsoft ends support on 31 December 2029, with security patches continuing to 30 April 2031. That is time to run a proper selection, and time to lose if the decision keeps being deferred.
A large number of mid sized manufacturers are reading comparisons like this one because of that date rather than because anything is broken. The precise dates are worth getting right, because several pages ranking for manufacturing software terms still print an older one. Microsoft originally announced 30 September 2029 and moved it to 31 December 2029 in its January 2025 lifecycle update, so customers could close a full fiscal year of payroll and tax rather than cutting over mid quarter. Security updates continue until 30 April 2031. The source is Microsoft's own Dynamics GP documentation.
What that deadline does not do is choose a destination for you. Business Central is the obvious path from GP and it is not automatically the right one, particularly if your production is process rather than discrete, or if the reason you have eleven spreadsheets around GP is that GP never did those jobs in the first place. Those spreadsheets will not migrate to anything. They are the specification for what you actually need, and the single most useful preparation available to you is writing them down.
The practical first step is an inventory rather than a demo: every export, every spreadsheet, every report someone built, every integration attached to the current system. You can produce it without hiring anybody, and it makes every subsequent conversation cheaper and shorter.
What will you still do in spreadsheets after the new system goes live?
Usually five things: finite scheduling against real constraints, customer specific pricing, the quality records one big customer demands in their own format, downtime and OEE capture, and anything that touches a supplier or customer system. No vendor list ends here, which is why the second year surprises people.
| What stays manual | Why |
|---|---|
| Finite scheduling against real constraints | The ERP schedules infinitely or on rules too rigid for how the plant actually books work, so the real schedule lives in a spreadsheet a planner maintains. |
| Customer specific pricing and terms | Contract pricing, rebates and tiered terms that the standard price list cannot express, reconciled by hand each month. |
| Quality records a specific customer demands | Your biggest account wants a certificate in their format, with their fields, on their portal. No ERP ships with that. |
| Downtime and OEE | Recorded on paper at the machine and typed in later, if at all, which is why the numbers are always a week old and nobody fully trusts them. |
| Anything involving a supplier's system | Portals, EDI variants and the one customer who still sends a PDF. Somebody rekeys it. |
This is not a criticism of any product on the list above. A general system cannot encode how your plant quotes, sequences or certifies without becoming a custom system, and the vendors are right not to try. The mistake is on the buying side: treating the selection as the end of the project rather than as the point where you find out which gaps remain.
So plan for it. During selection, as each vendor demonstrates, write down every place someone says "you would handle that outside the system" or "most customers use a report for that". That list is your real second phase, and it is far cheaper to scope while you still have the vendor's attention than eighteen months later when the planner has quietly rebuilt the spreadsheet they had before.
Our own work sits in exactly that gap. We do not sell or implement any ERP, and we are not the right call while you are choosing one. We are the right call when the system is in and a planner is still maintaining a schedule in Excel because the module was too rigid, or when a customer wants a certificate in a format nothing produces. If that is where you are, the manufacturing software page describes how we approach it, and systems integration covers the case where two systems simply need to agree.
What is manufacturing ERP software?
Manufacturing ERP software is the system of record for orders, inventory, purchasing, production costing and the general ledger, extended with functions a general business ERP does not have: bills of material, routings, work orders and shop floor costing. It is what most rankings mean when they compare manufacturing software companies.
The distinction from general business ERP matters when you read a comparison. A general ERP knows you bought materials and sold a product. A manufacturing ERP knows the recipe or the assembly that turned one into the other, how long each step should take, which machine it ran on and what it therefore cost. That middle part, the bill of material and the routing, is the whole difference and it is where products vary most.
This is also why a strong financial system can be a weak manufacturing system. Several products that appear high on lists of top manufacturing software companies began as accounting platforms and grew manufacturing modules afterwards. They handle the ledger beautifully and get thinner as the production question gets harder, which is invisible in a feature matrix and obvious the first time you try to schedule a constrained resource.
The practical test is to ask how the system handles a job that changes after it is released: a quantity increase, a material substitution, a revision to the drawing mid build. Every vendor can demonstrate a clean order flowing through. The differences appear when reality interferes, and reality interferes constantly.
What goes wrong in an ERP selection?
Five mistakes account for most regretted purchases: scoring features nobody will use, accepting the vendor's demo instead of your own, deciding without the people whose work changes, comparing licence cost rather than total cost, and treating go live as the finish line rather than the midpoint.
| Mistake | What it looks like | What to do instead |
|---|---|---|
| Scoring features nobody will use | A matrix of three hundred requirements, most copied from a template, weighted equally. The two functions that actually cost you hours score the same as a report nobody will open. | Pick the five things that decide it and weight everything else at zero. |
| Letting the demo be the vendor's demo | A polished walkthrough of clean data in an idealised process, which tells you nothing about your plant. | Send three real awkward jobs in advance and make every vendor run those. |
| Deciding without the people who do the work | The selection committee is finance and IT. The planner and the quality manager see it after signature. | Put the two people whose day changes most in the demos, with a veto. |
| Comparing licence cost | Two quotes compared on subscription price, when implementation is the larger and more variable number. | Compare total first year cost including implementation, migration, integration and training. |
| Treating go live as the finish | Budget and attention stop at launch, exactly when the gaps start appearing in daily use. | Reserve budget for the first six months after go live. You will need it and it is cheaper then. |
The third row is the one that quietly decides whether the system is used as intended. A planner who first sees the software after the contract is signed will find the one thing it cannot do by Wednesday, and will rebuild their spreadsheet by Friday. Two years later the official schedule is in the ERP and the real one is still in Excel, which is the single most common state we find mid sized plants in.
The fifth row costs the most money. Attention and budget peak at go live and then stop, at precisely the moment when the people using the system daily start discovering what it does not do. Those discoveries are cheap to address in the first six months, while the implementation team still has context, and expensive afterwards, when everyone has moved on and the workarounds have hardened into habits.
What should a smaller manufacturer do differently?
Buy less, and buy later. Under about two hundred people the risk is not choosing the wrong product, it is choosing a product large enough that implementing it consumes the handful of people who keep the plant running. Start with the one function costing you the most hours and leave the rest alone.
Most rankings are written as though every reader has an IT department and a project manager. A hundred and twenty person plant usually has neither. It has a controller who also owns the ERP, a planner who is the only person who understands scheduling, and an owner who signs things. The constraint is those three people's attention, and no feature comparison accounts for it.
That changes three decisions.
Scope the first phase much smaller than the vendor proposes. A full implementation across finance, inventory, production and quality in one programme is how a small team gets overwhelmed and how a project slips a year. Take the function that costs the most hours now, implement that properly, and let the plant absorb it before starting the next. It is slower on the plan and faster in reality, for the same reason incremental modernisation beats a big bang.
Weight implementation support above features. At this size, who actually turns up and how well they know your industry matters more than a module comparison. Ask who will be on site, for how many days, and whether they have implemented in your specific production mode. A product that scores slightly lower with an implementer who has done thirty plants like yours beats the reverse every time.
Be realistic about what you will not use. Smaller manufacturers routinely buy capability for a future that does not arrive, paying for modules that stay switched off. If the multi plant, multi currency, advanced planning functionality is for a growth plan three years out, buy it in three years. Systems are easier to extend than to finish implementing.
There is one thing worth spending more on rather than less: getting the data clean before migration. Item masters, supplier records, bills of material and routings. A small team cannot absorb both a new system and the discovery that the data in it is wrong, and the clean up is the one task that is genuinely cheaper to do before go live than after.
And consider whether you need a full system at all this year. Some of what sends mid sized plants shopping is one specific pain: a schedule that lives in a spreadsheet, a quality certificate nobody can produce, downtime nobody can measure. Where the rest of the operation is working, solving that one problem directly is often a fraction of the cost and disruption of replacing the system of record, and it leaves the bigger decision available to you later with better information. That is not an argument against buying an ERP. It is an argument for being specific about what you are buying it to fix.
Where should you start this week?
Write the inventory before you book a demo. Every spreadsheet, export, report and integration attached to your current system, with who maintains it and roughly how long it takes each week. It costs nothing, you can do it internally, and it makes every conversation afterwards shorter and cheaper.
That document does four things at once. It tells you which of the six software categories your actual problem sits in, which is usually not the one you assumed. It gives every vendor a concrete specification instead of a wish list, so their demos address your plant rather than their showcase. It becomes the migration checklist later, because those spreadsheets are the work that no system migrates automatically. And the hours column tells you what the project is worth, which is the only honest basis for a budget.
Two weeks of counting is enough. Ask the planner, the controller, the quality manager and whoever handles customer portals to note what they open, what they copy and roughly how long it takes. The surprises are consistent: the spreadsheet costing the most is rarely the one anyone complains about, and the task everyone complains about is often fifteen minutes a week.
If the hours concentrate in one place, you have a specific problem with a specific solution, and it may not require replacing anything. If they are spread across ten places and all of them trace back to the system of record, you have a selection project and now you can run it properly. Either way you have spent nothing to find out, and you are no longer choosing from a ranked list written by someone with a product to sell.
What should you ask every vendor before signing?
Five questions: what the total first year cost is including implementation, which production mode the product is genuinely strongest in, what your three awkward jobs look like in the demo, what will still be handled outside the system, and who owns your data and how you export it.
What is the total first year cost, including implementation, migration, integration and training? Ask for a range for a company of your size and complexity. Compare that number across vendors rather than the subscription line.
Which production mode is this product strongest in? A good answer names one and is honest about the others. An answer that claims equal strength in discrete, process and engineer to order is a sales answer.
Can we see our three most awkward jobs in the demo? Send the real ones in advance. How a vendor handles the request tells you nearly as much as the demo does.
What will we still handle outside the system? Every honest implementer has a list. One who says nothing is either unfamiliar with your industry or not being straight with you, and you will find out which in year two.
Who owns the data, and how do we get it out? Ask for the export format and whether it includes the intermediate tables rather than just the finished records. A system you cannot export from completely is a system you cannot leave, and this answer belongs in the contract rather than in an email.
FAQ
Common questions
Which manufacturing software companies are most commonly recommended?
Acumatica appears on every list reviewed for this page. Microsoft Dynamics 365 Business Central, SAP and Sage appear on most of them, and Oracle NetSuite, Epicor Kinetic, Infor CloudSuite Industrial and Plex recur. Frequency of appearance reflects marketing reach rather than fit, so treat it as a starting shortlist rather than a ranking.
Why do manufacturing software rankings disagree with each other?
Because most are published by companies that sell or implement one of the systems being ranked. One list on this search places its own publisher first on a self reported hundred percent implementation success rate, and that publisher is an implementation partner for a vendor on the same list. Check who publishes any ranking before reading it.
What is the difference between ERP and MES in manufacturing?
ERP is the system of record for orders, inventory, purchasing and costing: what should happen. MES records what is actually happening on the floor, by machine and by job. Many mid sized plants run an ERP and no MES, and capture floor data on paper or a whiteboard instead.
How much does manufacturing ERP cost to implement?
The licence is the smaller number. Implementation commonly runs one to three times the first year of licensing, driven by how far your processes sit from the product's assumptions, how clean your data is, and how many other systems have to integrate. Ask every vendor for a total first year range rather than a subscription price.
How do I choose an ERP for my type of manufacturing?
Match the production mode before comparing features. Repetitive, make to order, engineer to order and process manufacturing need different strengths, and process manufacturing in particular breaks assumptions that discrete systems make throughout. Then run each demo on your own three most awkward jobs rather than the vendor's sample data.
When does Dynamics GP support end?
Microsoft ends Dynamics GP support on 31 December 2029, with security patches continuing until 30 April 2031. The date moved from 30 September 2029 in Microsoft's January 2025 lifecycle update so customers could close a full fiscal year. Several third party pages still print the older September date.
Will a new ERP replace all our spreadsheets?
No, and planning as though it will is the most common second year surprise. Finite scheduling, customer specific pricing, quality records in a customer's own format, downtime capture and anything touching a supplier's system usually stay manual. Write down every gap the vendors mention during demos; that list is your real second phase.
Does Voliom sell or implement ERP systems?
No. We do not sell, resell or implement any ERP, and we take no referral fees from any vendor. We build the software that sits around one, which means we are the wrong call during selection and the right call when the system is in and gaps remain.
Keep exploring
Related
- Manufacturing software developmentThe gap your ERP does not cover
- Systems integrationMaking existing systems agree
- Application modernizationWhen the system is the problem
- Custom software developmentWhen it has to be built
Let's talk
Tell us what you're building.
Get a free 30-minute strategy call. You'll leave with a clear plan, a realistic estimate and our honest opinion, whether or not you work with us.
- Email usmail@voliom.com