Definition
B2B2C (business to business to consumer) is the enterprise selling to a consumer through an agent, a distributor, or another channel. For an IoT SIM, the enterprise sells the SIM to the channel, and the channel sells it to the person who uses it. Payment split fits this path: once the order is paid, the channel’s share can be taken automatically.
What B2B does not include
Plain B2B is the enterprise serving an enterprise customer directly. B2B2C adds a channel and a consumer. The enterprise has to offer user self-service, collection through WeChat Pay or Alipay, real-name registration, and an e-invoice, and it still has to run agents, distributors, and the share those channels earn.
Industries that sell this way
Connected vehicles run from the automaker to a dealer or operator and then to the owner. Shared devices run from the platform to a franchisee and then to the user. Smart hardware runs from the manufacturer to a dealer and then to the buyer. The platform has to cover the whole path: operator connection, plan packaging, data billing, consumer collection, channel share, and white label.
What each of the three roles needs from the platform
The same platform serves the enterprise, the channel, and the consumer. The enterprise connects to the operator, holds SIMs and plans, and sets the channel and the share. The channel gets an agent self-service portal or distributor management, resource allocation, and payment split. The consumer gets user self-service, WeChat Pay or Alipay, real-name registration, and an e-invoice. Once those three are connected, the enterprise reaches consumers through the channel and can operate at that scale.
How the consumer’s payment becomes a channel payout
After a consumer pays, sales attribution on the order can be traced to the agent or distributor who sold the SIM. An agent is paid by settlement revenue share: a settlement statement is raised on the settlement period and then paid. A distributor can be paid by payment split, using the revenue-share rate at the moment of payment. For the IoT Cloud Platform, this is how a B2B SIM business reaches a consumer, and it depends on plan provisioning, the payment callback, and resume actually closing the loop.
The same industries, and the path they share
Connected vehicles, shared devices, and smart hardware are the usual B2B2C cases: automaker to dealer or operator to owner, platform to franchisee to user, manufacturer to dealer to buyer. Each one needs operator connection, plan packaging, data billing, consumer collection, a channel share, and white label. The enterprise does not sell every SIM itself. It reaches the consumer through the channel.
Which slice of data the enterprise, the channel, and the user each hold
In IoT SIM sales, B2B2C is not a slogan. It is three identities present on the same SIM at once. The enterprise holds the number range and the settlement relationship with the operator. The channel holds quota or purchased stock, plus the revenue-share rules. The user holds the binding, the identity record, and the payment order. A SIM query has to be able to answer who bears the cost, whose retail order this is, and who is allowed to operate the SIM after signing in. Those three answers are stored in different fields. The channel id must not be written into the user id, and the enterprise tenant id must not be treated as the channel. If the user rebinds the SIM to another phone number, the channel attribution of the SIM should not move with it. When the enterprise takes unactivated SIMs back from a channel, a SIM already bound to a user has to be unbound or unsubscribed first. Changing the stock count alone is not enough. SimtoLink B2B2C roles and audit should authorize the three identities separately, and the audit log should show whether an enterprise employee, a channel account, or the user themselves requested suspend or resume.
The channel’s buy price and the user’s pay price are not one bill
The price the enterprise gives the channel, and the price the user pays on the self-service page, can have a margin between them, but the system has to keep two bookings. In the agent model, the channel first pays the enterprise the purchase price, and the user then pays the retail price to the channel, or to the enterprise for later sharing. In the distribution model, the user pays one retail price, and that payment is split by rate at the time it is taken. If the page stores only one “selling price,” month end cannot explain where the channel’s margin came from. The retail price from plan packaging, the purchase price on the price list, and the share rate have to be readable together. Changing the retail price must not rewrite a purchase price that has already closed. If a gifted trial allowance also goes through an order whose user payment is zero, a zero-amount order still has to be created, or the channel is missing a traceable stock-out. Who the e-invoice is issued to depends on who paid. A user claiming expenses is invoiced as an individual or as their organization. A channel settlement is invoiced to the channel. The cost bill the enterprise pays the operator cannot be used to invoice the user.
How to book an order when the identity holder and the payer differ
A vehicle owner who is the registered identity, a family member who pays, or a device owner who is not the account that scans to pay, is a common mismatch in B2B2C. Identity information follows the SIM and the regulatory requirement. The payment account follows the funds. The binding account follows who can sign in and query. The three identifiers are allowed to differ, but the order has to record all of them. Finding the SIM only by the payer books a family member’s payment to the wrong vehicle. Finding the order only by the registered identity cannot match the buyer in the payment channel when the person who paid asks for a refund. The refund should return to the original payment account, not to the bank card on the identity record, unless an offline approval was used. When a channel advances the money for the user, that money is the channel’s purchase or prepaid consumption. It is not a user order, and it must not earn the channel another share at the retail price. A SIM whose identity check is unfinished can be blocked from activation or from resume. That block is written on the SIM status. It should not be written as a payment failure. Payment can succeed and leave provisioning pending, and provisioning can run after the identity check is completed. The two failure codes cannot be shared, or the channel will collect again as if the payment had failed.