Routing rules
Eight problems every panel owner knows
Each one used to mean a ticket, a refund or a night of switching services by hand. Each one is now a setting on the service.
One provider goes down and takes your orders with it
The problem
A service is tied to a single provider. When that provider stops accepting orders, every new order fails. You hear about it from angry tickets, then switch providers by hand, sometimes at 3 a.m.
How the panel handles it
Give each service a list of backup providers. When one rejects an order, the panel sends it to the next one with the same quantity. Nobody has to be awake for it.
Watch the guide →
The cheapest provider for 100 is not the best one for 50,000
The problem
One provider is cheap on small orders and slow on big ones, another is the opposite. With one provider per service you give up either margin or speed.
How the panel handles it
Pick the route by order size: under 1,000 goes to A, anything larger goes to B. Or split one order: the first 500 to A and the rest to B, 20% to A and 80% to B, or chunks spread across several providers by weight.
Watch the guide →
Different links need different providers
The problem
Live videos, Reels and company pages often need a different provider. So you build duplicate services, and customers keep picking the wrong one.
How the panel handles it
Match by link pattern. One service sends links containing /live/ to one provider and everything else to another. The customer sees a single service.
Watch the guide →
A partial order turns into a refund and a lost sale
The problem
A provider delivers 6,000 of 10,000 and marks the order partial. You refund 4,000, and that revenue is gone.
How the panel handles it
Name a provider for leftovers. What the first one did not deliver is sent there automatically. Leftovers are resent once, so a bad provider cannot loop an order forever, and anything below every provider's minimum is refunded.
Watch the guide →
A big order lands all at once
The problem
Fifty thousand followers in one go is exactly the kind of delivery that drops, and drip-feed only happens when the customer remembers to turn it on.
How the panel handles it
Set the pace on the service: for example 2,000 every hour, or start the next part only after the previous one finishes. The customer still places one order.
Watch the guide →
A provider raises its price and you sell at a loss
The problem
A provider quietly raises its rate. You keep selling at the old price and find the loss days later in a report.
How the panel handles it
Provider rates are synced every hour. Before any money moves, the panel works out the worst-case cost of the order. If it would cost more than you charge, or more than the cap you set per 1,000, the order is refused instead of being sold at a loss.
Watch the guide →
One wrong edit breaks orders that are already running
The problem
You change a provider setting and orders in progress start going wrong. There is no undo and no record of what changed.
How the panel handles it
Edits start as a draft. Try it on a sample order, then replay it over the service's last 200 real orders to see where each would go and what it would cost. Running orders keep the version they started with. The last 50 versions stay one click away, with a diff between any two.
Watch the guide →
A timeout, and you pay for the same order twice
The problem
A provider times out or starts rate limiting you. The panel retries, the order is placed twice, and you pay for both.
How the panel handles it
A rate limit is treated as "wait", not "failed": the panel slows down for that provider and sends again later, to the same provider. When it is unclear whether an order went through, it is held for you to check instead of being placed a second time.
Watch the guide →