In this guide
A dropshipping store can be profitable on paper and still fail in the bank account. The reason is timing. You may need to pay a supplier today, wait several days for a platform payout, refund an order next week, and fund new ads before the first customers have received their packages.
The model removes inventory storage and large upfront stock purchases. It does not remove working-capital risk. Your cash still has to cover supplier invoices, processing fees, refunds, reships, chargebacks, software, and customer acquisition while the platform releases money on its own schedule.
This guide gives you a simple operating system for that gap. It is meant to sit beside our dropshipping pricing strategy guide, not replace it. Pricing answers whether an order can be profitable. Cash flow answers whether you can keep fulfilling orders while the money is moving.
The figures below are examples, not promises. Replace them with your own supplier terms, market, tax obligations, fees, refund history, and payout schedule. If you are still choosing a platform, read our Shopify review and then follow the complete Shopify dropshipping setup.
Cash flow is a timing problem, not just a profit problem
Profit asks whether the order created more value than it consumed after relevant costs. Cash flow asks whether the business can pay its next obligation when that obligation is due. Both questions matter. A product can have healthy contribution and still create a cash squeeze when the supplier needs payment before the customer payout arrives.
Do not treat a checkout balance as spendable profit. Part of it belongs to the supplier. Part belongs to the payment processor. Part may be needed for a refund or failed delivery. What remains after those obligations are funded is the amount that can safely support growth or owner withdrawals.
Watch out
If the plan only works when every payout is on time, every parcel is delivered, and nobody requests a refund, it is a best-case scenario rather than a cash-flow plan.
Build a cash map for one order
Start with one representative order instead of a monthly average. Identify every cash movement caused by a sale, including expenses that may not appear in the product import screen. Keep tax and owner compensation separate unless you have a specific reason to combine them.
A useful map begins with the actual customer payment, then subtracts landed cost, transaction fees, acquisition, expected customer-care cost, and the amount that must remain reserved until the order is settled. If a cost is uncertain, model a cautious and an expected case instead of deleting the line.
- 1
Record what the customer actually paid
Use the discounted checkout total, including shipping charges. List price is not cash received when a promotion is active.
- 2
Separate committed money
Supplier cost, transaction fees, refunds, taxes, and open-order obligations are not discretionary just because the account balance is visible.
- 3
Measure the payout gap
Count from customer payment to supplier payment, payout arrival, delivery, and the point where the highest-risk customer-care costs are known.
| Cash line | Illustrative amount | Timing question |
|---|---|---|
| Customer payment | $49.00 | When is it released to the bank? |
| Product and shipping | $18.00 | When must the supplier be paid? |
| Payment and platform fees | $1.72 | Are fees removed before payout? |
| Acquisition cost | $16.00 | When are ads or creator fees spent? |
| Refund and reship reserve | $4.00 | How long must this stay protected? |
| Uncommitted cash | $9.28 | Can this fund the next controlled test? |
Illustrative example only. Recalculate with your actual order value and costs.
Use landed cost and contribution margin
Supplier price is not the cost of selling the item. Landed cost includes product, shipping, packaging or customization, and per-order fulfillment fees. If you compare products using catalog price alone, you overstate the margin before traffic begins.
Contribution before ads is the amount left after variable order costs and fees. It is the pool that must pay for acquisition, refunds, support, software, taxes, and fixed overhead. Contribution after ads is the more useful number for a paid test because it tells you whether a new order creates or consumes cash.
A supplier with a slightly higher unit cost may still create more usable cash if it provides better tracking, fewer quality complaints, faster delivery, or more reliable packaging. Measure operational quality as part of the economics, not as a separate concern that can be ignored until later.
| Metric | Formula | Use |
|---|---|---|
| Landed cost | Product + shipping + fulfillment extras | Test whether the offer can be fulfilled as promised |
| Contribution before ads | Price - landed cost - transaction fees | Set the maximum acquisition cost |
| Contribution after ads | Contribution before ads - acquisition cost | Decide whether paid volume creates cash |
| Break-even ROAS | Revenue / contribution before ads | Set a product-specific ad threshold |
| Cash conversion gap | Payout date - supplier payment date | Estimate the reserve required |
Tip
A healthy gross margin does not make a product a good paid-traffic product. The offer also has to support acquisition and customer-care costs.
Calculate break-even ROAS before buying traffic
ROAS is revenue divided by ad spend. It is useful, but it is not a profit number by itself. A 3x ROAS can be profitable for one offer and unprofitable for another because their landed costs, discounts, fees, and refund rates differ.
If a customer pays $49 and variable non-ad costs total $25, the contribution available for ads is $24. The approximate break-even ROAS is $49 divided by $24, or 2.04x. The actual target should sit above that threshold to allow for attribution noise, refunds, and learning costs.
Treat the threshold as a planning rule, not a magic number. Check performance after orders settle, not only in the ad dashboard. A campaign can look efficient before refunds and support costs arrive.
- 1
Calculate contribution before ads
Subtract landed cost, discounts, transaction fees, and expected variable service cost from the real order value.
- 2
Divide revenue by that contribution
The result is an approximate break-even ROAS. Low contribution makes this threshold difficult to reach consistently.
- 3
Add a safety margin
Set a target that leaves room for refunds, attribution differences, and the cost of testing new creative.
Create a payout calendar and protected reserve
A reserve is money assigned to a known timing risk. List the next two weeks of supplier payments, planned ad spend, software bills, refunds, reships, taxes, and expected payouts. Compare the dates rather than looking only at a month-end balance.
Payment schedules vary by country, processor, account history, weekends, holidays, and risk reviews. Use the schedule visible in your own payment admin. Shopify Payments can deduct refunds from a future payout, and negative balances can require additional funds depending on location and account state. Check the current platform rules before building a forecast.
Keep four reserve rows visible: open supplier obligations, customer care, essential operating costs, and discretionary testing. The money can sit in one account, but the model should show who it belongs to and when it can be released.
| Reserve layer | Covers | Release rule |
|---|---|---|
| Open orders | Supplier invoices and shipping | Release after the obligation is paid and tracked |
| Customer care | Refunds, reships, failed delivery, chargebacks | Release as the order-risk window closes |
| Operations | Software, support, taxes, essentials | Release through a weekly operating budget |
| Testing | Creators, new creative, controlled paid tests | Spend only against a written hypothesis |
Watch out
Yesterday's revenue is not automatically today's ad budget. First check whether it is already committed to supplier invoices or likely customer-care events.
Model refunds, returns, and reships as normal costs
Refunds are part of the operating model, especially while product quality, delivery, sizing, and expectations are being validated. The aim is not to predict a perfect refund rate. It is to keep one difficult week from forcing you to delay supplier payments.
Track failure reasons separately. A changed mind, damaged product, address error, lost parcel, and inaccurate listing create different fixes. Record the amount, reason, supplier responsibility, support time, and whether a reship solved the issue.
Your page and post-purchase messages can reduce avoidable costs. State delivery windows honestly, show dimensions and materials, explain what arrives, and send tracking updates before the customer has to ask. Clarity protects both trust and cash.
- Set a conservative provisional reserve while order history is thin.
- Record the reason for each refund, not only the total amount.
- Update landed cost when reships or supplier failures become repeatable.
- Use customer questions to improve the product page and shipping promise.
- Do not hide a rising refund pattern inside a general overhead line.
Forecast growth with cautious, expected, and stress cases
The most dangerous forecast is a straight line from last week's sales. More orders create more supplier payments before payouts settle, more support conversations, and more opportunities for delivery or payment problems to become expensive.
Use at least three scenarios. The cautious case can use fewer orders and higher acquisition cost. The stress case should include a payout delay, a higher refund rate, or a supplier cost increase. The point is not perfect prediction. It is knowing which condition should make you pause before the bank balance makes the decision for you.
| Scenario | Assumption | Decision |
|---|---|---|
| Cautious | Lower volume, higher acquisition cost | Keep the testing budget flat |
| Expected | Current conversion and normal payout timing | Fund proven creative and review weekly |
| Stress | Higher volume, payout delay, more refunds | Pause discretionary spend until open orders are funded |
Use your own order counts. The important part is attaching a decision to each case.
Use tighter controls during the first 30 orders
Early orders are evidence about the product, supplier, offer, and expectations. Keep the system simple enough to see what each order teaches you. A spreadsheet is fine if it is updated consistently and tied to the order record.
Record product, price, discount, supplier cost, shipping, source, acquisition spend, payout date, tracking status, support contact, refund or reship outcome, and settled contribution. This is more useful than a revenue dashboard with no explanation for what the business kept.
- Do not withdraw owner income until open obligations and the reserve floor are covered.
- Keep a supplier payment method funded before launching more creative tests.
- Pause a product for a repeatable economic or operational problem, not one weak day.
- Review delivery promises after real tracked orders arrive.
- List discounts separately so conversion improvements do not hide margin erosion.
Know when to scale and when to pause
Scale when settled orders show repeatable contribution, the supplier can fulfill the volume, tracking is reliable, and the reserve remains above its floor after planned spend. A run of understandable numbers is more useful than one unusually profitable day.
Pause or reduce spend when new customer money is paying old obligations, the supplier queue is growing, refunds are rising without a fix, or paid traffic is below the contribution threshold. A pause protects customers and gives you time to fix the cause.
When you are ready for the operating stack, Shopify gives you a central place for products, orders, analytics, and payment settings. Use the Shopify setup guide to turn the cash map into actual store data.
Run a 30-minute weekly cash review
Review the same figures in the same order each week: cash available, open supplier obligations, expected payouts, unsettled orders, refunds and reships, ad spend, software, taxes, and the next seven days of fixed costs.
End with three written decisions: what to fund, what to pause, and which number would change your mind. This turns the spreadsheet into an operating rhythm and makes later decisions less dependent on the emotion of a good or bad day.
- 1
Reconcile the previous week
Compare planned versus actual orders, payouts, supplier payments, acquisition cost, refunds, and contribution. Investigate the largest variance first.
- 2
Project the next 14 days
Include open orders, planned spend, known bills, expected payouts, and a conservative customer-care allowance.
- 3
Set the spend ceiling
Choose discretionary spend that keeps the reserve intact in the expected case and survivable in the stress case.
Key takeaways
- Dropshipping can be profitable and cash-starved because supplier payments and customer payouts happen on different schedules.
- Build a per-order map with landed cost, fees, acquisition, refunds, reships, and the payout gap.
- Use contribution margin and break-even ROAS instead of revenue or ROAS alone.
- Protect visible reserve layers for open orders, customer care, operations, and testing.
- Forecast cautious, expected, and stress scenarios before increasing volume.
- Scale when settled-order data, supplier capacity, and the reserve support the next level of spend.
Frequently asked questions
There is no universal amount. Calculate supplier cost and the payout gap for the number of orders you can fund before payouts arrive, then add a reserve for refunds, support, essential software, and other obligations.