Burn Rate & Runway for E-Commerce

Burn Rate & Runway

Burn rate is the rate at which your e-commerce business spends cash, and runway is how long your recorded bank balance will last at that rate. MerchantFlow computes both from your synced data and surfaces them through the AI assistant, the risk-flag insights, and the MCP API rather than as a dedicated dashboard page.

What Is Burn Rate?

MerchantFlow uses a gross cash-out definition of burn - the money leaving the business on overhead and marketing, normalised to a month:

Monthly Burn Rate = (Operating Expenses + Ad Spend) / (days in period / 30)

Note what this deliberately excludes: COGS, payment fees, fulfillment costs, and revenue. It is not "expenses minus revenue" - it is the recurring cash outflow you would still owe if sales stopped, which is what runway is really asking about.

Example:

• Period: last 30 days
• Operating expenses: $35,000
• Ad spend: $60,000
• Burn Rate: $95,000/month

What Is Runway?

Runway is how many months your recorded bank balance can absorb that burn:

Runway (months) = Latest recorded bank balance / Monthly Burn Rate

Example:

• Bank Balance: $120,000
• Monthly Burn Rate: $15,000
• Runway: 8 months

Runway is only produced when a bank balance has been recorded and monthly burn is above zero. With no balance on file, or with zero burn, no runway figure is returned at all.

How to Access Burn Rate Data

There is no standalone burn-rate page. Burn rate and runway reach you through three surfaces:

• Flow AI assistant - ask "what is my burn rate" or "how much runway do I have"; the answer is built from the formula above
• Risk flags - MerchantFlow raises a "Low cash runway: {n} months remaining" flag whenever runway falls below 6 months, and a "Monthly burn exceeds current period profit" flag when burn outruns profit
• MCP API - the get_bank_balance tool returns the current balance plus a burn figure for each of the last 30, 60 and 90 days. That tool uses a different, net-profit-based definition of burn: each window's burn is the total net profit over it and the average per day, so a negative number means the business burned cash. It then reports a single projected_runway_days in days, derived from the 30-day average only, and returns null with a runway_status of "profitable" when that average is not negative. Its numbers will not match the assistant's monthly figure

To record and review the underlying cash position, go to Profit > Bank Balance.

What Feeds the Calculation

1. Operating expenses - your entered OPEX for the period (Profit > Expenses)
2. Ad spend - synced from every connected ad platform (Google, Meta, Snapchat, TikTok, and Pinterest/Klaviyo where enabled)
3. Bank balance - the most recent balance you recorded, used only as the runway numerator

COGS, payment fees and fulfillment costs are tracked in the P&L but are not part of the burn figure.

Healthy Runway Targets

Because burn here is a gross cash-out figure, judge it by runway, not by its sign.

Established Businesses

• Target: Runway comfortably in double digits, with net profit consistently covering the burn
• Indicator: Net profit exceeds monthly burn, so the balance grows
• Action: Reinvest surplus into growth

Growth-Stage Businesses

• Target: 12+ months runway while net profit is intentionally thin or negative
• Indicator: Deliberately spending ahead of profit to buy growth
• Action: Monitor runway closely and plan fundraising well before cash runs low

Early-Stage / Startups

• Target: High burn acceptable if tied to intentional growth investment
• Indicator: Rapid spending on customer acquisition and infrastructure
• Action: Maintain at least 6 months runway - below that, MerchantFlow raises a low-runway risk flag - and have a clear path to reducing burn

How to Reduce Burn Rate

Increase Revenue

• Raise prices on high-demand products
• Launch new marketing campaigns with proven ROAS
• Improve conversion rate on your store
• Expand to new sales channels

Reduce Expenses

• Audit and cut unnecessary software subscriptions
• Renegotiate supplier contracts
• Optimize ad spend by pausing low-ROAS campaigns
• Reduce fulfillment costs through better logistics

Optimize Cash Flow Timing

• Negotiate better payment terms with suppliers
• Offer incentives for faster customer payment
• Reduce inventory holding costs

Best Practices for Burn Rate Management

1. Record Bank Balance Regularly

For accurate runway calculations, update your bank balance at least weekly at Profit > Bank Balance. More frequent updates produce more accurate runway estimates.

2. Review Burn Rate Monthly

Check your burn rate trend every month. A steadily increasing burn rate without corresponding revenue growth is a warning sign.

3. Plan Ahead

Do not wait until runway drops below 3 months to take action. Start planning expense reductions or fundraising when runway falls below 6 months.

4. Separate Growth Spend from Operational Spend

Understand what portion of your burn is growth investment (ad spend, new hires) versus operational costs. Growth spend can be reduced quickly if needed; operational costs are stickier.

5. Use the AI Assistant

MerchantFlow's AI assistant recognizes burn rate as a metric. Ask questions like:

• "What is my current burn rate?"
• "How many months of runway do I have?"
• "How has my burn rate changed over the last 6 months?"

Troubleshooting Burn Rate Issues

Burn rate seems inaccurate

Possible causes:

• Missing expense entries (OPEX is half the formula)
• Ad spend not syncing from connected platforms
• Bank balance not updated recently, so runway is measured against a stale numerator

Solutions:

1. Review your expenses at Profit > Expenses
2. Verify ad platform connections at Settings > Integrations
3. Update your bank balance at Profit > Bank Balance

COGS coverage does not affect burn rate - product costs are excluded from the formula by design.

No runway figure is returned

Cause: Either no bank balance has been recorded, or monthly burn computed to zero (no OPEX and no ad spend in the period).

Solution: Record a balance at Profit > Bank Balance, and confirm your expenses and ad platforms are feeding the period you are asking about.

Runway seems too short

Possible causes:

• One-time large expense inflating monthly burn
• Recent increase in ad spend
• A short lookback window magnifying a spike (burn is normalised as total / (days / 30), so a $5,000 spike inside a 7-day window annualises hard)

Solutions:

1. Check if a one-time expense is skewing the calculation
2. Ask over a longer window so the normalisation smooths out
3. Compare against previous months to identify anomalies

Frequently Asked Questions

What is a good burn rate for an e-commerce business?

Because MerchantFlow's burn is a gross cash-out figure, it is always zero or positive - it never goes negative when you are profitable. Judge it against runway instead: 12+ months is comfortable for a growth-stage store, and below 6 months triggers MerchantFlow's own low-runway risk flag.

How is burn rate different from expenses?

Burn rate is your operating expenses plus ad spend, normalised to a 30-day month. It ignores revenue, COGS, payment fees and fulfillment entirely, so it answers "how fast is cash leaving" rather than "am I profitable". Use net profit for profitability.

Does MerchantFlow forecast future burn rate?

Not as a forecast product. Runway is a straight-line projection of your current balance at the current burn rate, and the MCP get_bank_balance tool reports burn over 30/60/90-day windows before projecting a single runway in days off the 30-day figure. There is no scenario-planning or trend-forecasting model.

How often should I update my bank balance for accurate runway?

Weekly updates are recommended. The more frequently you update, the more accurate your runway calculation becomes. Navigate to Profit > Bank Balance to add your current balance.

Related Topics

• P&L Overview - Complete profit tracking
• Bank Balance - Cash position tracking
• Ad Spend Tracking - Advertising cost tracking
• Profit Margins - Margin analysis
• Expense Tracking - Business expense management
• Orders - Revenue and order tracking

Last updated: August 29, 2026