SMM Panel AuditContact

What start count is and why it decides a refill claim

By Zane Roberts. Last updated:

I co-founded an SMM panel and still work on its operating side, which means a good part of my week goes on reading order records next to support tickets. Many of those tickets come down to one number, the start count. This guide covers where that number comes from, how a refill check uses it, and what to record yourself. It names no panels, and the numbers in it are made up to show the arithmetic.

What is start count on an SMM panel?

Start count is the count on the link at the moment delivery begins: the followers on a profile, the likes on a post, the views on a video. It is not the count when you placed the order. On a service that starts within minutes the two are close. On an order that sits in pending for hours or days, they can drift apart.

It is recorded once. Whoever starts the delivery, usually the supplier and sometimes the panel itself, reads the count from the platform at that moment and stores it with the order. On an order forwarded through an API, the supplier returns that figure along with the status, and the panel copies it into your order history. If the panel you paid buys from a reseller, the number may have passed down more than one step before you see it. Usually nobody along the way reads it again.

That single reading can be late. If the supplier's system reads the profile after the first batch has already landed, the start count includes part of your own delivery. It can also be missing: some orders show zero or a blank because the supplier never reported a figure. Either way, it is one reading taken by someone else.

How a refill check uses it

A refill check is a subtraction, and the start count is its first term. The panel or its supplier adds the quantity delivered to the start count to get a target, reads the current count, and treats any gap below the target as the drop it may refill. On a completed order the quantity delivered is the quantity you ordered; on a partial order it is the part the supplier reports as sent. The window, trigger and scope decide whether the gap qualifies. The start count decides how big the gap is.

An example. You order 3,000 followers for a profile that shows 8,200 when you place the order. The order waits in a queue, and by the time delivery starts the profile has slipped to 8,150. That is the start count. The order completes, so the target is 8,150 plus 3,000, which is 11,150. A few weeks later the profile shows 10,700. The check finds a shortfall of 450, and if the service still covers refill and the drop meets its trigger, 450 is what can be refilled.

The 8,200 on the order form plays no part in this.

Where the arithmetic goes wrong for the buyer

The check compares two readings of one number. Anything else that moved that number in between is counted as if it were delivery or loss.

Drops before delivery starts. The 50 followers lost between ordering and delivery in the example sit below the start count. No refill check will ever see them.

Organic growth. Suppose the same profile also gained 300 followers on its own after delivery. It now shows 11,000 instead of 10,700. The check finds a shortfall of 150, while 450 delivered followers have actually gone. Likes and views on a post that is still being shared suffer most, because they keep climbing for reasons unrelated to the order.

Overdelivery. If the supplier sent 3,200 instead of 3,000, the order still counts as 3,000 delivered and the target stays at 11,150. The surplus is used up first, so the profile has to lose more than 200 before any claim is possible, as the overdelivery entry explains.

Two orders on one link. Say a second order of 2,000 goes onto the same profile while the first is still running, and its start count is read at 9,400 because part of the first order has already arrived. The first order's target is 11,150. The second's is 11,400. Together they should have lifted the profile to 13,150. If it later shows 12,600, both orders pass their own check with room to spare, yet 550 followers are missing. Neither start count describes its own order.

A changed link. The check reads the order link a second time. If the username has changed, the profile has gone private, or the post was archived or deleted, there is nothing to read, or the link now points somewhere else. On many panels that ends the claim. Keep the link public and unchanged until the refill window has closed.

What should I record before ordering?

A start count is hard to question unless you have a figure of your own to set beside it.

Before you order, note the current count and the time, and take a screenshot that shows both. Copy the exact link you are about to paste. Make sure no other order is still running on that link. Do not assume the panel will catch a mistake: one order placed through a live panel API with the link "notaurl" was accepted, charged and later reported completed.

When the status moves from pending to in progress, note the count again with the time. This is as close as you can get to the moment the start count was taken. If the figure on the order is well above what you saw, the reading may have been late or the profile grew in the meantime. If it is well below, something dropped before delivery.

When the status changes to completed or partial, note the count once more. A shortfall at completion is a delivery problem, not a drop, and is easier to raise now than weeks later. Then check again shortly before the refill window ends.

How do I dispute a start count or a refill refusal?

Put the numbers in your first message, so the ticket can be passed up the chain without anyone coming back to you for them. Include:

If your note from just before delivery disagrees with the start count, say so and attach the screenshot. If organic growth or a second order muddies the check, say so up front. Support often has to ask its supplier, and a message with the working already shown is far easier to forward than a complaint that the followers went down.

Read the service terms before sending. If the claim falls outside the stated trigger or window, correct numbers will not rescue it; the guide on reading panel terms before ordering shows where those conditions tend to sit.

What start count is not

It is not the count on the order form, and it is not necessarily a figure the panel you paid measured itself. On many orders it was reported by a supplier and copied down.

It is not proof of delivery. A plausible start count next to a completed status still does not show that the full quantity arrived and stayed.

And it cannot be rebuilt later from the profile. It is a single reading that every later calculation on the order leans on, which is why your own timed note carries weight.

The limits of this measurement

This guide explains how start count is recorded and used, based on the author's work operating an SMM panel. It does not measure how accurately any supplier records start counts, how often refill claims are accepted, or how any individual panel handles disputes. Panels and suppliers differ in when they read the count, whether they show it to buyers and which figures their refill checks use, so the arithmetic here describes a common method rather than a rule every panel follows. The numbers in the examples are invented for illustration and do not come from real orders.

Frequently asked questions

What does start count mean on an SMM panel?

Start count is the number of followers, likes or views on your link at the moment the supplier begins delivering. It is the baseline for everything that follows. A panel checks whether an order delivered, and whether a later drop qualifies for refill, by comparing the current count against that baseline plus the quantity delivered.

Why is the start count different from the number I saw when I ordered?

Because it is taken when delivery starts, not when you pay. If the order waited in a queue, your count may have moved in between, through ordinary unfollows or organic growth. A reading taken slightly late can also include the first part of your own delivery, which pushes the figure above what you saw on the order form.

Who records the start count on an order?

Usually the supplier running the delivery reads it from the platform and returns it through the API along with the order status. Your panel copies that figure into your order history, and if it buys through another panel, the number passes through each step unchanged. A panel that produces the engagement itself may record it directly.

Why was my refill request refused when followers clearly dropped?

The check compares your current count with the start count plus the quantity delivered, so anything that lifted the count hides the loss. Followers gained organically since delivery, extra followers the supplier overdelivered, or a second order on the same link can all keep the profile above the target even though delivered followers have left.

Can I place two orders on the same link at the same time?

Some panels allow it and some reject it, but it weakens both orders. The second order's start count is read while the first is still delivering, so neither baseline matches its own order. Once both finish, each can pass its own refill check while followers are missing from the combined total. Wait for the first to complete.

What does it mean if my order shows a start count of zero?

A zero or blank start count usually means the supplier did not report one. That leaves any later refill check without a baseline, so ask support early which figure they will measure against. Your own count, noted with the time just before delivery began, then becomes the most useful evidence you have. Keep it with the order ID.

What should I send support when I dispute a refill?

Send the order ID, the start count shown on the order, and your own counts with the date and time each was taken. Then show the working: start count plus quantity, the target that produces, the current count and the gap. Attach screenshots. A ticket with the arithmetic already done can be forwarded to the supplier without another round of questions.