Drip feed explained: what runs and interval actually do
I run an SMM panel, and drip feed is one of the order options that produces more support tickets than its simplicity would suggest. Many of the ones I have handled came from buyers who understood what drip feed was for and misread a single field. What follows comes from setting up drip-feed services, watching the runs travel to suppliers and untangling the orders that went wrong. The numbers are illustrative.
What drip feed is and why buyers use it
A normal order sends the whole quantity to the supplier at once. However the supplier paces it, the profile gains the full amount as a single delivery. Drip feed breaks that into a series of smaller deliveries, placed one after another at a gap you choose.
Buyers want this for appearance. A post that picks up a few hundred likes in an hour and then goes still looks different from one that gains them in steps across a day. It is a scheduling tool. It does not change how the engagement is produced, and each individual run can still land in a quick burst.
The three fields: quantity, runs and interval
Switching drip feed on adds fields to the order form and quietly changes the meaning of one that was already there.
Quantity becomes the amount delivered in each run. Runs is how many times the panel places that quantity. Interval is the gap between one run being placed and the next, normally in minutes.
On some panels the quantity label does not change at all, and that is where the trouble starts.
Is quantity per run or the total?
Per run. The total the order delivers, and the total you pay for, is quantity times runs.
Take a buyer who wants 1,000 likes spread over ten steps, two hours apart. The correct entry is quantity 100, runs 10, interval 120. The panel places ten deliveries of 100, which adds up to 1,000.
Now the mistake I see most. The same buyer types the total they have in mind, 1,000, into the quantity field and sets runs to 10. The panel reads that as ten deliveries of 1,000. The order is now for 10,000 likes, ten times what was intended, and it is priced as 10,000.
If the form shows a total charge, read it before submitting. It is the quickest place to spot the error.
Schedule length works the same way: runs times interval. Ten runs at 120 minutes cover roughly 20 hours. On many panels the first run goes out as soon as the order is accepted, so the last run is placed one interval short of that mark, and it still needs its own time to deliver. If you are working to a deadline, add that delivery time and any queue at the start.
When you pay, and what each run has to satisfy
On many panels the charge for every run is taken from your balance when the drip-feed order is created, even if the last run is a day away. Your balance has to cover the whole total up front, and that money stays committed until the schedule ends or is cancelled.
The order stays one order on the panel, with one ID and one charge. Upstream, each run is usually sent to the supplier as its own delivery, with its own start count and status. On many panels that also means each run has to sit between the service's minimum and maximum by itself. Spread 1,000 across twenty runs and each run is 50. If the service minimum is 100, the order can be refused outright or the runs can fail one by one, even though the total is well above the minimum.
The interval can cause trouble in the other direction. If one run is still delivering when the next is due, the two overlap on the same link. Some panels refuse a new order on a link that already has an active one, and a run caught by that check can fail. An interval comfortably longer than one run takes to deliver avoids this.
What happens when a run fails or the service disappears
A drip feed stays open for hours or days, and in that time a supplier can stall or withdraw the service while half your runs are still waiting.
When that happens, the panel cannot place what remains. On many panels the remaining runs are cancelled, or the order is closed as partial, and the unused part of the charge goes back to your balance. Some panels reroute the order to another supplier, which keeps the schedule alive but can change how the later runs behave. Others refund nothing until you open a ticket. Check the order history rather than assuming the runs are still going out.
How cancelling a drip-feed order works
Cancelling normally stops future runs, not past ones. Runs already sent to the supplier exist there as separate orders, so they carry on delivering and stay charged unless they end partial. What returns to your balance is the cost of the runs that were never placed.
Some panels put a button on the drip-feed order, some handle it only through support, and some do not allow it once the schedule has started. If you might need to stop early, find out which applies before you submit.
How refill windows interact with runs
The refill guide covers the general mechanic. The drip-feed question is which date the window counts from. Depending on the terms, it may run from the first run, from the last run or separately for each run. A window counted from the first run can be half gone before the last run has delivered.
The arithmetic adds a second problem. A refill check compares the current count with a start count plus the quantity ordered. If followers from the first run drop before a later run begins, that later run's start count already reflects the loss. The first run's own check compares against a count that now includes every later delivery. The drop can vanish from both. Note the profile count before the first run and after every few runs, so you have your own record if you need to claim.
Drip feed, a slow service, or separate orders?
A naturally slow service delivers one order gradually at the supplier's pace. You get gentle growth without a per-run minimum or a multiplied quantity, but you do not control the pace, and the stated speed is only an estimate.
Drip feed hands you control of the timing, at the cost of the arithmetic above and a long open order with money tied up in it.
Placing separate orders yourself takes more effort. In return, each one is paid only when you place it, you can look at the result before committing to the next, and you can switch service if something seems off. Each order also gets a clean start count, which makes any later refill claim easier to argue.
A short checklist before you submit
- Multiply quantity by runs and confirm it matches the total you want.
- Check that the per-run quantity sits within the service minimum and maximum.
- Work out runs times interval, then add delivery time for the last run.
- Make the interval longer than one run takes to deliver.
- Confirm your balance covers the full total, since it may all be charged at once.
- Read how the service handles cancellation, failed runs and refill windows, following the approach in reading panel terms before ordering.
- Write down the profile count before the first run goes out.
The limits of this measurement
This guide explains how drip-feed orders are commonly set up, drawing on the author's experience running a panel and handling the orders and tickets they produce. It does not measure whether spreading delivery out affects drops, retention or how a platform treats an account, and it does not assess any individual panel. Panels implement drip feed differently, including when they charge, how they cancel and where they count refill windows from, so the behaviour described here is common rather than universal, and the terms of the service you actually order take precedence.
Frequently asked questions
Is the quantity in a drip-feed order per run or the total?
Per run, on panels that follow the usual drip-feed setup. What gets delivered and charged is that quantity multiplied by the number of runs. If you want 1,000 in total over ten runs, the quantity field takes 100. Typing 1,000 there with ten runs orders 10,000, and on many panels the charge for all of it leaves your balance the moment you submit.
How long will a drip-feed order take to finish?
Start with runs times interval. Ten runs at a 60-minute interval span roughly ten hours, a little less if the first run goes out immediately, as it does on many panels. Then add the time the final run needs to deliver, plus any queue before a run begins. A slow underlying service can push the real finish well past the schedule you typed.
Why was my drip-feed order rejected when the total was above the minimum?
On many panels each run is sent as its own delivery, and each run has to fit between the service minimum and maximum by itself. A total of 1,000 split into twenty runs is 50 per run, so a service with a minimum of 100 refuses it. Fewer, larger runs, or a service with a lower minimum, will usually get the order accepted.
Do I get money back if I cancel a drip-feed order?
Usually only for runs that have not been placed yet, and only if the panel lets you cancel at all. Runs already sent to the supplier exist there as separate orders and normally keep delivering, so their cost stays spent unless they end partial. Some panels cancel from the order page, some only through a ticket, and some not once the schedule has started.
What happens to my drip feed if the service is disabled halfway?
The panel can no longer place the remaining runs, so they are typically cancelled or the order is closed as partial, and the unused part of the charge returns to your balance. Some panels move the order to another supplier instead. Handling varies, so check the order status and history rather than assuming the schedule is still running quietly in the background.
Does refill cover every run of a drip-feed order?
That depends on the service terms. Some panels give each run its own refill window, some count the window from the first run and some from the last. Because each run records its own start count, a drop from an early run can be masked by later deliveries. Read the terms before ordering and note the profile count yourself as the runs finish.
Is drip feed safer than ordering the full amount at once?
It changes how growth looks on the profile, turning one jump into a series of smaller steps. It does not change how the engagement is produced, and each run can still arrive quickly. Nothing a panel sets on the order form stops a platform from removing engagement later, so treat drip feed as a way of pacing an order, not as protection.