Among the order states on an SMM panel, partially completed is the one that generates the most questions. It means part of the quantity you ordered was delivered and the rest could not be. This guide explains why it happens, how the refund is calculated and what you should do when you see it.
The order states and what they mean
Before looking at partials it helps to see the full set. Panels use broadly the same vocabulary, though the exact wording varies.
- Pending: the order has been created and passed to the provider but delivery has not started.
- Processing / In progress: delivery is under way; the counter is moving.
- Completed: the full quantity was delivered.
- Partially completed: some was delivered, the rest could not be, and the difference has been refunded.
- Cancelled: nothing was delivered and the full amount has been refunded.
An important detail: pending is not an error state. Some services queue for hours before starting, particularly where the provider batches work. An order sitting in pending is waiting, not failing.
Why an order stops part-way
There are four typical causes, and knowing which one applies tells you whether to reorder.
The provider ran out of capacity. The most common cause. A source can supply a certain volume for a given service at a given moment, and when demand exceeds it the remainder cannot be filled. This is temporary; the same order usually goes through later.
The target changed mid-delivery. If the account went private, the username changed, the post was archived or deleted, or comments were switched off, delivery stops at that point. This cause is within your control and is the one worth checking first.
The platform filtered part of the delivery. Platforms run periodic verification, and some of what was delivered can be removed. Where the panel detects this it reports the order as partial rather than complete.
The service was retired or paused. Occasionally a provider withdraws a service while orders are open. Those orders close as partial and the balance returns.
How the refund is calculated
The arithmetic is straightforward and proportional. If you ordered 10,000 units at $1.00 per thousand — a $10.00 charge — and 6,500 were delivered, you are charged for 6,500 and refunded for 3,500. That is $3.50 back to your balance.
Panels usually show the start count and the delivered quantity on the order record, so you can verify the figure yourself. The refund goes to your panel balance rather than back to your original payment method, because the balance is where the charge came from. It is immediately usable on another order.
The important point is that this is automatic. You do not need to open a ticket, ask for the difference or chase anyone. The order state changes, the balance updates, and that is the whole process.
What to do when you see a partial
Start by checking the target. Open the profile or post in a logged-out browser window and confirm it is still public and unchanged. If something did change during delivery, that is your answer, and reordering after restoring the original state usually works.
If the target is unchanged, the cause is on the provider side. Here the sensible move is to wait a short while and place a new order for the remaining quantity. Capacity problems generally resolve within hours. Placing the replacement order immediately, while the first shortfall is still being processed, sometimes runs into the same limit.
If the same service repeatedly returns partials, that is information worth acting on. A service that reliably delivers only part of what is ordered is a weak source, and the practical response is to move to a different line in the catalogue even if it costs more per thousand.
Partial versus drop
These two are often confused and they are not the same thing. A partial happens during delivery: the quantity never arrived, and you are refunded for it. A drop happens after delivery completed: the quantity arrived, the order closed as completed, and the count fell afterwards.
The distinction matters because the remedies differ. A partial produces an automatic refund. A drop is covered by the refill guarantee if the service has one, and you raise a replacement request rather than expecting money back.
Checking the order state tells you which you are looking at. If the order shows completed but the count has fallen, that is a drop. If the order shows partial, the quantity never arrived in the first place.
Reducing how often it happens
Partials cannot be eliminated but they can be made rarer. Splitting large orders is the most effective step: a single order for 100,000 is far more likely to exceed available capacity than ten orders of 10,000 placed across a day.
Leaving the target alone during delivery removes the one cause that is entirely within your control. No privacy changes, no username changes, no archiving, no deleting until the order shows a final state.
Choosing services with realistic speed tags helps too. A line promising 100,000 a day is more likely to run into capacity limits than one quoting a modest rate it can actually sustain.
Reading the numbers on the order record
Every order record carries three figures that together explain what happened, and learning to read them removes most of the guesswork. The start count is the value of the metric at the moment delivery began. The quantity ordered is what you asked for. The remaining figure is what was not delivered.
The start count is more useful than it looks. If it reads zero when you know the post already had engagement, the provider may have failed to read the target correctly — which often explains a partial better than any capacity story. If it matches what you saw, the order was aimed correctly and the shortfall happened during delivery.
Comparing the start count with the current value also tells you whether what was delivered is still there. A completed order whose start count plus delivered quantity no longer matches the live number means a drop happened after delivery — a different situation entirely, handled by refill rather than a refund.
When a partial is actually good news
It does not always feel like it, but a partial is the system working correctly. The alternative — charging for a full order and delivering part of it — is what happens on services with no proper state handling, and it is far worse. The partial state exists precisely so that the accounting stays honest.
There is also a practical upside on large orders. A partial tells you the real capacity limit for that service at that moment, which is information you can use. If a 50,000 order consistently completes at around 30,000, splitting future orders into 30,000 blocks will deliver reliably rather than repeatedly producing shortfalls.
Frequently asked questions
Do I need to request the refund?
No. The value of the undelivered portion returns to your panel balance automatically when the order closes as partial. There is no ticket to open.
Does the refund go back to my card or wallet?
It goes to your panel balance, because that is where the charge was taken from. It is immediately usable on another order.
What is the difference between a partial and a drop?
A partial means the quantity never arrived and you are refunded. A drop means it arrived, the order completed, and the count fell afterwards — that is covered by refill, not by a refund.
Should I reorder straight away?
Check the target first. If it is unchanged, waiting a short while before ordering the remaining quantity usually works better, because capacity problems tend to resolve within hours.