Speed, also known as drip-feed, spreads one order over time as repeated batches. A normal order requests its quantity once and follows the selected service's delivery pace. On the website, Speed is optional on services that support it: enter the total quantity, then choose how long the order should take. Leave it off when that extra scheduling does not serve the task.
Words such as “instant” or “fast” describe a service's intended start profile. They do not tell you whether the request is split into scheduled runs. On NotPanel, Avg. start helps you compare when delivery begins; Speed describes the order pattern after you choose a service.
Which order pattern fits your task?
| What you need | Order pattern to examine |
|---|---|
| One quantity for an existing target | A normal order using that service's usual delivery pace. |
| Several batches for the same target | A service that supports Speed, with a finish time or a batch count and interval. |
Read the actual service listing. Speed and refill are independent capabilities, and a capability shown for one service does not apply to every service in its category.
Two ways to set Speed, and the quantity math for each
On the website, you enter the total quantity you want to buy. The price is the service rate times that total, and Speed does not change it. Then pick one of two ways to spread the order:
- Finish in about… A slider with a total time of up to 48 hours. NotPanel makes the plan for you.
- Set batches yourself. Choose the number of runs and the interval between them. The total quantity must split evenly into the runs, so 1,000 or 990 splits more easily than 997.
In the API there are also two forms. With runs (2 to 100) and interval (1 to 1,440 minutes), quantity is the amount per run, so the total is quantity × runs. With drip_feed_total_minutes (1 to 2,880), quantity is the total. Do not send both forms in one request; that returns DRIP_FEED_CONFLICT. Sending runs=1 is a normal order.
For an illustrative 500-unit plan in the batch form, use 100 units per run and five runs. Entering 500 as the per-run quantity with five runs would request 2,500 units. That is a different purchase with a different charge.
Check both the minimum and the overall total. The total must stay within the service maximum. If a hypothetical service has a maximum of 1,000, five runs of 300 exceed it even though each run is below 1,000.
NotPanel Speed checker
The starting values are hypothetical. Copy the selected service’s current minimum, maximum and effective run/interval limits from New Order. This checks arithmetic only; it does not validate a target, price, balance or service availability. The “batches” form matches the API, where quantity is per run. On the website you enter the total quantity instead.
Passes these entered checks: 500 total units.
Runs × interval: 300 minutes (5 hours). First-to-last scheduled span: 240 minutes. These are scheduled intervals, not a completion estimate.
Speed can spread an order over at most 48 hours. The runs form uses runs × interval, including one interval for every run. Service limits can be tighter. Review the real order form before submitting.
What is the 48-hour limit?
Speed can spread an order over at most 48 hours. With runs and an interval, runs × interval must be at most 2,880 minutes. With a total time, the time itself can be at most 2,880 minutes. The service's run, interval and quantity limits must also pass. Those service-specific limits can be tighter than the overall limit.
| Runs × interval | Calculation | Duration result |
|---|---|---|
| 5 × 60 minutes | 300 minutes / 5 hours | Within the limit |
| 48 × 60 minutes | 2,880 minutes / 48 hours | At the limit |
| 49 × 60 minutes | 2,940 minutes / 49 hours | Exceeds the limit |
The calculation deliberately counts one interval for every run. A simple first-to-last schedule has only runs − 1 gaps: five runs spaced an hour apart have four gaps. Use runs × interval when checking whether NotPanel accepts the order, rather than substituting the shorter first-to-last span.
Read the start estimate separately from the full schedule
A five-run order can begin delivering during its first run while four runs remain. Its Avg. start describes the wait from order placement to first observed delivery. It does not add all scheduled intervals to that start or wait for the final batch to finish.
For example, a displayed start estimate of 12 minutes and a one-hour interval describe different things. The first is an estimate of when delivery begins; the second is the chosen interval between runs. Neither lets you calculate an exact completion timestamp without knowing actual delivery progress.
A short pre-submit check
- Confirm the target and service. Use the required link format and check that the service supports Speed.
- Write down the total you intend to buy. On the website, enter that total and choose a finish time, or check that it splits evenly into your runs.
- Check the limits. Review minimum quantity, the total, run count, interval and the 2,880-minute ceiling.
- Review the charge. Confirm the total in the order form before submitting.
- Keep the order number. Track the accepted order through Orders and use the same number for any support follow-up.
For an API integration, send runs and interval together as positive integers, with quantity as the per-run amount, or send drip_feed_total_minutes with the total quantity. Save one request_id for the purchase and reuse the same ID and payload for retries. The add-order reference has the field details.
Speed does not open a new cancel window
Speed orders cancel like any other order. The free full-refund cancel lasts 15 seconds from placement. After that you can request a cancel on services that allow it, and the undelivered part is refunded automatically once the cancel is confirmed. A later scheduled batch does not open a fresh window.
If an eligible ordinary order remains unresolved seven days after placement, NotPanel's full original-charge protection applies. A recognized refund can remain due until Wallet credit can be applied; check the credited amount in your account. The refund guide explains the protections that apply to eligible ordinary orders.
Questions about Speed and drip-feed orders
Does Speed (drip-feed) start more slowly than a normal order?
Speed describes how the order is spread out, not a fixed delay before the first delivery. Compare the selected service's Avg. start to understand when delivery typically begins. Later batches are a separate part of the schedule.
Can I spread a NotPanel order over seven days?
No. Speed can spread an order over at most 48 hours: runs multiplied by interval must be at most 2,880 minutes, or you choose a total time of up to 2,880 minutes. Individual services may impose tighter limits. The seven-day unresolved-order protection is a separate refund rule, not an available scheduling option.
Can I change the link or cancel later batches after the order starts?
You cannot edit a submitted order or cancel individual batches. You can cancel the whole order for a full refund during the first 15 seconds. After that, you can request a cancel where the service supports it, and the undelivered part is refunded automatically once the cancel is confirmed. Keep the order number for any support follow-up.
