Inventory Planning Challenges for Mid-Market CPG Brands and Manufacturers

What changes in inventory planning between $50M and $500M?

A CPG company in this band is no longer one buyer with one supplier and one channel. The same team now forecasts retail, wholesale, DTC and Amazon, buys raw materials shared across dozens of finished goods, and either books time at co-manufacturers or runs its own production lines. The ERP has usually been in place for a few years. The planning has not moved with it.

The table below sets out what typically changes, what breaks, and which kind of fix each problem needs.

The rest of this post takes the biggest of these in turn.

Why does the ERP hold the numbers but not the plan?

Most mid-market CPG companies run an ERP such as NetSuite or Sage 100 by the time they pass $50M. It records sales orders, invoices, receipts, inventory by location and purchase orders. It is the system finance closes the month on, and it should stay that way.

ERPs do include planning features, and they are worth knowing before you buy anything else:

• NetSuite Demand Planning is sold as an add-on module. It offers four projection methods: linear regression, moving average, seasonal average and a sales forecast you maintain.
• The person running the calculation picks one method for that run. It is not chosen per SKU from each item's own history.
• Safety stock is a fixed quantity entered on each item record. NetSuite adds it to the amount needed after calculating demand. It is not resized as demand variability changes.

For a company with a few stable SKUs, that is often enough. For a company with hundreds of SKUs across several channels, it usually means the real plan gets rebuilt in a spreadsheet, using an export from the ERP. The spreadsheet is right on the day it is built and drifts until the next rebuild, which is normally when something has already gone wrong.

The practical answer is to keep the ERP as the system of record and plan in a separate layer that reads from it. The NetSuite integration page shows how that split works in practice: the ERP keeps the transactions, and the planning layer keeps the forecast and the reorder plan.

What breaks when you sell through retail, wholesale, DTC and Amazon at once?

Each channel has a different demand pattern and a different lead time to plan against:

• Retail arrives as large, irregular purchase orders from retailer distribution centres, with an initial fill followed by replenishment that depends on sell-through.
• Wholesale and distributors order on their own cycles and can hold stock you cannot see.
• DTC moves with your own marketing calendar.
• Amazon replenishment follows Amazon's inbound limits and its own ordering patterns.

When all four are summed into one total and forecast together, the combined line looks smoother than any channel actually is. A retail reset can be hidden by a strong DTC month until the retailer's next order arrives. The fix is a forecast per SKU per channel, combined only when it is time to buy. Multi-channel demand planning covers the method in more detail.

Retail also needs its own inputs. A retail forecast is best built from door counts and units per store per week rather than from total shipments, because a change in either one is the earliest signal you get.

How do co-manufacturers and your own lines change the problem?

Making product, rather than buying finished goods, adds a second layer of planning: the raw materials and packaging behind each finished SKU, and the dates when production can happen.

If a co-manufacturer makes your product

You plan around the co-man's booked production windows. The questions are how much to make in this window, whether that covers demand until the next window, and whether the ingredients and packaging you supply will be at the co-man in time. Missing a window is expensive because the next one may be weeks away. Co-packer inventory management covers keeping visibility of stock held at the co-man.

If you make product on your own lines

You plan runs against line capacity, shifts and changeovers, and allergen sequencing adds rules about what can run after what. Moving one run changes the material requirement for every run after it. Line scheduling is the scheduler's job, usually supported by the ERP or a manufacturing execution system. Planning still has to give the scheduler a demand plan they can trust and a material plan that moves when the schedule moves.

If you are the co-manufacturer

Your demand is your customers' purchase orders and forecasts, which arrive at different levels of detail and reliability. Shared raw materials across several customers' products make contention a real risk: one customer's run can consume material another customer's run depends on.

In all three cases, raw materials are planned the same way: the finished-goods forecast is multiplied through the bill of materials, netted against stock on hand and on order, and timed to arrive before production. How to calculate raw material demand from a finished-goods forecast works through the arithmetic.

Which problems does a planning layer fix, and which need an ERP or a planner?

Buying software for a problem that is really a process problem is the most common mistake in this band. It helps to sort the work into three groups before evaluating anything.

Work that suits a planning layer

• A statistical forecast for every SKU and channel, refitted as patterns change
• Safety stock sized from each SKU's demand variability and your service-level target
• Reorder points and order-by dates that account for supplier lead times and MOQs
• Raw-material requirements from bills of materials, with shared components netted together
• Scenarios that show the purchase orders and cash a promotion or a retail launch commits
• A daily check of every SKU, so exceptions are found before they become stockouts

Work that belongs in the ERP

• Recording sales orders, invoices, receipts and inventory movements
• Placing and receiving purchase orders, and paying suppliers
• Costing, lot records and the financial close

Work that belongs to a person

• Overriding the forecast for a promotion, a lost listing or a new item, and recording why
• Negotiating MOQs, lead times and production windows with suppliers and co-manufacturers
• Deciding between service level and working capital when the two conflict
• Running the S&OP meeting, where sales, operations and finance agree one plan

If most of your pain sits in the third group, a planning tool will help less than a clear owner and a weekly S&OP routine. If it sits in the first group, the tool is the faster fix. If you are weighing an enterprise planning suite for it, price the whole project, not the license: the hidden costs of enterprise planning software covers what sits outside the quote.

Where does Planster fit?

Planster is demand and supply planning software for consumable CPG brands and manufacturers between $50M and $500M: food, beverage, supplements, beauty and household goods. It covers the first group above.

• Forecasting. Each SKU gets the statistical model that fits its history best: Prophet, ETS, SARIMA or linear regression. Channels are forecast separately and combined.
• Supply planning. Safety stock is set in days of cover and converted to units from the forecast, so it follows demand. Reorder points and order-by dates account for lead times and MOQs, and purchase orders are drafted for your team to approve.
• Raw materials. Bills of materials show which production runs are coming and what each one consumes, so shared components are planned once.
• Scenarios and retail deals. A promotion, a price change or a new retailer can be modelled before approval, showing the purchase orders and cash it commits.
• ERP. Planster reads NetSuite through Trackstar and Sage 100 Premium through a native connector, nightly and read-only, so the ERP stays the system of record.

Planster does not place orders or change a plan on its own. It drafts purchase orders and flags what needs a decision, and a person approves each one.

What to do first

1. List where the plan actually lives today: which spreadsheet, rebuilt how often, by whom.
2. Split your current problems into the three groups above.
3. Fix ownership first. Name who owns the forecast, who owns inventory targets and who owns purchasing.
4. Then pick tools for the first group, and keep the ERP as the system of record.