Many B2B executives believe legacy applications and disjointed platforms are bogging down their ecommerce and electronic growth.
Some 54 percent of B2B leaders surveyed stated their company’s technology stack was”holding them back from their electronic agility targets” and 59 percent thought that legacy applications was the”root cause” of the company’s technology issues, based on an Episerver poll of 700 business-to-business decision-makers.
See our products:
Many producers and distributors acquired enterprise resource planning applications or comparable systems decades ago. They made significant investments for servers and”business” software licenses. At the moment, these expensive systems provided a enormous improvement in productivity.
However, the costs associated with purchasing, upgrading, and replacing these ancient solutions made some companies reluctant to buy up-to-date applications and platforms. The end result is that some B2B businesses are relying on legacy systems which aren’t capable of supplying the contemporary B2B ecommerce encounter professional buyers seek.
There’s an array of issues with older, outdated B2B program. But four categories could explain all of them.
- Cost. Many legacy systems are proprietary, requiring expensive license and support agreements. It isn’t unheard of for a company to spend a few hundred million dollars for new modules or features that would otherwise cost a couple million dollars to develop on a contemporary and open application pile.
- Safety. Aged, antiquated systems may be less protected as hackers identify unpatched vulnerabilities. Moreover, legacy systems are often not maintained.
- Capabilities. Legacy systems often limit a B2B business’s ability to bring the features and capabilities to support a strong ecommerce experience. By way of instance, old merchandise management solutions frequently don’t have any concept of product groups. Therefore a manufacturer or distributor can’t afford, say, the identical style of jeans across multiple dimensions.
- Productivity. Outdated software could also hurt growth. No matter how great some workers become at working with or around antiquated applications, there’s still a cost in time, labour, and overall inefficiencies.
By way of instance, a multichannel series in the northwestern United States employed a heritage, text-based ERP. One of the provider’s longstanding workers was a master in the system. Having nearly twenty years of experience, she could string together keyboard shortcuts — sometimes using six or seven in a row — to reach a specific screen or finish a repetitive job. As good as she was, new workers were clueless and might take weeks to train.
All these classes — costs, safety, capabilities, and productivity — may interfere with a B2B company’s ability to give a robust digital-buying experience.
This is unacceptable. Professional buyers increasingly assess their suppliers based in part on the purchasing experience and the efficacy of buying (i.e., ecommerce).
Manufacturers and distributors can attack legacy applications in many of ways. However there are two common approaches.
Wrap the old applications. A legacy system could be replaced slowly with what some in the software industry predict the strangler pattern.
Typically this involves putting a facade or wrapper round the heritage system which enables a new solution to access its own data and take advantage of its business logic.
For instance, a business may use GraphQL (a data query language) to make an API that accesses a legacy accounting solution. The GraphQL API could then interact with client portals, the ecommerce site, and systems from external accountants.
In the beginning, this GraphQL wrapper might trust the legacy accounting applications completely. But over time the company could replace the accounts-receivable module with something contemporary. The users — who’d now obtain their data via an interface on the GraphQL API — see no change, but a bit of the underlying legacy system was replaced.
One-by-one each remaining module or service is upgraded.
Update systems at the same time. The patient and slow strangulation method described above does not work for every organization. Sometimes it is worth it to pull the Band-Aid off completely, all at one time.
In this approach, the business will often target a particular system. By way of instance, imagine your B2B business desires a client accounting portal as part of their business’s ecommerce platform.
Your existing accounting software will not do the trick, so you start to work with a new system, possibly an Acumatica module. You implement the new system in parallel with the legacy system. For a little while, your company might need to enter bills twice. Nevertheless, the double entrance allows time to check the new system and train your accounting team.
Once everyone is comfortable, make the change.