Launch your panel

Child Panels — Selling to Other Resellers

Panel Business 10 min read·

Selling to other resellers instead of to consumers sounds like the obvious upgrade: bigger orders, fewer customers, less support. Some of that is true and some of it is the opposite of true. A child panel changes who your customer is, and that changes the margins, the support load and the failure modes in ways that are worth understanding before you offer it. This post covers what it actually is and where it gets harder.

What a Child Panel Is

A child panel is a storefront you give someone else, running on their own subdomain or domain with their branding, while fulfilment flows through your panel to your providers.

From their side it is their business. Their customers see their name, pay their prices, and never know you exist. From your side they are a single wholesale account whose order volume is the sum of all their customers.

That is different from giving someone a discounted account on your panel. With a discounted account they are your customer using your storefront. With a child panel they have a storefront of their own, and their customers belong to them.

It is also different from API access. An API lets someone connect their own system to yours; a child panel gives them a working storefront without building anything. Some people want one, some the other, and a few want both.

The practical distinction that matters for you: with a child panel you are now a supplier, and suppliers are judged on reliability rather than on service.

The Economics Are Thinner Than They Look

This is the part that surprises people, so here are the mechanics.

Your margin on a child panel order is the gap between what you charge them and what your provider charges you — and they are buying at wholesale, so that gap is narrower than your retail margin by definition. On real panels retail blended margin runs around 65%. Wholesale to a reseller is necessarily below that, because you are now competing with the provider they could go to directly.

What you are selling for that thinner margin is not the service. It is the absence of setup: they do not need provider accounts, minimum deposits, currency conversion, or the knowledge of which services actually deliver. That is real value, and it is what the margin is for.

The volume argument only works if the volume arrives. A child panel with no customers of its own sends you nothing, and most new panels take very few orders — so a dozen child panels can easily produce less than one good retail channel.

So the honest model is: thinner margin per order, potentially more orders, and a portfolio where most of them do nothing.

Support Does Not Go Away, It Changes Shape

The expectation is fewer, more competent customers. The reality is different in a specific way.

You get fewer messages, but they are harder. A consumer asks why their followers have not arrived. A reseller asks why service 412 returned a different start count than the API reported, or why their child's order forwarded but yours did not. These take longer and you cannot answer them with a template.

You also inherit their problems at one remove. When their customer complains, they come to you, often with incomplete information and with their own customer waiting. You are now the second line of a support chain you cannot see into.

And the timing is worse. A consumer can wait until morning. A reseller with a customer waiting cannot, and they will judge you on how fast you answer rather than on how well.

The thing that reduces this load is not being more responsive. It is making the information available without you — order status, provider errors surfaced plainly rather than swallowed, and refunds that land automatically.

Four Things That Make It Harder Than Expected

In rough order of how often they cause trouble.

Price transparency. Your child can see your rates and can find your provider's public rates. If the gap looks unreasonable they will go direct, and the ones with volume are exactly the ones who will check. Your pricing has to be defensible rather than opportunistic.

Concentration risk. If one child grows into most of your volume, you no longer have a portfolio — you have one customer who now has leverage over your pricing, and whose departure would take most of your revenue with them.

Failure amplification. A dead service on your panel used to affect your own customers. Now it affects every customer of every child panel simultaneously, and you hear about it from all of them at once. The concentration data makes this worse: roughly 20 services carry half of all orders, so one dead service is a large event.

Disputes you did not witness. When a child's customer claims non-delivery, you are arbitrating with no view of what was promised. This is why order records, timestamps and stored start counts matter more once you have children than they did before.

Who Should Actually Offer This

Being direct, because the wrong fit wastes months.

It makes sense if your fulfilment is genuinely reliable — provider health monitored, dead services caught quickly, automatic refunds. A supplier's entire value is reliability, and offering wholesale on shaky fulfilment converts one unhappy customer into a chain of them.

It makes sense if you already have people asking. Resellers who want a child panel usually ask for one; manufacturing that demand is much harder than serving it.

It makes sense if you can hold a defensible price — near enough to your provider's rates that going direct is not obviously worth the effort.

It does not make sense as a fix for slow retail sales. If your own panel is not selling, a child panel does not add demand; it adds people depending on infrastructure that has not been tested under load.

And it does not make sense if you cannot answer a technical question within a few hours during the evening, which is when both your orders and theirs peak.

What to Have in Place First

A short readiness list, all of which you would want anyway.

Automatic order forwarding, with retries. A human in the loop cannot serve a chain.

Automatic refunds to wallet on failure. This is what stops one provider problem becoming a dispute at every level of the chain.

Provider health checks that run without you — balance reads and stale-sync alerts. You are now the reason someone else's business works.

A mapped backup service for each of your top sellers, so an outage is a switch rather than a search.

Order records you can actually cite: timestamps, start counts, provider responses. When you arbitrate a dispute you did not witness, these are the only facts available.

And a price you can explain out loud. If you cannot say why your rate sits where it does relative to the provider's, your best children will work it out and leave, which is the most common way this model quietly fails.

A child panel makes you a supplier, and suppliers are judged on reliability rather than service. Expect thinner margins, fewer but harder support requests, and failures that now propagate through everyone below you. Have automatic forwarding, automatic refunds, unattended provider health checks, mapped backups and citable order records before you offer it — and be able to explain your price out loud, because your best children will compare it with going direct.

Frequently Asked Questions

What is the difference between a child panel and a discounted account?

A discounted account means they are your customer using your storefront at better rates. A child panel gives them their own storefront on their own domain with their branding, where their customers pay their prices and never see you. The key consequence is ownership: with a child panel their customers belong to them, and you become a supplier rather than a seller.

Are child panel margins better than retail?

No, they are necessarily thinner. They buy at wholesale, and your margin is the gap between your rate and your provider's — a gap constrained by the fact that they could go to that provider directly. Retail blended margin on real panels runs near 65%; wholesale sits below it. What you sell for that margin is the absence of setup, not the service.

Does offering child panels reduce my support load?

Fewer messages, but harder ones, and with less patience. A consumer asks where their followers are; a reseller asks why the API reported a different start count. You also inherit their customers' problems at one remove, with incomplete information and someone waiting. What reduces the load is surfacing information without you, not answering faster.

What is the biggest risk in this model?

Two, closely related. Concentration — if one child becomes most of your volume you have a single customer with leverage, not a portfolio. And failure amplification: a dead service now affects every customer of every child at once, which matters because roughly 20 services carry half of all orders on a typical panel.

When should I not offer child panels?

When your own panel is not selling, because a child panel adds dependents rather than demand. Also when your fulfilment is not reliably automated — a supplier's entire value is reliability, so offering wholesale on shaky fulfilment turns one unhappy customer into a chain of them. And when you cannot answer a technical question within a few hours in the evening.

Ready to run your own panel?

Launch a fully branded SMM panel with your own domain, payments and automated delivery — set up in under an hour.

Get started →