SGP.32 Turns African Enterprise Fleets Into MVNO Candidates

GSMA Intelligence counts roughly four billion cellular IoT connections in the field today, rising to six billion by 2030, with eSIM at 37% and iSIM at 34% of that base by decade's end. That is the number African enterprise buyers should be staring at this week.

Because a specification quietly published by the GSMA, SGP.32, has changed what a fleet owner can do with a SIM. Simplex Wireless has been arguing across a run of August 2026 posts, including one titled "The eIM Is the First Enterprise System eSIM Has Ever Had," that SGP.32 and its companion eIM function are the first enterprise-grade control system for eSIM at scale. Treat the vendor framing with the caution it deserves. The underlying shift is real.

What SGP.32 Actually Changes For A Fleet Owner

Until now, an enterprise with tens of thousands of connected vehicles, meters, trackers or point-of-sale terminals had two bad choices. Buy connectivity from a mobile operator and inherit that operator's coverage, pricing and roadmap for the life of the device. Or negotiate multi-operator deals and carry the integration cost on every SKU.

SGP.32 rewrites that trade. The specification lets a central platform, the eIM, provision and reprovision SIM profiles across a fleet remotely, without touching the device and without the device maker sitting in the middle. One team, one dashboard, millions of endpoints. The host network becomes a variable the enterprise controls, not a vendor that controls the enterprise.

For a logistics operator running trackers across three countries, that is the difference between a procurement cycle measured in quarters and one measured in days. For a utility rolling out smart meters, it is the difference between locking in a decade of wholesale rates at launch and renegotiating them as the estate grows.

Why This Matters More In Africa Than Anywhere Else

The African context sharpens the argument. Mobile-first economies have built their commercial infrastructure on cellular in a way European and North American markets never had to. Vehicle tracking, agri-monitoring, prepaid electricity, informal retail point-of-sale, community water metering. All of it rides on SIMs, and almost all of it currently rides on connectivity bought retail or semi-wholesale from an MNO.

That arrangement was defensible when the alternative was a heavy MVNO build. It is harder to defend now. SGP.32 collapses the operational overhead that used to make an in-house IoT connectivity play viable only for the very largest fleets. The threshold at which an enterprise should consider owning its connectivity layer has moved down, and the control benefits show up long before the pure cost benefits do.

There is a competitive angle too. An African logistics group, insurer or retailer that owns its connectivity layer can bundle it, price it, and use it to lock in customers of its own. An enterprise buying retail airtime cannot. In a challenger landscape where MTN and Vodacom set the reference prices, owning the SIM is one of the few durable moats a non-telco brand can dig.

The Trap Is Treating This As A Procurement Decision

The mistake enterprises are already making is to hand SGP.32 to the procurement team and ask for a cheaper unit rate. That misses the point. A branded IoT SIM is a product line, not a line item. It needs a customer value proposition, a pricing model, billing that can handle machine-to-machine traffic patterns, revenue assurance against silent SIMs and fraud, and a go-to-market that explains to the buyer's own customers why the connectivity is now part of the offer.

In other words, it needs the full MVNO lifecycle. Strategy, CVP, platform, launch, operate. Enterprises that stop at platform selection, which is what most IoT connectivity vendors will sell them, end up with a technically functional SIM estate and no commercial engine around it. The specification does not run the business.

This is where the distinction between MVNO support and MVNO enablement bites. Support keeps a platform running. Enablement builds the business the platform serves. An African enterprise moving into branded IoT for the first time needs the second, not the first, and needs a partner willing to sit at the wholesale negotiation table with the host MNO on their behalf.

What To Do This Quarter

The stance is straightforward. If you run a substantial fleet of connected devices in an African market, or expect to within eighteen months, stop renewing your MNO airtime contract on autopilot. Model the branded IoT SIM alternative properly, with SGP.32 and eIM as the operational backbone, and cost the full five-step lifecycle rather than only the connectivity rate.

The enterprises that move in the next twelve months will set the wholesale reference prices that the rest of the market inherits. The ones that wait will be buying from them.