Definition
Global SIM Pool is a pooling management capability provided by ICMP, centralizing SIM card resources from multiple countries and operators into a single pool. It supports flexible allocation, data pool traffic sharing, Pooled Data pooled traffic, and Multi-Operator multi-operator aggregation, achieving unified management and efficient utilization of SIM resources across regions.
Core Capabilities
The Global SIM Pool includes: Pooling Management — SIM cards are stocked according to batch, region, and operator, supporting inventory inquiry, allocation, and recovery; Traffic Sharing — in coordination with data pool, multiple cards share traffic quotas to improve utilization; Flexible Allocation — cards can be allocated by customer, project, or order, supporting batch allocation and recovery; Multi-Operator Aggregation — integrating Multi-Operator and Roaming Partner resources for global coverage. Cards in the pool support full lifecycle management including Activation, Suspension, and Decommissioning.
Application Value
The Global SIM Pool helps enterprises reduce procurement and inventory costs, simplify multi-country card management, and improve resource utilization. Customers do not need to interface separately with operators in each country; they can access global connectivity via ICMP. Combined with Cross-Border Card Management and Cross-Border Billing, it provides end-to-end capabilities of 'one pool to manage the world.'
Implementation in ICMP
SimtoLink ICMP's Global SIM Pool covers over 200 countries/regions worldwide, supports physical SIM cards and eSIM; deeply integrates with Multi-Operator and Roaming Partner; provides capabilities such as inventory management, allocation, Activation, Usage Analytics; supports RESTful API and SDK integration.
What May Enter the Pool, and What Allocation Covers
A global SIM pool puts SIMs from different countries, carriers, and form factors into one inventory and allocation ledger. It does not make those SIMs interchangeable connections. Stocking a SIM only means the platform holds its identity, batch, and allocatable status. Whether it can attach still depends on whether the carrier allows provisioning, whether the device supports that network, and whether the target country is inside the SIM’s service footprint. Shared data is a further ledger: only SIMs explicitly placed in the same shared allowance consume one another’s balance. Other SIMs in the same stock pool are still charged on their own plans.
Use the pool when purchasing, stocking, allocation, and provisioning can stay sequential. After intake, sample the batch and confirm the identity is readable and the status is allocatable. Draw a batch for an order or project, then provision that batch. On return, stop service first, then put the identity back into the allocatable set, so the same identity is not live under two customers. If the business is single-SIM retail and does not share data, the pool can be inventory only, with no forced quota sharing. Price belongs on the matching rate card. The word “pool” does not imply one unit price.
Mistaking Stock for an Attached Connection
A common error is to report stock quantity as connections available for sale. A stocked SIM may not yet be provisioned with the carrier, may already be reserved for an unshipped order, or may be frozen with its batch and no longer allocatable. Another error is to assume that entering a global pool automatically grants local rates in every country. The pool concentrates registration and distribution. Coverage and price still follow each SIM’s home network, roaming arrangement, and product rules. Assigning a SIM that may be used in only a few countries to a project elsewhere shows up on site as a failure to attach, while the inventory system still says allocated.
Shared data makes it easy to treat the pool total as a ceiling every SIM can use. Once a few SIMs exhaust the total, the others in the pool are throttled or suspended even if they have used almost nothing. If allocation changes only the customer field on the platform and not the carrier-side ownership, later CDRs post to the old account. When handling the pool, check stock status, provisioning status, sharing scope, and CDR ownership separately. Allocation is complete only when those four agree.
Stock status should at least distinguish awaiting inspection, allocatable, reserved, provisioned, frozen, and pending return. A reservation holds an identity for an order. If the agreed time passes with no shipment or provisioning, release it, or unfinished orders will occupy the available count indefinitely. Freeze is for a batch quality problem. A frozen SIM cannot be allocated and must not be treated as provisioned. Pending return means service has stopped and no new CDRs are arriving, but the identity is not yet back in the allocatable set. Collapsing these into “in stock” and “not in stock” leads warehouse and operations to opposite decisions on the same batch.
Plastic SIMs and embedded SIMs should not sit in one stock pool with no form-factor mark. Plastic SIMs involve shipping, receipt, and damage. An embedded SIM involves whether the profile has already been downloaded to the device. Counting a profile that has not been downloaded as shippable stock leaves the site with nothing to install. A SIM already soldered into a device cannot be taken back through the plastic-SIM return process either. The allocation record should state form factor, target project, and planned country of use, so a batch that covers only a few countries is not sent somewhere outside that plan.
When moving a SIM between customers, stop service and the shared allowance under the old customer, then change ownership, then provision again under the new customer’s product. Changing only the customer name on the stock record leaves the old invoice still receiving CDRs, while the new customer cannot see usage. Usage before and after the move must be cut by time. The same SIM number must not be merged into one record that forever belongs to the last customer.