SMM Panel Refill, Drip-Feed and Cancel Explained

In an SMM panel, refill means the provider tops an order back up after some of what was delivered drops, within a set number of days. Drip-feed means one order is split into several smaller runs delivered with a gap between them. Cancel means stopping an order before it is delivered and refunding it. All three are set per service, and all three cause most of the disputes a panel owner handles.

This guide explains what each one means for the customer, what the rules are on FlashyPanels, and how to handle the arguments that come with them. The field and button names are the real ones from the admin area.

What Refill Means in an SMM Panel

Followers, likes and views can drop after delivery, usually when a platform removes accounts or engagement it considers fake. A refill puts the order back to the quantity that was bought.

Refill is a promise with a time limit. A "30-day refill" service means drops reported within 30 days of completion are topped up. After that, the customer is on their own. Services without refill are cheaper because nobody is promising anything after delivery.

The person who actually does the refill is your provider. Your panel passes the request on and tracks the answer. That is the source of almost every refill dispute, so it is worth understanding exactly how the request flows.

Refill Rules on FlashyPanels

Each service has three refill settings in its edit form:

• Refill Enabled turns the refill button on for that service.
• Refill Days is the window, counted from when the order completed. Leave it at 0 and the window never closes, so always set a number when Refill Enabled is on.
• Refill Mode is Automatic, where the request goes straight to the provider's API, or Manual, where it lands on your Tasks page for you to handle.

A customer can request a refill only when all of these are true:

1. The order is completed. Pending, in-progress and partial orders cannot be refilled.
2. The service has refill enabled.
3. The order is still inside its Refill Days.
4. There is no refill already pending or in progress for the order.
5. At least 24 hours have passed since the order completed, and since the last refill the provider accepted.

The same rules apply to the refill button in the customer area and to the refill action in the API, so resellers and retail customers see the same answers.

Where You See Refills

Every refill request appears on the Tasks page, under the Refill type, with its status: Awaiting, In Progress, Approved, Denied or Error. Automatic refills show the provider's answer. Manual refills wait for you to approve or deny them.

If a provider declines a refill, the customer sees "The provider declined this refill". That message is accurate and it is also where the ticket starts.

Handling Refill Disputes

A customer says their followers dropped and the refill was declined. Before you reply:

1. Open the order and check the start count and the completion date.
2. Check whether the order is still inside the service's Refill Days.
3. Read the provider's refill terms for that service. They often come with conditions, so check the order meets them.
4. If the provider is wrong by its own terms, open a ticket with them from Orders using Create Ticket On Provider.

The real fix happens before the dispute: copy the provider's refill terms into your service description, word for word. If you sell "30-day refill" and your provider gives 7, the other 23 days are your cost.

What Drip-Feed Means in an SMM Panel

Drip-feed splits one order into runs. The customer picks a quantity per run, a number of runs, and an interval in minutes between them. 1,000 likes per run, 10 runs, 1,440 minutes apart is 10,000 likes over ten days instead of all at once.

People use drip-feed for launches that should build over days, for accounts that should not jump overnight, and for spreading a big order across several posts' worth of time. On the New Order page the customer switches on Drip-feed and fills in Runs and Interval; through the API it is the runs and interval fields on a normal order. A drip-feed needs at least 2 runs.

Turn it on per service with Dripfeed Enabled in the service form. Only enable it on services where your provider accepts repeated orders on the same link, or runs will fail halfway through.

How the Charge Works

The customer is charged for the whole drip-feed when they place it: quantity per run times runs, at your rate. Each run then becomes its own order sent to the provider when it is due. The per-run charge is the total divided by the number of runs.

Managing Drip-Feeds

Under Orders → Dripfeeds, each row is the parent schedule, with the user, service, link, total charge, charge per run, progress such as 3/10, status (Active, Completed or Canceled), quantity per run and interval. The actions:

Runs that already exist are never changed by these actions. If one run failed, handle that order on the Orders page like any other.

Refills on Drip-Feed Orders

Because every run is its own order, every run also has its own refill window, counted from when that run completed. On a ten-day drip-feed with a 30-day refill, the first run's window closes about nine days before the last run's. Customers rarely expect that. If you sell refill services with drip-feed, say in the description that refill applies per run, and check the run's own completion date when a request comes in.

What Cancel Means in an SMM Panel

Cancel stops an order that has not been delivered and refunds it. Customers want it when they pasted the wrong link or changed their mind. Whether it works depends on the provider, because the provider may already be running the order.

On FlashyPanels a customer can cancel only when:

• The service has Cancel Enabled in its form.
• The order is pending, processing or in progress.
• No cancel request is already open for that order.

If the order is with a provider, the panel asks the provider to cancel it. If not, a cancel task appears on your Tasks page. Either way, the Tasks page shows the request and its result.

Customer Cancel vs Admin Cancel & Refund

Customers request cancels. You decide them. From the Orders page you can also Cancel & Refund any order yourself, for example when a provider has stalled for days and you would rather refund than keep the customer waiting. Use it carefully: if the provider later delivers, you have paid for an order you refunded.

Partial: The Fourth Outcome

Partial is not a feature you switch on, but customers lump it in with cancels. A partial order delivered only part of the quantity. The panel refunds the undelivered part to the customer's balance automatically, and the order status shows Partial. There is nothing for you to calculate.

Setting Up a Service the Right Way

When you add or import a service, set these together:

Then write the description from the answers. A customer reading it should know the start time, the refill period, and whether cancel and drip-feed are available.

A Description Template That Prevents Disputes

Most refill and cancel tickets come from a description that promised more than the service does. A short, fixed format helps:

• Start: how long the service usually takes to begin.
• Speed: roughly how much it delivers per day.
• Refill: the number of days, or "No refill".
• Cancel: available while pending, or not available.
• Drip-feed: available or not.
• Link: what to paste, for example a public profile or a post URL.

Use the same format on every service so customers learn where to look. Services with clear descriptions get fewer tickets, and when a dispute does happen you can point to what the customer read before ordering.

Refill, drip-feed and cancel make your panel more useful and also more work. Turn each one on only where your provider supports it. Our guide on how SMM panels work shows where they fit in the order lifecycle, choosing an SMM panel provider covers testing refill support, and the features page lists the rest of the order tools. Plan limits are on the pricing page.