In the SMM supply chain, the provider supplies and delivers the services, and the reseller sells those services to their own clients at their own prices. A child panel is a separate storefront that runs on top of another panel's services. Each role handles a different part of an order, so knowing who does what makes client questions much easier to answer.
What does an SMM provider do?
A provider is the wholesale source of the services. The provider publishes a services list, takes orders from the dashboard or by API, and handles delivery. The provider also sets the rules for each service, such as minimum and maximum quantity, average time and whether refill is offered.
On a provider panel, each service row usually shows:
- the price per 1,000
- the min and max quantity
- the average time
- whether the service has refill, and the refill period if it does
- whether drip-feed is available
The provider also reports order statuses and handles refills on eligible completed orders. For example, if a reseller orders 2,000 views and only 1,500 can be delivered, the provider marks the order Partial and refunds the undelivered remainder to the reseller's balance. You can see how these service details look on the helnsocial services list with prices, min/max and refill options.
What does an SMM reseller do?
A reseller buys services from a provider and sells them to their own clients. The reseller owns the client relationship. That covers pricing, client communication, collecting the correct links and explaining results.
Resellers come in several shapes. Some are agencies that add social growth to a larger package. Others are freelancers taking orders from a handful of clients, or panel owners running their own public website with a self-built storefront connected to a provider by API.
For example, a freelancer might buy 1,000 followers at a wholesale price, sell that package to a client at their own price, and keep the difference. The freelancer places the order, checks the status, and tells the client what to expect. If you are setting this up from scratch, the guide on how to start an SMM reseller business covers the first steps.
What is a child panel?
A child panel is a ready-made SMM panel website that runs on another panel's services. The owner gets their own domain and storefront, but the service catalogue and order processing come from the parent panel. The owner sets their own prices and serves their own customers.
Think of it as a reseller with a shop window. The child panel owner does not run delivery. They pass orders up the chain and present the results to their buyers under their own brand.
For example, an agency might run a child panel so its regular clients can place small orders themselves at any hour. Every order a client places there still goes to the parent panel for delivery.
How is a child panel different from an API storefront?
With an API storefront, the reseller builds or sets up their own website and connects it to a provider with an API key. With a child panel, the website itself comes ready-made from the parent setup. Both end with the same result: orders flow up to the provider and statuses flow back down.
How do the three roles compare?
The table below shows who is usually responsible for each part of an order. Exact setups vary, but the split of work stays fairly stable.
| Task | Provider | Reseller | Child panel owner |
|---|---|---|---|
| Delivers the service | Yes | No | No |
| Sets wholesale price per 1,000 | Yes | No | No |
| Sets the client's retail price | No | Yes | Yes |
| Owns the client relationship | No | Yes | Yes |
| Defines refill period and min/max | Yes | No | No |
| Collects the correct link from the client | No | Yes | Yes |
| Explains statuses to the end client | No | Yes | Yes |
| Runs its own branded website | Yes | Optional | Yes |
The pattern is simple. The provider handles the service itself. The roles further down the chain handle people, prices and communication.
How does a single order move through the chain?
Following one order from start to finish shows where each role steps in. Here is a worked example with numbers used only for illustration.
- An end client asks an agency for 5,000 views on a video and sends the link.
- The agency checks the link, then places the order on its provider panel, either in the dashboard or through the add order API call.
- The order shows Pending. It has been received but has not started yet.
- The status may move to Processing. This means the order was sent to processing and is usually waiting to start. It does not mean delivery is underway.
- The status changes to In progress once delivery has started. The start count is recorded at this point. For example, the video had 1,200 views when the order started.
- The order finishes as Completed, so the target is 1,200 + 5,000 = 6,200 views.
- The agency reports the result to its client.
If some views drop later and the service has refill, the agency can press the refill button within the refill period shown on the service. Refill restores the count down to start count plus ordered amount, so 6,200 in this example. If the count falls below the starting 1,200, no refill is done until it is brought back up to 1,200.
Which order statuses should resellers explain to clients?
Clients rarely see a provider dashboard, so resellers translate statuses for them. Getting the wording right prevents most support conversations.
- Pending: the order was received but has not started.
- Processing: the order was sent to processing and is usually waiting to start. Delivery is not underway yet.
- In progress: delivery has started.
- Partial: part of the order was delivered and the undelivered remainder was refunded to the balance.
- Completed: the order was fully delivered.
- Canceled: the order did not go ahead and the charge returned to the balance.
For example, a client who sees no change on a Processing order may think something is wrong. A short note that the order is waiting to start usually settles it.
Who is responsible when a link is wrong?
The link is collected at the reseller or child panel level, so checking it is their job. The provider delivers to the link it receives. On helnsocial, the link on an existing order cannot be changed, so a wrong link needs a new order.
For example, if a client sends a private profile link or a link to the wrong post, the order cannot simply be redirected. A quick check before ordering saves both money and a difficult conversation with the client.
How do balances and money move between the roles?
Each level in the chain pays the level above it. A reseller adds funds to their provider balance, and each order is charged from that balance. The reseller collects payment from their own clients separately, on their own terms.
Refunds follow the same path. When an order is Partial or Canceled, the provider returns the amount to the reseller's balance. For example, if a reseller paid for 3,000 likes and 2,400 were delivered, the cost of the missing 600 goes back to the balance, and the reseller decides how to handle it with their client.
Where does the API fit in the supply chain?
The API connects a reseller's own system to the provider. With an API key, a storefront can pull the services list, add orders, check status for one order or many, request refills, cancel where allowed and read the balance. This is how panel owners automate orders instead of placing each one by hand.
For example, a panel owner with a public storefront might receive dozens of small orders a day. Each one is passed to the provider by an add order call, and a multi status call later updates them all at once. The helnsocial API v2 documentation lists every available call, and the SMM panel API guide explains how to use them.
What should resellers keep in mind about platform rules?
None of the roles in the chain sets the rules of the social platforms themselves. Platforms set their own rules on what counts and how engagement is reviewed. Read the official policy before promising a client a result, especially for followers, watch hours or monetization goals.
For example, a client asking for help reaching a monetization threshold should hear that the platform makes the final decision. Clear wording at the start keeps expectations realistic. If the topic touches legal questions in your country, check your local rules.
What this means for resellers and agencies
Your job sits between the service and the client. The provider delivers and defines each service, while you set prices, check links and explain statuses in plain words. Once your clients understand start count, refill period and Partial orders, most questions answer themselves.
When you are ready to place orders yourself, create an account and get your API key.
Frequently asked questions
Can a reseller also run a child panel?
Yes. Many resellers start by ordering for clients directly and later add a storefront, either a child panel or their own site connected by API.
Do end clients ever deal with the provider directly?
Usually not. The reseller or child panel owner handles all client contact, and the provider only sees the orders placed on its panel.
Does drip-feed change who does what?
No. Drip-feed only spreads delivery over time on services that support it. The reseller still sets it up and explains it to the client.