> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/core-product-structure/sim-options-and-fulfilment-models.md).
# SIM Options & Fulfilment Models
Supported SIM types and fulfillment models, plus inventory, MOQ, and customization options.
### Overview
Reach supports multiple **SIM types** and **fulfilment models** to match different **launch strategies**, **distribution channels**, and **device experiences**.
This page covers how each SIM model works, how inventory is managed, and how brands can order and receive bulk physical SIM stock.
All models run on the same **provisioning** and **activation** framework. What changes is:
* **How SIMs are delivered**
* **Who manages inventory**
* **How activation happens**
* **What branding and customization options are available**
### At a glance
* **Brand-held inventory:** bulk pSIM orders start at **500** and ship to one location per request
* **Supported SIM types:** pSIM, eSIM, and SIM-in-hand and
* **Inventory models:** Reach-managed, brand-held, and hybrid
* **This page includes:** lifecycle flows, bulk ordering, and generic vs custom SIM options
### Brand-managed SIM inventory, ordering, and customization
Brands can choose how SIM inventory is held and how bulk physical SIM orders are supplied.
* **Inventory models:**
* Reach-managed
* Brand-held (SIM-in-hand)
* Hybrid
* **Controls:**
* MOQ for physical SIMs
* Bulk shipment to brand locations
* Custom SIM branding
* Custom kits, packaging, inserts
{% hint style="info" %}
MOQ, customisation scope, and logistics vary by commercial agreement. For brand-specific details (MOQ, branding feasibility, kit components, pricing, and logistics), contact your Reach Account Manager.
{% endhint %}
### SIM types and lifecycle flows
The sections below show each supported SIM type and how its lifecycle works in practice.
### Supported SIM types
Reach supports:
* **Physical SIM (pSIM)**
* **Embedded SIM (eSIM)**
* **SIM‑in‑hand (brand‑held physical SIM inventory)**
Each SIM type follows a defined lifecycle from provisioning to activation.
#### Decision driver
| Area | Impact |
| ---------------- | ----------------------------------------- |
| Customer Journey | Digital vs physical onboarding experience |
| Logistics | Shipping vs instant delivery |
| Branding Control | Standard vs fully customizable |
| Time to Launch | Immediate vs setup-dependent |
### 1) Physical SIM (pSIM)
#### What it is
A physical SIM (pSIM) is a removable SIM card. It is shipped to the end customer as part of a SIM kit (or welcome kit).
The customer inserts the SIM into a compatible device to enable network access.
Standard Physical SIM Kit
#### pSIM lifecycle (inception to activation)
{% stepper %}
{% step %}
**Provision and stock SIMs**
Reach sources pSIM inventory per the agreed commercial model.
SIMs are registered in the Reach inventory and made available for assignment.
{% endstep %}
{% step %}
**Reserve a SIM for an order**
A SIM is reserved when a customer order is created.
A reservation prevents the double allocation of the same SIM.
Reservation links a SIM to an order and prevents it from being assigned to another customer.
It does not activate the line.
{% endstep %}
{% step %}
**Fulfillment**
Reach (or the brand, depending on the model) ships the SIM kit to the customer.
Tracking and shipment status flows back into the platform.
{% endstep %}
{% step %}
**Activation**
Customer activates service using the SIM’s activation identifier (typically a barcode).
Reach provisions service with the network and confirm line activation.
{% endstep %}
{% endstepper %}
### 2) Embedded SIM (eSIM)
#### What it is
An eSIM is a digital SIM profile. It is installed on a compatible device.
No physical SIM card is shipped.
#### eSIM lifecycle (inception to activation)
{% stepper %}
{% step %}
**Provision eSIM profiles**
Reach (and the underlying carrier stack) provisions eSIM profiles for the tenant.
Profiles are made available for assignment during the purchase or SIM-change flow.
{% endstep %}
{% step %}
**Assign and deliver the eSIM**
The eSIM is delivered electronically.
Common delivery patterns include:
* QR code display/download.
* In-app installation prompts.
{% endstep %}
{% step %}
**Install on device**
Customer installs the eSIM on a compatible device.
Device connectivity depends on device OS support and carrier bundle behavior.
{% endstep %}
{% step %}
**Activation**
After installation, Reach completes provisioning and confirms line activation.
See also: [Activation identifiers](/core-product-structure/product-catalog-offering/account-and-customer-management.md).
{% endstep %}
{% endstepper %}
### 3) SIM‑in‑hand (brand-held physical SIM)
#### What it is
SIM‑in‑hand is a model where physical SIMs are shipped in bulk to the brand.
The brand distributes SIMs to customers via its own channels. Examples include retail stores, enterprise onboarding, field sales, or device bundles.
#### Brand-held inventory
In the **brand-held** model, Reach ships physical SIMs to the brand in bulk.
The brand then stores, manages, and distributes that inventory through its own channels.
This model is commonly used for:
* retail stores
* field sales
* enterprise or partner distribution
Distributing a SIM does not activate service.
Activation happens later when the SIM identifier is used in an activation flow.
#### How brands place bulk orders with Reach
Use this flow when the brand needs physical SIMs for brand-managed inventory.
{% stepper %}
{% step %}
### Submit the request
The brand submits a bulk SIM order request through Reach.
The request includes:
* **SIM type:** physical SIM (**pSIM**)
* **Quantity:** minimum **500** SIMs, in multiples of **500**
* **Delivery address:** one delivery location per request
* **Additional details:** delivery notes or internal reference IDs, if needed
If the brand needs more than one shipment location, each location must be submitted as a separate request.
{% endstep %}
{% step %}
### Review and confirm
Reach reviews the request for completeness and eligibility.
Once accepted, Reach confirms the order through the request workflow.
Standard handling is:
* **Payment terms:** NET 30 from invoice
* **Delivery timeline:** typically **4–8 weeks** from confirmation
{% endstep %}
{% step %}
### Prepare the shipment
Reach allocates inventory, prepares the correct SIM SKU, and queues the order for fulfilment.
No end-customer details are needed.
This is a bulk shipment to the brand, not a subscriber-level order.
{% endstep %}
{% step %}
### Dispatch and track
Once packed, the shipment is dispatched to the requested delivery address.
Tracking details are shared through the same workflow.
Status updates typically include:
* dispatched
* in transit
* delivered
{% endstep %}
{% step %}
### Receive into brand inventory
Once delivered, the SIMs become brand-managed inventory.
The brand can then:
* store SIMs for future use
* distribute SIMs through brand channels
* use the SIMs in later activation journeys
{% endstep %}
{% endstepper %}
#### SIM‑in‑hand setup and logistics
* Reach ships SIM inventory in bulk to brand-specified locations.
* The brand controls downstream distribution and on-hand inventory.
* SIM activation still occurs in Reach journeys using the SIM’s activation identifier.
Distributing a SIM to a customer does not activate service.
Activation occurs only when the SIM identifier is used and the line is activated.
#### SIM‑in‑hand lifecycle (inception to activation)
{% stepper %}
{% step %}
**Bulk inventory delivery**
Reach delivers physical SIM inventory to the brand.
SIMs are registered in the Reach inventory before distribution.
{% endstep %}
{% step %}
**Brand distribution**
The brand distributes SIMs to customers through brand-owned channels.
This can happen before or after a purchase, depending on the channel.
{% endstep %}
{% step %}
**Activation**
Customer (or an agent) activates service by entering/scanning the SIM identifier.
Reach completes provisioning and activation with the network.
{% endstep %}
{% endstepper %}
### Generic vs Customized SIM
| Area | Generic SIMs | Custom SIMs |
| ------------------- | ---------------------------------------------------- | ----------------------------------------------------------------------- |
| Availability | Immediate availability. No custom profile setup. | Setup required before launch. |
| SPN | Standard SPN: “Home” on-network, “Roam” off-network. | Custom SPN. Brand name appears on device. |
| SIM card printing | Standard SIM card format. | Custom SIM card printing. |
| SIM kit | Standard SIM kit packaging in SMART KIT formats. | Custom SIM kit with brand colors, fonts, and layout within constraints. |
| Support details | Standard support details. | Custom support details, including phone and email. |
| Activation URL | Standard activation URL. | Custom activation URL. |
| QR behavior | Standard QR behavior. | QR can redirect to the brand app. |
| Supported SIM types | Supports pSIM and eSIM. | Supports pSIM and eSIM. |
| Timeline: pSIM | \~4 weeks | \~12 weeks for first run, \~6 weeks for repeat runs |
| Timeline: eSIM | \~2 weeks | \~2–3 weeks |
{% hint style="info" %}
Questions or clarification? Reach out to your respective account manager or email us at for help and support.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.reachplatform.com/core-product-structure/sim-options-and-fulfilment-models.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
