Published 2020-08-12
A child panel is a reseller storefront connected to a parent panel. It can give you a place to manage customer orders without building the whole system yourself. The trade-off is control: the parent supplies the services, and some capabilities depend on that relationship.
BulkFollows offers free child panels for eligible customers. That makes the setup fee one part of the decision, not the whole decision. Before choosing a child panel or a more independent setup, compare who handles the customers, the orders and the things that go wrong.

First separate being a customer of a panel from operating a storefront. A regular customer account lets you place orders. A child panel is for reselling through a connected storefront. A more independent panel setup gives its operator a different level of control and responsibility, depending on the software and contract.
Perfect Panel's 2020 explanation describes its child panels as limited-feature panels linked to a regular panel. Its provider guide distinguishes a child panel's single parent provider from a regular panel's ability to connect multiple providers. These explain that platform's model, not a universal promise about every product called a child panel.
| Your situation | Route to consider | Question to settle first |
|---|---|---|
| You place orders for your own work | Customer account | Do you actually need a storefront? |
| You want to resell one supplier's services | Child panel | Are the parent's catalogue and controls sufficient? |
| You need supplier choice or custom workflows | Independent setup or integration | Who will maintain and support it? |
The BulkFollows offer is for eligible customers. Do not assume an old article's monthly price applies, or that every account qualifies automatically. Ask support to confirm your eligibility and the current scope before planning a launch around it.
Then separate the panel offer from operating expenses. Ask whether you need to arrange a domain, which payment arrangements are available, how service orders are funded and who pays any transaction costs. A free panel should not be described to a business partner as a business with no costs.
Keep those answers in a simple launch record. “Included,” “separate cost” and “not confirmed” are more useful categories than one headline price.
Find out how service changes reach your storefront. If a service becomes unavailable or its supplier rate changes, who updates your listing? You want an answer before a customer places an order at an outdated price.
Ask which administrative controls you receive, who else has access and what order or customer records you can retain. Do not assume that using your own branding means you control every part of the underlying system.
Decide who answers your customer and how an issue reaches the parent supplier. A customer's purchase reference and the supplier's order ID may differ. Your support process needs a way to connect them.
Ask about export and migration arrangements before you need them. You do not have to move immediately, but you should understand what would happen to your domain, records and outstanding orders if the setup stopped fitting your business.
Imagine two resellers comparing setups. These are illustrative situations, not customer case studies.
| Reseller | Requirement | Reasoned next step |
|---|---|---|
| Reseller A | One supplier, a small catalogue, no custom routing | Review a child panel's current controls and eligibility before launch |
| Reseller B | Two suppliers and custom order-routing rules | Investigate an independent setup or integration before choosing a storefront |
Reseller A is not choosing “less ambition.” The simpler arrangement matches the current job. Reseller B has a requirement that needs to be demonstrated, not assumed. In both cases, the useful test is whether the setup supports the workflow, not whether its label sounds more advanced.
A connected storefront does not write clear service descriptions, resolve misunderstandings or set realistic expectations on its own. Show the correct destination format and the relevant service conditions before an order is placed. Keep delivery estimates separate from guarantees.
When an order needs review, explain what you know and what is still being checked. Do not promise a refill or refund simply because a customer asks for one. The refund and refill guide explains why account refunds, order credits and replacement quantities are different remedies.
Also check the rules of the social platform involved. Neither a child panel nor an independent setup removes those rules or guarantees genuine audience interest.
Write down the few things your storefront must do now. Confirm those capabilities and the free-offer eligibility, then walk through an order and a support case before inviting customers. If the route needs custom software, the API integration guide shows the records and failure handling to discuss with your developer.
Choose a setup you can explain and operate. That is a stronger starting point than choosing the cheapest headline and discovering the responsibilities afterward.
Source-checked 16 November 2026. Examples are illustrative; no customer results are claimed.