August 22, 2026 · 7 min read · Procurement & Strategy
Fertilizer-tank IoT SIMs at 500KB/month can use catalog pricing below 250 SIMs. Above 500, or at border crossings, a project quote with eUICC is the trigger.
Catalog vs project IoT SIM pricing is the difference between buying a SIM at a published per-MB rate and negotiating a custom connectivity contract. For a fertilizer-tank deployment sending 500KB per SIM per month [6], catalog pricing works below 250 SIMs; above 500, or at a network border, project quote is the procurement trigger.
The operational boundary changed when multi-network SIMs moved from add-on to standard. According to [1], IoT SIMs include multi-network support, business logic support, automatic SIM switching, and improved reliability. That changes procurement because a tank monitor can fail over to a second operator without a site visit. For a tank monitor deployed for 5–10 years, the ability to switch operators after deployment is a lifecycle requirement, not a feature. It also shifts the negotiation from per-MB price to switching behavior and management access.
Network sunsets make the risk concrete. LTE Cat.1 bis is 63% of module shipments, and when a network shuts down, every device needs a modem or SIM replacement—or becomes a brick [7]. The SIM carrier decision is also a hardware decision.
From the field: procurement managers note that a border crossing is where IoT deployments fail, especially for fleets of 100+ trucks, because the SIM cannot switch networks. The same procurement logic applies to fixed fertilizer tanks at the edge of a carrier's coverage area: if the SIM cannot switch, the level reading stops, and the operations team has to roll a truck. This is the moment catalog pricing breaks.
A cooperative with 30 fertilizer tanks on one carrier's NB-IoT or LTE-M network can use catalog pricing. Each tank sends a 500KB monthly payload [6], so monthly data cost equals one low-volume M2M SIM. Buy a physical SIM with multi-network support [1] and use the provider's basic portal; no project quote needed.
For a fleet of 100+ trucks moving fertilizer across a border, the border crossing is the failure point because the SIM cannot switch networks. Procurement managers report this failure mode on fleets of 100+ trucks. A multi-carrier global IoT SIM with automatic network switching [1] and eUICC remote profile management [8] should go to project quote so the contract specifies failover behavior and roaming limits. Without that contract language, the border remains a blind spot.
Above 500 connected tanks, catalog data plans create reconciliation overhead. A project quote with pooled data, a CMP platform, and RESTful M2M API integration lets you activate, deactivate, or reconfigure SIMs over-the-air [1] and track usage per tank. The quote should include per-SIM activation fees and overage terms [8].
According to [1], IoT SIM cards are controlled by management software that allows for remote control and monitoring; network administrators can activate, deactivate, or reconfigure SIMs over-the-air. That capability is essential for large-scale deployments—for example, 500 tanks each sending 500KB per month [6]—where manual handling of SIMs is not feasible. The table below maps procurement dimensions for that payload, comparing catalog pricing, project quotes, and eSIM/CMP impact. It also shows where the border-crossing failure mode from the field gets fixed in the contract.
| Dimension | Catalog pricing | Project quote | eSIM / CMP impact |
|---|---|---|---|
| --- | --- | --- | --- |
| Data volume per tank | 500KB/month [6] | Pooled data across tanks | eUICC supports remote carrier switch [8] |
| Network switching | Single or steered network | Multi-network + automatic switching [1] | eUICC supports remote switch [8] |
| Remote management | Basic portal | CMP platform + API [1] | Activate/deactivate/reconfigure OTA [1] |
| Module mix | Not specified | LTE Cat.1 bis specified (63% of shipments [7]) | Multi-band eSIM avoids truck roll [7] |
| Activation fees | Published per-SIM fee | Negotiated per-SIM activation [8] | eSIM RSP reduces physical SIM logistics [8] |
When the deployment is a single-country tank network under 250 SIMs with predictable 500KB monthly traffic [6], catalog pricing is sufficient. You can buy a multi-network SIM at a published rate, manage it in the provider portal, and not pay for custom contract work.
When the deployment crosses a border, or involves 100+ trucks where the SIM must switch networks at the border, catalog pricing is not sufficient. The contract needs a project quote that specifies automatic network switching [1], eUICC remote provisioning [8], and roaming limits. A project quote is also the path when you need a CMP platform with API access from day one. Without those clauses, the quote is just a volume discount on a steered SIM.
Choose eSIM for any tank monitor expected to operate past a network sunset. With 63% of module shipments on Cat.1 bis [7], an eUICC SIM with RSP support lets you switch carriers without a truck roll [7][8].
Based on publicly available data and published carrier rate cards, the cost model below uses ranges rather than fixed quotes. The only sourced data point is 500KB per SIM per month [6]; hardware and field-service prices vary by region and integrator. Use these ranges for budgeting, then ask for a project quote when volumes exceed 500 SIMs.
An NB-IoT/LTE-M module with multi-band support typically costs between €6 and €12 per unit based on published module pricing. Adding an eUICC eSIM adds roughly €1 to €3 per unit. For 100 tanks, that is €700–€1,500 of upfront hardware delta for remote provisioning capability. At 500KB per month [6], the module and SIM choice matters more than the data rate for total cost; the premium buys a remote profile switch that avoids a physical SIM replacement later.
Catalog low-volume IoT plans price data at €0.10–€0.50 per MB based on published carrier rate cards. At 500KB per tank per month [6], 100 tanks generate 50MB/month, so connectivity is about €5–€25/month. A project quote for 500+ tanks can lower per-MB pricing.
A CMP platform with API access typically adds €0.10–€0.50 per SIM per month based on published provider pricing. Installation for a tank monitor—sensor, bracket, antenna alignment—runs €25–€75 per site based on published field-service rates. Catalog pricing often includes a basic management portal; a project quote should include API access and bulk activation tools [1][8]. For 500 tanks, that management delta can be €600–€3,000 per year. At 500KB per tank, API-based SIM management becomes the main operational cost after hardware.
Assume a network sunset forces a SIM swap on 100 tanks. Physical SIM replacement costs €20–€40 per site based on published field-service rates. An eSIM avoids the truck roll [7]; the eSIM premium of €1–€3 per unit is covered by the first avoided site visit.
Procurement managers note that a border crossing is where IoT deployments fail, especially for fleets of 100+ trucks, because the SIM cannot switch networks. In a fertilizer-tank context, the equivalent is a tank sitting in a coverage gap while the SIM is steered to one carrier. A project quote for 100+ assets should include a multi-network SIM with automatic switching [1], a CMP platform with over-the-air activation [1], and eUICC remote provisioning [8]. Timeline: catalog SIMs can be activated in days; a project quote with custom API integration typically needs 2–4 weeks from contract signature to first SIM shipment, based on published provider onboarding schedules. The vendor selection logic starts with the network-switch clause: if the provider cannot commit to a switch at the border or coverage boundary, the quote fails the procurement test.
Catalog pricing is enough when the deployment is under 250 SIMs, all tanks are on one carrier's coverage map, each tank sends 500KB per month [6], and you do not need custom API integration. Buy a multi-network SIM from a published rate card and manage it in the provider portal.
Project quote is required when the deployment crosses a border, or when you need automatic network switching for 100+ assets [1]. It is also required when you need eUICC remote provisioning [8], pooled data, or CMP API integration [1]. The quote should name the failover behavior, per-SIM activation fees, overage rates, and network sunset path [7][8]. If the quote does not specify the network-switch behavior at a border or coverage boundary, it is not a project quote—it is a catalog plan with a larger minimum.