Seasonal retail brands rarely fail because the products stop selling. They fail in the eight weeks after the best quarter of their lives, when the inventory bill lands before the marketplace payout clears and the bank balance goes somewhere nobody modeled.
A profit and loss statement will not warn you about that. It records a sale when the invoice is raised and a cost when it is incurred, which is exactly the wrong lens for a business whose money moves on a completely different calendar. The gap between those two calendars is where seasonal brands get hurt.
A rolling 13-week cash forecast closes that gap. It is a deliberately short, deliberately granular view: one quarter ahead, one column per week, every real receipt and every real payment placed on the week it actually moves. It is the single most useful finance artifact a growing retail brand can maintain, and it takes an afternoon to build.
In short
- Profit and cash diverge hardest in seasonal retail, because inventory is paid for months before it sells and revenue arrives days or weeks after the customer pays.
- Thirteen weeks is the right horizon: long enough to see a full inventory cycle and a payout cycle, short enough that every line can be estimated from real commitments rather than guesses.
- Payout lag is the most commonly missed line. Marketplace and processor settlement timing can move a week of revenue across a month boundary and turn a positive week negative.
- Peak trading week is almost never the cash peak. The cash peak usually lands two to four weeks later, and the trough that follows it is the number the forecast exists to expose.
- Two scenario columns beat ten. Slow sell-through and late delivery cover most of the realistic downside, and both are modeled by shifting timing rather than rewriting the model.
Why retail cash flow surprises profitable brands
Every founder who has been caught by a cash squeeze says a version of the same sentence afterwards: the business was profitable the whole time. Usually that is true. Profitability and solvency are different questions, and only one of them stops payroll clearing.
Retail makes the divergence worse than most sectors because the working capital cycle is long and front-loaded. You commit cash to inventory, you wait for it to be manufactured, you wait for it to ship, you wait for it to sell, and then you wait again to be paid. Each of those waits is a separate lag, and they stack.
Profit is a judgment, cash is a date
Accrual accounting exists to tell you whether the business model works. It matches revenue to the period that earned it and spreads costs sensibly across time. That is genuinely useful for understanding D2C unit economics and whether each order makes money.
It is close to useless for answering the only question that matters in week nine: will there be enough in the account on Thursday. Cash forecasting throws out the matching principle entirely. A payment belongs in the week the money leaves, regardless of what period it relates to.
That difference explains why a brand can post a record gross margin and run out of money in the same quarter. The margin was real. It was simply locked up in cartons sitting on a boat.
The lags that do the damage
Four lags account for most seasonal cash surprises, and a good forecast models each one explicitly rather than folding them into an average.
- Production lag: deposit paid, goods made over 30–90 days, balance due before release.
- Transit and clearance lag: freight, duties and clearance fees hit while nothing has sold.
- Sell-through lag: stock lands weeks before the demand curve peaks.
- Settlement lag: the customer has paid, but the money sits with a marketplace or processor.
Brands that move from roughly one million to ten million in revenue feel these lags multiply rather than grow linearly, which is one reason cash discipline becomes a bottleneck at that stage. Anyone working through that transition should read our honest account of scaling D2C from one million to ten million alongside this piece, because the cash mechanics and the operational mechanics fail together.
Why the short horizon is the point
Annual budgets are strategy documents. They are built top down, they contain aspiration, and they are rarely accurate at the week level even in month one. A 13-week forecast is built bottom up from commitments that already exist: signed purchase orders, known rent dates, scheduled payroll, contracted freight.
The discipline of the short horizon is what makes it credible. You are not forecasting demand thirteen weeks out so much as scheduling money you have already agreed to move. Uncertainty concentrates in a handful of lines, which is exactly where the scenario work belongs.
What goes into each of the 13 weeks
Structurally the model is trivial. Thirteen columns across, one per week, usually starting on a Monday. Down the left, four blocks: opening cash, receipts, disbursements, closing cash. Closing cash in week one becomes opening cash in week two, and so on across the quarter.
The craft is entirely in the line items and the timing rules attached to them. A generic small business template will have five receipt lines and eight cost lines. A seasonal retail brand needs more receipt granularity and far more precision on inventory.
The line items a retail brand actually needs
Split receipts by settlement behavior rather than by product or by marketing channel. The forecast does not care whether an order came from paid social or email. It cares enormously whether the money arrives in two days or in fourteen.
Split disbursements by how controllable they are. Payroll and rent are fixed and dated. Ad spend is fixed in practice but adjustable in a crisis. Inventory payments are large, lumpy and tied to milestones. Keeping them separate is what lets you answer the question a bank or investor will ask: what can you actually stop.
| Block | Line item | Timing rule | Common error |
|---|---|---|---|
| Receipts | Owned site sales (card) | Gross sales minus fees, offset by processor payout lag | Booking gross sales on the day of the order |
| Receipts | Marketplace sales | Settlement cycle, typically biweekly, with reserve held back | Ignoring the reserve entirely |
| Receipts | Wholesale invoices | Invoice date plus agreed terms, plus a realistic slip factor | Assuming net 30 means paid on day 30 |
| Receipts | Refunds and chargebacks | Negative receipt, lagged behind the sales peak | Netting refunds inside the sales line |
| Disbursements | Inventory deposits | On purchase order confirmation | Modeling one payment instead of two |
| Disbursements | Inventory balances | Before shipment release, not on arrival | Timing the balance to the landing date |
| Disbursements | Freight, duty and clearance | At clearance, often as one combined broker invoice | Leaving duty out because it is not a supplier cost |
| Disbursements | Payroll and contractors | Fixed pay dates, plus seasonal temp uplift | Forgetting peak season temporary labor |
| Disbursements | Marketing | Card billing threshold, not the spend date | Assuming platform spend bills monthly |
| Disbursements | Debt service and facility fees | Scheduled, plus any covenant-linked step-ups | Omitting undrawn facility fees |
| Disbursements | Sales tax and VAT remittance | Filing calendar, which is rarely monthly in every jurisdiction | Treating collected tax as available cash |
Opening balance discipline
Start from the bank balance, not the accounting system. Pull the actual cleared balance across every account on the Monday morning you build the model, and reconcile any difference against the ledger before you go further. A forecast that starts from a wrong number is wrong in every column.
If the brand holds cash in more than one currency, model each currency separately and only convert at the point of an actual planned transfer. Blending currencies at a single rate hides the timing of the conversion, which in a volatile quarter is a material number on its own.
Granularity rules that keep it maintainable
Twelve to twenty lines is the right size. Below twelve you lose the timing precision that justifies the exercise. Above thirty the model becomes an accounting task nobody finishes on a Monday morning, and an unmaintained forecast is worse than none at all.
Anything smaller than roughly one percent of quarterly outflow belongs in a single “other operating” line with a flat weekly estimate. Precision on small lines is a comforting waste of effort. The variance that matters will always come from inventory and settlement.
Marketplace and processor payout lags
This is the line most brands get wrong, and it is the line that most often converts a comfortable week into an overdraft. The customer has paid. The order is shipped. The money is somewhere else.
Every sales channel holds funds for a period, and the period is rarely the one stated in the marketing copy. Standard card settlement on an owned store is usually short. Marketplace settlement is longer, runs on a fixed cycle rather than on a rolling basis, and frequently includes a reserve held against returns.
Cycles, not delays
The distinction between a delay and a cycle matters more than the length of either. A two-day rolling delay simply shifts your revenue curve two days to the right. A biweekly settlement cycle bunches two weeks of revenue into a single date, which means the week containing that date is flush and the week before it can be empty.
For a seasonal brand that difference is severe. If the settlement date falls the wrong side of a large inventory balance payment, a quarter that nets out comfortably can contain a week with no money in it. The forecast exists to find that week.
| Channel type | Typical settlement pattern | Reserve behavior | How to model it |
|---|---|---|---|
| Owned store, standard card processing | Rolling, short lag measured in days | Usually none once established | Shift daily net revenue right by the lag, then aggregate to weeks |
| Owned store, newly onboarded processor | Rolling, but with an extended initial hold | Rolling reserve on a percentage of volume | Model the reserve as a separate build-up line that releases later |
| Large marketplaces | Fixed cycle, commonly biweekly | Reserve held against returns and claims | Place the full settlement on the specific date, net of the reserve |
| Social and live commerce channels | Fixed cycle, tied to order completion rather than dispatch | Held until the return window closes | Lag from the end of the return window, not from dispatch |
| Wholesale and retail accounts | Invoice terms, commonly net 30 to net 90 | Not applicable | Terms plus a slip factor based on your own payment history with that account |
| Buy now, pay later providers | Rolling, often faster than card | Chargeback reserve varies by provider | Model separately, since the fee is higher and the timing differs |
Deriving your own lag instead of assuming one
Do not use the published figure. Export twelve months of payouts from each channel, match each payout to the order dates it covers, and calculate the actual median gap. Most brands find their real lag is longer than the documented one, because the documented figure describes the fastest case.
Use the median rather than the mean. Payout data contains occasional long outliers caused by disputes or verification holds, and the mean will be dragged by them in a way that makes ordinary weeks look worse than they are. Model the outliers separately in the downside scenario if they are frequent enough to matter.
Cross-border settlement adds a second layer
Selling into another market introduces a currency conversion and often a second settlement hop before the money reaches the home account. Both add days, and the conversion adds a rate that is not fixed. Brands expanding into new markets should model each corridor separately, a point we cover in more depth in our guide to scaling D2C internationally without losing your margin.
Inventory deposits, balances and freight timing
Inventory is where the largest numbers in the model live, and where the timing is least intuitive. Most retail brands pay for a single purchase order in at least three separate movements, sometimes four, spread across two or three months.
The typical chain runs: deposit on order confirmation, balance before release from the factory, freight on booking or on arrival depending on terms, then duty and clearance charges via the customs broker. Only after all of that does a single unit become available to sell.
Model the chain, not the invoice
A common mistake is to enter one inventory payment on the week the stock lands. That single error can misplace six figures by a month in either direction. Enter each movement on its own trigger event, and tie the trigger to the document that controls it: the purchase order for the deposit, the shipping notice for the balance, the clearance entry for duty.
Factories move. If a production date slips by two weeks, the balance payment slips with it, which is helpful for cash and unhelpful for the peak. That coupling is precisely why the late delivery scenario later in this article is worth building.
Duties and landed cost belong in the cash model
Duty, brokerage and any applicable fees are cash out of the account even though they never appear on the supplier invoice. Rates and thresholds vary by product classification and by origin, and they change, so the current figures should always be confirmed against the relevant customs authority rather than carried forward from last season’s file.
Where a brand imports into the United States, published tariff schedules and entry procedures are maintained by US Customs and Border Protection and by the Office of the United States Trade Representative. Treat any number in your own model as a working estimate until it is checked against those sources for the specific classification you are importing.
When the forecast says you need financing
A 13-week forecast frequently produces a clear and specific answer: the business needs a defined amount of cash for a defined number of weeks, bridging a gap that closes when peak receipts land. That is a far stronger position to borrow from than a vague sense that things are tight.
The specificity changes the conversation. A lender asked to cover a six-week working capital gap against confirmed purchase orders is being asked a very different question than one asked for a general facility. Our comparison of inventory financing options for growing retail brands covers the structures that fit that shape of gap, and the forecast is what tells you which one you actually need.
Build the facility into the model once it exists. Draws are receipts, repayments and interest are disbursements, and undrawn commitment fees are a small recurring line that brands routinely forget until the statement arrives.
Modeling a seasonal peak and the trough after it
Seasonality is not a modifier you sprinkle on the revenue line. It is a structural feature that moves every block of the forecast on a different schedule, and the whole value of the exercise for a seasonal brand is capturing that offset correctly.
The inventory outflow peaks first. The trading peak follows. The cash receipt peak follows that. Then everything falls away at once while fixed costs continue at full rate. Drawn on the same chart, those four curves are what a seasonal retail year actually looks like.
Peak trading week is not the cash peak
If the trading peak is the last week of November, the cash peak for a marketplace-heavy brand may not arrive until mid-December. For a wholesale-heavy brand on net 60 terms it may not arrive until February. Neither is a problem as long as the model knows it.
The failure mode is spending against the trading peak rather than against the cash peak. Reorders placed on the strength of a record sales week, paid for before the corresponding settlement clears, are a classic way to turn a great quarter into a crisis.
The trough is the number that matters
Read the model for its lowest closing balance, not its ending balance. The ending balance tells you whether the quarter works. The minimum closing balance tells you whether you survive it.
Set a minimum cash floor and mark it on the model explicitly. Most retail brands land on something between four and eight weeks of fixed operating costs, held as an untouchable buffer. Any week where projected closing cash falls below that floor is an action item, not an observation.
Seasonality needs a demand view underneath it
The weekly revenue split driving the receipt lines has to come from somewhere defensible. Last year’s weekly shape, adjusted for growth and for any change in channel mix, is usually the best available starting point for an established brand.
Brands without a usable history, or with a mix that has changed too much for last year to transfer, need a proper bottom-up view. Our walkthrough of forecasting demand without an enterprise tool covers a method that produces the weekly curve this model requires. Broad seasonal context is also available from official statistics: the US Census Bureau monthly retail trade data publishes both adjusted and unadjusted series, and the gap between them is a clean read on category-level seasonality.
Scenario columns: slow sell-through and late delivery
A single-path forecast is a prediction, and predictions about retail demand are usually wrong. A forecast with two downside cases is a planning tool, because it tells you which weeks break first and what warning sign precedes the break.
Resist the urge to build five scenarios. Two well-chosen downside cases capture most of the realistic risk, and both work by moving timing rather than by rewriting the model, which keeps them maintainable week after week.
Scenario one: slow sell-through
Model a sales shortfall of fifteen to twenty-five percent against plan, held flat across the remaining weeks rather than recovering. The recovery assumption is the one founders always slip in, and it is the one that makes the scenario useless.
Carry the second-order effects through properly. Lower sales mean lower settlement receipts on a lag, higher closing inventory, and pressure to discount, which cuts margin on the units that do move. The reorder that was planned for week eight probably should not happen, and the scenario should show what deferring it saves.
Scenario two: late delivery
Shift a major inbound shipment four to six weeks later and follow every consequence. The balance payment moves with it, which helps cash in the short term. Freight may move to a faster and more expensive mode, which hurts. Peak-week availability drops, so revenue moves or is lost outright.
Late delivery is the more instructive of the two scenarios because its cash effect is ambiguous in the first weeks and clearly negative later. A brand looking only at the next month would read the delay as good news for the bank balance. The full quarter shows otherwise.
| Dimension | Base case | Slow sell-through | Late delivery |
|---|---|---|---|
| Trigger to watch | Plan holds | Two consecutive weeks 10% or more below plan | Missed factory milestone or booking rollover |
| Revenue effect | As planned | Down 15–25% and flat thereafter | Shifted later, with partial permanent loss at peak |
| Inventory outflow | On milestone schedule | Unchanged for committed orders, reorder deferred | Balance payment delayed, freight cost up |
| Near-term cash | Baseline | Worse from week three onward | Better for two to four weeks, then worse |
| Minimum closing balance | Above the floor | Typically breaches the floor in the post-peak trough | Breaches later, in the following quarter |
| Primary lever | None required | Defer reorder, cut discretionary marketing | Split shipment, renegotiate balance timing |
| Decision deadline | Not applicable | Before the next purchase order is confirmed | At the point of freight booking |
Attach a decision to every scenario
A scenario without a pre-agreed response is theatre. For each downside case, write the specific action, the person who takes it, and the week by which it has to be taken. Two sentences per scenario is enough.
Pre-committing to the decision removes the hardest part of the moment: deciding under pressure, with incomplete information, when optimism is loudest. The founder who agreed in September to defer the January reorder if sell-through missed by twenty percent will find that call far easier to make in November.
Updating the forecast weekly without dread
Most 13-week forecasts die in week three. They die because the first version was too detailed, the update took two hours, and the second month of the quarter was busy. Build for maintainability from the start and the model survives the season.
Rolling is the key property. Each week you drop the week that has completed and add a new week thirteen, so the horizon stays constant. That is a genuinely different habit from a static quarterly model, and it is the one that keeps the forecast useful rather than historic.
The Monday routine
Thirty minutes is a realistic target once the structure is stable. Pull the actual closing bank balance for the week just finished. Enter actuals against forecast for the major lines. Add the new week thirteen. Update any inventory milestone that has moved. Re-read the minimum closing balance.
Do it at the same time every week and do it before the trading review, not after. Reviewing sales first anchors everyone on revenue, and the cash conversation then gets compressed into whatever time is left.
Track variance, not just position
Keep last week’s forecast alongside this week’s actuals in a small variance block. Over six to eight weeks that block teaches you more about the business than the forecast itself, because it shows which of your assumptions are systematically wrong and in which direction.
Most brands discover two or three persistent biases: receipts consistently later than modeled, refunds consistently higher after a discount event, freight invoices consistently larger than quoted. Correct the assumption rather than the individual week and the model gets steadily more accurate.
Keep it in one place and keep it boring
A spreadsheet is entirely adequate and remains the most common tool at this stage. One tab for the model, one for assumptions, one for the variance log. Avoid linking to live data sources until the structure has been stable for a full quarter, because a broken link on a Monday morning is how the habit dies.
Who should see it
The founder, the finance lead and whoever controls inventory purchasing. That third seat is the one most often left out, and it is the one whose decisions move the largest numbers in the model. Access to seasonal working capital is a persistent constraint for smaller firms, a pattern documented in the annual Federal Reserve Small Business Credit Survey, and the brands that navigate it well are generally the ones where purchasing and finance read the same forecast.
One practical note on scope. This article is general information about a planning technique, not financial, tax or accounting advice, and it does not take account of any particular brand’s circumstances. Cash forecasting intersects with tax remittance calendars, debt covenants and, for importers, customs obligations, all of which carry real consequences if they are handled wrongly. Work with a qualified accountant, and where imports are involved a licensed customs broker, on the specifics of your own situation, and verify any rate, threshold or filing deadline directly with the relevant authority before relying on it.
FAQ on 13-week cash forecasts
Why 13 weeks rather than 8 or 26?
Thirteen weeks is one quarter, which aligns with how most retail brands already plan inventory and reporting. It is long enough to contain a full production and settlement cycle, and short enough that nearly every line can be built from commitments that already exist rather than from demand assumptions. Eight weeks tends to cut off the post-peak trough, which is usually the number you most need to see.
How is this different from the cash flow statement my accountant produces?
The statement of cash flows is historic and reported monthly or quarterly, reconciling accounting profit back to cash movement for a period that has already happened. A 13-week forecast is forward-looking, weekly, and built from expected payment dates rather than from accounting periods. They answer different questions and a growing brand needs both.
Do I need accounting software to build one?
No. A spreadsheet is the normal starting point and stays adequate well past the point most brands expect. Accounting software is useful as a source for accounts payable and accounts receivable aging, but the forecast itself is a separate artifact with its own timing logic. Automate it only once the structure has been stable for a full quarter.
How accurate should the forecast be?
Week one should be close to exact, because almost everything in it is already committed. Accuracy degrades with distance, and being within roughly ten percent by week six is a reasonable working standard for an established brand. The value is less in the point accuracy than in reliably identifying which weeks fall below the cash floor.
What if my sales are too unpredictable to forecast weekly?
Unpredictable revenue is an argument for the model rather than against it. Build the disbursement side precisely, since costs are far more knowable than sales, then run the revenue line at a deliberately conservative level. That alone tells you how long the business can operate if sales disappoint, which is the most useful output for a volatile brand.
How do I handle a credit facility or overdraft in the model?
Model the facility explicitly rather than assuming it smooths everything. Draws appear as receipts, repayments and interest as disbursements, and any undrawn commitment fee as a small recurring line. Show both the cash position and the remaining headroom, since a week that is fine on cash but at the borrowing limit is not actually fine.
Should returns and refunds have their own line?
Yes, for any brand with meaningful return rates, particularly in apparel and footwear. Refunds lag the sales peak by several weeks and land in exactly the period when the cash position is already weakening, so netting them inside the revenue line hides the timing. Model them as a negative receipt on a lag derived from your own return window data.
How long does it take to build the first version?
An afternoon for the structure if the purchase order schedule and payout history are to hand. Deriving the real settlement lags from a year of payout exports is usually the longest single task and is worth doing carefully, since it is the assumption that most often turns out to be wrong. Weekly updates should settle to around thirty minutes once the model is stable.
What is the first sign the forecast is telling me something serious?
A projected closing balance that drops below your stated cash floor in any week inside the horizon, particularly in the weeks immediately after the trading peak. The second signal is a persistent one-directional variance, where receipts land later than modeled several weeks in a row. Both call for a decision while options still exist, which is the entire purpose of looking thirteen weeks ahead.