Production planning decides what to make and when. Inventory control decides how much to keep, of finished goods and of materials. They're often named together, PPIC for short, because each is the other's input: you can't decide what to make without knowing what's on the shelf, and what's on the shelf is the result of what you made. Run them apart and you get a warehouse with three weeks of one product and none of another. Together they come down to two sums done every week. What to make = what will ship + the cushion you want − what you have. What to buy = what the plan needs − what's on hand − what's already coming. Below is a week for a made-up nut butter maker, both sums, the numbers each side sets, and a sheet.
The short version
- Planning answers what to make. Inventory control answers how much to keep.
- To make = expected to ship + safety stock − on hand.
- Round up to whole batches, and look at the stock that leaves.
- To buy = needed for the plan − on hand − on order.
- A material that's short stops its batch: check before the week starts.
- Do both sums every week, from counted stock.
- TaroStack does the two sums from live stock and names what's short. More below.
Sum one: what to make
| Product | Expected to ship | On hand | Safety stock | To make | Batch size | Batches | Planned | Stock at the end of the week |
|---|---|---|---|---|---|---|---|---|
| Peanut butter, 16 oz | 900 | 350 | 200 | 750 | 240 | 4 | 960 | 410 |
| Almond butter, 12 oz | 400 | 260 | 100 | 240 | 120 | 2 | 240 | 100 |
| Cashew butter, 12 oz | 150 | 210 | 60 | 0 | 120 | 0 | 0 | 60 |
| Chocolate hazelnut spread, 12 oz | 300 | 40 | 80 | 340 | 120 | 3 | 360 | 100 |
Peanut butter. 900 jars are expected to ship. The maker wants 200 left as a cushion and has 350. So it needs 900 + 200 − 350 = 750. A batch is 240 jars, and 750 is 3.1 batches, so it makes four: 960. That leaves 410 on the shelf at the end of the week, 210 more than the cushion.
Cashew butter. 210 on hand covers the 150 expected and the 60 wanted in reserve. Nothing is made. Without the sum, a batch of cashew gets made out of habit.
Chocolate hazelnut. 40 on hand against 300 expected. It needs three batches, and it needs them early in the week.
The rounding is where planning and inventory meet. Four batches of peanut butter in place of 3.1 puts 210 extra jars on the shelf. Whether that's right depends on how long the product keeps and what next week looks like. Three batches, 720 jars, would leave 170, under the cushion. This maker takes the four.
Sum two: what to buy
| Material | Needed for the plan | On hand | On order, due before its batch | To buy | Needed by |
|---|---|---|---|---|---|
| Peanuts, roasted | 960 lb | 600 lb | 500 lb | 0 | Monday |
| Almonds, roasted | 180 lb | 90 lb | 0 | 90 lb | Wednesday |
| Hazelnuts, roasted | 162 lb | 200 lb | 0 | 0 | Thursday |
| Cocoa and sugar mix | 108 lb | 150 lb | 0 | 0 | Thursday |
| Jar and lid, 16 oz | 960 | 1,400 | 0 | 0 | Monday |
| Jar and lid, 12 oz | 600 | 380 | 0 | 220 | Wednesday |
| Labels, almond | 240 | 1,000 | 0 | 0 | Wednesday |
Needed is the plan multiplied through each recipe: four batches of peanut butter take 960 lb of peanuts.
Two lines have something to buy. The almonds are 90 lb short. The 12 oz jars are 220 short, and they're shared: almond butter and the hazelnut spread both use them, 240 and 360. Looked at one product at a time, there are enough jars for either. Together there aren't.
The peanuts are only covered because 500 lb are on order. That's fine if they arrive before Monday's first batch. "On order" is a date, not a quantity. The full method is in material requirements planning example.
The numbers each side sets
| Number | Who sets it | What it trades |
|---|---|---|
| Safety stock | Inventory control | Running out, against money and shelf life on the shelf |
| Reorder point for a material | Inventory control | A stopped batch, against stock paid for early |
| Batch size | Production | Changeovers and cleaning, against stock made ahead of need |
| The week's sequence | Production | Hours lost to washdowns, against what ships first |
| Expected to ship | Sales, with the planner | A promise, against what can be made |
These pull against each other, and there's no setting that satisfies all five. A bigger batch saves a changeover and adds stock. A thinner cushion frees cash and risks an empty shelf. The weekly sums are where the trade is made in the open, with numbers. How to set the cushion is in safety stock formula, and the level that triggers a purchase in reorder point example.
The weekly loop
- Count, or trust a count that's kept current. Both sums are only as good as "on hand".
- Sum one: what to make, in whole batches.
- Sum two: what to buy, with dates.
- Check it fits: hours, people, equipment.
- Publish the schedule, and place the orders.
- Afterward, set the plan against what was made: see production plan vs actual.
Who does this, and on which day, is in production planner: roles and responsibilities. A schedule to publish is in master production schedule template.
Get the sheet
Download the planning and inventory control sheet. Two sheets and a read-me: one works out what to make from what will ship, the stock on hand, the safety stock and the batch size, and shows the stock left at the end of the week. The other sets the materials the plan needs against what's on hand and on order. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
Both sums start from "on hand", and on a spreadsheet that's whatever was typed after the last count. The second sum's "needed" column is worse: someone has to multiply every planned batch through its recipe by hand, and shared materials, like the 12 oz jars, have to be added across products. With four products that's ten minutes. With forty, it doesn't get done, and the week finds out what was short on the day the batch should have started.
How TaroStack does it
TaroStack does both sums from stock that's kept current.
Stock moves when things happen: receiving adds lots, a batch takes its materials and adds what it made, shipping takes what left.
Planning, on Growth, says what to make, what to buy and what to move, and when, in plain words. Every suggestion is a draft you approve.
It names the exceptions: what will run short, arrive too late, or expire before it's used.
Safety stock and min/max for each item, and reorder points suggested from how stock actually moves.
"What could I make right now" says which batches the materials on hand will cover, shared ones included.
| The sum | Spreadsheet | In TaroStack |
|---|---|---|
| On hand | The last count typed in | Kept current |
| What to make | Sum one, by hand | Planning, on Growth |
| What the plan needs | Multiply through each recipe | Worked out from the recipes |
| A shared material that's short | Easy to miss | Named, with the day |
TaroStack doesn't decide the trade between a bigger batch and a fuller shelf: it shows you the numbers. Recipes, batches and lots are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes, with planning). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
