What are MVNOs and MVNEs?
A mobile virtual network operator (MVNO) sells mobile services using wholesale access to a host network. The mobile network operator (MNO) operates the radio access network; buying access lets the MVNO sell services without building that entire network. A mobile virtual network enabler (MVNE) supplies technical capabilities that help mobile brands operate. The division of responsibility varies: a branded reseller, a light MVNO and a full MVNO may own very different parts of the service. Establishing that division is the first step in deciding which systems the business needs.
What do you need to start an MVNO? You need a network access agreement and the technical arrangements to deliver the offer, plus the means to manage customers, plans, activation, usage, billing, payments and support. In a simple journey, a customer signs up, an account and plan are created, and a Subscriber Identity Module (SIM) identifies their subscription to the network. An eSIM uses a downloadable profile on a compatible embedded chip. The service is activated, calls and data generate usage records, prices are applied, and the resulting charges are billed and paid. This page explains the systems and decisions behind that journey.
MVNO management software links the commercial offer with the subscriber's service lifecycle. The operation needs customer accounts, product and plan records, SIM identities, activation processes, usage handling, billing, payments and customer care. Business Support Systems (BSS) manage the commercial side, including customers, plans, billing and payments. Operations Support Systems (OSS) deal with service delivery and operation. Agree which functions the network partner or enabler supplies and which your own systems must manage.
Subscriber management must retain the relationship between the customer, the mobile service and the current package. Contacts and communication history belong in the customer relationship management (CRM) record; service identifiers and lifecycle events explain what has happened to the subscription. One customer may have several lines, so a name or email address is not enough to identify the affected service.
Someone researching how to start an MVNO should agree who supplies SIMs, manages network requests, delivers usage records and resolves faults. Ask how responsibilities change if the offer expands or a supplier is replaced. The MVNO fundamentals guide explains the operating models, and the MVNE selection guide helps structure the technical and commercial questions before platform selection.
MVNO/MVNE provisioning: SIM, eSIM and number portability
Mobile provisioning turns an agreed subscription into a request for network service. Customer and package details must be associated with the correct physical SIM or eSIM identity. Activation then needs confirmation from the relevant provider. An order accepted by a back-office system and a subscription ready for use are distinct milestones.
For eSIM onboarding, establish the delivery and activation process supported by the selected partner. Staff need a way to identify the subscription and investigate an incomplete setup. Replacing a SIM or moving service between supported states should preserve the account relationship and the history of the request, rather than creating an unexplained new record.
Number portability adds another coordinated workflow. A customer retaining a mobile number needs the appropriate transfer details and a way to follow progress. For UK mobile transfers, a Porting Authorisation Code (PAC) is used when retaining a number; a Service Termination Authorisation Code (STAC) applies when switching without retaining it. Record requests, references and provider responses so staff can tell the difference between a submitted transfer and a completed one. Test a number transfer as part of launch preparation, not only a new-number activation.
Service changes also need defined ownership. Suspension, reactivation, replacement SIMs and data controls can have customer and commercial consequences. Decide who authorises an action, how the request is confirmed and who explains the outcome. Automating a request does not remove the need to investigate an unexpected response.
For example, a customer may contact support after a SIM swap because a service is not working as expected. The team needs the previous and current service identifiers, request history and package details to establish the next step. If the business also sells connected-device subscriptions, IoT connectivity services explains the different fleet and account-allocation requirements; these should not be assumed to match a consumer mobile offer.
MVNO billing software: usage rating, invoices and payments
MVNO billing combines recurring subscriptions with chargeable voice, messaging and data usage. Supplier usage records are commonly referred to as call detail records (CDRs), even when the activity includes data or messaging. Mediation prepares records for processing, rating applies the prices, known as tariffs, and eligible allowances, and billing combines the resulting charges with account subscriptions.
This sequence matters when investigating an invoice. A missing usage file, an incorrect service mapping and a wrong tariff are different problems. Staff should be able to trace a disputed amount back to the relevant records and package. The CDR processing guide and telecom rating guide explain those stages in more detail.
Before launching a mobile plan, test included usage, out-of-bundle activity and any applicable destination or roaming rules. Agree how late records and plan changes are reviewed. Confirm whether the business needs postpaid invoicing, real-time prepaid charging or both: an invoice-based rating process is not automatically an online balance-control system.
Payment handling requires a defined method, collection result and reconciliation process. Match receipts to customer balances, assign failed payments for follow-up and distinguish a collection problem from a disputed usage charge. Customer care needs access to the evidence behind both the service and the bill, along with earlier communications about the issue.
For upgrades, downgrades and cancellations, agree the effective service and charging changes and retain the previous package history. Customer care needs to know what was requested, what the provider confirmed and which terms apply to the next bill.
When choosing an MVNO platform, demonstrate an activation, a number transfer, a usage query and an unpaid invoice. Review data migration, access responsibilities and the procedure for missing supplier records. Reporting should distinguish subscribers, usage processed, charges billed and payments received so the team can identify where work or revenue collection is falling behind.
How Axiom supports MVNO and MVNE workflows
Axiom maintains subscriber accounts, service and package records, communications and financial information in the same operational context. Configured usage processing and rating link relevant consumption to invoicing, alongside recurring subscriptions. Teams can review the customer and service detail behind a charge, then use recorded payments and balances to follow up the account. Client-scoped administration supports work across multiple client accounts, with the commercial scope of an enabling deployment agreed separately.
The configured mobile integration supports physical SIM and eSIM onboarding and actions including activation, SIM swaps, suspension, reactivation and data barring. Supported portability workflows include PAC and STAC retrieval and port-in requests. Available actions depend on the supplier and subscribed product. These functions should be evaluated against the actual carrier arrangement; they do not establish a complete mobile core or a real-time prepaid charging service.
For a subscriber enquiry after a SIM replacement, staff can review service identifiers, package information and provider responses alongside the account history. The usage and invoice records supply the charging context. That combination helps the team distinguish an issue with the service request from a question about the bill, while keeping the customer conversation associated with the relevant account.
Operational Intelligence adds recorded mobile events, usage-related notifications, account summaries and communication history to help prioritise customer attention. Staff still use the underlying provider and billing records to investigate the outcome. A useful demo can follow a proposed plan through activation, sample usage, invoicing and a customer enquiry, while also checking who owns carrier exceptions and which MVNO or MVNE responsibilities remain with other partners.