"My order has been sitting in Pending for an hour, the money is gone and nothing is happening" is the single most common support message on any SMM panel. Most of the time nothing is wrong and nobody needs to touch anything, but you have to explain that in one message, otherwise the first ticket is followed by a second. Here is what Pending means, how long an order normally sits in it, what keeps it there longer and what the panel owner should do about it.
There is a sixth reason that stands apart: the service the order was placed on no longer exists at the provider. Such an order will not clear itself and waiting is pointless - that case is covered in the piece on what to do when a provider has deleted a service.
What the Pending status means
Pending means "accepted and waiting". The panel took the order, charged the customer's balance and queued the job to be sent to the provider. Nothing is broken: the work simply has not started yet.
What matters more is what Pending does not mean:
- It is not a payment problem. The balance has already been charged, so there is no reason to place the order again - that only produces two orders and two charges.
- It is not a provider refusal. A refusal moves the order to
canceledand the amount returns to the balance automatically. - It is not a stall. The status changes on its own as the provider gets polled; neither the customer nor the operator has to press anything.
The full status set in a panel is short: pending, processing, partial, completed, canceled. What each one means, and how Partial differs from a refund, is covered in a separate piece on SMM panel order statuses. This article stays on the first one, which is where almost all of the questions land.
How long is normal
The rule of thumb is minutes, not hours. A panel gets no notifications from its provider - it polls the provider on a schedule. In our core that poll runs every five minutes, so until the first poll a fresh order honestly shows Pending and zero delivered, even when the provider accepted it instantly. That produces the most common false alarm of all: the customer places an order, refreshes the page ten seconds later and sees Pending. That is not a delay, that is a poll that has not happened yet.
After that, the timing depends on what was bought:
- Views. Usually the fastest to move, starting within 5-15 minutes.
- Followers and likes. Start within 5-30 minutes, then the volume builds up gradually.
- Comments and anything a human has to write. A few hours before the start is normal, not a fault. Put those timings straight into the service description, or every single order turns into a ticket.
- Drip-feed orders. Here Pending is held deliberately: batches go out at intervals and the first one can be scheduled later. How that works is in the breakdown of what drip-feed is.
A practical threshold for the owner: a followers or views order that has been in Pending for more than two hours is worth looking at rather than waiting on. For comments, that same threshold starts at about a day.
Five reasons an order sits longer
- The provider's own queue. They accepted the order but have not started it: they have their own pool of workers and their own backlog. The panel can do nothing here, and this is by far the most common reason. The order will go out by itself.
- You are out of money for the purchase. The most painful reason and the only one that is entirely yours. The customer paid you, but your balance with the provider is empty, so the purchase does not go through and the order stays queued. Some panels even give this its own status, along the lines of
partial_awaiting_topup. The only cure is prevention: watch the provider balance and top it up before it runs out. - A failed send. The provider did not answer, answered with garbage or timed out. Inside the panel such an order is flagged as
error, but the customer still sees "Pending" - and that is deliberate. A failed send is our internal problem, retries grind it down (every half hour in our case, plus a sweep for stuck orders every ten minutes) and no money is refunded meanwhile. The word "Error" in a customer's dashboard would only breed tickets about an order that is going to leave on its own in a few minutes. The operator sees the real status in the admin panel. - The provider pulled the service. They removed the item from their catalogue, but it is still in your panel and still on sale. No signal arrives when this happens: the provider simply stops returning that service in the list. Finding those items takes reconciling your catalogue against the provider's - one more reason to know up front which providers connect to the panel and how often their catalogue refreshes.
- The profile is private, renamed or gone. The provider cannot work with a private account or a broken link. Some providers refuse immediately, others hold the order in the queue for a manual check. This is the one case where waiting is pointless: cancel and place it again.
Pending versus Processing
There is exactly one difference and it is the important one. Pending means the work has not started and nothing has been delivered. Processing (In progress in some panels) means the provider has confirmed the start and already delivered something, so the remains counter has begun to fall.
The practical consequence for support: an order in Pending can still be cancelled with a full refund, an order in Processing cannot, or only partly. So a customer who pasted the wrong link has to reach you while the status is still Pending, and it is worth saying that in the service description in advance. If an order lands only partially, Partial and refills take over from there - there is a breakdown of drop and refill for that.
What to tell the customer
A good reply closes the question in one message and promises nothing you do not control. A working template has three parts: what the status means, when to expect the start, and what happens if it never starts.
"Pending means the order has been accepted and is queued with the provider; the funds are already reserved. For this service the start is usually within 30 minutes. If the status has not changed in two hours, message us and we will cancel the order and return the amount to your balance."
What must not be in that reply: "try placing it again" (that buys you a double charge and a second ticket), "this is an error on our side" (in Pending there usually is no error) and any exact deadline the provider never gave you. The general approach to replies like this, and to refunds, is in the piece on customer support and refunds.
What to set up so Pending stops piling up
- Put start times in every service description. The cheapest measure and the most effective one: half of all Pending questions are questions about timings that are written down nowhere.
- Keep a buffer on the provider balance. An empty balance turns a normal queue into stuck orders across the whole panel at once.
- Reconcile your catalogue with the provider's. An item they pulled keeps selling on your side and reliably produces a stuck order and a refund.
- Watch the age of orders, not their count. Twenty orders in Pending from the last ten minutes is normal. Three orders in Pending since yesterday evening is a breakage to be handled by hand.
- Do not show internal failures to customers. Technical statuses are for the operator; the customer needs a clear "Pending" and a timeframe.
Wrapping up
Pending is not an error, it is the normal first state of an order: accepted, funds reserved, provider not started. The normal duration is measured in minutes, and a long Pending almost always comes down to one of five reasons - only one of which is yours. The difference between a panel where Pending eats the support queue and one where it goes unnoticed is not in the engine; it is in the service descriptions and in the habit of watching how old the orders are.
You can test that without spending anything: orders that go through our own catalogue are not metered at all, and with third-party providers the first 100 orders a month are free - enough to push your first deals through and see how your services behave against real timings.
