Legacy software complexity may be your most expensive cost
Ad
Why structural OPEX reduction for fuel retailers and mobility providers starts with architecture and not with software licences.
A customer calls, a fuel card need to be blocked, new drivers added and an invoice is incorrect. For the customer, it is a single request. Internally, however, it may require employees to open multiple systems, re-enter data, trace transactions and involve several suppliers just to explain a single discrepancy.
The customer experiences delays. Management mainly sees separate software licences, maintenance contracts and staffing costs. But the true cost of complexity rarely appears as a single line in the budget.
Hidden OPEX is found in your cost-to-serve
Fuel retailers and mobility providers are expected to offer an increasing number of services: fuel, EV charging, parking, payments, loyalty and fleet services. At the same time, margins are under pressure.
The key question is therefore not only: What does our software cost? But more importantly: What does it cost us to serve one customer, process one transaction correctly and launch one new service?
That is your cost-to-serve. And it is largely determined by the architecture behind your operations.
Most IT landscapes have been built up system by system over the years. One solution for cards, another for CRM, billing, payments, loyalty, charging and parking. Each decision made sense on its own. Together, however, they often create a landscape with duplicate customer data, point-to-point integrations, manual checks and multiple suppliers. Technology complexity becomes operational complexity.
Where the costs arise every day
This becomes particularly visible in processes that occur continuously.
Take pricing. A price change may affect the forecourt controller, price sign, card pricing, discount agreements and invoicing. If these components do not use the same data and rules, employees need to check afterwards whether the correct price has been applied everywhere.
The same applies to inventory management. Delivered volumes, tank measurements and sales volumes often come from different sources. If this data is not automatically brought together, wetstock management becomes a manual checking process rather than a daily monitoring tool. For operators, this has a direct impact on settlement. The more data sources and corrections are required, the longer it takes before figures are final and can be verified.
Then there is clearing. With cross-acceptance, transactions from different networks, tariffs, commissions and billing flows come together. On the purchasing side, supplier invoices also need to be matched against actual deliveries. If transactions, prices and invoices are stored in different systems, reconciliation becomes manual work.
The risk is not only the time involved. An incorrect pricing rule, a transaction that is not invoiced or a discrepancy in a supplier invoice may seem small. At scale, it affects your margin.
You pay for complexity twice
There is another cost as well. Employees carrying out these checks, corrections and administrative tasks cannot spend that time elsewhere.
One Moveyou customer, for example, indicated that clearing supplier invoices and managing customers on a daily basis across different systems requires so much capacity that employees have less time to approach prospects and further develop existing customer relationships.
This means an organisation pays for complexity twice: in operational hours and in commercial capacity.
Automation is therefore not simply about reducing FTEs. It is primarily about enabling the same people to spend more time on higher-value work.
Complexity also makes every change more expensive
Legacy complexity does not only increase the cost of running today's operation. It also increases the cost of changing it.
Adding EV charging, entering a new market, introducing a new card proposition or connecting another mobility service should be a commercial decision. But when customer data, transactions, pricing and billing are spread across different systems, each change can quickly become another integration project. The result is not only higher OPEX, but also a slower time-to-market.
OPEX reduction starts with architecture
The biggest savings do not necessarily come from making ten individual systems slightly cheaper. The greater opportunity lies in eliminating systems, integrations and manual processes that are no longer needed. That requires a shared architecture.
Not one closed system in which everything must be placed, but a foundation that allows customer data, transactions, pricing, invoicing, cards, payments and mobility services to use the same data, workflows and business rules.
The value is not in having one large system. The value is in having one connected model.
Simplify without replacing everything
Consolidation does not automatically mean that your entire existing landscape needs to be replaced. Keep what works. Connect what's needed.
An existing forecourt controller, ERP system, payment provider or charging platform can remain in place if it works well. A modular, API-first platform can instead provide the connecting layer, allowing functionality to be integrated or replaced step by step. This reduces migration risks and prevents simplification itself from becoming another multi-year IT project.
How complex is your operation really?
A useful way to assess hidden OPEX is to look beyond software licences and ask:
- How many systems does an employee need to answer one customer question?
- How many manual checks are required before transactions can be invoiced?
- How much reconciliation takes place between transactions, prices and supplier invoices?
- How many suppliers need to be involved when something changes?
- How long does it take to introduce a new service, proposition or market?
- How much employee capacity is spent handling exceptions instead of customers and growth?
From an IT issue to profitability
Moveyou supports mobility issuers with a single modular, API-first environment for customer management, onboarding, card management, transactions, pricing, payments, invoicing, clearing, loyalty, fuel, EV charging and parking. Existing systems can remain connected while processes are simplified step by step.
The relevant question for management is therefore not only how much the current IT landscape costs. But: How much capacity, margin and room for growth are currently being lost because of the complexity surrounding it?
You have limited influence over fuel prices, geopolitics and market volatility. But you can influence the amount of internal complexity required to serve one customer and process one transaction correctly.
That is why a fragmented technology landscape is not just an IT problem. It is an OPEX problem. And ultimately, a profitability problem.
Reducing OPEX is not about cutting costs everywhere. It is about removing unnecessary complexity from your daily operation.
By bringing systems, integrations and processes together in one platform, you create a technology landscape that is easier to manage, easier to scale and better prepared for what comes next.
Want to see how Moveyou can help simplify your mobility operation? Discover our platform and solutions at moveyou.com.
