I was on a call recently with a senior executive at a major IoT connectivity platform. When the conversation turned to manufacturing strategy, he summarized his company’s approach with confidence: “Oh yeah, we’re just manufacturing a SIM into the device with a global bootstrap.”
He said it the way you describe a solved problem. Everyone on the call nodded. And that reaction is exactly the issue.
What he described is not In-Factory Profile Provisioning. It is not even close. But his understanding reflects where the vast majority of the IoT industry stands today: conflating the act of soldering an eUICC onto a circuit board with a preloaded bootstrap profile, a practice that has existed for years, with IFPP, an architecturally distinct manufacturing process that changes where, when, and how operational connectivity is embedded into a device. The gap between those two things is where first-connectivity failures, stranded inventory, and preventable field service costs accumulate at scale.
- • •
What “Bootstrap at Manufacturing” Actually Means
The approach most connectivity platforms describe when they say they “do IFPP” follows a well-established pattern. An eUICC chip is placed onto the device’s PCB during standard SMT assembly. That eUICC ships from the silicon vendor with a bootstrap profile already loaded: a minimal connectivity credential that enables the device to attach to a single designated network for the sole purpose of reaching 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 legitimate and functional architecture. It works. But it has three structural limitations that its advocates consistently understate.
First, it requires successful first-connectivity. The entire provisioning model depends on the device being able to reach a network using the bootstrap profile at 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 attachment is not guaranteed. When it fails, the device is inert. It has a SIM. It has a bootstrap. It has no operational connectivity. The result is a truck roll, a field service dispatch, or a return-to-factory event, all of which erase the cost savings the bootstrap model was supposed to deliver.
Second, it does not solve the single-SKU problem. A bootstrap profile is typically tied to a specific carrier or carrier group whose network the device will use for initial attachment. An OEM shipping devices to thirty countries still needs to manage which bootstrap profile corresponds to which destination market, or accept the roaming costs and coverage limitations of a single global bootstrap that may not have agreements in every target geography. The promise of “one SKU for the world” remains a logistics exercise, not a manufacturing simplification.
Third, it conflates SIM placement with profile provisioning. Placing an eUICC on a board is a hardware manufacturing step. Loading a bootstrap is a supply-chain procurement step. Neither constitutes provisioning in the architectural sense that GSMA’s specifications define. They are prerequisites, not the activity itself.
- • •
What In-Factory Profile Provisioning Actually Is
IFPP is a fundamentally different process, and the distinction begins upstream of the OEM’s factory floor.
In a true 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 operate dedicated eUICC personalization lines where each chip is cryptographically individualized: unique keys are generated, 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 extended 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 arrives at the OEM’s manufacturing line already carries 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 distinction has cascading implications across the manufacturing and deployment lifecycle:
True single-SKU manufacturing. Because operational profiles are loaded at the eUICC personalization stage, the OEM’s production line is entirely decoupled from carrier and geography decisions. The same hardware, the same firmware, the same assembly process produces every device. Regional connectivity differentiation happens upstream, at the eUICC vendor’s facility, where profile configurations are managed as data rather than as production variants. The OEM’s bill of materials has one line item for connectivity, not thirty.
Eliminated first-connectivity risk. A device with a pre-installed operational profile does not need to negotiate its way onto a network for the first time. It attaches using credentials that were provisioned in a controlled, secure environment with validated carrier agreements already in place. For deployments in challenging RF environments (underground infrastructure, dense urban canyons, remote sites with marginal coverage), this eliminates the single largest source of activation failure.
Security architecture aligned with SGP.32 and SGP.42. IFPP workflows are designed to be compatible 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 demonstrated at MWC 2026 have incorporated post-quantum cryptographic protections into the IFPP process, securing profile data against future cryptanalytic threats from the moment of personalization. A bootstrap-only approach, by contrast, relies on the security of the first over-the-air provisioning transaction, which occurs in an uncontrolled environment.
Supply chain as provisioning infrastructure. IFPP transforms 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, effectively, a staging ground for pre-connected devices. This is a fundamentally different operational model from one in which connectivity activation is deferred to the field.
- • •
Why the Confusion Persists
The reason the bootstrap-equals-IFPP misconception is so persistent is that it serves almost everyone’s short-term commercial interests.
Connectivity platforms benefit from describing their existing bootstrap-based workflows as IFPP because it positions their current offering as state-of-the-art 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 our 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.
The post The Bootstrap Delusion: Why Embedding a SIM with a Global Profile Is Not In-Factory Profile Provisioning appeared first on IoT Business News.
