FinancePublic

90-Day Cash Runway For A New Ecommerce Store

Use a 90-day cash runway plan to schedule inventory, ad tests, subscriptions, logistics, refunds, and payback before a new store runs out of room.

By RanfengJun 3, 20265 min read
90-Day Cash Runway For A New Ecommerce Store

Start with this read

Use a 90-day cash runway plan to schedule inventory, ad tests, subscriptions, logistics, refunds, and payback before a new store runs out of room.

How much ad budget should a new store reserve for the first 90 days? There is no fixed percentage. Confirm starting cash, inventory, refund buffer, and fixed cost first, then split ad spend into test rounds with stop conditions.

The most dangerous early-store state is not zero revenue. It is revenue that appears to grow while cash gets tighter every week. Inventory is paid upfront, ad spend leaves daily, Shopify and apps charge monthly, packaging and logistics need deposits, refunds arrive later, and payment payouts may lag. If the first 90 days are judged only by sales, the store can run out of testing room before it finds a stable product-market path.

A 90-day cash runway is not a formal finance report. It is an operating rhythm. It separates cash into three buckets: money that must be committed before learning, money whose pace can be controlled, and money that should only be added after evidence appears. The goal is not to spend the budget. The goal is to buy enough validated learning to know whether the product, page, ads, fulfillment, and support promise can work together.

Build a 13-week cash view before deciding how many tests remain

Start with cash that is actually available today. Schedule committed supplier payments, inventory buys, fixed tools, ad-test envelopes, and a refund reserve by week, then list processor payouts, known receivables, and other expected inflows separately. Do not mix committed outflows and forecast revenue into one comforting balance; a store can look profitable for the month and still run short of cash mid-cycle.

Keep at least a base case and a more conservative case, and give each ad or inventory round a maximum spend plus a review point. If an irreversible outlay would push cash below your operating buffer before the next reliable payout, reduce the inventory, production, or test scope first instead of assuming the next round will sell better.

Protect irreversible cash first

Irreversible cash includes initial inventory, samples, creative production, theme work, baseline apps, packaging, domain and email, payment setup, shipping tests, and required compliance material. Once spent, these costs are hard to recover. Do not load too many SKUs before demand is tested, and do not subscribe to tools simply because a complete stack looks professional.

Attach a validation job to every irreversible cost. Samples validate quality and creative production. Inventory validates first fulfillment. Apps should solve named workflows, not decorate the admin. Fixed spend without a validation job should usually wait.

Allocate ad budget by learning rounds

The first 90-day ad budget should not be pushed into one long burn. Divide it into rounds. The first round validates tracking and page handoff. The second validates creative angles and audience quality. The third tests profit, repeatability, and scaling potential. Each round needs a stop condition, otherwise sunk cost starts pretending to be strategy.

Ad cash flow also depends on payout timing. Even when orders arrive, processor payouts, fulfillment costs, refund windows, and restocking lead times delay cash recovery. A campaign can appear ROAS-positive and still strain cash if payouts are slow, inventory requires prepayment, or refunds rise.

Inventory is not safer just because there is more of it

Too little inventory creates stockouts, but too much inventory locks cash into an unproven assumption. In the first 90 days, learning speed matters more than warehouse size. Use smaller inventory to test images, price, sizing, shipping time, and support questions before committing to a larger replenishment.

Judge inventory by turnover and quality, not only sales. A fast-selling SKU with high returns, heavy support questions, and ad dependency may be fragile. A slower SKU with strong margin, low return risk, and repeat use may be healthier. Track cash tied in inventory, expected sell-through date, and replenishment lead time.

Treat refunds and support as cash-flow events

Refunds are not only support issues. They reverse revenue, may leave payment fees behind, consume shipping cost, and require support labor. The first 90 days need a refund buffer, especially for categories exposed to sizing, quality, shipping time, duties, or expectation mismatch.

Support tickets can warn cash flow before finance reports do. Repeated questions about shipping, duties, sizing, returns, or product use mean the page promise is unclear. Moving those answers into product pages, policy pages, and emails can reduce future refunds and protect cash.

Make one major cash move per week

When cash feels tight, teams often change price, creative, inventory, budget, and apps at the same time. That makes cause and effect unreadable. In the first 90 days, pick one main cash action per week: restock, increase budget, change promotion, add an app, or pause a channel. Record the expected effect and review date.

If cash falls below the safety line, protect actions that keep learning alive. Keep payment, logistics, support, and a small amount of controlled testing. Pause unnecessary apps, low-confidence creative production, and speculative inventory. Cash management lets the store survive enough rounds to become smarter.

Use three lines to judge runway

The first line is the survival line: after the next 30 days of fixed cost, committed inventory, logistics, and refund buffer, how much cash remains usable? The second is the learning line: how many clear ad or page tests can that cash still support? The third is the payout line: how long does order revenue take to become usable cash, and how far ahead must inventory be paid?

When the three lines conflict, slow down. If cash covers only 45 days, replenishment lead time is 30 days, and ad testing needs a 14-day read, the team cannot safely increase both stock and budget. The better move may be narrowing SKUs, lowering test spend, or improving inventory turnover instead of chasing higher gross sales.

90-day cash runway table

StageCash focusAvoidReview metrics
Days 1-30Validate product, payment, tracking, and first fulfillmentLarge inventory buys and extra appsTest orders, page conversion, support questions
Days 31-60Validate creative angles, ad quality, and refund reasonsScaling from one good dayROAS, contribution margin, refund rate, inventory turnover
Days 61-90Decide restock, scale, or narrow the catalogExpanding many markets and SKUs at onceCash balance, payout timing, replenishment lead time

A 90-day cash plan is not conservative by default. It makes each dollar buy usable evidence. Early survival often depends less on whether the first ad test wins and more on whether the store has enough cash to run a better second and third test.

After the plan is written, run price and ad thresholds through the pricing, ROAS, and break-even ROAS tools. Scaling is justified only when cash, profit, and data all point to the same decision.

Sources

Next path

Connect this article to execution

A 90-day cash runway should connect startup cost, real profit, ROAS, and inventory turnover rather than only sales.

FAQ

How much ad budget should a new store reserve for the first 90 days?

There is no fixed percentage. Confirm starting cash, inventory, refund buffer, and fixed cost first, then split ad spend into test rounds with stop conditions.

Should inventory or ads come first?

Keep enough inventory to validate product and fulfillment, then use controlled ad tests to validate page and traffic. Do not lock most cash into stock before conversion evidence exists.

Does the cash runway need daily updates?

Weekly is the minimum early on. During ads, restocks, or promotions, check cash balance, ad spend, orders, refunds, and payouts every two to three days.

Why can cash be tight when ROAS is acceptable?

Payout delays, prepaid inventory, refunds, shipping, payment fees, and daily ad spend all affect cash timing. Platform ROAS is not cash-flow health.

#cash runway#startup cost#inventory#ad budget#cash flow