7.5.1.2 - What are Reserve Policies & Their Triggers? (Difficulty: Advanced | Path: Scale)

In the high-stakes world of digital commerce, there is a dangerous misconception that "Sales equal Cash." You launch a campaign, the notifications light up your phone, and your dashboard shows a skyrocketing revenue graph. You immediately ramp up ad spend, order more inventory, and hire support staff, believing that the money flowing into your Shopify or WooCommerce dashboard is yours to spend. It is not. Between the moment a customer clicks "Pay" and the moment those funds hit your bank account, there stands a gatekeeper: the payment processor.

This gatekeeper—whether it is Stripe, PayPal, or a traditional merchant bank—views your explosive growth not as a success story, but as a liability. To them, every dollar you collect is a potential debt they might have to repay if you fail to deliver the product or if the customer disputes the charge. To protect themselves from this risk, they utilize a mechanism known as a Reserve. A reserve is essentially a forced, non-interest-bearing savings account where the processor locks away a portion of your revenue for a set period, ranging from 90 to 180 days.

For a scaling business, a surprise reserve placement is often the catalyst for a "cash flow death spiral." Imagine processing $100,000 in a month, expecting a payout of $97,000 (after fees), but suddenly receiving a notification that 25% is being held for 120 days. You now only have $72,000 accessible, but you have already committed $40,000 to ads and $40,000 to inventory based on the original number. You are now insolvent, despite being profitable on paper. This is the "Liquidity Trap" that kills more scaling e-commerce brands than lack of product-market fit.