Definition
Resource allocation is the mechanism by which a company allocates card pool and data plan pool quotas to distributors, controlling channel inventory. Distributors can allocate quotas to lower-level distributors, forming a tiered allocation. Once the quota is used up, additional requests must be applied for. Unlike agents who purchase at agent prices (without quota limits), resource allocation is the core of the distributor model.
Allocation Dimensions
- Card pool quota: The maximum number of IoT SIM cards that can be issued and activated in the allocation; distributors issue cards to C-end users within the quota.
- Data plan pool quota: The allocated quantity or monetary limit of data plans that can be sold, controlling the scale of data plan sales.
- Tiered allocation: After a first-level distributor receives a quota, it can redistribute it to lower-level distributors, forming a multi-level quota tree.
Difference from Agents
Agents purchase at the agent price on the agent price list. The purchase occupies enterprise inventory at once, and there is no pre-allocated quota. Distributors receive a quota through resource allocation and sell within it. When the order is paid, profit is shared automatically through payment splitting. Resource allocation lets the enterprise control channel inventory and risk.
Allocation Process and Quota Management
After the company creates card pools and data plan pools, it allocates quotas according to the distributor hierarchy. Once a primary distributor receives a quota, they can reallocate to their subordinates, forming a multi-level quota tree. When the quota is exhausted, distributors must request an additional quota from the company or their superior. The platform needs to support quota inquiry, quota modification, and quota usage statistics. Resource allocation works in conjunction with payment splits: distributors sell to C-end users within the quota, and when the user pays, the amount is automatically shared with the split receivers at each level according to the profit-sharing ratio. Quota control can prevent channel overstocking and reduce company capital and inventory risks.
Resource Allocation and Sales
Within the quota, distributors open cards and sell plans to C-end users. Sales attribution on the order can be traced to the distributor level. After the user pays, payment splitting automatically shares the amount with each level according to the profit-sharing ratio. Resource allocation contrasts with an agent purchase at the agent price: an agent purchase occupies inventory, and there is no pre-allocated quota; a distributor sells within a quota, and the profit share happens when the order is paid. Resource allocation is the core control for the distributor system under the B2B2C model. It has to work with card-pool management and data plan configuration on the IoT Cloud Platform.
Quota Management
Resource allocation supports card pool quotas, data plan pool quotas, and hierarchical allocation. After first-level distributors receive quotas, they can redistribute them to lower levels, forming a multi-level quota tree. When the quota is exhausted, distributors need to apply to the enterprise or higher level for additional quotas. The platform should support quota inquiry, quota changes, and quota usage statistics. Quota control can prevent excessive channel stockpiling, reducing enterprise funding and inventory risks. Resource allocation is the core of the distributor model, and it is used together with payment splitting and the split receiver.
Which action deducts the quota
Resource allocation assigns the number of cards that may be sold, the number of plans that may be sold, or an amount ceiling, down the levels to distributors, so a channel can open cards and sell plans only inside its quota. It governs permission to use stock. It is not a profit-sharing ratio. The parameters that matter are the quota type, the quantity remaining, whether a lower level may allocate further, and the moment of deduction. If deduction waits until the user pays successfully, a channel can first hold up the display with a large number of unpaid orders. When payment fails and the quota is not returned, fake orders eat the quota. If deduction happens at the moment of the order, quota must be added back when the order is closed or payment times out. Otherwise a cancelled order occupies stock permanently.
Card-pool quota and plan-pool quota are counted separately. Opening one silent card consumes card quota and does not automatically consume plan quota. The plan quota is consumed later, when the user buys a monthly pack for that card. If the two pools share one number, cards can still be opened after plans are already oversold, or plans are plentiful while cards cannot be issued. An added quota should record whether the source is a transfer from the level above or an increase from the enterprise. Quota taken back cannot fall below the quantity already occupied.
How redistribution to a lower tier avoids overselling
When a first tier reallocates its own quota to a second tier, the first tier’s available quantity goes down and the second tier’s available quantity goes up. The enterprise total does not change. If the system only adds to the second tier and does not subtract from the first, the same batch of cards can be sold by two channels at once. Taking quota back runs in the opposite direction, and only the part the second tier has not yet occupied can be taken back. A cross-level view has to show occupied, available, and frozen as three columns. Frozen means ordered but not paid, or already allocated to a lower level that has not opened the card yet.
It is easy to build resource allocation as if it were an agent purchase. An agent purchase settles money and goods, and ownership of the card or settlement responsibility has already moved. A distribution quota is a permission. The card stays in enterprise stock until it is sold, and only then does attribution change. After the two are mixed, month-end settlement treats quota that has not been sold as sales revenue. SimtoLink’s distributor management maintains this quota tree. The card-opening and ordering APIs read the remaining quota before they run and refuse the request when it is short, instead of smoothing a negative quota after the fact.
Frozen, occupied, and available are not the same number
The remaining quota a distributor sees has to be split into at least three columns. Available is the quantity that can be newly opened right now. Frozen is ordered but not paid, or already given to a lower level that has not opened the card yet. Occupied is already opened or already sold, and cannot be taken back. If only one remaining number is shown, the channel treats frozen quantity as still sellable. After payment times out, frozen quantity is released back to available. After a grant to a lower level, the upper level’s available quantity decreases and frozen quantity, or the lower level’s available quantity, increases. The enterprise total does not change. SimtoLink distribution quota deducts only available quantity in the card-opening API. It does not deduct frozen quantity a second time.