Definition
Agent-price purchasing is an agent buying IoT SIMs and plans from the enterprise at the prices on the agent price list, then selling them to end customers. A distributor is allocated a quota and paid by split at checkout. An agent is managed as a buyer: the price list, the order, the purchase record, sales attribution, and settlement revenue share.
How an order moves
- Set the price: The enterprise publishes the agent price list, by plan and by purchase-volume step.
- Place the order: The agent reads the list on the self-service portal and orders SIMs and plans.
- Keep the record: Each purchase stays on file. Settlement can be a prepayment or an account term.
- Sell and share: Once those SIMs are sold to end users, the sale is credited to the agent and the share is calculated from the rule.
How the price is chosen
The agent price can follow the plan, or a volume step. Each agent can have its own list. A lower unit price at higher volume is there to grow the purchase. A share on sales is there to grow what the agent sells to end users.
What the order does to stock
The agent picks a plan, enters a quantity, and submits on the agent self-service portal. That order takes the SIMs or plans out of enterprise stock and puts them in the agent’s name. The purchase record has to stay complete, because sales attribution and settlement revenue share are calculated from it. A distributor receives stock through resource allocation against a quota. An agent has no quota and buys what it needs. The enterprise still has to keep enough SIMs and plans on hand for those orders.
How the purchase is settled
Payment can be a prepayment or an account term. Purchase records are rolled up on the settlement period into a settlement statement. Sales attribution and the revenue-share rate then produce the settlement revenue share. After the SIM is sold to a consumer, that user’s renewal and plan order stay credited to the agent, and the share follows the rule. Together with the agent price list and multi-level agents, this is the agent program. Operator mapping and the data plan have to be set correctly, or the order cannot match a price to a product.
What the agent does on the portal
On the agent self-service portal the agent opens the agent price list, chooses a plan, enters a quantity, and submits. The order takes enterprise stock and assigns the SIMs or plans to that agent. The record is kept for sales attribution and for settlement revenue share. Unlike a distributor drawing on resource allocation, the agent is not capped by a quota and buys to demand. For the agent model, this purchase is the main transaction.
Which volume tier this order actually hits
A tiered price has to state how volume is accumulated, or the same price list produces two prices. There are three common bases: the quantity on this purchase order alone, purchases already made in this settlement period plus this order, or the running total for the calendar year. Take an order for five thousand SIMs when the month already stands at ten thousand. If the rule is progressive within the period, the unit price should fall into the higher tier. If the rule is per order, it stays on the five-thousand tier. The boundary quantity has to say whether the top of the band is included. “From one thousand” might mean the discount starts at SIM number one thousand and one, or at SIM number one thousand. The order page should show the tier that was hit, the unit price, and the amount lines back to the agent, rather than a single total. When the price list changes, say whether unpaid orders are recalculated. An order whose price is already locked keeps the old tier, and only a new order uses the new tier, so the two sides are not reconciling from different screenshots. SimtoLink agent management keeps the price list, the tiers, and the purchase order on the same channel file. The purchase record has to be able to point back to the tier in force at the time, not only to a final amount.
Prepayment and account terms are not the same stock movement
Moving stock and whether the money has arrived are two separate facts. Under prepayment, a balance that does not cover the order should not move SIMs out of enterprise stock, or the goods sit in the agent’s name with no payment behind them. Under account terms the SIMs can move first and be totaled on the settlement date, but there must be a credit limit or a cap on the open amount. Past that cap, new orders stop. They do not hang on the account without a ceiling. A partial payment cannot mark the whole order complete: the quantity that has been paid can be transferred, and the unpaid quantity stays awaiting payment. When an order is cancelled, only SIMs that have not yet been transferred, or have not yet been activated, can return to the enterprise pool. A SIM that is already activated, or that already has a usage record, goes through a returns approval. It cannot be voided on the purchase order itself. The purchase order number should be written into the SIM’s movement log, so later sales attribution can show which purchase took the SIM out.
When the purchase and the sales credit disagree, which fields to read first
When revenue share is wrong, the rate is often not the field that was mistyped. The record of the SIM leaving enterprise stock lost the agent id. Check in this order: the agent on the purchase order, the target party in the transfer log, the SIM’s current attribution, and the sales attribution on the subscription order. If the four do not agree, the authority is the successful transfer that took the SIM out of enterprise sellable stock, not the latest manual edit of attribution. If the agent sells the SIM on to a downstream party and the platform has no multi-level purchase relationship, the downstream retail order still returns to the original purchasing agent, unless a second attribution was configured in advance. Empty-SIM purchases and purchases that include a plan are booked separately. If only the number is bought and the end user orders the plan later, purchase share and renewal share cannot sit on the same rule. Test orders and gift SIMs should be marked as excluded from revenue share, or a few trial SIMs become money owed to the channel at month end.