Dropshipping Cash Flow Calculator

Behind the number

Cash flow in this model is unusually favourable in one respect and unusually hostile in another. The customer pays before the supplier is paid, which means no inventory investment, but the ad platform charges continuously while the processor settles on a delay.

Working capital required = daily ad spend × settlement delay in days, plus any processor reserve held against disputes.

That is the whole of the funding requirement, and it scales directly with ad spend.

A real example

At $150 a day of ad spend and a seven-day payout cycle, roughly $1,050 is outstanding at any moment.

Scale to $600 a day and the requirement is $4,200. The business is more profitable and needs four times the float, which has to exist before the scaling produces the cash to fund it.

Add a processor reserve: commonly 5% to 10% held for 90 days on a merchant with elevated disputes: and at $18,000 of monthly revenue that is a further $900 to $1,800 unavailable.

So a business scaling from $150 to $600 a day of spend needs perhaps $5,000 to $6,000 of float it did not need last month, and the profit from the higher spend arrives after the float is required.

The usual mistakes

The absence of inventory investment makes the model look like it needs no working capital, and that is true only at a constant spend level. Growth needs funding here exactly as it does anywhere else.

Refunds also come out of current settlements rather than the settlement that contained the original sale, so a spike in refunds reduces incoming cash immediately while the associated revenue was banked weeks earlier.

Using the result

Calculate the float requirement at your intended spend level before scaling, not after the payout gap appears. It is a simple multiplication and it is the reason scaling stalls more often than performance is.

Then keep dispute rates low deliberately, because processor reserves are the difference between a manageable float and an impossible one, and they are imposed rather than negotiated.

Why processors treat this model cautiously

High chargeback rates, long delivery times, and a business with no trading history are the three characteristics payment processors most associate with risk, and this model frequently has all three.

The consequences are real: rolling reserves, delayed payouts, or account termination with funds held for months. A business whose entire cash position sits with one processor is exposed to a decision it cannot appeal.

The protections that work are keeping the dispute rate well under the scheme thresholds, setting clear delivery expectations to prevent disputes rather than fighting them, and holding a second processor relationship before it is needed. The third costs nothing to arrange and is worth a great deal on the day the first one imposes a reserve.

Keeping a cash buffer separate from the operating float, sized to cover a month of refunds and a processor reserve.

The scenarios that end these businesses are rarely gradual: a product goes wrong, refunds spike, and the processor holds funds at the same moment. A buffer that covers that combination is the difference between a bad month and a closed business.