A wholesale rate card can make an MVNO business case look compelling in a spreadsheet and unworkable six months after launch. This MVNO wholesale agreement guide focuses on the clauses that determine whether the brand can control its customers, protect margin and change course when market conditions move.
The agreement is not simply a procurement document between an MVNO and a host MNO, or between an MVNO and MVNE. It is the operating constitution of the business. It defines who owns the subscriber relationship, what happens when a port fails, how usage is measured, which party carries regulatory exposure and how much freedom remains when the original proposition needs to evolve.
Start with the operating perimeter, not the rate card
Founders often begin negotiations by asking for the best voice, SMS and data rates. That is understandable, but rates have little meaning until the operating model is clear. A light MVNO using an MVNE for BSS, CRM, provisioning and customer care will need a very different agreement from a thick MVNO operating its own core network functions and policy controls.
Set out the functional boundary in practical terms. Who provisions SIMs and eSIM profiles? Who manages the HLR/HSS or subscriber data management layer? Who controls the P-GW, UPF, IMS and roaming configuration where relevant? Who investigates charging disputes? These decisions shape cost, launch speed, customer experience and accountability.
The host MNO may insist on standardised interfaces and processes, particularly where the MVNO is small or the host has a mature wholesale portfolio. That is not automatically a problem. Standardisation can reduce implementation risk. The issue is whether the standard model supports the differentiation on which the MVNO business case depends.
Customer ownership must be explicit
An MVNO can market under its own brand yet still have limited control over the customer relationship. The agreement should make clear that the MVNO owns customer acquisition, billing communication, consent management and retention activity, subject to regulatory requirements. It should also define what data the host or MVNE may access, process and use.
Customer ownership matters most when things go wrong. If a subscriber disputes a charge, loses service or requests a PAC, the customer should not be passed between brands. The contract needs a defined responsibility model, including escalation routes, contact centre obligations and response times.
It also matters at exit. If the partnership ends, the MVNO must be able to retain its subscriber base, port numbers where permitted and extract the data required to continue service with another provider. A customer base that cannot be migrated is not an asset the MVNO fully controls.
MVNO wholesale agreement guide: commercial terms that matter
Wholesale pricing should be evaluated as a system, not as three unit rates for minutes, texts and gigabytes. The relevant question is whether the complete commercial structure works at the expected mix of usage, subscriber tenure and scale.
Usage charges may be measured from network records that differ from the MVNO’s retail billing records. The agreement must specify the authoritative source, rounding rules, rating windows, treatment of partial sessions and the process for challenging records. A minor discrepancy per session can become material across a large database.
Minimum revenue commitments deserve particular attention. They can secure better rates, but they transfer volume risk to the MVNO. A commitment linked to total wholesale spend may be more manageable than one based on active SIMs or data volume, especially for propositions with seasonal usage such as travel, events or education. The contract should state whether unused commitment can roll forward, whether it can be offset against onboarding fees and what happens when a host-side service issue suppresses usage.
Marketing support, device subsidies, SIM logistics, eSIM enablement, roaming, number porting and fraud controls can all sit outside the headline rate card. Ask for a complete schedule of one-off, recurring and pass-through charges. This is where apparently attractive wholesale offers commonly lose their appeal.
Price review provisions are equally important. A host will seek protection against rising costs and regulatory changes. The MVNO needs protection against arbitrary price increases after it has built a customer base around a retail price point. Define review triggers, notice periods, evidence requirements and a right to terminate or renegotiate where a change materially damages the business case.
Service levels are a commercial issue
A generic availability SLA is not enough. A 99.9 per cent figure may sound acceptable, yet it says little about the services that affect an MVNO’s daily operation. Provisioning failures, delayed number ports, rejected top-ups, rating faults and eSIM download errors can create more customer damage than a short network interruption.
The agreement should distinguish between the radio network, wholesale platform, API layer, billing feeds and operational support. Each has different failure modes and different owners. Define incident severity, acknowledgement times, restoration targets, communications obligations and root-cause reporting. Service credits have value, but prompt remediation and a credible escalation path matter more.
For an MVNO using a cloud MVNE, the interface commitment should be tested before signature. API documentation, sandbox access, change-notification periods and version control are operational necessities, not technical decoration. If the MVNO cannot integrate its CRM, digital onboarding flow or VAS platform reliably, it cannot deliver the proposition it has sold.
Keep data, compliance and fraud responsibilities aligned
Data protection schedules are often treated as legal boilerplate. They should instead reflect the real movement of personal data, call detail records, location-related information and payment data between parties. Identify controller and processor roles, permitted purposes, retention periods, security measures, breach notification duties and international transfer arrangements.
The same discipline applies to regulatory obligations. Depending on the market, obligations may cover emergency calling, lawful intercept, KYC, consumer protection, number portability, complaints handling, accessibility and tax. The host may provide core network capability, but the retail brand cannot assume that responsibility has disappeared. The agreement should allocate each obligation and specify the evidence each party will provide for audits or regulator enquiries.
Fraud is another area where vague drafting is expensive. Clarify who monitors unusual international traffic, subscription fraud, premium-rate exposure, SIM farms and roaming abuse. Set financial caps where possible and define the notification threshold. An MVNO should not discover after the event that a host’s fraud tool was informative rather than preventative.
Build change and exit rights before launch
The first agreement will not survive unchanged. New eSIM channels, 5G access, enterprise APNs, IoT offers, roaming destinations and VAS partners will create change requests. A workable contract has a transparent change-control process with estimated costs, delivery dates, acceptance tests and a route to challenge unreasonable delays.
Term length should reflect the investment on both sides, but long commitments need counterweights. Seek break rights for persistent SLA failure, material price changes, regulatory barriers, repeated security incidents and failure to deliver agreed roadmap items. If the host or MVNE is acquired by a direct competitor, the MVNO should have a clear option to reassess the relationship.
Exit planning is not pessimism. It is commercial hygiene. Agree the format, timing and cost of data extraction; number porting support; treatment of stock and eSIM inventory; transition assistance; and continued service during migration. Test whether the migration provisions are genuinely executable, not merely a promise to cooperate reasonably.
Negotiate in the order the business will operate
A disciplined negotiation starts with the proposition and target segment, then maps the operating model, customer journey and technical dependencies. Only then should the parties model economics across realistic scenarios: low adoption, high data consumption, delayed launch, seasonal peaks and a major customer-care event.
The most productive discussions are usually held with commercial, operations, technology, finance and legal stakeholders in the same room. Wholesale teams can agree a rate while implementation teams know that a requested capability is not available. Surface that conflict early. A signed agreement that depends on unpriced development work is not a launch plan.
The right wholesale partner does not have to offer every capability on day one. It does need to be candid about what is standard, what is chargeable and what will remain unavailable. That clarity gives an MVNO the chance to simplify its proposition before complexity becomes contractual debt.
Treat the agreement as a design test for the MVNO you intend to run. If customer ownership, operational accountability and exit rights cannot be explained plainly to the board, the commercial model is not ready to carry the brand into market.
