SMM Panel Order Statuses Explained: Pending, In Progress, Partial, Completed, Canceled

An SMM panel order stuck pending is usually waiting in a queue: a supplier line with a backlog, another order running on the same link, or a link the supplier can't reach, such as a private profile. Check the link first, don't place a second order on the same link, and compare the wait with the service's usual start time.

Statuses look simple, but each one says something specific about where the order is and what happens to your money. Once you can read them, most "is my order broken?" moments answer themselves, and you can tell your clients something accurate instead of guessing.

What does each SMM panel order status mean?

These are the statuses used by the standard SMM panel API and by Orbismm. On Orbismm the price of an order is fixed when it's placed and charged to your balance at that moment.

You'll see the same status in the panel and in the API. The v2 status action returns status, start_count, remains and charge, and charge already reflects any refund, so a Partial order shows what it actually cost. Refunds go to your Orbismm balance; the balance can't be withdrawn or transferred. Full details are on refill and cancel and in the refund policy.

Why is my SMM panel order stuck on pending?

Pending and Processing orders sit still for a handful of reasons, and only one or two of them are actual problems:

• Supplier queues. Popular services run on lines that take orders in turn. During busy hours a line may accept an order but take a while to begin it.
• Supplier load or outages. A line can slow down or stop taking orders for a period. On a panel that relies on a single line, your order simply waits.
• Private or unreachable links. A private profile, an age-restricted video or a deleted post can't receive delivery. The order waits or fails, depending on the supplier.
• Wrong link type. A post link on a followers service, or a profile link on a views service, often stalls. On Orbismm the panel reads the pasted link and offers only services that accept that link type.
• Another order on the same link. Many suppliers won't start a second order on a link until the first one finishes.
• Slow services by design. Drip-feed orders and gradual-delivery services are meant to start or run slowly.

What should you do when an order is stuck?

1. Open the link in a logged-out browser. If you can't see the content, neither can the supplier.
2. Compare how long it has waited with the service's median start time, not with how fast the last order went.
3. Check the order's log in the panel. It shows each step, including moves between lines and refunds.
4. On a cancellable service, you can cancel. Not started means a full refund.
5. If something looks wrong, open a ticket from the order on support. Tickets opened from an order attach it, so nobody has to ask for the ID.

Why shouldn't you re-order the same link?

When two orders run on one link, both record a start count from the same profile or post. As delivery overlaps, neither order can tell how much it delivered, a supplier may see the target already reached and mark its order complete early, and a later refill request has no clean baseline to measure a drop against. You pay twice and end up with numbers you can't explain to your client.

On Orbismm, a second order by the same reseller for the same link waits until the first one finishes, on services where that matters. It's queued, not rejected, so you can place both and they will run one after the other with clean start counts.

How does Orbismm handle a stalled order?

Every service runs on a primary supplier line with tested backups behind it. Each service also has a start window and a stall window. Here is what happens when an order doesn't behave:

1. If an order hasn't started within the start window, or stops progressing within the stall window, we cancel it at the supplier.
2. The undelivered part goes to the next backup line: automatic rerouting to a backup line. You don't have to ask.
3. At most 2 supplier lines receive money for one order, so a bad day can't turn into an endless chain of attempts.
4. Anything that can't be delivered is refunded to your balance automatically, with a ledger entry that says why.
5. If a line can't be cancelled, the order is flagged and our team handles it by hand.

For example: you order 1,000 followers. Line 1 delivers 400 and stops. After the stall window, the remaining 600 move to a backup line, which delivers 520 before it slows down too. The order closes as Partial, and the 80 that weren't delivered are refunded to your balance with a ledger entry. You see every step in the order log.

What's the difference between Partial and Canceled?

Both are final. If a Partial order later drops on a service with refill, what refill covers explains how that works.

How should API users check order status?

Panel scripts poll status on a schedule. Poll every few minutes, not every second, and check many orders in one call: the v2 status action accepts orders with comma-separated IDs. The default rate limit is 60 requests per second per key. The request formats are in the API v2 docs, and the SMM panel API explained walks through them. On API v1, signed webhooks remove most of the need to poll.