IoT CMP vs. Carrier Portal: What’s the Difference for Resellers and MSPs?

The tool your connectivity business runs on defines what it can become

Most IoT resellers reach the same point about 18 months in. The carrier portal that worked fine for the first handful of accounts stops keeping up: a customer wants pooled data, another wants their own branding on the platform, a third is deploying devices in a country the carrier covers poorly. The portal has no answer for any of it. That is when the question of what kind of infrastructure to run the business on becomes urgent.

The distinction between a carrier portal and an IoT Connectivity Management Platform is not academic. It determines what the business can offer, at what margin, and under whose brand.

What a carrier portal is, and what it is not

A carrier portal is the operational interface a mobile network operator provides to its wholesale customers. It is built to manage connectivity on that carrier’s network, on that carrier’s pricing, in the countries that carrier covers.

Carrier portals handle the essentials: SIM activation, usage monitoring, basic suspension and reporting. For a single-carrier deployment in one geography, that coverage is sufficient.

Beyond that scope, the constraints compound. Other carriers’ SIMs are invisible. There is no pricing layer: what the carrier charges is what you work with, and you cannot build your own plan structures or billing logic on top of it. Reporting reflects the carrier’s data model. When a device goes offline because the carrier has a regional outage, the portal shows you the problem but gives you no way to route around it.

There is also the branding reality. Every customer-facing interface in a carrier portal carries the carrier’s identity. You are reselling access to someone else’s platform. The customer relationship reflects that, because the customer can see it too.

What an IoT Connectivity Management Platform adds

An IoT Connectivity Management Platform (IoT CMP) is a centralized operational layer built for connectivity providers, resellers, and enterprises managing SIM and eSIM fleets at scale. It sits above the carrier network rather than within it, which is what makes multi-carrier management, custom billing, and white-labeled customer environments possible from a single interface.

The scope is broader than a carrier portal by design. A CMP manages SIM and eSIM lifecycle from provisioning through deactivation, across multiple carriers, with billing logic, customer account management, and reporting all in one environment. Every customer’s devices are visible from one login, regardless of which network they use. Pricing is yours to set. Invoices go out under your brand.

The multi-carrier dimension matters operationally as well as commercially. When a device on one network loses signal, a CMP with carrier-switching capabilities can redirect it to an alternative network in real time, through an automation rule, a manual action, or an API call. A carrier portal cannot do this because it has no visibility beyond its own network.

For MSPs, API access changes how connectivity fits into the stack. SIM provisioning triggers automatically when a device is deployed through an RMM workflow. Usage data flows into client reporting without manual exports. Threshold alerts fire in the monitoring tools the MSP already uses, not in a separate portal that someone has to remember to check.

The billing gap

The margin conversation is where carrier portals and CMPs diverge most visibly. A carrier portal reflects the carrier’s billing model. You see what you consumed and what you owe. There is no mechanism to build your own pricing on top of it, create pooled data plans for your customers, or run prepaid wallet logic for smaller accounts.

A CMP includes a billing engine. You define the plan types: prepaid bundles, PAYGO, pooled data across a customer’s device fleet, subscription models with trial periods. You set the retail pricing. The CMP calculates what your customers owe based on the plans you created, generates the invoice under your brand, and integrates with your finance system via API. The carrier receives one wholesale invoice from you. Your customers receive invoices that reflect your pricing structure.

For a reseller managing fifty accounts across multiple verticals, the difference is whether you run a connectivity business or a connectivity resale arrangement.

White labeling and what it actually means

White labeling in the context of a carrier portal is usually limited to removing a logo from certain views, or a co-branded experience on some screens. The underlying system remains the carrier’s.

A full white label IoT platform works differently. Your logo, your domain, your colour scheme, your communication templates. Customers log into an environment that looks and functions like your product, because operationally it is. The management interface, the customer-facing eSIM store if you run one, the automated notifications, the invoices: your identity throughout.

For a reseller building a managed connectivity proposition rather than distributing SIMs, the brand layer is not cosmetic. It is what the customer relationship is built on.

Where eSIM Orchestration enters the picture

A CMP manages active connections: usage, alerting, activation, suspension. An eSIM Orchestrator works one layer lower, controlling which carrier profile sits on a device and executing changes to that profile over time based on location, regulation, or policy. Vendors often use both terms loosely, which makes it worth asking specifically what a platform does at the profile layer before committing to it.

A carrier portal has no eSIM Orchestration capability. It manages profiles on that carrier’s network and cannot execute profile switches across operators. A standard CMP without eSIM Orchestrator integration manages active connections competently but does not control the profile layer: it can suspend a SIM but cannot move a device from one carrier’s profile to another without a separate provisioning workflow.

A platform that combines both functions handles the full lifecycle from profile provisioning to billing in one environment. For resellers managing device fleets that operate across multiple countries with different regulatory environments, that integration matters. A device entering a market where permanent roaming is restricted needs a local carrier profile. Without eSIM Orchestration, that means a manual step or a separate SIM product per market. With it, the profile switch happens automatically based on location and pre-configured rules.

SGP.32 and why it changes the CMP conversation

SGP.32 is the GSMA standard for remote SIM provisioning in IoT devices. It introduces the eIM (eSIM IoT Remote Manager) as the server-side component that manages eSIM profile lifecycle across device fleets, without physical access, user interaction, or manual steps. The IPA (IoT Profile Assistant) is the device-side component that executes what the eIM instructs.

The reason SGP.32 is relevant to the CMP discussion is that it creates provisioning capabilities a carrier portal cannot support and that a CMP without eIM integration can only partially address. Zero-touch provisioning, where a device powers on in the field and receives its operational carrier profile automatically, requires eIM infrastructure. So does over-the-air profile management for deployed devices across multiple operators.

Enterprise and automotive IoT buyers are already evaluating SGP.32 readiness in vendor selection. Soracom described SGP.32 readiness as a defining criterion in enterprise IoT procurement at Mobile World Congress 2026. A reseller whose platform cannot support SGP.32 deployments will encounter that question in sales conversations before long.

The practical issue is not just whether a CMP supports SGP.32 in principle, but whether the eIM is integrated with the connectivity management interface or sits in a separate system that needs to stay in sync. Fragmented architecture at the platform level recreates the operational overhead the CMP was supposed to eliminate.

Which tool fits which business

A carrier portal is appropriate when the business is starting out, the deployment is geographically contained, and the customer base is small enough that the carrier’s reporting and billing model covers what you need. There is no operational reason to run a full CMP on a portfolio of three accounts in one country.

The signals that a CMP is the right next step tend to arrive together rather than one at a time. A customer asks for a data plan structure the carrier portal cannot support. A second customer wants to see their own devices in a branded environment. A third is deploying in a country where the primary carrier has poor coverage and there is no fallback. Any one of those is manageable as a one-off. When they arrive at the same time across different accounts, the carrier portal stops being a tool and starts being a constraint.

The timing of the move matters more than most resellers anticipate. Migrating an established customer base from a carrier portal to a CMP means moving SIMs, reconfiguring accounts, and rebuilding billing logic while keeping existing customers operational. Resellers who make the switch before the carrier portal is visibly limiting do it at a pace they control. Those who wait until accounts are at risk do it under pressure.

What the carrier portal cannot show you

The carrier portal shows you what you have. It does not show you what the ceiling is.

Running a connectivity business through a carrier portal means the pricing is fixed, the billing model is the carrier’s, the brand is not yours, and the platform cannot grow beyond what that carrier supports. The accounts you are not winning because your product looks like a resale arrangement, the margin you are not capturing because you cannot set your own pricing, the customers who leave because the service feels like a commodity: none of that shows up in the carrier portal’s reporting.

A CMP does not solve those problems automatically. It provides the infrastructure to address them. What you do with that infrastructure is the business.