Definition
The agent self-service portal is the online desk built for an agent. The agent looks up prices, places a purchase, and reads purchase history and settlement revenue share without waiting on an operations contact.
What the agent can do there
- Read the price: Open the enterprise agent price list and see the purchase price of each plan and each volume step.
- Order online: Buy IoT SIMs and plans at the agent price. The purchase stays on record.
- Review purchases: Filter past purchases by date and by plan.
- Read the share: Open sales attribution and the share calculation when reconciling.
Why a channel uses it
Moving price checks, orders, and share lookups onto the portal cuts the back-and-forth with operations. The agent can see the price rule and the share rule, and can trace each purchase. Prepayment and account terms are both available, so the portal is not locked to one way of paying the enterprise.
Screens and who may open them
A typical portal covers price lookup against the agent price list that applies, online purchase of SIMs and plans with a quantity and a submitted order, order status from unpaid through paid to in delivery, share detail for each settlement period including the settlement statement and the amount, and account settings for profile, password, and the payout account. A higher-grade agent can be given a different price and a wider permission set. Data is separated from the main console: the agent sees only its own records. With white label, the enterprise can put its own brand and layout on the portal.
SIMs the agent can manage after purchase
SIMs bought through the portal show up there with status and data plan. The agent can activate, suspend, and resume them. After a SIM is sold to a consumer, sales attribution stays with that agent, and settlement revenue share uses the revenue-share rate. The portal and user self-service are the two fronts of the same platform: the agent buys and manages SIMs, and the consumer binds a SIM and renews. For agents, this portal is the main door into the IoT Cloud Platform.
What is on the menu
The menu is price lookup for the applicable agent price list, online purchasing, order management, share detail by settlement period and settlement statement, and account management. Each agent grade can carry its own price and its own permissions. The agent cannot see another agent’s records, and cannot see the enterprise-wide pool. White label changes the brand and the styling the agent sees. It does not merge that agent’s data with anyone else’s.
What orders are visible after sign-in
The boundary of the agent self-service portal is that it shows only data tied to that agent. It is not the enterprise console with a different skin. The price list shows only the rows that apply to that agent’s grade and region. Floor prices for other grades should not be in the API response, not merely hidden on the page. Purchase records, SIMs in the agent’s name, and revenue-share lines all filter by agent id. An export has to apply the same filter, or the file walks around the list permission. If a downstream agent is allowed to sign in to the same portal, the default is that they see their own purchases and the SIMs they developed. Whether a parent can see a child’s detail is a separate grant. A parent-child link in the organization tree does not open it by itself. Unpaid orders, transferred numbers, and draft settlement statements sit at different sensitivity levels: a buyer may receive the number file, while the settlement amount may be limited to the finance account. After the session times out, an old export link must not still download the full number list. If SimtoLink offers the portal as white-label, swapping the mark and the domain does not move this data boundary. Brand settings and permission settings stay apart.
What to check when the order button is disabled
When an order fails in the portal, do not start by editing the price. Walk the conditions the page can actually collect: whether the plan is still on the shelf, whether it is on this agent’s price list, whether stock still covers this order’s quantity, whether the prepaid balance or the account-term limit covers the amount, and whether the account has query rights but no purchase rights. Stock that looks available but fails on submit often means available stock has already subtracted quantity locked by unpaid orders, while the list still counts that locked quantity as sellable. If the SIM and the plan must be bought together, both stocks have to be satisfied at once. If there are enough SIMs and not enough plans, the message should say which item is short. A double click produces two orders, so the portal should treat the purchase request id as idempotent and create only one purchase order for the same request id. If the enterprise changes the price after the page was opened, submit should reprice on the server and ask the user to confirm the new amount. It should not keep the old unit price cached in the browser.
Suspend and resume on the portal are not the main console buttons
An agent can see SIMs in their name on the portal. That does not mean they can run the batch suspend or the attribution change that belongs to the enterprise. The allowed actions should be an explicit list: query, activate against a purchase order, start a renewal for a SIM suspended for nonpayment, and view revenue share. What should not be open by default includes transferring a SIM to another agent, editing the price list, resuming while skipping identity checks, and exporting the enterprise’s whole number range. For a SIM suspended for a violation or frozen by hand, “pay and resume” on the portal should be refused, and the suspension reason code should be shown, so the channel does not treat it as a failed payment. Portal order status and main-platform order status should use the same purchase order number. The portal must not show paid while the main platform still shows awaiting transfer. If the white-label portal’s support number is changed to the agent’s own number, the ticket should still be able to bring back the SIM status from the enterprise side. Otherwise the user calls the channel, and the channel cannot see the operator receipt in the portal.