A boutique sales forecast is traffic multiplied by conversion rate multiplied by average order value, adjusted for season and for the fact that a new store starts slow. Everything else is detail. Build the monthly version of those three numbers, run it at a conservative, base, and stretch level, and you have a forecast that tells you what to buy, what you can afford to spend, and how far you are from covering your costs.
I am Carina Hatton, boutique owner since 2013 and ecommerce coach since 2019. Every number below is a clearly labelled hypothetical used to demonstrate the method. They are not benchmarks, industry averages, or predictions about your store.
Quick answer
Use the Boutique Sales Goal Calculator to see how many orders, visitors, and daily traffic targets you need to hit your revenue goal.
Open the Boutique Sales Goal Calculator →The formula
Transactions = traffic × conversion rate
Revenue = transactions × average order value
So: revenue = traffic × conversion rate × average order value
Average order value = revenue ÷ transactions
Conversion rate is expressed as a decimal in the calculation, so 2% is 0.02. These and the rest of the numbers a boutique runs on are collected in retail math formulas.
Where each input comes from
| Input | Online boutique | Physical storefront | If you have no data yet |
|---|---|---|---|
| Traffic | Sessions from analytics | Door count, or a manual tally over sample days | Estimate from your reach and location, then correct it quickly with real counts |
| Conversion rate | Orders divided by sessions | Transactions divided by people who entered | Use a deliberately cautious placeholder and replace it in month one |
| Average order value | Revenue divided by orders | Revenue divided by transactions | Build it from your own price points and a realistic items-per-sale assumption |
Do not import someone else's conversion rate as a target. Use a cautious placeholder, then replace it with your own measurement as soon as you have a few weeks of data. The Conversion Rate Calculator and the Traffic Needed Calculator let you work the relationship in both directions.
Worked hypothetical example: one month
Illustration only, for a small online boutique.
- Traffic: 4,000 sessions
- Conversion rate: 1.5%, or 0.015
- Transactions: 4,000 × 0.015 = 60
- Average order value: $72
- Revenue: 60 × $72 = $4,320
Now see how sensitive it is. Hold traffic and conversion steady and raise average order value to $85, and revenue becomes $5,100. Hold the value at $72 and lift conversion to 2%, and revenue becomes $5,760. Leave both alone and add a thousand sessions, and revenue becomes $5,400. That sensitivity is the useful part of a forecast, because it shows you which lever is worth your effort this month.
Conservative, base, and stretch
One forecast is a guess. Three is a plan, because you can buy inventory against the conservative case and prepare for the stretch case without betting on it.
| Scenario | Traffic | Conversion | Average order | Monthly revenue |
|---|---|---|---|---|
| Conservative | 3,000 | 1.2% | $65 | $2,340 |
| Base | 4,000 | 1.5% | $72 | $4,320 |
| Stretch | 5,500 | 1.8% | $80 | $7,920 |
The spread between conservative and stretch is wide on purpose, because all three inputs move together in real life. Commit your inventory dollars closer to the conservative end and let the upside be a good surprise rather than a cash problem.
The startup ramp
A new boutique does not open at its steady-state numbers. Traffic starts small, your product photos and descriptions are still improving, you have no repeat customers, and email and social audiences are being built from zero. A forecast that assumes month one looks like month twelve will overstate your first year and make you buy too much inventory.
Model the ramp explicitly. A hypothetical version might run something like this, with the store reaching its base case gradually rather than immediately.
| Month | Share of base case | Hypothetical revenue | What is driving it |
|---|---|---|---|
| 1 | 35% | $1,512 | Launch interest from people who already know you |
| 2 | 45% | $1,944 | Launch bump fades, early content starts working |
| 3 | 60% | $2,592 | First repeat customers, better listings |
| 4 | 75% | $3,240 | Email list growing, assortment corrected by real data |
| 5 | 90% | $3,888 | Reorders of proven sellers in stock |
| 6 | 100% | $4,320 | Base case reached |
Your ramp depends on the audience you start with. Someone opening to an existing following moves faster than someone starting cold, and a storefront on a busy street has a different shape again.
Seasonality
Retail is not flat across the year, and your own pattern depends on what you sell and where. Gift-heavy assortments concentrate around gifting occasions. Apparel follows weather and seasonal wardrobe changes. A store near a school, a beach, or a tourist route follows its local calendar. Build a seasonal index by assigning each month a share above or below your average rather than repeating one number twelve times, and correct it every year with your own history. Do not import a national seasonal curve and treat it as yours.
Online and storefront assumptions differ
Online traffic is measurable from day one, arrives from specific channels, and can be grown deliberately, but conversion is typically lower than in person and shipping affects the order value. A storefront has to count traffic manually and depends on location and weather, but the people who walk in are further along in deciding, and average order value often benefits from being able to touch the product and get help from staff. If you run both, forecast them separately and add them, because blending the assumptions hides what is actually happening in each channel.
Connecting the forecast to break-even
A forecast on its own tells you about revenue. What you need to know is whether that revenue covers your costs. Take your fixed monthly costs, apply your gross margin, and find the revenue level where the two meet. If your conservative scenario sits below that line, you are looking at the real risk in the plan, and it is much better to see it in a spreadsheet than in a bank balance.
Run it in the Break-Even Calculator, and make sure the margin you feed it comes from landed cost rather than wholesale cost, using the landed cost guide and the Profit Margin Calculator.
Connecting the forecast to inventory
This is the part most forecasts skip, and it is the reason to build one. Your forecast tells you roughly how much merchandise you need to sell each month at retail. Convert that to cost using your margin, and you have an approximate monthly buying requirement. Compare it against what you already own and what is on order, and you have your open-to-buy.
Work the monthly version in the Open-to-Buy Calculator with the method in open-to-buy for small boutiques. For the opening buy, use how much inventory to start a boutique and, depending on your budget, the $5,000 or $10,000 allocation examples.
How often to update
- Monthly. Replace forecast inputs with actual traffic, conversion, and average order value. This is the only update that really matters.
- Quarterly. Revisit the seasonal shape and the scenario spread now that you have evidence.
- After any major change. A new sales channel, a price change, a new category, or a marketing push all shift the inputs.
- Before every buying decision. The forecast exists to size orders, so check it before you commit money.
Keep the old versions. Comparing what you forecast with what happened is how your estimates get better, and by the second year your own history beats any assumption you could borrow.
Building the twelve-month view
Once you have a base month, a ramp, and a seasonal shape, the annual forecast is arithmetic. Take your base monthly revenue, apply the ramp share for each of the opening months, then apply your seasonal index to every month of the year. The result is a monthly revenue line you can plan buying and cash against rather than a single annual figure that hides every timing problem.
Timing is the part that catches new owners out. Inventory is paid for before it sells, often weeks before, so a strong month usually requires spending in a weaker one. A forecast that only shows revenue looks comfortable while the bank account tells a very different story. Put the expected order payments on the same monthly line as the revenue and the cash squeeze becomes visible early, which is when it is still fixable.
Keep three columns per month: forecast revenue, forecast merchandise spend, and actual results once they exist. That third column is what turns a forecast into a tool instead of a document.
Sanity-check the forecast in units
Revenue forecasts can drift into fantasy because dollars are abstract. Units are not. Convert the forecast and see whether it is physically plausible.
Take the hypothetical base case above: $4,320 in a month at a $72 average order is 60 orders, which is about two a day. If your average order is roughly two items, that is around 120 items leaving the store in a month. Now ask the practical questions. Do you own enough inventory to support that? Can you pack two orders a day alongside everything else? Does your traffic assumption support 60 buyers?
| Check | Question to ask | If the answer is no |
|---|---|---|
| Orders per day | Can you fulfil this volume with the time you have? | The forecast is an operations plan problem, not just a sales one |
| Units sold | Do you own or have on order enough merchandise? | Increase the buy or lower the forecast, but do not keep both |
| Traffic required | Do you have a concrete plan to reach this many people? | The gap is a marketing plan, not an assumption to raise |
| Average order value | Do your actual price points and items per sale produce it? | Rebuild the figure from your real prices |
Work the traffic requirement backwards with the Traffic Needed Calculator. If the number of visitors implied by your forecast is far beyond anything you have reached, the forecast is describing a marketing plan you have not built yet.
Which lever to pull when you are behind
The value of forecasting with three inputs is that when results fall short, you can see which one caused it instead of guessing.
- Traffic below forecast, conversion and order value fine. The store works and not enough people are seeing it. This is a visibility problem, and the answer is marketing consistency rather than discounting.
- Traffic fine, conversion below forecast. People arrive and do not buy. Look at product photography, descriptions, pricing clarity, shipping cost presentation, and how easy checkout is.
- Conversion fine, order value below forecast. People buy one inexpensive thing. Look at your price ladder, bundles, and whether anything encourages a second item.
- All three slightly down. Usually seasonal, or the assortment is not matching the customer. Check against last year before reacting.
Discounting is the reflex response to all four, and it only genuinely addresses the conversion case, at the cost of margin. Diagnosing first is cheaper. Use the Conversion Rate Calculator to confirm where the shortfall actually is before changing prices.
Common forecasting mistakes
- Forecasting a revenue goal backwards instead of forecasting the inputs that produce it.
- Assuming month one performs like a mature store.
- Borrowing a conversion rate from an unrelated business and treating it as a plan.
- Using a flat monthly number with no seasonal shape.
- Building only one scenario and buying inventory against it.
- Forgetting that returns, discounts, and shipping reduce what actually lands in the bank.
- Never comparing the forecast to actual results.
A revenue forecast does not tell you whether the money will be in the account when a supplier invoice lands. Pair it with the boutique cash flow example.
What to do next
- Write down your three inputs, using cautious placeholders where you have no data.
- Calculate a base month, then build conservative and stretch versions.
- Apply a ramp for the opening months and a seasonal shape for the year.
- Check the conservative case against break-even.
- Convert the forecast into a monthly buying requirement.
- Update it monthly with real numbers and keep the history.