July 2026 product roundup
Mikk Lemberg
Cellular connectivity is getting more complicated.
Companies are starting to roll out SGP.32 IoT eSIMs while still running traditional UICCs and SGP.02 eUICCs. More often than not, they're all using the same connectivity under the same commercial agreement.
Until now, 1oT Terminal’s data-package structure didn’t reflect that reality.
July's biggest improvement changes that.
No more duplicate data packages because of SIM technology
A data package defines the commercial terms and pricing for a set of SIMs.
Previously, different SIM technologies often meant different data packages — even when everything else stayed exactly the same. Same carrier. Same rates. Same coverage. Same billing logic. Same agreement.
That meant duplicate data packages for what was effectively a single commercial setup. Keeping pricing aligned became another thing to maintain, while billing and reporting grew unnecessarily cluttered, all because the SIM technology was different.
Well, not anymore.
A single data package can now cover different SIM and eSIM technologies, provided the underlying connectivity and commercial terms are the same. That includes traditional UICCs, eUICCs based on different eSIM standards, and eSIM profiles delivered through an SM-DP+.
Of course, if pricing, coverage or commercial terms differ, separate data packages still make sense. But SIM technology alone is no longer a reason for the split.
Existing data packages won't be merged automatically, however, unless you specifically request it.
Why this matters: The connectivity market is moving towards a mix of SIM technologies within the same deployment. Terminal’s commercial structure now accommodates that mix without turning one connectivity agreement into several parallel packages.
Laying the groundwork for SGP.32
The change also removes an important prerequisite for our future SGP.32 experience.
More companies are beginning to procure SGP.32 IoT eSIMs for upcoming deployments. Full SGP.32 support in Terminal is still under development, so we’re not ready to show the complete experience yet. But supporting different SIM technologies within one data package gives us the right commercial and billing foundation to build on.
There’s more to come as the implementation takes shape.
More precise network identification
Mobile Country Code (MCC) and Mobile Network Code (MNC) values are now visible alongside network names in the data package’s Pricing tab and the Network access section of the roaming footprint.
Operator brand names are easier to scan, but network experts often work directly with MCC and MNC values—especially where similar names or several network entities make identification ambiguous. You can now use either without looking the codes up elsewhere
Wrapping up
IoT connectivity is evolving, and the tools for managing it need to evolve too.
This release brings Terminal a step closer to that future by simplifying today's mixed SIM environments while building the foundation for what's next.
.avif)
