It is 10pm on a Tuesday in February. You are looking at your warehouse report and doing the math on a pallet of organic elderflower that has been sitting since October. You ordered it in August because last summer's sell-through was the strongest you had ever seen. You were confident. You ordered 40% more than the prior year. You sold 60% of what you brought in. The rest has four weeks left on its shelf life and no buyer lined up. That is $18,000 in write-offs sitting on a pallet, and the worst part is that you made a completely reasonable decision with the information you had at the time.
This is the core problem with demand planning for food brands. The decisions feel reasonable in the moment. The consequences show up months later, in a warehouse, on a spreadsheet, as a line item that quietly destroys your margin. The goal of this guide is to give you a framework that catches those decisions before they become write-offs.
Why Standard Demand Planning Models Fail for Food Brands
Most demand planning frameworks were built for businesses where inventory does not expire, suppliers can be swapped on short notice, and lead times are measured in days rather than weeks. Food brands operate in a fundamentally different environment, and the five variables below are what make generic forecasting models break down in practice.
Shelf life on both sides of the supply chain. You are not just managing the shelf life of your finished goods. You are managing the shelf life of your raw materials simultaneously. An ingredient with a 9-month shelf life that arrives in March needs to be consumed in production before December. If your production schedule slips or demand softens, that ingredient becomes a liability. Most forecasting tools track finished goods inventory. Very few track the expiration exposure on your ingredient inventory in a way that connects back to your production plan.
MOQ minimums that do not match your demand curve. Your supplier requires a minimum order of 500 lbs. Your next production run needs 320 lbs. You order 500 lbs because you have to. Now you are holding 180 lbs of excess ingredient that needs to be consumed before it expires. This is not a purchasing mistake. It is a structural constraint that your demand plan needs to account for explicitly. The question is not just "how much do I need?" It is "how much do I need over the full shelf life window of this ingredient, and does that number justify the MOQ?"
Co-packer lead times of 4 to 8 weeks. When a retailer calls and tells you they want to run a feature promotion in six weeks, your co-packer may already be at capacity for that window. You cannot manufacture on demand. Your demand plan needs to be far enough ahead of your production schedule that you have real options when demand signals change. A forecast you update monthly is already too slow for a co-packer relationship.
Seasonal ingredient availability. Some ingredients are only available during a harvest window. If you miss the window, you either pay a significant premium for off-season supply or you reformulate. Neither option is good. Your demand plan needs to connect your sales forecast directly to your ingredient procurement calendar, with enough lead time to commit to seasonal purchases before the window closes.
Organic certification constraints. If you are running an organic product, you cannot simply switch ingredient suppliers mid-run because your primary supplier ran short. Your alternate supplier needs to be certified, approved, and ideally already on your label. This means your demand plan needs to carry a higher safety stock buffer for certified organic ingredients than you would for conventional equivalents, because your substitution options are limited and slow.
The five variables that break standard demand planning for food brands are shelf life on raw materials and finished goods, MOQ minimums that exceed near-term demand, co-packer lead times of 4 to 8 weeks, seasonal ingredient availability windows, and organic certification constraints that limit supplier substitution. A demand plan that does not account for all five will produce write-offs.
The Demand Planning Inputs You Actually Need
Before you can build a useful demand plan, you need to gather the right inputs. Most founders try to forecast from sales history alone. That is necessary but not sufficient. Here are the six inputs that actually drive a reliable food brand demand plan.
Sales velocity by channel, not just total sales. Your DTC velocity, your Amazon velocity, and your retail velocity behave differently. Retail velocity is driven by shelf placement, promotional calendars, and seasonal resets. DTC velocity is driven by your email and paid media schedule. Amazon velocity is driven by ranking, reviews, and whether you are running a deal. If you blend these into a single number, you lose the signal that tells you which channel is driving a change and whether it is likely to repeat.
A seasonal index built from at least two years of data. A seasonal index is a multiplier that adjusts your baseline velocity up or down based on the time of year. To build one, calculate your average monthly sales across all periods, then divide each month's actual sales by that average. A month with an index of 1.4 means that month typically runs 40% above your annual average. Apply these multipliers to your forward forecast to get a seasonally adjusted demand plan. With only one year of data, you cannot distinguish a true seasonal pattern from a one-time event, so two years is the minimum.
Your co-packer lead time, confirmed in writing. Do not use the lead time your co-packer quoted you when you first signed the agreement. Call them. Ask what their current scheduling horizon looks like. Lead times expand during peak season and contract during slow periods. Your demand plan should use the current confirmed lead time, not a historical assumption.
Ingredient shelf life by SKU, mapped to your production schedule. For every ingredient in your formulas, you need to know the shelf life from the date of receipt and the quantity you currently have on hand. From there, you can calculate the latest date by which that ingredient must be consumed in a production run. This is your expiration exposure, and it needs to be visible in your demand plan, not buried in a separate inventory spreadsheet.
MOQ constraints by supplier. Document the MOQ for every ingredient and packaging component. Then calculate how many units of finished goods that MOQ produces. If your elderflower MOQ produces 4,200 units of finished product and your 6-month demand forecast is 2,800 units, you have a structural over-order risk that needs to be resolved before you place the purchase order, not after the ingredient arrives.
Your retailer promotional calendar. Ask your retail buyers at the start of each quarter what promotions are planned for your SKUs. Get it in writing if you can. A retailer feature ad can double or triple your weekly velocity for a 2-week window. If that spike is not in your demand plan, you will either stock out and miss the opportunity or scramble to expedite a production run at a higher cost.
A reliable food brand demand plan requires six inputs: sales velocity by channel, a seasonal index from at least two years of data, confirmed co-packer lead time, ingredient shelf life mapped to your production schedule, MOQ constraints by supplier, and your retailer promotional calendar. Missing any one of these inputs creates a blind spot that will eventually produce a write-off or a stockout.
How to Build a Simple Demand Plan in a Spreadsheet
If you are running a $1M to $5M food brand and you are not yet using dedicated operations software, a spreadsheet demand plan is a reasonable starting point. Here is how to structure it, and where it will break down.
Start with a 13-week rolling horizon. Columns are weeks. Rows are SKUs. For each SKU, enter your baseline weekly velocity by channel, then apply your seasonal index multiplier for each week. Sum the channel velocities to get a total weekly demand forecast per SKU. This is your demand plan at the finished goods level.
Next, work backward from your demand plan to your production requirements. For each SKU, calculate the total units you need to produce over the next 13 weeks, then add your target safety stock. Subtract your current finished goods inventory. The result is your net production requirement. Divide that by your co-packer's minimum production run size to determine how many runs you need to schedule, and when those runs need to start given your co-packer's lead time.
From your production requirements, calculate your ingredient needs. For each production run, multiply the units to be produced by the ingredient quantities in your formula. Sum across all runs to get your total ingredient demand over the 13-week horizon. Compare that to your current ingredient inventory, accounting for expiration dates. The gap between what you need and what you have, adjusted for MOQ minimums, is your purchase order requirement.
This approach works. It is better than nothing. But it has four failure modes that will cost you money if you run a food brand at any meaningful scale.
The first failure mode is version control. The moment two people are editing the same spreadsheet, or the moment you have a v2 and a v3 floating around in email, your demand plan is no longer a single source of truth. Decisions get made on stale data.
The second failure mode is that the spreadsheet does not update automatically when your sales data changes. You have to manually pull your sales numbers, paste them in, and recalculate. Most founders do this monthly at best. That means your demand plan is always 2 to 4 weeks behind reality.
The third failure mode is that the spreadsheet does not alert you when an ingredient is approaching expiration faster than your production schedule will consume it. You have to check manually, and manual checks get skipped when things are busy, which is exactly when you need them most.
The fourth failure mode is that the spreadsheet does not connect your demand plan to your purchase orders. You still have to manually translate your ingredient requirements into POs, which introduces transcription errors and delays. For more on how these errors compound into COGS problems, see our guide on CPG COGS optimization for food brands.
A spreadsheet demand plan is a viable starting point for early-stage food brands, but it has four structural failure modes: version control drift, manual data refresh cycles, no automated expiration alerts, and no connection to purchase order generation. Each failure mode produces either write-offs or stockouts over time.
Manual Workflow vs. Guidance Workflow: The Over-Order Scenario
Scenario: Forecasting a seasonal organic ingredient with a 6-month shelf life and a 500 lb MOQ
The founder pulls last year's sales data from Shopify and their distributor portal in late July. They see strong summer velocity and extrapolate forward. They order 500 lbs of organic elderflower concentrate, the supplier MOQ, because last year they ran short in September. The ingredient arrives in August with a shelf life through February.
The spreadsheet demand plan is updated monthly. By October, it is clear that retail velocity has softened because a competing product launched in the same category. The founder does not see this signal clearly until the November update, when they notice finished goods inventory is higher than expected. By then, the ingredient has four months of shelf life remaining and there is no production run scheduled that will consume the full quantity before expiration.
Result: $18,000 write-off in February. The decision to over-order was made in July with no automated signal that the MOQ exceeded the demand forecast over the ingredient's shelf life window.
In July, the founder opens Guidance and reviews the demand plan for the elderflower SKU. The system has pulled the last 90 days of sales velocity by channel and applied the seasonal index. The forward 6-month demand forecast shows 310 lbs of ingredient consumption across planned production runs. The supplier MOQ is 500 lbs. Guidance flags a structural over-order risk: the MOQ exceeds the 6-month demand forecast by 190 lbs, and the ingredient shelf life is 6 months from receipt.
The founder has three options surfaced directly: negotiate a lower MOQ with the supplier, find a secondary use for the ingredient in another SKU, or accept the over-order risk with a documented decision. They contact the supplier and negotiate a 350 lb minimum for the season. They order 350 lbs. When retail velocity softens in October, Guidance flags the change in sell-through rate and adjusts the forward demand forecast automatically. The founder sees the signal in real time, not at month-end.
Result: No write-off. The MOQ vs. shelf life conflict was surfaced before the purchase order was placed, not after the ingredient arrived.
How to Handle Demand Spikes Without Over-Committing
Demand spikes in food brands come from two sources: retailer promotions and organic seasonal peaks. Both are manageable if you plan for them. Both are expensive if you do not.
For retailer promotions, the key is to get the promotional calendar from your buyers before you finalize your quarterly demand plan. A feature ad at a major natural grocery chain can produce a 2x to 4x velocity spike for a 2-week window. If you know about it 8 weeks in advance, you can schedule a production run with your co-packer in time to have finished goods on shelf before the promotion starts. If you find out 3 weeks before the promotion, you are likely too late to produce additional inventory and you will stock out during the highest-velocity window of your quarter.
The practical workflow is this: at the start of each quarter, send a one-paragraph email to every retail buyer who carries your product. Ask them to confirm any planned promotions for your SKUs in the coming 12 weeks. Most buyers will respond. The ones who do not respond are the ones who will surprise you with a last-minute feature, so follow up. Build the confirmed promotions into your demand plan as a multiplier on top of your baseline velocity for the relevant weeks.
For organic seasonal peaks, the challenge is different. You know the peak is coming because it happens every year. The question is how much to produce and hold in finished goods inventory versus how much to produce closer to the peak. The answer depends on your finished goods shelf life. If your product has a 12-month shelf life, you can produce 6 to 8 weeks before the peak and hold inventory without meaningful expiration risk. If your product has a 4-month shelf life, you need to time your production runs much more precisely to avoid holding finished goods that expire before the peak sells through.
The framework for sizing a seasonal production run is straightforward. Take your peak-period demand forecast, which is your baseline velocity multiplied by your seasonal index for the peak weeks. Add your target safety stock for the peak period. Subtract your current finished goods inventory. The result is your net production requirement for the peak. Schedule that run to complete no earlier than your finished goods shelf life allows, and no later than your co-packer lead time requires. The window between those two constraints is your scheduling target.
How to Use Sell-Through Rate and Days-on-Hand to Set Reorder Triggers
Reorder triggers are the mechanism that converts your demand plan from a static forecast into an active purchasing system. Without them, you are reviewing your inventory manually and making reorder decisions based on gut feel. With them, you have a defined rule that tells you exactly when to place a purchase order or schedule a production run. For a deeper look at how to calculate reorder points specifically, see our guide on reorder point calculation for food brands.
Sell-through rate measures how quickly you are depleting your current inventory relative to what you started with. Calculate it as units sold divided by units available at the start of the period, expressed as a percentage. A sell-through rate of 85% over 30 days means you sold 85% of your available inventory in that period. A sell-through rate of 40% means you are moving inventory much more slowly than expected. Tracking sell-through rate by SKU and by channel gives you an early warning signal when demand is softening before it shows up as excess inventory.
Days-on-hand measures how many days of supply you have remaining at your current sales velocity. Calculate it as current inventory divided by your average daily sales rate. If you have 1,800 units on hand and you are selling 60 units per day, you have 30 days of supply. Your reorder trigger should be set so that you place a purchase order or schedule a production run when your days-on-hand falls to the level that equals your co-packer lead time plus your target safety stock buffer.
For a food brand with a 5-week co-packer lead time and a target safety stock of 2 weeks, your reorder trigger is 7 weeks of days-on-hand. When your days-on-hand for a given SKU drops to 49 days, you need to act immediately. Waiting until you have 30 days of supply means you will stock out before your next production run completes.
The complication for food brands is that days-on-hand needs to be calculated against your shelf life, not just your sales velocity. If you have 90 days of supply on hand but your finished goods expire in 60 days, you do not have 90 days of supply. You have 60 days of supply and a 30-day write-off risk. Your days-on-hand calculation needs to cap at the remaining shelf life of your current inventory lot.
| Metric | Formula | What It Tells You | Action Trigger |
|---|---|---|---|
| Sell-Through Rate | Units sold / Units available at period start | How fast you are depleting inventory relative to what you had | Below 60% in 30 days: investigate demand softening |
| Days-on-Hand | Current inventory / Average daily sales | How many days of supply remain at current velocity | Below (lead time + safety stock days): place reorder |
| Shelf Life Adjusted DOH | Min(Days-on-Hand, Days until expiration) | True usable supply accounting for expiration | Below lead time days: expedite or accept stockout risk |
| MOQ Coverage Ratio | MOQ-implied units / Demand forecast over shelf life window | Whether your MOQ creates over-order risk | Above 1.0: negotiate MOQ or find secondary use for ingredient |
Setting these triggers in a spreadsheet is possible but requires manual recalculation every time your sales data updates. The more practical approach is to have your operations system calculate these metrics automatically and surface alerts when a trigger is hit. The goal is to move from reactive purchasing, where you notice you are running low and scramble, to proactive purchasing, where you place orders based on a defined rule before the urgency creates bad decisions.
Set reorder triggers using days-on-hand capped at remaining shelf life, not just raw inventory levels. Your trigger point should equal your co-packer lead time plus your target safety stock buffer. For a brand with a 5-week lead time and a 2-week safety stock target, any SKU dropping below 49 days-on-hand requires immediate action. Waiting until you feel the urgency means you are already too late.
Stop Managing Demand in Spreadsheets
Guidance connects your sales velocity, ingredient shelf life, co-packer lead times, and MOQ constraints into a single demand plan that updates automatically and alerts you before problems become write-offs.
See How Guidance WorksFrequently Asked Questions
What is demand planning for a CPG food brand?
Demand planning for a CPG food brand is the process of estimating how much of each SKU you will sell over a future period, then working backward to determine when to order ingredients, schedule co-packer runs, and build finished goods inventory. For food brands, demand planning must account for shelf life constraints on both raw materials and finished goods, co-packer lead times of 4 to 8 weeks, supplier MOQ minimums, and seasonal ingredient availability. It is not just a sales forecast. It is a coordinated plan that connects your sales projection to your purchasing and production schedule.
How far out should a food brand forecast demand?
Most food brands running at the $1M to $10M revenue range should maintain a rolling 13-week demand plan updated weekly, with a longer 6-month horizon used for ingredient procurement and co-packer capacity planning. The 13-week window gives you enough runway to act on your co-packer lead time without locking in commitments so far out that your forecast is meaningless. The 6-month horizon is specifically for ingredients with long lead times, seasonal availability windows, or high MOQs that require advance commitment.
How do I handle demand planning when a retailer runs a promotion I did not know about?
The honest answer is that you cannot fully prevent this, but you can reduce the damage. First, build a promotional calendar into your demand plan as a standing input. Ask your retail buyers at the start of each quarter what promotions are planned for your SKUs. Second, maintain a safety stock buffer calculated specifically for your highest-velocity retail SKUs. Third, if a promotion is announced with less lead time than your co-packer requires, communicate immediately with your co-packer about expedite options and with your buyer about realistic fill rate expectations. Surprises happen, but a documented demand plan gives you a defensible position and a faster response.
What is a seasonal index and how do I calculate one for my food brand?
A seasonal index is a multiplier that adjusts your baseline sales velocity up or down based on the time of year. To calculate it, take your average monthly sales for a given SKU over the past two years, then divide each month's actual sales by that average. A month with an index of 1.4 means that month typically sells 40% above your annual average. A month with an index of 0.7 means it sells 30% below. Apply these multipliers to your forward forecast to get a seasonally adjusted demand plan. You need at least two full years of sales data to build a reliable seasonal index. With only one year, you cannot distinguish a true seasonal pattern from a one-time event.
How do MOQ constraints affect demand planning for small food brands?
MOQ constraints force you to order in quantities that may not match your actual demand, which creates two risks. If your MOQ is larger than your near-term demand, you risk over-ordering and holding excess inventory that may expire. If your MOQ is smaller than your demand spike, you may need to place multiple orders and pay higher per-unit costs. The right approach is to calculate your demand over the full shelf life window of the ingredient, not just your next production run. If your ingredient has a 9-month shelf life and your MOQ covers 7 months of demand at current velocity, that is an acceptable order. If your MOQ covers 14 months of demand and the ingredient expires in 9 months, you have a structural problem that requires either renegotiating the MOQ or finding a secondary supplier.
Ready to Build a Demand Plan That Actually Works?
Guidance was built by a food brand operator for food brand operators. Connect your sales channels, map your ingredient shelf lives, and get a demand plan that updates automatically.
Get Early Access Browse Resources