How to Choose an eUICC eSIM Provider for IoT: An 8-Step Checklist

The eSIM market is about to get crowded with buyers who have never bought one before. A January 2026 study from Juniper Research found that the number of devices using eSIMs will grow by 30% in 2026, rising from 1.2 billion in 2025, and it names connected logistics as one of the fastest-growing sectors for IoT eSIM connections. A lot of those buyers will be fleet operators, telematics companies, and hardware makers choosing an eUICC eSIM provider for IoT for the first time, and most of them will be choosing from a shortlist of companies that look identical on paper.

That last part is the real problem. In our experience selling IoT connectivity to solution providers, most companies in this space do the same thing. They try very hard to make out that they have something unique, and most of them do not. So the sales pages will not help you decide. What helps is a short list of questions where the answers actually differ from one IoT eSIM provider to the next, and a clear idea of what a good answer sounds like.

This guide gives you eight of those checks. It is written for anyone who has to sign a connectivity contract for embedded devices: a fleet or telematics operator, an equipment manufacturer building cellular into a product, or an integrator managing SIMs for a customer. It is not a ranked list of vendors. It is the checklist we would want a buyer to bring to any eSIM provider for IoT, including us.

What You Are Actually Buying From an eUICC eSIM Provider

Start with the vocabulary, because the buyers who get the best contracts are the ones who use it precisely.

eSIM: an embedded SIM. The SIM function is delivered as software that can be loaded onto a chip, instead of being fixed to one plastic card from one carrier. An eSIM can be a soldered chip inside the device or a removable card that happens to support remote loading.

eUICC: stands for embedded Universal Integrated Circuit Card. It is the chip (or the chip design inside a plastic SIM) that can hold more than one carrier profile and can accept a new profile sent to it over the air. When a buyer asks for “eUICC,” they mean “a SIM I can re-program remotely without swapping the card.”

Carrier profile: the set of credentials that lets a device attach to one specific mobile network. A carrier profile on an eUICC is what a physical SIM card used to be.

Form factor: the physical shape. 2FF is the old full-size mini SIM, 3FF is the micro SIM, 4FF is the nano SIM, and MFF2 is the soldered chip form that is embedded onto a circuit board. Buyers who are replacing an existing supplier tend to say “3FF” and “eUICC” in the same sentence. We see that exact pairing on inbound inquiries from companies moving away from another provider, and it tells us in one line that they know what they have in the field and what they need next.

Now the important part. When you sign with an eUICC eSIM provider for IoT, you are buying three separate things, and many “providers” only supply one or two of them:

1. The eUICC hardware: the physical SIM or embedded chip, in the form factor your device needs, rated for the temperature and vibration it will see.
2. The carrier profiles and network agreements behind it: which mobile networks the provider can load onto that chip, in which countries, on what commercial terms, and whether those are the provider’s own agreements or resold from someone else.
3. The management platform: the portal and API (application programming interface, the way your software talks to theirs) used to activate SIMs, watch data use, suspend a device, switch a profile, and get a bill.

A company that sells you a chip with one profile and a login to a reseller’s portal is a SIM distributor, not an eUICC provider. A company that only sells the software layer is a platform vendor. You want to know which of the three a provider owns and which it rents, because the rented parts are where support gets slow and prices change without warning.

This matters more than it used to. Berg Insight estimates that roughly 10 percent of the global installed base of cellular IoT devices used an eSIM at the end of 2024, which means the other 90 percent are still on plain physical SIMs and most providers built their businesses on that older model. When you ask an IoT eUICC SIM supplier detailed eUICC questions, you are often testing a capability they added recently.

Multi-IMSI versus eUICC, in one paragraph: IMSI stands for International Mobile Subscriber Identity, the number that identifies a subscription on a network. A multi-IMSI SIM carries two or more of those identities pre-loaded at manufacture, and a small program on the card picks the best one for the country the device wakes up in. That solves coverage and roaming for a lot of deployments without any remote provisioning at all. True eUICC profile switching is for when you need to add a carrier that did not exist in the deal when the device shipped, or move a device to a local profile years later. If your devices will live in two or three known countries for a few years, ask about our multi-IMSI IoT SIM plans before you pay an eUICC premium. If they will live for a decade or cross into countries with local-only rules, you want the eUICC.

Step 1: Confirm the Provider Is Carrier-Agnostic (and What That Means in the Contract)

Carrier-agnostic (also called carrier-independent): the provider is not owned by, or commercially tied to, one mobile network operator, so it can load profiles from more than one carrier and you are not locked to a single network. The practical test is one question: “Can I change carrier on a device already in the field without changing the SIM?” If the honest answer is no, the provider is not carrier-agnostic, whatever the brochure says.

Carrier lock-in: what it looks like in a contract. The profile on your eUICC is owned by one operator and they will not load a second. There is no clause that lets you request a different profile from the eUICC provider. There is an exit fee per SIM, or a minimum term that restarts every time you add devices. The management portal belongs to the carrier, so leaving the carrier means losing the tool you run your fleet from.

Questions to ask any carrier-agnostic eSIM provider:

• Which networks can you load onto this eUICC today, by country, and are those agreements yours or a wholesaler’s?
• If I want to move my devices to a different profile in year three, what does that cost, who does the work, and how long does it take?
• If I leave you entirely, can another provider load a profile onto the same eUICC, or is the chip keyed to you?
• Show me the clause in your agreement that covers profile changes and termination per SIM.

What a good answer looks like: a named list of networks per region with a plain statement of which are direct and which are wholesale, a per-SIM profile change process with a stated turnaround, and a termination clause you can read in under a minute. What a bad answer looks like: “we are carrier-agnostic” followed by a coverage map with no network names on it.

One more thing to check in this step. Ask whether the provider offers a single-network plan as well as a multi-network one. That sounds backwards in a guide about carrier independence, but it is a useful tell. A provider that can only sell you “all networks” has usually built its whole offer on one wholesale roaming deal. A provider that can also put you on one carrier’s native plan, because that is cheaper for a device that never leaves one region, is showing you it has real choices behind the curtain. We keep both on the menu for exactly that reason.

Step 2: Check the Provisioning Standard: SGP.32, SGP.02, or Proprietary

Remote SIM provisioning is the process of sending a carrier profile to a device over the air and telling the eUICC to download, enable, disable, or delete it. There are three ways an IoT eSIM provider can do this, and the choice decides how much freedom you have later.

SGP.02: the older GSMA specification for machine-to-machine eSIMs, in use since around 2014. It works, but it was built around the carrier. Profile operations depend on servers the carrier or its partner controls, and moving to a new provider often means the old provider has to cooperate.

SGP.32: the newer GSMA IoT specification, published in 2023 and now shipping in modules and platforms. It introduces two pieces worth knowing by name. The eIM (eSIM IoT remote Manager) is the server that sends profile commands to devices. The IPA (IoT Profile Assistant) is the small piece of software on the device or eUICC that carries out those commands. The point of the design is that the eIM can belong to you or to a provider you choose, not to the carrier whose profile is currently active.

Proprietary: the IoT eSIM provider’s own mechanism. It may be fast and simple, but it usually means only that provider can ever manage that chip.

A few more terms you will hear in this step. The bootstrap profile is the first profile loaded at manufacture, whose only job is to get the device online long enough to download a real one. The profile lifecycle is the sequence of download, enable, disable, and delete that every profile goes through, and each of those four operations should be something you can trigger from the portal or API, not something you email a ticket to request.

Questions to ask about provisioning:

• Which specification does your eUICC and platform run: SGP.32, SGP.02, or your own?
• Who operates the eIM, and can I point my devices at a different eIM later?
• Can I download, enable, disable, and delete a profile from your portal and API myself, per device and in bulk?
• What is the bootstrap profile, which network is it on, and what does it cost to keep it alive while a device sits in a warehouse?
• Do you support in-factory profile provisioning, so devices can be built with the right profile already loaded?

What a good answer from an eUICC eSIM provider looks like: a clear statement of the standard, the name of the eIM operator, and a demonstration of all four lifecycle operations from the portal. If your devices will be in the field for five years or more, or will move between regions with local-only rules, SGP.32 support should be a requirement rather than a nice-to-have. If the deployment is one country and a three-year life, a multi-IMSI card with no remote provisioning at all is often the more sensible purchase, and a good eUICC provider will tell you that rather than sell you the more expensive option. For a plain-English walkthrough of loading profiles at the factory, see our post on in-factory profile provisioning.

Step 3: Check Coverage the Way It Will Be Used: Coverage Maps, Roaming Agreements, and Local Profiles by Region

A coverage map shows where a signal exists. It does not show what your device will be allowed to do there, for how long, or at what price. Three questions sit behind every map.

First, is the coverage native or roaming? A native (also called local or domestic) profile means your device is a home subscriber on that network. A roaming profile means it is a visitor from another country’s network. Roaming is fine for a truck that crosses a border and comes back. It is a problem for a device that sits in one country permanently, because of the next point.

Permanent roaming restrictions: the regulatory reason a buyer needs local profiles in some countries. Several governments limit how long a foreign-registered SIM can stay attached to their networks, and a device that never goes home can be cut off. 

Second, which networks in each country, not just how many? “500 networks in 180 countries” is a fine headline number, and we use one like it ourselves, but for your deployment the only numbers that matter are the two or three networks in the places your devices will actually be. Ask for those by name. Ask whether the provider can localize onto them (load a native profile) or only roam onto them.

Third, what happens at the border? For a vehicle fleet this is the whole ballgame. A multi-network SIM should switch to another network when the first one drops. Ask how long that switch takes, whether it is automatic or needs a device reboot, and whether the data session survives the switch.

Questions to ask about coverage:

• For each of these countries (give your list), which networks can you offer, and is each one native or roaming?
• In which of those countries can you load a local profile onto my eUICC, and what does localization cost per SIM?
• Which countries on my list have permanent roaming limits, and what is your answer for each?
• What is the fallback behavior when the primary network drops, and how fast does it happen?

What a good answer looks like: a per-country table from the eUICC provider, not a world map. A provider that says “we can localize in these eight countries and roam everywhere else, and here is the price difference” is telling you the truth. A provider that answers a country question with a global number is not.

Step 4: Evaluate the Management Platform and API

Connectivity management platform (CMP): the portal and API where SIMs are activated, monitored, suspended, given data limits, moved between plans, and billed. For a deployment of any size, you will spend more time in this tool than in any conversation with the provider, so it deserves a proper trial.

Everyone in this business has a platform. Very few show it. When we published a short video of the actual back end of our own IoT Suite, it stood out only because so few providers put real screens of their platform on their websites. So the first question in this step is simple: ask to see the real thing, on a live account, with your own SIMs on it, before you commit. Not a slide deck.

Then work through what the eSIM provider’s platform actually lets you do:

• Activation and lifecycle: activate, suspend, and deactivate a SIM, and change its profile, one at a time and in bulk from a file.
• Monitoring: data and SMS use per SIM in near real time, session history, last-seen network and country, and diagnostics that tell you why a device is offline.
• Alerts and limits: usage caps and automatic alerts per SIM or per group, so one faulty device cannot run up a bill.
• API: documented endpoints for every action the portal can do, with sample code, sandbox access, and a stated rate limit. If your own software needs to activate SIMs when a device ships, the API is the product.
• Users and roles: separate logins for your operations team, your finance team, and your own customers if you resell.
• Multi-network visibility: if a device can sit on several networks, the platform should show which one it is on right now and let you force a change.

Questions to ask about the platform:

• Can I have a trial login with two or three test SIMs for a month, and can I try the API against them?
• Is every portal action available through the API, and where is the documentation?
• What does the platform show me when a device goes offline, and does it tell me whether it is a network, SIM, or device problem?
• Does the platform support my eUICC operations (profile download, enable, disable, delete), or is that a separate tool?

What a good answer from an IoT eSIM provider looks like: a trial account, a public API reference, and a screen-share on a real customer estate with names blurred. If you want a longer view of what to expect from these tools, our guide to the best IoT connectivity platforms covers the features in more depth.

Step 5: Security Features to Require

The security questions buyers send us are more specific than the ones in most provider guides. A recent inquiry described the whole setup in two lines: a few dozen SIMs on a private APN, with an OpenVPN tunnel between two or three of them for a secure private connection. That is the level of detail you should bring, and the level of detail an eUICC eSIM provider should be able to answer without a follow-up call. Here is what to require, in plain terms.

Private APN: APN stands for Access Point Name, the gateway a device uses to get from the mobile network onto the internet. A private APN is a gateway reserved for your devices only, so their traffic never touches the public internet on the way to your servers. It is the single most useful security feature for IoT and the first one to ask for. Our post on private APNs for secure IoT explains how it is set up.

VPN or IPsec tunnel: VPN stands for Virtual Private Network, and IPsec is a standard way of building one. This is an encrypted tunnel from the provider’s network into yours, so that even inside the private APN, the data is scrambled in transit. Ask whether the provider supports a site-to-site tunnel to your data center or cloud, and whether they will support your own OpenVPN setup if that is what you already run.

IMEI lock: IMEI stands for International Mobile Equipment Identity, the serial number of the cellular modem. An IMEI lock ties a SIM to one device, so if the SIM is pulled out and put in a phone, it stops working. Ask whether your eUICC eSIM provider lets you set and clear it from the portal and API.

SIM-level authentication and profile encryption: the carrier profiles on an eUICC are encrypted, and the keys that allow a profile to be loaded or changed live somewhere. Ask where. Ask who can issue a profile download command to your devices, and whether the provider or the eUICC manufacturer holds those keys.

Static or fixed IP addresses: useful if your servers need to reach devices directly, and often only available inside a private APN.

Questions to ask about security:

• Can you provide a private APN for my SIMs, and what does it cost to set up and per month?
• Do you support an IPsec or OpenVPN tunnel from your core to my network, and who configures it?
• Can I set an IMEI lock per SIM from the portal and the API?
• Who holds the keys that allow a profile to be loaded onto or removed from my eUICC?
• What logs can I get if I suspect a SIM has been misused?

What a good answer looks like: yes to private APN and IMEI lock as standard, a clear answer on the tunnel, and a direct statement of who holds the profile keys. An eSIM provider for IoT that describes its security as a list of adjectives has not been asked these questions before.

Step 6: Pricing Models and Total Cost of Ownership

Price is where most comparisons collapse into what one of our own team calls a price beauty contest: five quotes for a per-megabyte rate, lowest one wins, and the buyer finds out a year later that the cheap rate came with everything else charged separately. The way out is to make every IoT eSIM provider quote against the same model, then add up the things that are not in the headline rate.

Pricing model	How it works	Best for	Watch for
Per-SIM, per-month	A fixed monthly fee per active SIM with a data allowance included	Steady fleets with predictable use	Overage rate above the allowance; whether suspended SIMs still bill
Pooled data	All SIMs share one pool of data each month; heavy and light devices balance out	Mixed device types, fleets with seasonal use	Pool size resets; cost per megabyte once the pool is used up
Pay-as-you-use	You pay only for the data actually used, plus a small platform or SIM fee	Very low-data devices, pilots, unpredictable use	A per-SIM minimum can make this dearer than it looks for idle devices
Prepaid multi-year	One upfront payment covers a fixed data amount for a fixed number of years	Devices with tiny, known data needs and no budget for recurring bills	No refund for unused data; what happens after the term ends
Regional or zone add-ons	The base plan covers one region; other zones cost extra per SIM or per megabyte	Deployments that are mostly in one place	A device that wanders into zone three for a week

Then add the items below to each quote, because they are where the real differences hide:

• Overage: the rate per megabyte after the allowance, and whether you get an alert before it starts.
• SIM and profile costs: the one-time price of the eUICC in your form factor, the price to load an additional carrier profile, and the price to localize a device onto a native profile in a restricted country.
• Suspended and idle SIMs: does a SIM in a warehouse or on a broken device still bill? At what rate?
• Platform and API fees: some providers charge for the portal, for API calls above a limit, or for extra user seats.
• Private APN, static IP, and VPN: usually setup plus monthly fees.
• Minimum commitments: minimum monthly spend, minimum active SIMs, or a term that restarts when you add devices.
• Exit costs: per-SIM termination fees and whether your profiles can be transferred.

Questions to ask an IoT eSIM provider about pricing:

• Quote me on this exact profile: this many SIMs, this much data per month, this many SMS, in these countries, with a private APN, over 36 months. Show every line.
• What does a SIM cost me in a month when it uses zero data?
• What is the total cost to move a device to a local profile in a restricted country?
• What changes in my price when I go from 50 devices to 500 to 5,000?

What a good answer looks like: an itemized 36-month quote against your specification, with the idle-SIM rate and the overage rate shown, and a clear price step at each volume tier. Our own view, for what it is worth: at fewer than a few hundred devices, the difference between two providers’ per-megabyte rates will almost never be the biggest number in the total. The idle-SIM rate, the private APN fee, and the cost of one badly configured device running up overage will be.

Step 7: Uptime, SLAs, and Support

An SLA (service level agreement) is the part of the contract that says what the provider promises to deliver and what happens if they do not. Most connectivity SLAs are about the provider’s core network and platform, not the radio networks your devices attach to, because the provider does not own those towers. Read the SLA with that in mind.

What an SLA should actually state:

• Scope: which parts are covered (the platform, the eSIM provider’s core network, the private APN gateway) and which are explicitly not (the carrier’s radio network, your device).
• The measure: what counts as downtime, how it is measured, and over what period.
• The remedy: service credits, how they are claimed, and whether they are automatic.
• Support response times: by severity, with hours of coverage stated in a time zone.
• Escalation: a named path to a person who can actually change something.

Support is where a small provider can genuinely beat a large one, and where a provider on the wrong side of the world can quietly fail you. We say this from experience on the other side of the table: we have pointed buyers in some far-off regions toward a local provider when, purely from the point of view of payments and support hours, a local provider would serve them better. A provider that is honest about that is doing you a favor. A provider that will sell to anyone anywhere and support them from one office in one time zone is not.

Two practical qualification factors that most provider guides skip, because they come from real sales conversations rather than from a features list:

• Payment method and terms: can you pay by card, by bank transfer, or on invoice in your currency? Do they require prepayment for new accounts? A provider that cannot take your money the way your finance team pays is going to be a monthly headache.
• Support in your working hours: when your fleet goes offline at 7 a.m. in Atlanta, who picks up? Ask the eUICC provider for the support hours, the time zone, and whether you get a named contact or a ticket queue. Our own model is that your account manager is also your service manager, one person who knows your deployment, and we would suggest asking every provider whether they can say the same.

Questions to ask about SLAs and support:

• What exactly does your SLA cover, and what is the credit if you miss it?
• What are your support hours, in which time zone, and do I get a named contact?
• How do I pay, in what currency, and on what terms?
• When a device is offline, walk me through what your support team does in the first hour.

What a good answer looks like: an SLA you can read in ten minutes, support hours that overlap with yours, a named person, and payment on terms your finance team already uses. Do not accept an uptime percentage as the whole answer. Ask what it covers.

Step 8: Match the Provider to Your Use Case and Scale

The right eUICC eSIM provider for IoT depends on what the devices do and how many there will be. A few common cases.

Vehicle Fleets and Telematics

Devices move, cross borders, and lose signal under bridges and in yards. What matters: multi-network switching that is fast and automatic, a clear answer on native versus roaming coverage in every country the vehicles enter, a platform that shows which network each vehicle is on right now, and pricing that does not punish a truck for one week in a neighboring country. Video telematics adds a data-volume question: dashcams upload a lot, so pooled data and a sensible overage rate matter more than the base per-SIM fee. This is our own strongest area, and the questions in Steps 3 and 6 are the ones that separate providers here.

Industrial and Harsh Environments

Devices sit still for years in heat, cold, and vibration. What matters: an industrial-grade eUICC with a stated operating temperature range, an MFF2 embedded form factor if the device is sealed, very low idle costs because many of these devices send a few kilobytes a day, and long profile life. If the site is in a country with permanent roaming limits, native profiles are not optional. Ask about SGP.32 here, because a ten-year device will outlive at least one carrier agreement.

OEM Hardware Products

You are building cellular into a product you will sell to other people, often in countries you have not chosen yet. What matters: in-factory profile provisioning so devices ship ready, a bootstrap profile that costs nothing while units sit in inventory, an API your production line and your customer portal can call, and a carrier-agnostic eSIM provider that can localize later without a recall. This is the case where the eUICC earns its premium.

Small Pilots Versus 1,000+ Device Rollouts

Here is something we see constantly: a buyer needs five SIMs now and may need five hundred next year, and neither they nor the provider can say which. That makes it hard to qualify a provider by size alone, so look at how each one behaves at both ends. Will they send you five SIMs and a platform login with no minimum commitment? And will they give you a written price step at 500 and at 5,000, so you are not renegotiating from scratch when the pilot works?

The inquiries that turn into good long-term accounts tend to be written like a specification: we need multi-network coverage in these countries, this much data per month, this many SMS, access to a platform, and an initial batch of this many SIMs. Write your requirement in that shape before you contact anyone. It forces every eSIM provider for IoT to quote against the same thing, and it tells the provider you know what you are buying.

Common Mistakes When Choosing an Embedded SIM Supplier

• Comparing per-megabyte rates and nothing else. The idle-SIM fee, the overage rate, and the private APN charge usually move the total more. Ask for an itemized 36-month quote instead.
• Trusting a coverage map. A map shows signal, not permission or price. Ask for named networks per country and whether each is native or roaming.
• Ignoring who owns the profile keys. If the provider or its carrier partner holds the keys, “carrier-agnostic” is a marketing word. Ask who can load and remove profiles from your eUICC.
• Buying eUICC when multi-IMSI would do. For a short-life, few-country deployment, a multi-IMSI SIM is cheaper and simpler. Ask the provider to tell you honestly which one you need.
• Signing before seeing the platform on a live account. Slides are not a trial. Ask for test SIMs and a login for a month.
• Not checking payment and support fit. A provider that cannot bill you the way you pay, or answer the phone in your working hours, will cost you time every month. Ask both questions before price.
• Locking in a minimum term that restarts when you add devices. Read the termination and expansion clauses, or have someone read them for you.

Provider Evaluation Scorecard

Use this table to score each eUICC provider on your shortlist. Weight is a suggestion; adjust it for your deployment.

Criterion	Question to ask	What a good answer looks like	Weight
Carrier independence	Can I change carrier on a fielded device without changing the SIM, and what does the contract say?	Yes, with a per-SIM process, stated turnaround, and a readable termination clause	15
Provisioning standard	SGP.32, SGP.02, or proprietary, and who operates the eIM?	SGP.32 support, a named eIM operator, all four lifecycle actions available to me	15
Coverage by country	For my country list, which named networks, native or roaming, and can you localize?	A per-country table with network names, localization options, and prices	15
Management platform and API	Can I trial the portal and API with test SIMs, and is every action available by API?	A month-long trial, public API docs, a live screen-share of a real estate	15
Security	Private APN, VPN or IPsec, IMEI lock, and who holds the profile keys?	Private APN and IMEI lock as standard, a clear tunnel option, a direct answer on keys	10
Pricing and total cost	Itemized 36-month quote against my spec, including idle-SIM and overage rates?	Every line shown, with price steps at each volume tier	15
SLA and support	What does the SLA cover, what are support hours and time zone, and how do I pay?	A short SLA with credits, overlapping support hours, a named contact, terms my finance team uses	10
Fit for use case and scale	Will you serve my pilot with no minimum and give me written prices at 10x and 100x?	Yes to both, in writing	5

Score each cell 1 to 5, multiply by the weight, and total. The exercise is less about the final number than about the questions a provider cannot answer. Those are the ones to worry about.

How Trafalgar Wireless Fits These Criteria

Against the eight steps above, here is where we stand, stated plainly so you can compare us the same way you compare everyone else.

We are carrier-agnostic. Trafalgar Wireless provides eSIM and eUICC IoT SIMs in MFF2 embedded and 2FF, 3FF, 4FF, and tri-cut plastic forms, with access to more than 500 mobile networks in around 180 countries, and we can provision localized eSIM profiles on AT&T and Verizon, with roaming on T-Mobile. As an IoT eSIM provider we also sell single-network native plans, multi-network plans, and multi-IMSI plans, and we will tell a buyer when the cheaper option is the right one. Our IoT Suite platform handles activation, suspension, data limits, alerts, diagnostics, and profile management from one dashboard, with an open API, and we publish real footage of its back end rather than a mock-up. Private APNs, site-to-site VPN, and IMEI lock are part of our security services for fleet, telematics, and industrial customers.

On the parts of this list that are about how a provider behaves rather than what it sells: your account manager is also your service manager, we are based in Atlanta and support US working hours, and we would rather turn away an inquiry we cannot serve well than sign it and disappoint you. We do not upsell features you will never need or hide behind technical language. If you bring us the scorecard above, we will fill it in with you, line by line.

Frequently Asked Questions

What is the difference between an eSIM provider and a carrier?

A carrier owns a mobile network: the towers, the spectrum, and the subscriber systems. An eSIM provider packages profiles from one or more carriers, puts them on an eUICC, and gives you a management platform to run them. Some carriers also act as eSIM providers, but a carrier-owned provider will rarely load a rival’s profile onto your chip, which is the whole point of buying eUICC.

Do I need SGP.32 support?

If your devices will be in service for five years or more, or will sit permanently in countries with rules against permanent roaming, yes. SGP.32 lets you change carriers on a fielded device through an eIM you control, without the original carrier’s cooperation. For a single-region deployment with a three-year life, a multi-IMSI SIM is often enough and cheaper, and a good IoT eSIM provider will say so.

How many carrier profiles should an eUICC hold?

Enough for every country and fallback network in your deployment plan, plus at least one spare slot for a carrier you add later. Chip capacity varies by manufacturer and profile size, so rather than fixing on a number, ask the provider to confirm that the eUICC they are quoting can hold the specific profiles you need with room to add one.

Can I move existing devices to a new provider?

Only if the eUICC and its keys allow a new profile to be loaded by someone other than the original provider. Under SGP.02 and proprietary systems this often needs the old provider’s cooperation. Under SGP.32 it depends on whether you can point the device at a new eIM. Ask this question before signing, not after, and get the answer in writing.

What is a reasonable minimum order?

The buyers we talk to range from a few dozen SIMs on a private APN to requests for thousands of eSIMs for a product launch, and many of them do not know in year one which end they will be at in year two. A reasonable provider will start you with a small batch and a platform login with no minimum commitment, and give you written price tiers for when you grow. Treat a large forced minimum as a signal about how the provider thinks about small customers.

What security features should an IoT eSIM provider offer as standard?

A private APN, IMEI lock, and the option of a VPN or IPsec tunnel into your network, all manageable from the portal and API. Beyond that, a straight answer on who holds the keys for loading and removing profiles on your eUICC. If the provider cannot say who holds the keys, keep looking.

Key Takeaways

• You are buying three things: the eUICC hardware, the carrier profiles and agreements behind it, and the management platform. Find out which ones the provider owns and which it rents.
• Carrier-agnostic has a test: can you change carrier on a fielded device without changing the SIM? Check the contract, not the brochure.
• The provisioning standard decides your freedom later: SGP.32 with an eIM you can change is the safe choice for long-life or multi-country devices; multi-IMSI is often enough for short, single-region ones.
• Coverage means named networks per country, native or roaming, and a plan for countries with permanent roaming limits.
• Trial the platform and API on real SIMs before signing. Ask to see the actual back end.
• Require a private APN, IMEI lock, a tunnel option, and a clear answer on profile keys.
• Price the whole 36 months, including idle SIMs, overage, security add-ons, and exit costs, not the per-megabyte rate.
• Payment method and support hours are qualification factors, not afterthoughts.
• Write your requirement as a specification before you talk to anyone, so every quote answers the same question.

Choosing an eUICC eSIM provider for IoT is mostly a matter of asking eight sets of questions and noticing which providers answer them in specifics and which answer them in adjectives. The providers really do look alike on their websites. They stop looking alike about ten minutes into a call that follows this list.

If you are a fleet operator, telematics company, or hardware maker comparing an eUICC eSIM provider for IoT, Trafalgar Wireless supplies carrier-agnostic eSIM and eUICC IoT SIMs, multi-network data plans, and the IoT Suite management platform, with hands-on support from people who understand your deployment. Talk to an IoT connectivity expert, or request a testing SIM and score us against the checklist yourself.