Definition
An agent price list is the purchase price an enterprise sets for an agent. It states what that agent pays the enterprise for IoT SIMs and plans. It is the price source for agent-price purchasing. The agent reads it in the self-service portal and then places the order.
How prices are set
- By plan: Each plan type can carry its own agent price.
- By volume step: A larger purchase quantity takes a lower unit price, which gives the agent a reason to buy more.
- By agent: Each agent can have a separate list, so a regional agent and an industry agent do not have to share one price.
Where a separate list is used
A regional agent can be priced by territory. An industry agent, for connected vehicles or shared devices, can be priced for that industry. In a multi-level agency, a downstream agent can sit on a different volume step from the parent. Because the list is visible, the agent can look it up and order on the agent self-service portal.
Keeping the list aligned with what is sold
Rows on the list have to match the data plan and the operator product, or an agent-price order will not find a price. The enterprise can keep a different list for each agent grade, region, and industry. When a price changes, orders already placed and not yet settled still need a rule, or the two sides will dispute the amount. On the agent self-service portal the agent sees the list that applies and orders against it.
Volume steps and the share paid later
Volume steps usually run beside the revenue-share rate and sales attribution. A bigger purchase lowers the unit price. Settlement revenue share is then calculated on purchase quantity or sales amount, so the buy price and the later payout pull in the same direction. The list should accept operator, plan type, and region as separate columns, which is what a multi-level agency needs. Keep a version when the list changes, so reconciliation and audit can still see the old price.
From the list to the purchase order
The list is what agent-price purchasing prices against. The agent opens it on the agent self-service portal and orders. Each row has to line up with a data plan and with plan packaging, so the order picks both the price and the product. Different agents can hold different lists, split by region, industry, or level. A change should not silently reprice an order that was bought and is still unsettled. Inside an agent program, this list is one of the settings the rest of the channel flow depends on.
Volume steps on their own
The same list can price each plan at a flat agent price, or drop the unit price as the purchased quantity crosses a step. That drop is meant to reward a larger buy. The step table is read together with the revenue-share rate and with sales attribution when the payout is calculated. Columns for operator, plan type, and region let a multi-level agency keep distinct prices. A version history should remain after each change.