First: verify before you react
When a customer reports a problem — or you spot one yourself — resist the urge to act immediately. The first step is always verification: open the order in the panel, check its current status, and compare what was ordered against what was delivered. Many "failed" orders turn out to be delayed, and many "stuck" orders turn out to be complete. Acting on wrong information creates new problems.
Stuck vs. failed: know the difference
A stuck order is one that started but is not progressing — the status shows in progress, but the count is not moving. A failed order is one the provider could not complete at all — the status shows failed, canceled, or the order was refunded by the provider. Stuck orders may still recover; failed orders need a decision: re-place or refund.
Common causes and what to check
| Cause | Symptoms | What to check | Action |
|---|---|---|---|
| Wrong link or username | Order fails quickly or never starts | Open the link yourself; check spelling, privacy settings, and that the account or post exists | Fix the link and re-place, or refund if the customer cannot provide a correct one |
| Private account | Order fails or stalls at zero | Check whether the target account is private — most services require public accounts | Ask the customer to go public during delivery, then re-place |
| Service temporarily down | Multiple orders on the same service stall at once | Check provider announcements; test with a small order | Pause new orders on that service; switch customers to an alternative |
| Order exceeds service limits | Large orders partially deliver then stop | Compare the order quantity against the service's min/max | Split large orders into smaller ones within limits |
| Content removed or changed | Order stalls midway | Check the post or account still exists and is unchanged | Re-place on the new link, or refund the undelivered portion |
| Provider-side delay | Status in progress, slow movement, no error | Compare against the service's normal speed; check for maintenance notices | Wait if within normal range; update the customer; escalate if far beyond it |
| Duplicate orders | Counts overshoot or orders conflict | Check whether the same link has overlapping active orders | Let them finish; avoid placing duplicates in future |
Your troubleshooting sequence
- Check the link. Most failures start here. Open it, verify it is public, and confirm it matches what the customer intended.
- Check the service status. Is the service active? Are other orders on it progressing?
- Check the order details. Quantity within limits? Correct service for the platform and content type?
- Check with the provider. If everything looks right on your side, open a provider ticket with the order reference and a clear description.
- Decide: wait, re-place, or refund. Set a personal deadline — for example, if a stuck order shows no movement for 48 hours beyond its normal timeframe, act.
Document everything
For every troubled order, keep a short note: what went wrong, what you checked, what you did, and what the customer was told. This record is invaluable when a customer disputes the outcome weeks later, and it reveals patterns — if the same service fails repeatedly, you will see it in your notes before you see it anywhere else.
Preventing repeat failures
- Validate links at order time — a quick check before placing saves most "wrong link" failures.
- State requirements clearly on your order form: public account, correct link format, no changes during delivery.
- Keep a private list of unreliable services and stop selling them, no matter how popular they look.
- Never place the same order twice "just in case" — duplicates cause their own problems.
Calm, methodical, documented
Troubleshooting is a skill that improves with practice. The resellers who handle failures best are not the ones with the fewest failures — they are the ones with a system: verify, diagnose, act, document. Build the habit now, and every future problem gets easier.