Pooled, Shared, or Individual: Which IoT SIM Plan Structure Is Right for Your Saudi Fleet?

STC, Mobily, and Zain all offer M2M data plans in three structures: individual, shared, and pooled. The names suggest minor variations on the same product. In practice, the structures behave very differently, and choosing the wrong one for your deployment profile creates ongoing cost problems or service interruptions.

The decision comes down to how predictable and uniform your data usage is across devices. A fleet of identical GPS trackers on similar routes will have consistent per-device consumption. A mixed IoT deployment with vehicle trackers, cold chain sensors, and video cameras will have wildly different consumption profiles across device types. Here is how each plan structure handles each scenario.

Individual Plans: Predictable but Inflexible

In an individual plan, each SIM has its own dedicated monthly data allowance. If a SIM's allocation is 100MB and the device uses 80MB, 20MB is wasted. If the device needs 120MB, it runs out early — what happens next depends on the carrier: some throttle to a very low speed, some suspend the SIM until the next billing cycle, some charge overage fees.

Individual plans work well when you know exactly how much data each device uses and that usage is consistent from month to month. A GPS tracker sending position every 30 seconds, on a vehicle that operates a regular shift pattern, uses roughly the same amount of data each month. If you have 200 identical trackers on similar routes, individual plans at a calibrated allocation are simple to manage and predictable to budget.

The risk with individual plans is the tail. Even in a homogeneous fleet, some devices will occasionally exceed their allocation — a vehicle parked in a remote area where it keeps trying to reconnect, a tracker that malfunctions and floods the server with data. Without pooling, each SIM absorbs its own overages independently.

Shared Plans: Low Cost, Low Flexibility

In a shared plan, a fixed total data allocation is divided evenly across all SIMs at the start of the month. 100 SIMs on a 10GB shared plan each get 100MB. Unlike individual plans, the allocation is pre-divided — a SIM cannot draw more than its share even if other SIMs are using nothing.

Shared plans are typically the cheapest per-MB option when carriers offer them, because the carrier is essentially selling bulk data with simple distribution. The trade-off is zero flexibility. If a vehicle makes an unusually long run one month and its SIM needs 200MB, it hits its limit at 100MB with no way to draw from neighbouring SIMs' unused allocations. This makes shared plans unsuitable for deployments with variable or unpredictable usage.

Shared plans are a good fit for sensor deployments where every device does the same thing — a set of cold chain sensors, all identical, all reporting at the same interval. If you have verified through a pilot that each sensor uses under 10MB per month and you have 100 sensors, a 1GB shared plan gives you headroom and costs less than 100 individual 10MB plans.

Pooled Plans: Flexible and Cost-Efficient at Scale

In a pooled plan, all SIMs draw from a single shared data pool. There is no pre-division. A SIM that needs 200MB this month gets 200MB. A SIM that needed 100MB last month but only uses 20MB this month contributes the unused 80MB back to the pool for other devices to use.

For most fleet deployments, pooled plans are the optimal structure. A fleet of 200 trucks will have variable usage: some trucks are idle because of driver leave, breakdowns, or seasonal project slowdowns. Their unused allocation flows to active vehicles. In practice, a pooled plan with a total allocation sized at the average expected consumption — rather than the maximum possible — is consistently adequate because peaks and troughs across the fleet cancel out.

Pooled plans require active management. If the entire pool runs out before month end, all SIMs throttle simultaneously. The tools that matter: real-time usage dashboards (available through Mobily's Jasper platform and STC's enterprise portal), automated alerts when the pool reaches 80% consumed, and the ability to add a data top-up for the current month without waiting for the billing cycle to reset.

Right-Sizing Your Pool or Allocation

The most common mistake with M2M plans is wrong-sizing. Over-sizing (buying more data than you use) wastes money. Under-sizing causes service interruptions. The correct approach:

• Run a pilot of 10–20 devices for 60 days on individual plans, tracking actual consumption
• Identify the average, the 90th percentile, and the maximum per device per month
• For pooled plans: size the total pool at average consumption × 1.2 (20% headroom)
• For individual plans: size each allocation at the 90th percentile consumption
• Review sizing quarterly for the first year — usage patterns change as operations scale

Mixed Deployments: Different Plan Types for Different Device Types

A single fleet deployment often contains multiple device categories: GPS trackers, in-cab Wi-Fi access points for driver apps, cold chain sensors, and tyre pressure monitors. These have very different consumption profiles. One approach that works well: individual or pooled 4G plans for the high-usage devices (trackers, Wi-Fi), and a separate NB-IoT shared plan for the low-usage sensors. Managing two plans with different structures is marginally more complex than a single plan, but it avoids the cost of over-provisioning sensors to accommodate tracker consumption patterns.

Overage Handling: Know Before You Sign

All three Saudi carriers handle SIM overages differently — and the contract terms are not always prominently disclosed. Before signing an M2M contract, confirm in writing: what happens when a SIM hits 100% of its allocation? (Throttle to 128kbps? Suspend? Charge per-MB overage?) What is the per-MB overage rate if applicable? Can the account manager add mid-month top-ups via the portal or API, or does it require a phone call? For critical GPS tracking applications where a suspended SIM means a vehicle goes dark, overage suspension is not acceptable — negotiate for throttling or automatic top-up instead.