White-label panels: what you control and what you do not

A white-label panel puts your brand on a storefront that someone else supplies. The domain, the logo and the support voice are yours. The catalogue, the delivery clock and the platform's enforcement are not. The deal works when both sides are clear about that line, and it fails when the contract implies control the supplier does not have.

This guide separates what you control, what you influence and what you do not control at all. It also names the contract clauses that decide who pays when an order fails, and it states this panel's own position: the API is available today, and a white-label storefront is a roadmap item, not a shipped feature.

What white-label usually means

In this market, white-label usually means a supplier gives you an API and a catalogue, and you run the storefront. Your customer sees your domain, your prices and your support address. Behind the page, the order goes to the supplier, the supplier delivers, and the supplier reports the result back through the API.

The label can also mean a hosted storefront with your logo on the supplier's domain. That is a different product with a different risk: the supplier holds the customer account, the payment and the support inbox. Read which one is on offer before you compare prices, because the two are not the same business.

The common thread is that the supply chain is not yours. You are buying a delivery and reselling it. The brand is yours, the liability is shared, and the customer experience is assembled from parts you did not build.

What you control

Layer	What you decide	What the customer sees
Domain and brand	The name, the logo, the domain, the tone	Your identity, not the supplier's
Catalogue	Which services you expose and in what order	A shorter, curated list
Retail price	Your price, your currency, your rounding	The number at checkout
Support	Your inbox, your reply time, your escalation path	Your voice, your promises
Refund promise	What you refund, in what form, how fast	Your policy, backed by the supplier's terms
Payment	Which methods you accept and who holds the funds	The checkout flow

A control map, not a contract. The payment row depends on who holds the merchant account.

The retail price is the clearest example. The supplier charges you a cost; you charge your customer a price. The difference pays for your panel, your payment fees, your support time and the orders that fail. A white-label offer that sets your retail price for you has taken the main decision out of your hands.

The catalogue is the second. A supplier may carry thousands of rows; you do not have to show all of them. A shorter list that you can support is easier to run than a full list with services you have never tested. The supplier's catalogue count is not your catalogue count.

What you influence but do not control

Start times. You can choose a service with a shorter published start, and you can set a customer expectation around it. You cannot make the supplier's queue move faster. A white-label page that repeats the supplier's start number as a promise is borrowing a fact it does not own.

Delivery quality. You can test services, drop the weak ones and keep the strong ones. You cannot change the pool, the platform limit or the supplier's method. The delivery is the supplier's, and your brand is attached to it.

Refill terms. You can choose services with a refill flag and a window that fits your customers. You cannot extend the window or make the supplier honour a request it rejects. Your customer's refill promise has to be the supplier's term, restated in your words.

Service availability. You can monitor the catalogue and remove a service that disappears. You cannot keep a paused service alive. A white-label panel without a monitor will show dead rows until a customer complains.

Supplier balance. You can keep your own balance funded. You cannot top up the supplier's account, and a supplier shortfall becomes a queued order on your page. The queue timeout is the remedy, not a delivery.

What you do not control

Platform enforcement. Instagram, TikTok, YouTube and Telegram decide what counts as inauthentic activity and what to remove. A white-label panel cannot promise a count will stay, because the platform can remove accounts after any delivery. The supplier's refill window is a remedy, not a shield.

Supplier uptime. The supplier's API can time out, return an error or change a status name. Your panel can retry a read, but it cannot make the supplier answer. A white-label contract should say what happens to open orders when the supplier is down.

The supplier's own brand. A supplier that puts its name in an error message or a status page can leak through your white label. The API can return unbranded JSON, but the supplier's error text is still the supplier's. Scrub it before it reaches your customer.

The vocabulary of the API. The status labels are the supplier's or the platform's, not yours. Your panel can map them to your own words, but the underlying state is not yours to define. A customer who sees "Queued" on your page is seeing a supplier state with your brand on it.

The symptom that brings people here

What you see: your customer asks what a status word means, or the supplier's name appears in an error, or a service vanishes from your catalogue, or a refund you promised is not covered by the supplier.

What it means: the white label is a brand layer over a supply chain you do not own. Each of those symptoms is a place where the layer is thinner than the page suggests.

Next action: map every status word to a sentence your customer can read, scrub supplier names from errors, monitor the catalogue for missing rows, and check the refund path in the contract before you promise one.

The status word is a frequent leak. A customer who sees "Partial" on your page does not know whether the order stopped or is still delivering. A sentence next to the word, written in your voice, closes the gap. The supplier's label stays underneath; your explanation is the product.

The contract clauses that matter

Who holds the wallet. If the supplier holds your balance, a supplier shutdown can strand it. If you hold the customer's payment, a customer refund is your liability first and the supplier's credit second. The contract should say which balance is whose and what happens on termination.

Who owns the customer data. A white label that lets the supplier email your customers is not a white label; it is a shared relationship. The contract should name the data owner, the export format and the deletion rule.

The refund path. A refund can be a wallet credit, a card reversal or a manual transfer. Each has a different speed and a different evidence trail. The contract should name the path for a failed order, a partial delivery and a cancellation, and who pays the payment fee.

The notice period. A supplier can change a price, a service or a term. The contract should say how much notice you get and what happens to open orders when a term changes. A notice period without an open-order clause is a warning, not a plan.

The service level. A white-label contract can promise a response time, an uptime target or a refund window. Read the remedy, not only the target. A target without a remedy is a number with no consequence.

The data export. If you leave, you need your orders, your customers and your wallet history. A contract that does not name an export format leaves you with screenshots.

This panel's white-label position

This panel does not sell a white-label storefront today. The reseller page lists a white-label storefront as a roadmap item with no date, next to sub-accounts, your own prices inside the panel and webhooks. Those are not shipped features, and a plan that depends on them is a plan that depends on a date nobody has published.

What exists today is the API. It returns unbranded JSON, it has four actions, and it lets you run your own storefront with your own brand. Your retail price lives in your panel. The API key belongs to one account; separate balances mean separate accounts. There is no push callback, so your panel polls status.

The catalogue behind the API currently carries 4,079 active services across 20 platforms. Your white label does not have to show all of them. The number is a supply fact, not a recommendation to expose every row.

A worked example: who pays when the order fails

Suppose your customer pays your retail price for a hypothetical 1,000 unit Instagram followers order. The panel charge at the median rate is $0.73. You set the retail price above that charge, with your margin and your payment fee inside it.

If the order fails before delivery, the panel credits its charge to your wallet. You refund the retail price to your customer. Your net is zero minus the payment fee, assuming the processor does not return it. The margin was never earned, so it is not lost. The customer is whole and your brand keeps the trust.

If the order is delivered and the customer disputes it as a goodwill refund, the supplier has no reason to credit you. You refund the retail price and absorb the full amount. That is the case where the margin matters: at a 20% margin on cost, one goodwill refund costs several sales of margin. A white-label business that refunds generously without counting is a business that is buying goodwill with its working capital.

If the supplier closes while an order is open, the outcome depends on the contract and the supplier's balance. A white label without a termination clause is a brand with an open-ended liability. The contract should name the notice, the refund path and the data export before the first customer arrives.

What to do next

If your customer sees a status word they do not understand, write a one-sentence explanation for every label your panel can show. Put it next to the label, not in a help centre three clicks away. The explanation is your product; the label is the supplier's.

If the supplier's name appears in an error, scrub it before display and log the original for support. The API can return unbranded JSON, but the error text is still the supplier's words. A white label that leaks the supplier's name has lost the point of the label.

If a service disappears, remove the row from your catalogue and tell the customers who have open orders on it. A dead row with a working checkout is worse than a missing row with an explanation.

If you are comparing white-label offers, ask for the six clauses above in writing before you compare prices. A cheaper offer with no data export and no termination clause is not cheaper; it is a different risk.

For the current reseller offer and roadmap, read the reseller page. For the four API calls, open the API documentation. For the terms that govern this panel, read the terms page, and for a contract question, use the support page.