Refunds, cancellations and queues: what a fair policy looks like

A refund policy is not a promise that everything will be refunded. It is a map of who carries the cost when an order does not go as planned. A fair policy answers four questions in writing: when an order can be cancelled, how a partial delivery is refunded, where the money goes, and how long a queue may hold an order before it is refunded in full.

Most buyers read the policy after something goes wrong. That is the worst time to read it, because the answer is already fixed and the only question left is whether the panel will follow its own text. Read it before the first deposit. It takes two minutes and it tells you more about the panel than the home page.

Four clauses a fair policy needs

The cancellation window. The policy should say when an order can be cancelled and what happens to the charge. Before the supplier accepts, a cancellation should be a full refund. After acceptance, the supplier's rules apply, and the panel should say so instead of promising a cancellation it cannot deliver.

The partial delivery formula. The policy should say that the undelivered share is calculated from the supplier's reported remains, that the refund is credited to the wallet, and that the calculation is rounded in the customer's favour. It should not require a ticket for arithmetic the panel can do itself.

The destination of the money. A wallet credit and a refund to the original payment method are different remedies with different timelines. The policy should name both and say when each applies. A policy that says "refund" without saying where is a policy that leaves the answer to the support agent.

The queue deadline. An order that cannot be placed should not sit in a queue forever. The policy should state the deadline and the remedy: a full refund to the wallet when the deadline passes. The deadline should be measured from payment, not from the last support reply.

The cancellation window

An order has a short window in which cancellation is clean. Before the supplier accepts, the order is still in the panel's hands. The panel can stop it and return the charge. After acceptance, the units are in the supplier's queue, and the supplier may have already started or reserved accounts.

A fair policy states the boundary in terms the customer can see: pending or placing means cancellable, in progress means not cancellable unless the supplier allows it. A policy that says "cancellation is possible before delivery" sounds generous and is impossible to apply, because delivery is the thing being cancelled.

If the panel cannot place the order at all, the cancellation is not a customer request. It is a failure to deliver, and the refund should be automatic. The policy should distinguish the two cases: a customer who changes their mind, and a panel that cannot place the order. The first may have a fee or a window. The second should not.

The partial delivery formula

Partial delivery is the normal failure mode, so the formula should be the most specific part of the policy. The supplier reports a remains value. The panel calculates the undelivered share from the order quantity and the remains. The refund is the undelivered share at the order rate, rounded up in the customer's favour.

The formula should use the rate that was charged, not the current rate. A panel that reprices the service after the order and then calculates the refund at the new rate can produce a number that is smaller or larger than the charge. The customer agreed to the old rate, and the refund should use it.

The formula should also state the rounding. A refund rounded down by a fraction of a cent is small, but it is a signal: the panel is applying the rounding in its own favour. A fair policy rounds the refund up, because the customer did not receive the units. The direction of the rounding is a small clause that tells you how the rest of the policy is written.

Where the money goes

A wallet credit is the default in this market because it is immediate and because it can be reused for another order. It is a real remedy: the balance is yours and it can be spent on any service. A panel that credits the wallet promptly is not avoiding a refund. It is choosing the quickest form of one.

A refund to the original payment method is slower because it depends on the processor. The policy should say whether it is available, what the minimum amount is, and how long it takes. A policy that offers only a wallet credit is acceptable if it says so. A policy that promises a card refund and then offers a wallet credit is not.

The destination should match the failure. A partial delivery is a small, frequent event, and a wallet credit is the right remedy. A cancelled order that never started is a full charge with no delivery, and the customer should be able to choose the destination if the panel can support it. A policy that treats both the same is simpler to write and less fair to use.

The queue deadline

A queue is not a delivery. An order can wait for supplier funds, a supplier top-up, a service restart or a manual placement. The wait is sometimes minutes and sometimes hours. The policy should put a number on the outside: if the order has not been placed by the deadline, it is refunded in full.

The deadline should be visible on the order page, not buried in the terms. A customer who can see the deadline can decide whether to wait or to cancel. A customer who cannot see it has to ask support, and the answer may change with the agent.

The deadline also protects the panel. A queue that is allowed to run forever accumulates orders the panel cannot place, and each one becomes a support ticket. A stated deadline turns an indefinite liability into a bounded one. It is good policy for both sides, which is why panels that skip it usually do so for a reason they do not want to write down.

A worked example: 10,000 ordered, 7,300 delivered

Take a hypothetical 10,000 Instagram followers order at the median rate in our market table. The full charge is $7.35. The supplier reports 2,700 remains. The delivered share is 7,300 and the undelivered share is 2,700.

At the same rate, the delivered share is worth $5.37 and the undelivered share is worth $1.98. A fair policy credits the second number to the wallet, rounded up if the arithmetic produces a fraction, and shows the remains it used. The customer does not need to open a ticket.

Now change one variable. Suppose the order completes at 10,000 and the count falls to 7,300 inside the refill window. The remedy is a refill, not a refund, because the supplier delivered the full quantity. The two cases produce the same profile count and different remedies. A policy that does not separate them will produce a support argument instead of a resolution.

Refill and refund are different remedies

A refund returns money for units that were not delivered. A refill replaces units that were delivered and then disappeared. The first is a delivery failure. The second is a maintenance promise. Mixing them is the most common source of confusion in this market.

A fair policy states the order: undelivered units are refunded, delivered units that drop are refilled inside the window, and the two are calculated from different baselines. A weak policy uses a refill to cover an undelivered unit, which turns a money remedy into a promise of more accounts, or uses a refund to cover a drop, which turns a maintenance promise into a cash cost the panel did not price.

If a service has no refill, the drop is the customer's risk. The policy should say so before the order, not after. If a service has a refill, the policy should state the window and the limit. A refill that is advertised but never honoured is worse than no refill, because it changes the buying decision without changing the remedy.

What the catalogue says

The current catalogue has 3188 active services, 1 with a refill flag and 1508 with a cancellation flag. Those counts describe the rows, not the outcome of any order, but they show which remedies the catalogue is built around.

Catalogue flag	Active services
Services with refill enabled	1
Services with cancellation enabled	1508
Active services in total	3188

Counts are read from the active catalogue when this page is rendered. A flag is a property of the row, not a promise about a specific order.

A catalogue with many refill flags and few cancellation flags is telling you that the business expects to replace rather than stop. A catalogue with the opposite balance expects to stop orders and refund them. Neither is wrong. The flags should match the policy text, and the policy text should match what support actually does.

A fair policy compared with a vague one

Clause	A fair policy	A vague policy
Cancellation	A named window and a clear boundary	"Before delivery"
Partial delivery	Automatic credit from the reported remains	"Contact support"
Rounding	In the customer's favour	Not mentioned
Destination	Wallet, with the card path named	"Refund" with no destination
Queue	A deadline and a full refund	No deadline
Refill	Separate from refund, with a window	Used for both failures
Evidence	The order id and the remains	A screenshot request

A qualitative comparison. It contains no market figures.

The right column is not always malicious. Some panels write vague policies because they have not decided how to handle the edge cases, and the support team improvises. The result is the same for the customer: the remedy depends on who answers the ticket. A written policy is a promise to be consistent, which is the thing a vague policy cannot offer.

How to read a refund policy in two minutes

1. Find the cancellation boundary. Look for the state names: pending, placing, in progress. If the policy uses "before delivery", keep reading for a definition.
2. Find the partial formula. Look for "remains", "undelivered" or "partial". If the policy only says "contact support", the formula is not written.
3. Find the destination. Look for "wallet" and the original payment method. A policy that says only "refund" has not answered the question.
4. Find the queue deadline. Look for a number of minutes or hours and the words "full refund". If there is no number, there is no deadline.
5. Find the refill clause. Look for the window, the limit and the baseline. A refill clause without a baseline cannot be applied.

If all five are present, the policy is specific enough to use. If two or three are missing, the policy is a summary and the details live in support. That is not automatically a reason to walk away, but it is a reason to ask before you deposit.

What to do when the policy is not followed

Start with the order id and the clause. "Order 12345 is partial with 2,700 remains; the policy says the undelivered share is credited to the wallet" is a message that points at a written rule. "You owe me a refund" is a message that invites a negotiation.

If the first reply does not resolve it, ask for the specific reason the clause does not apply. A support team that can name the reason is following a process, even if the process is not the one you wanted. A support team that repeats the marketing copy is not reading the policy.

Keep the evidence: the order page, the wallet ledger, the start count and the remains. A refund dispute is usually a dispute about a number, and the side with the number wins. The panel has the database; you have the screenshots. The policy is the thing that decides which number is supposed to be used.

For the delivery side of the same question, read what happens to your order between payment and delivery. For the test that reveals how a panel applies its policy, read how to test a new panel. The written policy is on the refund page, and the wider terms are on the terms page.