Launch your panel

The Cheapest Provider Usually Isn't — Three Things That Break Rate Comparison

Panel Business 10 min read·

Every panel owner compares provider rates, and most do it by putting the numbers side by side. That method is wrong often enough to matter, and the errors all run the same direction — they make the wrong provider look cheapest. This post is built from an actual catalogue: 60,964 services synced from 44 providers with their currencies verified against each provider's own balance API. Three specific things break the comparison, and all three are measurable.

More Than Half The Market Does Not Quote In Rupees

This is the big one, and it is bigger than most people expect.

Of 60,964 catalogued services across 44 verified providers, 54.9% are quoted in USD. By provider count the split is 34 INR against 10 USD — but the USD providers carry the larger catalogues, so by service count they are the majority.

What that does to a naive comparison is severe. Here are real rows from the catalogue, Instagram followers, with the number the provider lists next to what it actually costs in rupees:

A service listed at 0.1161 is really ₹10.98 per 1,000. Listed at 0.1243, really ₹11.89. Listed at 0.1354, really ₹12.80.

The multiplier is about 94.5×. So a USD provider sitting next to an INR provider in your spreadsheet does not look slightly cheaper — it looks like it costs almost nothing, and it will win every "cheapest" sort you ever run.

The practical damage is not that you overpay. It is that you pick a provider for a reason that was never true, and then wonder why your margin does not match the plan.

How To Tell What Currency A Provider Uses

You cannot tell from the rate, and you cannot tell from the label.

Guessing from the number does not work, because plenty of INR services are genuinely priced under ₹1 and plenty of USD services are priced in whole dollars. Magnitude tells you nothing reliable.

Guessing from the panel's name or its country does not work either. A .in domain with rupee branding can still return USD from its API.

The answer is to ask the provider's own API. Every standard SMM API exposes a balance endpoint, and it returns the account currency alongside the balance. That is the provider telling you directly, and it is the only source worth trusting.

Once you have it, store it against the provider and convert every rate into one currency at sync time. Do not convert at display time and do not convert in your head. The comparison should happen on a column that is already in rupees, so that a sort by price cannot silently be a sort by currency.

If you cannot verify a provider's currency, the right move is to exclude it from your rankings rather than guess. A wrong guess produces a confidently wrong answer, which is worse than a missing one.

Roughly One Service In Twenty Has A Rate That Is Not Real

The second problem is dirtier and less discussed.

In the same catalogue, 5.4% of 61,077 services carry a rate that cannot be true — 3,249 priced above ₹5,000 per 1,000 and 35 priced at zero or below.

These are not expensive premium services. They are sentinel rows, placeholders, mislabelled currency, and entries a provider never cleaned up. Some are services that were switched off by setting an absurd price rather than deleting them.

They matter for two reasons. If you sort ascending they are invisible, so you may never notice. But the moment you compute anything in aggregate — an average cost, a margin report, a "what does this category cost me" figure — a handful of rows priced in the millions will drag the number somewhere useless.

The fix is a sanity band. Decide what is plausible for your market, discard anything outside it, and count what you discarded. That last part matters: if the discard rate jumps from 5% to 30% on one provider, that is a signal about the provider, not about your filter.

This is also why a below-cost alert on your own panel should be treated sceptically before you act on it. A package that appears to sell below cost is very often a junk provider rate, not a pricing mistake.

A Rate Is Only Comparable If The Order Size Is Comparable

The third break is structural and catches careful people.

Provider rates are quoted per 1,000 units, but every service also carries a minimum and a maximum. A service with min 1,000 and max 1,000 is not selling you a rate — it is selling a fixed pack, and its per-1,000 figure is arithmetic rather than a price you can act on.

So a comparison is only valid between services that can actually accept the order you intend to place. If you sell 100-unit orders, a provider whose minimum is 500 is not cheaper than one whose minimum is 50 — it is unavailable, and putting it in the ranking is how you end up promising something you cannot fulfil.

The same applies to pricing model. Some catalogue entries are subscriptions or bundles rather than per-unit services. Their per-1,000 number is meaningless in a rate comparison and should be filtered out entirely.

The rule that follows is simple: filter by the order size you actually sell before you sort by price. A ranking that ignores min and max is answering a question nobody asked.

A Provider That Stopped Syncing Looks Perfect Forever

One more failure worth knowing, because it is silent.

Most panels track whether a service is still alive by counting how many times it went missing from a sync. That works — but the counter only advances when a sync actually runs. If a provider's API key dies, or its endpoint starts refusing you, nothing syncs, nothing goes missing, and every one of its services keeps its healthy status indefinitely.

The result is a provider that has been unreachable for weeks still sitting near the top of your cheapest list, because dead data does not decay on its own.

Guard against it with a last-successful-sync timestamp, and exclude any provider that has not synced recently from every price ranking. Staleness needs to be an exclusion rule, not a note in the corner of a dashboard.

This pairs with the dead-service problem on the retail side. A service deleted at the provider will keep selling on your panel and cancel every order it takes, and from the customer's side that is indistinguishable from being cheated.

What A Correct Comparison Looks Like

Putting the four rules together, a rate comparison you can act on does all of this before it sorts.

Converts every rate to one currency, using a currency each provider confirmed through its own balance endpoint, and drops providers whose currency could not be verified.

Discards rates outside a plausible band, and reports how many it discarded so a spike is visible.

Filters to services that can accept your actual order size, and removes pricing models that are not per-unit.

Excludes providers that have not synced successfully within a recent window.

Only then sorts by price.

Every one of those steps removes candidates that would otherwise have won on a technicality. That is the point — the cheapest row in an unfiltered list is usually cheapest because something about it is wrong, not because it is a better deal.

And the final check is the one that costs money to skip: place a small real order with the provider before moving volume. A rate is a claim about price. Delivery, start time and drop behaviour are the things you are actually buying, and none of them appear in the rate column.

Rate comparison fails in four predictable ways, and all of them favour the wrong provider: currency that was never converted, rates that are not real prices, services that cannot take your order size, and providers that stopped answering weeks ago. Fix those four and the ranking becomes trustworthy. Then place a small real order anyway, because price is a claim and delivery is the product.

Frequently Asked Questions

How do I know if a provider quotes in USD or INR?

Ask its API, not its branding. Every standard SMM API has a balance endpoint that returns the account currency, and that is the provider telling you directly. You cannot infer it from the rate magnitude, because genuine INR services exist under ₹1, and you cannot infer it from a .in domain or rupee-styled marketing. If you cannot verify it, exclude that provider from rankings rather than guessing.

How much of the market actually quotes in dollars?

In a catalogue of 60,964 services across 44 verified providers, 54.9% were quoted in USD. By provider count it is 34 INR to 10 USD, but the USD providers carry bigger catalogues so they dominate by service count. At roughly ₹95 to the dollar a USD service looks about 94 times cheaper than it is, which is why it wins every unconverted cheapest sort.

Why does my margin report show services selling below cost?

Very often because the provider rate is junk rather than because your price is wrong. About 5.4% of catalogued services carry an impossible rate — over ₹5,000 per 1,000, or zero and below — from sentinel rows, placeholders and mislabelled currency. Apply a plausibility band before computing any aggregate, and count what you discard so an unusual provider stands out.

Can I just sort by rate and take the cheapest?

Not safely. A valid comparison first converts currency, discards impossible rates, filters to services that accept the order size you actually sell, removes bundle and subscription entries whose per-1000 figure is arithmetic rather than a price, and excludes providers that have stopped syncing. The cheapest row in an unfiltered list is usually cheapest because something is wrong with it.

Why would a dead provider still look healthy?

Because most panels mark services dead by counting how often they go missing from a sync, and that counter only moves when a sync runs. If the API key dies nothing syncs, nothing goes missing, and every service keeps its healthy status forever. Track the last successful sync per provider and exclude stale providers from rankings — staleness has to be an exclusion rule, not a dashboard note.

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 →