Guest post by Jared Miller, President of ENODA Ventures Inc.
During a recent call with a top executive at a leading IoT connectivity platform, the topic shifted to manufacturing strategy. He confidently stated: “Oh yeah, we simply build a SIM into the device with a global bootstrap.”
He spoke as if it were a finished solution. Everyone on the call agreed. And that reaction is precisely the problem.
What he described is not In-Factory Profile Provisioning. It is not even remotely close. Yet his view mirrors the stance of most of the IoT industry today: confusing the practice of soldering an eUICC onto a circuit board with a preloaded bootstrap profile, a method that has been around for years, with IFPP, a unique manufacturing process that changes where, when, and how operational connectivity is embedded into a device. The difference between these two approaches is where first-connectivity failures, stranded inventory, and avoidable field service costs pile up at scale.
What “Bootstrap at Manufacturing” Really Means
The method most connectivity platforms refer to when they claim they “do IFPP” follows a familiar pattern. An eUICC chip is mounted onto the device’s PCB during standard SMT assembly. That eUICC arrives from the silicon vendor with a bootstrap profile already loaded: a basic connectivity credential that lets the device connect to a single designated network solely to reach a remote provisioning server. When the device powers on for the first time in the field, it uses that bootstrap connection to authenticate with an SM-DP+ (Subscription Manager Data Preparation) server, which then downloads and installs the actual operational profile the device needs for its intended carrier and geography.
This is a valid and working architecture. It functions. But it has three structural drawbacks that its supporters consistently downplay.
First, it depends on successful first-connectivity. The entire provisioning model relies on the device being able to reach a network using the bootstrap profile the moment it is first powered on in its deployment environment. For devices installed in basements, underground utility vaults, rural agricultural sites, or inside metal enclosures, that first network connection is not assured. When it fails, the device is dead. It has a SIM. It has a bootstrap. It has no operational connectivity. The outcome is a truck roll, a field service dispatch, or a return-to-factory event, all of which wipe out the cost savings the bootstrap model was meant to provide.
Second, it does not fix the single-SKU problem. A bootstrap profile is usually linked to a specific carrier or carrier group whose network the device will use for initial connection. An OEM shipping devices to thirty countries still has to manage which bootstrap profile matches which destination market, or accept the roaming costs and coverage limits of a single global bootstrap that may not have agreements in every target geography. The promise of “one SKU for the world” stays a logistics task, not a manufacturing simplification.
Third, it mixes up SIM placement with profile provisioning. Mounting an eUICC on a board is a hardware manufacturing step. Loading a bootstrap is a supply-chain procurement step. Neither counts as provisioning in the architectural sense that GSMA’s specifications define. They are prerequisites, not the activity itself.
What In-Factory Profile Provisioning Truly Is
IFPP is a completely different process, and the difference starts before the OEM’s factory floor.
In a real IFPP architecture, operational profiles, not bootstrap credentials, are loaded onto the eUICC during the chip’s personalization phase at the eUICC vendor’s secure facility. Companies like STMicroelectronics, Thales, and IDEMIA run dedicated eUICC personalization lines where each chip is cryptographically individualized: unique keys are created, certificates are injected, and the chip’s secure element is locked to the appropriate SM-DP+ and SM-DS (Subscription Manager Discovery Server) infrastructure. In an IFPP workflow, this personalization step is expanded to include the installation of one or more operational carrier profiles, coordinated between the eUICC vendor, the target MNO or connectivity platform, and the SM-DP+ operator.
The device that reaches the OEM’s manufacturing line already holds a working connectivity profile. When it is assembled, tested, packaged, and shipped, it leaves the factory ready to connect. There is no first-call-home dependency. There is no bootstrap negotiation with a remote server. There is no RF-environment lottery at the deployment site. The device is born connected.
This difference has ripple effects across the manufacturing and deployment lifecycle:
Genuine single-SKU manufacturing. Because operational profiles are loaded at the eUICC personalization stage, the OEM’s production line is fully separated from carrier and geography decisions. The same hardware, the same firmware, the same assembly process makes every device. Regional connectivity differentiation happens upstream, at the eUICC vendor’s facility, where profile configurations are handled as data rather than as production variants. The OEM’s bill of materials has one line item for connectivity, not thirty.
Removed first-connectivity risk. A device with a pre-installed operational profile does not have to negotiate its way onto a network for the first time. It connects using credentials that were provisioned in a controlled, secure environment with validated carrier agreements already in place. For deployments in difficult RF environments (underground infrastructure, dense urban canyons, remote sites with marginal coverage), this removes the biggest source of activation failure.
Security architecture aligned with SGP.32 and SGP.42. IFPP workflows are built to work with GSMA’s SGP.32 specification for IoT eSIM remote management and with the emerging SGP.42 specification that formalizes in-factory provisioning procedures. Early implementations shown at MWC 2026 have included post-quantum cryptographic protections in the IFPP process, securing profile data against future cryptanalytic threats from the moment of personalization. A bootstrap-only approach, on the other hand, depends on the security of the first over-the-air provisioning transaction, which happens in an uncontrolled environment.
Supply chain as provisioning infrastructure. IFPP turns the eUICC supply chain from a component logistics operation into a connectivity provisioning pipeline. The personalization facility becomes the provisioning point. The shipping manifest becomes the activation schedule. The warehouse becomes, in effect, a staging area for pre-connected devices. This is a completely different operational model from one where connectivity activation is postponed to the field.
Why the Confusion Continues
The reason the bootstrap-equals-IFPP misconception is so widespread is that it serves almost everyone’s short-term business interests.
Connectivity platforms gain from describing their current bootstrap-based workflows as IFPP because it makes their existing offering appear cutting-edge.
You are a paraphrasing software that takes an article in HTML format and rewrite it in a way that is easy to read and understand, Keep HTML as-is, change the text as far as you can. Do not change the content language: without requiring them to build the eUICC vendor integrations, SM-DP+ coordination workflows, and carrier pre-provisioning agreements that true IFPP demands. It is, candidly, easier to sell a bootstrap and call it provisioning than to engineer the supply chain relationships that genuine factory provisioning requires.
OEMs accept the description because it confirms what they want to hear: that their connectivity problem is already solved at the point of manufacture. Questioning the distinction means acknowledging that their manufacturing process may need to change, that their eUICC procurement relationships may need to expand, and that their connectivity vendor may not be delivering what they promised.
And the broader industry tolerates the ambiguity because IFPP, done properly, requires coordination between entities that do not traditionally work together. An eUICC silicon vendor, a profile provisioning server operator, one or more mobile network operators, and the OEM must align on technical interfaces, commercial terms, and operational timelines. That coordination is difficult. Pretending a bootstrap solves the problem is easier.
What Enterprises Should Ask
For any enterprise evaluating an eSIM-based manufacturing strategy, three questions will immediately separate genuine IFPP capability from rebranded bootstrap workflows:
Where is the operational profile loaded? If the answer is “in the field when the device first powers on,” that is not IFPP. If the answer is “at the eUICC personalization facility before the chip reaches your production line,” you are in the right conversation.
Does the device require network connectivity to become operational? If the device must successfully attach to a network and contact a provisioning server before it can perform its intended function, the first-connectivity dependency has not been eliminated. It has been deferred. IFPP eliminates it.
Who coordinates the profile provisioning with the target carrier? If your connectivity platform cannot articulate the specific relationship between the eUICC vendor’s personalization process, the SM-DP+ operator, and the destination MNO, the integration does not exist. IFPP is a supply chain orchestration problem, not a software feature.
The IoT industry is moving toward a future in which devices are born connected, globally routable, and remotely manageable from the moment they leave the factory. GSMA’s SGP.32 and SGP.42 specifications are building the architectural foundation for that future. But reaching it requires the industry to be honest about the difference between embedding a SIM with a bootstrap profile, a solved problem, and provisioning operational connectivity at the point of manufacture, a problem most of the industry has not yet seriously attempted to solve.
The first step is calling it what it is. A bootstrap is not a strategy. A SIM on a board is not provisioning. And the enterprise that ships a device with nothing but a bootstrap profile and a hope for first-connectivity is not doing IFPP. It is doing what the industry has done for a decade, with a newer acronym attached.
About the author: Jared Miller is President of ENODA Ventures Inc., an IoT connectivity consultancy focused on enterprise eSIM architecture, GSMA standards adoption, and global fleet management strategy. He has over 15 years of experience spanning telecom operator, platform, and independent advisory roles across North America and international IoT markets.
