How consumer packaged goods manufacturers run formulas, batches, pack-out, yields, lots, and co-packers in NetSuite.
Consumer packaged goods (CPG) manufacturers turn ingredients and packaging into retail-ready product at high volume and thin margin: snacks, baked goods, beverages, sauces, supplements, and personal care. The cost of every case is decided on the production floor, by the formula, the yield of each batch, the packaging consumed on the line, the time lost to changeovers, and the product that ends up as waste or giveaway. Every ingredient and every finished lot also has to be traceable in both directions, often against a best-by date. This guide covers the production side of a CPG business in NetSuite, stage by stage: what NetSuite handles natively, the setup decisions that matter most, and where Consule’s products fill the gaps. For the selling side (retail EDI, trade spend, and deductions), see NetSuite for CPG wholesale distributors.
Most manufacturing software assumes a parts list: so many components per finished unit, the same every time. CPG production does not work that way, for six reasons.
Most CPG manufacturers run a process stage and a packaging stage, and many also use co-packers for some products. Each stage needs its own bill of materials, its own constraints, and its own data captured on the floor.
| Stage | What it produces | What the bill of materials holds | Main constraint | What to capture |
|---|---|---|---|---|
| Batch (process) | A bulk intermediate: dough, sauce, beverage base, lotion, blend | Ingredients by weight, scaled to the batch size | Kettle, mixer, or oven capacity; allergen sequence | Ingredient lots and actual quantities, batch yield |
| Pack-out | Finished SKUs: retail units, cases, and pallets | The bulk intermediate plus film, bottles, cartons, labels, and cases | Line speed and changeovers | Finished lot and best-by date, packaging usage, rejects and overfill |
| Co-packing | Finished SKUs made by a partner | Your ingredients and packaging plus a conversion charge | The partner’s schedule and minimum runs | Material sent, output received, the co-packer’s yield |
Modeling the bulk intermediate as its own item, with its own formula and lot, is the single most useful structural decision in a CPG implementation. It lets one batch feed several packaging runs, keeps traceability intact from ingredient to case, and shows where yield was lost: in the kettle or on the packaging line.
A CPG product moves through seven stages from formula to finished, costed, traceable inventory. The records change at each stage, but the lot and the cost have to stay connected the whole way.
In NetSuite, the bulk intermediate and each finished SKU are assembly items with bills of materials, and the Advanced Bill of Materials feature keeps revisions with effective dates, so a reformulation does not overwrite the recipe that made last month’s lots. Record allergens and other attributes on ingredient items so they carry into formulas and scheduling. Cost the formula at every level: the batch, the retail unit, the case, and the pallet, including packaging, so pricing decisions are made on the unit the customer actually buys. Where a product has several approved recipe versions or batch sizes, ProShop’s FlexBOM manages the versions and scales ingredients to the batch.
NetSuite Demand Planning builds demand plans from sales history and a supply plan that turns demand into suggested work orders and purchase orders (our NetSuite demand planning guide covers the setup). CPG planning then has to translate those suggestions into real batches: quantities rounded to kettle or mixer sizes, runs sequenced so allergen-free and light products go before allergen-containing and dark ones, and changeover and sanitation time reserved on each line. FactorySync puts that schedule on a visual board inside NetSuite, with line capacity and conflicts shown before the week starts.
Ingredients and packaging are received by lot, with expiration or best-by dates captured at the dock and the supplier’s lot number recorded against your own. Material that needs testing or a certificate of analysis should not be available to production until it passes. NetSuite’s Quality Management SuiteApp manages inspections at receipt and during production through a quality inspection queue, and inventory statuses keep quarantined material out of picks until it is released. Landed cost (freight, duties, and brokerage) belongs on the receipt so ingredient cost is complete.
Production of the bulk intermediate runs on work orders issued against the formula. Record the actual ingredient lots and quantities consumed, not just the standard, because that record is what lot traceability and yield analysis depend on. With the Manufacturing Work in Process and Manufacturing Routing features, labor and machine time are captured by operation. CPG batches raise needs native NetSuite does not cover well on its own: one batch feeding several work orders, actual yield that differs from standard, and co-products or by-products from the same run. ProShop’s BatchWizard manages a batch across multiple work orders, YieldCraft records actual yield and adjusts cost and inventory, and CoYield creates inventory for every output with cost allocated by value, weight, or a set split.
Packaging work orders consume the bulk intermediate by lot along with film, containers, labels, and cases, and create finished lots for each SKU. Define every unit level (each, inner pack, case, and pallet) with its own conversions and GTIN, because customers order, receive, and scan at different levels. Capture packaging usage and line rejects, and watch overfill: product given away above the declared net weight is a direct cost that never shows up on a standard. For random-weight products, ProShop’s CatchIQ records actual weight alongside the unit count. Where lot-controlled components are consumed automatically at completion, decide carefully whether to backflush or issue manually, since backflushing without lot selection breaks traceability.
Each finished lot gets a best-by date calculated from its production date and the product’s shelf life, and can be held by inventory status until quality release. From there, NetSuite’s lot and serial number trace follows any lot backward to the ingredient lots and suppliers that made it and forward to every customer who received it. For foods on the FDA Food Traceability List, the FSMA 204 rule requires traceability lot codes and key data elements for each critical tracking event, with records available to the FDA within 24 hours of a request, and the compliance date is July 20, 2028. A lot structure set up properly now makes that a report rather than a project. Run a mock recall before go-live to prove it.
Standard costing is common in CPG because it separates purchase price variance, ingredient usage variance, and yield variance from product margin, so a jump in ingredient cost or a bad batch shows up as a variance rather than silently changing margin. Review variances by formula and line every month, revalue standards on a set calendar (quarterly for most manufacturers), and allocate overhead by line or work center so high-changeover products carry the time they consume. Co-packer conversion charges belong in product cost too, not in a general expense account.
Many CPG manufacturers make their core products in-house and use co-packers for overflow, new items, or formats their own lines cannot run. NetSuite’s outsourced manufacturing feature ties a purchase order for the conversion service to an outsourced work order. The ingredients and packaging you supply move to a location that represents the co-packer, they are consumed when finished goods come back, and the co-packer’s charge becomes part of the finished cost.
Three habits keep co-packing under control. Treat each co-packer as an inventory location, not only as a vendor, so material sitting at their plant stays on your books and reconciles. Record the co-packer’s lots and dates on the finished goods you receive, so traceability does not stop at their door. And compare their actual yield against the formula, because material usage at a partner’s plant is one of the least watched costs in CPG.
Model the batch output as its own lot-controlled item with its own formula, then build each finished SKU from it. This is what makes one batch feed many SKUs, keeps traceability intact, and separates process yield from packaging yield.
Define each, inner pack, case, and pallet with conversions and GTINs before anything else, and use matrix items for flavor and size families so reporting rolls up by product line. Labels, EDI, and warehouse scanning all depend on it, and it is the hardest thing to change after go-live.
Decide which items are lot-controlled (all ingredients and finished goods, and often packaging), how best-by dates are calculated, and which inventory statuses hold material until quality release.
Set a standard yield for each formula and agree what counts as normal loss, rework, or waste. Then capture actual yield on every batch. A yield that is never measured becomes a cost variance nobody can explain.
Use standard costing with a revaluation calendar, include packaging and labor in every standard, and decide how overhead is allocated to lines. The goal is a variance report that tells you whether a margin change came from purchasing, the formula, or the floor.
Ingredient weights, batch yields, and line output are only as good as the way they are recorded. Tablets or scanners at the kettle and the packaging line beat paper batch sheets keyed in at the end of the shift, and machine data can flow into NetSuite directly: see how Consule and Factbird are bringing live machine data onto the NetSuite work order.
NetSuite covers the core of CPG production well: assemblies and bills of materials with revisions, lot and expiration control, work orders with routings, quality inspections, outsourced manufacturing, demand and supply planning, lot trace, and standard costing. Where CPG manufacturers most often run past native capability is inside the batch: recipes with several versions and batch sizes, one batch spread across several work orders, yields that differ from standard, several outputs from one run, product sold by weight, and repacks that have to keep lot trace. Those gaps usually end up in spreadsheets beside the system.
ProShop fills them inside NetSuite. BatchWizard manages batch production across multiple work orders, FlexBOM handles recipe versions and scales ingredients to the batch, YieldCraft records actual yields and adjusts cost, CoYield creates inventory for co-products and by-products with cost allocation, CatchIQ handles items sold by weight, and Repack Orders turns bulk into retail, club, or private-label packs with every output linked to its source lot. It runs natively, with the same login and no separate system to maintain. See how BatchWizard handles batch manufacturing and the hidden costs of formula manufacturing on spreadsheets.
If any of these comes from a spreadsheet today, it points to the part of the process that is not yet running in the system.
CPG implementations go better in phases, each of which is useful on its own.
For new NetSuite customers, Consule runs this sequence as a NetSuite implementation (our NetSuite implementation guide covers the phases, timelines, and cost drivers). For manufacturers already on NetSuite whose batches, yields, or lots have drifted into spreadsheets, a NetSuite optimization engagement starts with an assessment of where production leaves the system (see our NetSuite optimization guide), and the Consule CARE program covers ongoing support after go-live.
Production is only half of a CPG business. Retailers send orders by EDI, set labeling and ship-window rules, and pay net of promotions and deductions, so the item and lot structure built for production has to serve the order desk too. When Consule implemented NetSuite for Stellar Snacks, a snack food manufacturer and distributor, the project covered manufacturing and production workflows alongside SPS Commerce for retail EDI and Vividly for trade promotion management, all connected to NetSuite. The selling side is covered in detail on our CPG wholesale distribution page.
CPG production requirements run through several of the industries we work with: bakery and snack manufacturing, brewing, distilling, and beverage manufacturing, cosmetics and personal care, pharmaceutical and nutraceutical manufacturing, meat, seafood, and protein processing, and food and beverage. Each of those pages covers the industry-specific requirements on top of the CPG foundation described here. For how NetSuite’s manufacturing features fit together across every type of production, see our complete guide to NetSuite manufacturing.
Yes, for most mid-market CPG manufacturers. NetSuite covers assemblies and bills of materials with revisions, lot and expiration control, work orders with routings, quality inspections, outsourced manufacturing, demand planning, lot trace, and standard costing in one system with financials. Consule’s ProShop adds formula and batch production, actual yields, and co-products inside NetSuite.
Natively, NetSuite runs formulas as assemblies with bills of materials and work orders. For batch-specific needs, such as one batch across several work orders, recipe versions scaled to batch size, actual yield, and co-products, ProShop’s BatchWizard, FlexBOM, YieldCraft, and CoYield extend it without a separate system.
Lot numbers and expiration dates are recorded when ingredients are received, consumed on work orders, created on finished goods, and captured on every shipment. NetSuite’s lot and serial number trace follows a lot backward to its ingredients and suppliers and forward to every customer who received it, which is also the foundation for FSMA 204 traceability records.
Yes. The outsourced manufacturing feature links a purchase order for the conversion service to an outsourced work order, so the ingredients and packaging you supply are tracked at the co-packer, consumed when finished goods are received, and the co-packer’s charge is included in product cost.
Most use standard costing that includes ingredients, packaging, labor, and overhead, with actual consumption and yield recorded on every batch. The resulting purchase price, usage, and yield variances show whether a margin change came from purchasing, the formula, or the floor. Standards should be revalued on a set calendar.
Running CPG production on paper batch sheets, an older ERP, or a NetSuite account that stops at the work order? Get in touch to walk through your formulas, batches, and yields, or see how ProShop runs formula production inside NetSuite.
