A new packaging development process is a controlled sequence that takes a pack from a business need to an approved commercial solution. The 9-gate framework moves through product brief, technical requirements, concept screening, material and structure selection, prototype, design validation, supplier qualification, pilot or line trial, and specification and launch release. Each gate needs a decision owner, documented evidence and a clear go, hold or stop outcome.
Many packaging projects lose time because teams move from an attractive idea straight to quotation or tooling. A more reliable route tests the right questions earlier: Does the pack protect the product? Can it run on the intended line? Can qualified suppliers make it consistently? Will it survive the real distribution environment? Is the final specification complete enough for purchasing, quality and operations to work from the same version?
Table of contents
- What is a new packaging development process?
- Why use a stage-gate framework?
- The 9-gate framework at a glance
- How to run each gate?
- Who should approve each gate?
- What documents are needed?
- Common process failures and how to avoid them?
- How Acumen Packaging can support development?
- Frequently asked questions
What is a new packaging development process?
New packaging development is the planned work of converting product, market, operational and user requirements into a pack that can be produced, filled, distributed, used and controlled at launch. It includes design, but it goes beyond design. It also covers packaging specifications, supplier capability, validation, line readiness, documentation, implementation and post-launch monitoring.
The process applies to a completely new product, a redesigned pack, a material change, a new closure, a pack-size extension, an e-commerce shipper or an effort to simplify a portfolio. The depth of work should match the risk. A label refresh may require limited checks, while a new pharma bottle, food-contact structure, high-barrier pouch or automated filling format needs more formal controls.
Why use a stage-gate framework?
A stage-gate process separates the work into manageable phases. Between phases, a decision gate asks whether the project has enough evidence to continue, needs more work or should change direction. The approach prevents teams from treating every project as urgent production activity and makes responsibilities visible before cost, risk and rework increase.
Packaging research supports this approach. A 2023 study in Packaging Technology and Science describes packaging development as the transformation of a packaging concept and assumptions about manufacturing, packaging technology and user needs into a package available for use. It notes that formal development processes commonly use discrete stages and milestones with go or stop decisions.
The benefit is not bureaucracy. It is better decision quality. At every gate, the team should know what question is being answered, who owns the decision, what documents prove readiness and what happens if an assumption is not yet verified.
The 9-gate framework at a glance
| Gate | Name | Decision question | Minimum output |
| 1 | Product brief | Is there a defined business and product need? | Approved project charter and initial risk view |
| 2 | Technical requirements | What must the pack do? | Requirements matrix and acceptance criteria |
| 3 | Concept screening | Which concepts deserve development resources? | Selected concept with rationale and risk register |
| 4 | Material and structure selection | Which pack system can meet the brief? | Feasible material, structure and sourcing route |
| 5 | Prototype | Does the proposed solution work in physical form? | Prototype review and iteration record |
| 6 | Design validation | Does the design meet intended-use requirements? | Test plan, evidence and corrective-action closure |
| 7 | Supplier qualification | Can an approved supplier deliver the pack consistently? | Supplier assessment, samples and agreed controls |
| 8 | Pilot or line trial | Can the full pack run in a realistic production setting? | Trial report and production-readiness actions |
| 9 | Specification and launch release | Can the business produce, buy, inspect and control the pack? | Released specification, approved artwork and launch checklist |
Gate 1: Product brief
The packaging development brief The project starts when the business need is clear enough to define scope. Describe the product, category, target user, channel, markets, anticipated volumes, target timeline, brand role, cost expectations and major constraints. For an existing product, capture the problem in measurable language. “The pack feels premium” is not a requirement. “The customer must dispense a repeatable dose with one hand” is closer to one.
Accountable gate owner: Project sponsor or business owner
Minimum gate evidence: Approved project charter, stakeholders, initial budget range, timeline, risk list and go or hold decision.
Gate 2: Technical requirements
Technical packaging requirements Translate the brief into packaging requirements. This includes product compatibility, fill volume, dimensions, barrier or shelf-life needs, closure function, product-contact considerations, visual requirements, transport risk, storage conditions, e-commerce needs, machinery constraints, regulatory review needs, sustainability objectives and target cost. Separate mandatory requirements from preferences.
Accountable gate owner: Packaging lead with R&D or quality input
Minimum gate evidence: Requirements matrix with measurable targets, test approach, assumed conditions and approval criteria.
Gate 3: Concept screening
Generate and compare practical concepts before committing to a single route. A concept can combine pack format, material, structural features, graphics, closure, secondary pack and distribution approach. Screen concepts against the requirements matrix rather than personal preference alone. Include feasibility, risk, supplier availability, consumer use, operations, cost and sustainability trade-offs.
Accountable gate owner: Cross-functional steering group
Minimum gate evidence: Shortlist, concept scorecard, updated risk register, budget estimate and a documented selection decision.
Gate 4: Material and structure selection
Select the material and structural route that can meet the required function. Packaging is a system, not an isolated component. A primary pack can perform well in a lab and still fail when its shipper, pallet pattern, handling method or storage environment changes. Assess material properties, pack geometry, closure, decoration method, secondary packaging and intended logistics together.
Accountable gate owner: Packaging technical lead
Minimum gate evidence: Material and structure rationale, preliminary drawings, sourcing strategy, sample plan and controlled change assumptions.
Gate 5: Prototype
Build and review prototypes that answer the current uncertainty. Early prototypes may validate size, appearance, ergonomics, fit, assembly or basic user interaction. Production-intent samples are needed later for properties that depend on the actual material, process, mould, tooling or converter controls. Record what each sample proves and what it does not prove.
Accountable gate owner: Packaging lead and project manager
Minimum gate evidence: Prototype review record, feedback log, revised drawings and a decision to iterate or move to validation.
Gate 6: Design validation
Packaging design validation Validate the design against the agreed requirements. Verification asks whether the design outputs meet the defined inputs. Validation asks whether the pack is fit for its intended use. The test plan should state the sample condition, number of samples, test method, acceptance criteria, responsible party and action path for nonconformities. Applicable work can include dimensional checks, compatibility assessment, seal or closure checks, transport simulation, compression, vibration, drop, print review, user assessment and line-related checks.
Accountable gate owner: Quality, R&D and packaging decision owners
Minimum gate evidence: Approved validation report, deviations, corrective actions, retest results and formal release to supplier qualification.
Gate 7: Supplier qualification
Confirm that the selected supplier can deliver the specified pack under controlled conditions. This is more than collecting a commercial quote. Review technical capability, relevant process controls, documentation, capacity, sample consistency, material traceability where needed, change-notification practices and logistics capability. The qualification route should reflect project risk and the brand’s quality system.
Accountable gate owner: Procurement with quality and packaging input
Minimum gate evidence: Supplier assessment, approved samples, commercial agreement path, control plan and alternate-source strategy where needed.
Gate 8: Pilot or line trial
A pilot or line trial checks how the pack performs in a realistic process. It can expose issues that a bench review cannot: filling variability, cap application, sealing, label placement, coding, torque, conveyor handling, pack-out, case packing or changeover time. Define trial objectives before the run and include the people who will own the process after launch.
Accountable gate owner: Operations owner with packaging and quality
Minimum gate evidence: Trial protocol, production data, defect log, corrective actions, approved settings and readiness decision.
Gate 9: Specification and launch release
Release only when the pack can be consistently ordered, received, inspected, filled, shipped and changed under control. The final package should include current specifications, drawings, approved artwork, bill of materials, quality limits, inspection criteria, test evidence, supplier details, change-control rules and launch responsibilities. Hold a final cross-functional review to confirm that known risks have owners and dates.
Accountable gate owner: Project sponsor or designated release authority
Minimum gate evidence: Signed release package, training or handover plan, launch checklist, change-control route and post-launch review date.
Who should approve each gate?
A stage-gate framework works when accountability is explicit. The names and approval thresholds vary by company, but the responsibilities below are a practical starting point.
| Gate | Accountable approver | Essential contributors |
| Product brief | Business sponsor | Marketing, product, packaging, finance |
| Technical requirements | Packaging lead | R&D, quality, operations, regulatory or compliance as applicable |
| Concept screening | Cross-functional steering group | Procurement, logistics, brand, operations |
| Material and structure selection | Packaging technical lead | R&D, quality, procurement and operations |
| Prototype | Project manager | Packaging, brand and user-research representatives as relevant |
| Design validation | Quality or technical release owner | Packaging, R&D, operations and relevant external test partners |
| Supplier qualification | Procurement and quality | Packaging technical lead and operations |
| Pilot or line trial | Operations owner | Quality, packaging, maintenance and supplier technical support |
| Specification and launch release | Business sponsor or release authority | All functional workstream owners |
What documents should the process produce?
The document set should be appropriate for the risk and complexity of the project. The objective is traceability: a reviewer should be able to see what the project needed to achieve, what solution was chosen, what evidence was reviewed and how changes will be controlled.
- Project charter and stakeholder map
- Requirements matrix and risk register
- Concept scorecard and selection record
- Drawings, component specifications and approved artwork
- Prototype review and sample-tracking log
- Validation plan, test records and deviation closure
- Supplier assessment, sample approval and control plan
- Pilot or line-trial protocol and report
- Released master specification, inspection criteria and change-control procedure
- Post-launch review and corrective-action record
How Acumen Packaging supports new packaging development?
Acumen Packaging is an ISO 9001:2015 certified packaging consultancy that supports brands from packaging strategy through practical project execution. The company works with FMCG, pharma, food, beauty and e-commerce brands across paper, plastics, glass and metals. Its role is advisory and execution-focused. Acumen does not manufacture, supply or distribute packaging materials.
For a complete view of available modules, explore Acumen’s packaging consultancy services. Teams considering an early design or feasibility review can also use Acumen’s packaging project and onsite support when they need experienced packaging capacity alongside internal teams.
Gate 6 and Gate 8 benefit from planned evidence. Read Acumen’s guide to packaging testing methods for related testing context. When the project also needs commercial optimisation, see packaging value engineering services. Examples of packaging project work can be reviewed in Acumen’s packaging case studies.
What are the most common development-process failures?
| Failure | What it causes | Better practice |
| Starting without a measurable brief | Teams debate solutions before agreeing the real product, consumer, logistics and commercial requirements. | Create a signed requirements matrix before concept selection. |
| Treating a prototype as final proof | An early model may show look and feel but cannot prove production material, tool, barrier, fill or transit performance. | State what each sample validates and plan production-intent testing. |
| Leaving operations out until late | The chosen design may not fill, seal, label, pack or change over reliably on the intended line. | Include operations and maintenance at Gate 2 and Gate 3, then require a defined trial at Gate 8. |
| Choosing a supplier only on unit price | A lower quote may hide capability, quality-control, capacity, traceability or change-control risk. | Use a cross-functional supplier qualification route. |
| Allowing unrecorded changes | A material, artwork or process change can invalidate earlier evidence. | Use formal change control with impact review and revalidation as needed. |
| Releasing incomplete specifications | Purchasing, quality and suppliers may work from different assumptions or versions. | Release one controlled master specification and inspection criteria before launch. |
How should the framework change by industry?
FMCG and food
FMCG and food teams often need to balance speed, shelf appeal, cost, product protection, retail handling and high-volume production. The technical requirements should address the full system, including primary pack, secondary pack, distribution pack, filling conditions and route to market. Food-related requirements need product-specific regulatory, safety and supplier-document review.
Pharma and regulated products
Pharma and regulated projects may require deeper controls for product contact, material documentation, traceability, change management, qualification and validation. The gates remain useful, but acceptance evidence and formal approval responsibilities usually increase. Final decisions should be reviewed against applicable regulations, product safety requirements, supplier certifications and validated technical documentation.
D2C and e-commerce
D2C projects need to look beyond the primary pack. The pack must work in warehouse handling, parcel distribution and customer unboxing. Gate 2 should therefore define transit risks, packing method, returns considerations, dimensional efficiency and the role of secondary protection. Gate 8 should simulate the intended fulfilment process as closely as practical.
FAQ
The new packaging development process is a structured way to turn product and business requirements into a commercially ready package. It normally includes a brief, technical requirements, concept selection, material and structural design, prototypes, validation, supplier qualification, line trials, controlled specifications and launch review.
This guide uses 9 stages: product brief, technical requirements, concept screening, material and structure selection, prototype, design validation, supplier qualification, pilot or line trial, and specification and launch release. A team can adapt the detail, but each stage should have evidence, ownership and a go, hold or stop decision.
A stage-gate process divides packaging development into work stages separated by decision points. At each gate, a defined owner reviews whether requirements, evidence, risks, costs and resources are sufficient to proceed. The result is normally a go, hold, redirect or stop decision, recorded with the supporting documentation.
Verification checks whether design outputs meet defined design inputs, such as whether a drawing, dimension or specification meets the approved requirement. Validation confirms whether the finished packaging solution can meet its intended use, such as protecting the product, functioning for consumers and performing through the intended process and supply chain.
