You're not looking for a new ERP because you want to. Something has changed. Maybe your software isn't keeping up, processes have become harder than they should be, or you're losing time and money to inefficiencies you know can be fixed.
Perhaps Epicor BisTrack's move to cloud has prompted you to look at your options. Maybe you're using ECI Spruce, DMSi Agility or another ERP and questioning whether the software, service or vendor still fits where you're heading.
Before you start comparing products and vendors, ask yourself these 12 questions. Think of them as your reality check. They’ll help you decide whether change is justified, define what better looks like and know what to look for in your next ERP and the company behind it.
12 Questions to Ask:
1. What's making you question your ERP in the first place?
Something brought you here. Maybe it's the phasing out of Epicor’s BisTrack on-premises software, poor support, too many spreadsheets and workarounds, or simply the feeling that your ERP hasn't kept pace with your business.
Before you start looking at alternatives, document what's bothering you. Include the big issues, but don't overlook the everyday frustrations you've learned to live with: reports that take too long, manual processes, missing integrations, information that's difficult to access or tasks that are harder than they should be.
Seeing everything in one place can be revealing. What felt like a handful of unrelated annoyances may turn out to be a pattern that's been building for years.
It also gives you something concrete to share with other stakeholders. Instead of debating whether your ERP software is ‘good enough’, you can agree on what's working, what isn't and where change could make the biggest difference.
"We knew that continuing with our outdated, clunky ERP system would keep us at a significant disadvantage."
- Michelle Lowe, Director of Business Systems, Christmas Lumber.
For Christmas Lumber, that realization was enough to start looking at what a more modern ERP could offer.
Start your ERP search with the problems you need to solve, not a list of software features.
2. What is it really costing you?
Now put some numbers against the frustrations you've documented. Not just what you pay for your ERP, but what it costs you to work around it.
Add up annual license and maintenance fees, additional software subscriptions, integrations and support. Then estimate the labor cost of managing multiple systems, duplicate entry, manual reporting, administration and other processes that could be automated. It doesn't have to be exact. A sensible estimate will give you somewhere to start.
Then consider the costs that are harder to put a number on: delayed decisions, missed sales opportunities, margin leakage, poor visibility and time spent searching for information instead of acting on it.
In conversations with our U.S. sales team, manual processes repeatedly come up as a significant hidden labor cost. One example involved thousands of purchase orders being entered manually each month by several employees, work that could potentially be reduced through automation and better system integration.
Get as much of it as you can down in black and white. You need to know the cost of staying where you are before you can properly judge the cost of changing.
3. How did you get here?
Look back at the frustrations you've documented. How many processes started as a workaround for something your ERP couldn't do?
A spreadsheet gets added. A manual process fills a gap. Another system gets brought in. It solves the immediate problem, so you keep doing it. A few years later, nobody questions why.
But your business has changed. Your customers, suppliers and the wider LBM market have changed too. So, ask yourself: are your processes still the best way to run your business, or simply the way you've learned to work around your software?
In a recent episode of the Construction Leadership Podcast with Bradley Hartmann, GenetiQ CEO Justin Lawless talked about how ERP projects can reveal the gap between how a business thinks work gets done and how it actually happens day to day. That’s when hidden workarounds, manual steps and process dependencies often come to light.
Whatever led to those workarounds, don't assume they need to follow you into your next ERP. Modern systems can give you far more flexibility to shape screens, workflows, processes and information around how you want to work.
Don't carry old workarounds into a new ERP just because ‘that's how we've always done it.’
4. What does better look like?
Now you've worked out what isn't working and how much it is costing you, define what you want instead.
Create two lists: what you must have and what you'd love to have. Involve the people who use your ERP every day and ask what would save them time, give them better information or make their jobs easier.
Don't limit that list to features. Think about the outcomes you want: fewer manual processes, everything you reasonably can in one system, stronger integrations, faster access to information, better visibility, more flexibility and support you can rely on.
For RLH Inc., the benefits of automating manual processes go beyond saving time.
"That means faster, more accurate service for our customers, and it frees our team to spend more time on sales and growing the business instead of on routine work." - Ellen Harmon, CEO & Co-Owner, RLH Inc.
Then look further ahead. If you're choosing an ERP you could be using for the next decade, what might you need that you don't need today? Think about growth, new locations or services, changing customer expectations, automation, AI and how you may want to use your data differently.
If you're moving on from Epicor BisTrack, ECI Spruce or DMSi Agility, use that list to judge every alternative you explore, including newer LBM ERP platforms. Keep the evaluation focused on what you need, not what a vendor wants to show you.
Define what better looks like before a vendor shows you their version of it.
5. How much control will you have over your ERP?
You’re choosing an ERP to support your business for years, so ask what happens when you want to change something once you’re live.
Can you change a screen, add a field, build an approval workflow or adapt a process yourself, without needing SQL or other specialist technical skills? Or will you need to raise a support ticket, wait for the vendor and potentially pay for consultancy or development every time you want to make a small change?
This matters because your business won't stand still. You'll add products, services, locations and new ways of working, and your ERP needs to keep up without every change becoming another project.
Ask vendors to show you what you can configure yourself, what requires their involvement and what happens when you want to make those changes across multiple locations.
“I love that we can set up our own approval process to ensure business processes are adhered to, giving us full control and visibility.” - Jack Reid, Stockgap
You're not just buying functionality. Find out how much freedom you'll have to shape your ERP once it's yours.
6. Can you see what you need to see?
Having plenty of data isn't much use if getting a simple answer takes half a day (or longer!).
Think about the questions you regularly ask. What's happening to your margins? Which customers are buying less? Which product categories could they be buying elsewhere? How are your locations performing? Where is inventory tying up cash?
How quickly can you get those answers today?
If you're waiting for weekly reports, exporting data into spreadsheets or relying on someone else to pull the numbers together, expect more from your next ERP. Look for live business metrics you can drill into and act on while the information still matters.
Chase Hackner, our U.S. LBM Solutions Advisor, sees that demand for quicker answers first-hand:
“A lot of lumberyards are still relying on a report every Monday morning. That’s static data. What they really want is a quick answer now.”
GenetiQ is designed to give you that kind of visibility, helping you get to the answers you need without waiting for the next report.
So write down the business questions you need answered every day, week and month, then ask each vendor to show you exactly how you'd find the answers in their system.
‘Yes, we can report on that’ isn't the same as showing you how quickly you can get the answer.
7. What should your ERP do as standard?
Decide which capabilities you expect to be part of your core ERP, which might come as optional modules and which are better handled by separate specialist software.
Look particularly closely at areas such as financials, reporting, analytics, rebate management and other key requirements, where different ERP vendors may provide the functionality in very different ways.
If they rely on optional modules, partner applications or integrations, understand what that means for you - additional licenses, other vendors, support arrangements and how your data moves between systems.
That doesn't mean every specialist system should disappear. If an application does a particular job brilliantly and adds real value, keep it. The important thing is that everything works together cleanly, so you can still rely on one source of truth across the business.
Don’t assume two ERP systems that tick the same boxes are built the same way. A capability such as financials or rebate management might be native in one ERP, delivered through a closely integrated partner application in another, or sit in a separate product but connected to the ERP.
All these approaches are valid options. What matters is understanding what sits behind each one and how it could affect your day-to-day operations.
For each capability, ask who provides and supports it, what it costs, how upgrades are handled and whether it relies on an integration to keep the data in sync.
Know how each part of the solution is provided and how it works together, not just whether the feature appears on the list.
8. Does the ERP offer an open REST API?
If you want to keep specialist applications that already work well, or add new ones later, an open REST API gives you a recognized way to connect them with your ERP and exchange data between systems.
Not every ERP vendor offers an open REST API, and the level of access can vary between systems.
Ask potential vendors what API access is available, what information can move between systems, how integrations are typically handled, what support is available and what costs are involved.
If you want the freedom to add specialist technology around your ERP, make sure it gives you a practical way to connect it.
9. Are you buying yesterday's ERP or tomorrow's?
When you’ve been using the same ERP for years, it’s easy to miss how quickly the market has moved on and how much more choice you now have.
But don’t mistake a modern-looking browser interface for modern technology underneath. Some ERP products have added newer browser experiences while much of the underlying platform is still based on older architecture. That may not be obvious in a demo, so ask what the system is built on, whether it was built for the cloud or adapted for it, and how flexible the platform will be as your needs change.
Then look beyond what you’re being shown today. Ask where the vendor is investing, how regularly the platform is updated and what’s on the roadmap. Ask how they’re approaching AI too, but don’t be distracted by the label. What will it genuinely help you do better, faster or with less effort?
You’re likely to live with this decision for years, so don’t just assess what the software can do now.
"GenetiQ’s evolution positions us years ahead of competitors still operating with stagecoach-era systems." - Michelle Lowe, Director of Business Systems, Christmas Lumber.
Make sure you understand both the technology you’re buying today and where the product is heading next.
10. What happens when you need your ERP vendor?
Once you start talking to vendors, pay attention to how the relationship feels from the very first conversation, not just what you see in the demo.
Do they listen properly? Do they ask enough questions to understand your business? Do they challenge you when they need to? Do you feel like they’re trying to find the right fit, or simply move you through a sales process?
That early experience matters because it often gives you a glimpse of what working together will be like later.
"I have worked with other ERP software implementations in the past, but I have never worked with a more dedicated and effective support team. The amount of support is vast and if you need an expert in a certain module, they are not too far out of reach." - Michael Thompson, General Manager, White's Lumber & Supply Co.
Look beyond the sales process too. Who will support you once you’re live? Do they understand LBM and the way your business operates? How easy is it to speak to someone? What happens when an issue needs escalating? And when you raise an issue or suggest an improvement, is there a clear route to the people who can act on it?
Speak to customers too. Ask what support is like when things haven’t gone to plan, not just when everything is working well.
Don’t just evaluate how a vendor sells to you. Pay attention to how they make you feel, how well they understand you and how they’ll work with you once you’re a customer.
11. Is the thought of implementation holding you back?
Even when you know your current ERP isn’t right anymore, the thought of replacing it can be enough to make you put the decision off.
There’s data to move, processes to review, people to involve, training to plan and a business to keep running at the same time. It can feel easier to stay with what you know, even when you know it’s costing you.
Speaking with Bradley Hartmann on the Construction Leadership Podcast, GenetiQ CEO Justin Lawless described ERP change as much more than a technology project:
“Technology is at the core of it, but it’s a full business change.”
That’s why it helps to understand what a move would really involve rather than letting the unknown make the decision for you. Ask potential vendors how they approach implementation, what they would need from you, who should be involved, how training and data migration are handled and what support you’ll have through go-live and beyond.
Speak to customers who have already made the move too. Ask what was harder than expected, what made the process easier and what they would do differently.
Then go back to Question 2 (What is it really costing you?).
Changing ERP takes effort. But so does continuing to work around a system that no longer fits your business and keeps costing you time or money.
12. Are you comparing the market, or just following the obvious path?
Once you’ve worked through these questions, you should have a much clearer picture of what needs to change and what better looks like.
Don't limit your research to the vendors or products you've known for years. If Epicor, ECI or DMSi are already on your radar, include them, but don't stop there. Look at newer LBM ERP providers too, then measure every option against the same requirements you've documented.
Your current vendor should absolutely be part of that comparison. But if moving to their newer platform still means data migration, retraining, process changes and disruption, give it the same scrutiny you’d give a completely different ERP.
Look at the bigger picture. Which option solves more of the problems you started with? Which gives you the right mix of LBM functionality, modern technology, flexibility, visibility and support? And which vendor leaves you feeling informed, reassured and confident about the move rather than pressured or overwhelmed?
If you’re going through the pain of change anyway, make sure the destination is worth it.
Put GenetiQ through the same test.
You've spent this guide asking questions of your current ERP and working out what you need from your next one. Now put GenetiQ to the test. Bring the awkward questions too. We’re happy to dig into the difficult stuff.
Ask us what's built in and what's integrated. Ask what you can change yourself. Ask us to show you how you'll get the numbers you need, how GenetiQ works with the specialist technology you want to keep and what implementation will really involve.
Talk to us about what matters to you. Then make us prove it.
FAQs:
How do you know when it’s time to replace your ERP?
If you’re spending more time working around your ERP than working with it, that’s a strong sign something needs to change. Maybe spreadsheets and manual processes have become normal, getting answers takes too long, support is frustrating or the system simply isn’t keeping pace with where your business is going. One issue on its own may not justify a move, but when they start adding up, it’s worth looking at your options.
What should you look for in an LBM ERP system?
There isn’t one fixed list but be clear about the capabilities you expect to sit at the heart of your ERP. Financials, reporting, analytics, rebate management and other key LBM requirements may be built in, supplied as optional modules or provided through partner applications and integrations. Ask what is included, what costs extra, who supports each part and how everything works together. A feature appearing on the list doesn’t necessarily tell you what you’re actually buying.
What should an ERP include as standard?
Core capabilities such as financials, CRM, reporting, analytics and essential LBM processes are worth assessing carefully. Ask vendors what is native to the ERP, what comes from integrated third-party products and what will cost extra.
What should you consider when looking for an Epicor, ECI or DMSi alternative?
Start with the problems you need to solve rather than comparing feature lists. Document your current frustrations, costs, must-haves, integrations and future requirements, then evaluate each ERP against the same criteria. Include established products and newer LBM ERP platforms in your research. And if you can, visit a customer using the system you’re considering. A demo shows you what the software can do. A customer can tell you what it’s like to live with the software and the vendor every day.
Should you stay with your existing ERP vendor when moving to a new system?
Your existing vendor should be considered, but don’t assume staying with them will automatically mean an easier move. A new platform may still involve data migration, retraining, process changes and implementation work, so assess it with the same scrutiny you would give any other ERP.
And don’t expect any new ERP to solve every single problem. You may have to compromise in some areas, while gaining capabilities, flexibility or opportunities you didn’t have before. The question is whether what you gain outweighs what you give up, and whether you have confidence in both the software and the people you’ll be working with for years to come.

