Quick Answer
Build a multi-SKU packaging system with a matrix linking each formula and capacity to its bottle, closure, decoration and artwork revision. Share components only when fit and performance are approved for each combination. Visual consistency does not justify using one dispenser or material for every formula.
A growing skincare range creates more combinations than its product count suggests. One serum may have a retail bottle, travel version and gift-set carton. A small change to a cap can affect several products. A component matrix makes those relationships visible before the purchasing team places an order.
Start with functional requirements by SKU
Give each finished product a unique reference and record its formula version, nominal fill and application route. Then identify the required container and closure. Keep formula compatibility and dispensing approval separate from the appearance brief; matching colours do not make two assemblies interchangeable.
For each row, record the actual component codes rather than descriptions such as white pump or small jar. Similar-looking components may differ in neck finish, gasket or outlet. Include the filling partner’s requirements and any approved assembly method.
Build the matrix at component level
| Field | Purpose |
|---|---|
| SKU and formula revision | Identifies what the packaging must contain |
| Container and closure references | Defines the approved assembly |
| Decoration and artwork revision | Prevents mixed versions |
| Carton or label reference | Links the correct information panel |
| Approval status and sample | Shows what can be purchased and filled |
Add a shared-component flag only where the same approved component is genuinely used. Do not copy the flag from a supplier catalogue without confirming the exact reference. A matrix should show both common parts and exceptions.
Set a visual rule without forcing identical structures
Define logo position, type hierarchy and the relationship between product names and capacity information. Apply the rules to the real printable areas of each pack. A tube, jar and bottle need different layouts even when they belong to one family.
Compare assembled samples together, including different capacities. Decide which differences are intentional, such as a larger product-name area on a jar, and which are errors. Retain a family reference set so future additions are assessed beside the current range.
Control artwork versions at purchasing
Use one release identifier for the approved artwork file and proof. The purchase order should refer to that identifier, not merely the latest file. Mark superseded versions and prevent old labels or cartons from being mixed into a revised SKU.
When a shared design element changes, review every affected row. A new logo size may fail on the smallest bottle even if it fits the main retail pack. The brand’s responsible reviewer should also check that required product information remains present and legible.
Approve substitutions through the same matrix
If a supplier proposes an alternative cap, liner or pump, list every SKU that uses the current reference. Review which fit, compatibility, dispensing and artwork checks need repeating. Do not approve the substitution for the whole range based on one convenient sample.
Include inventory consequences: remaining old components, minimum quantities for revised decoration and the transition date. Keep both old and new references visible until the change is complete.
Release a family reference set
- Matrix has unique references and current artwork revisions.
- Each formula-pack combination has its own approval status.
- Shared components and exceptions are explicitly marked.
- Family appearance is checked on physical samples.
- Substitution and obsolete-stock responsibilities are assigned.
Use the sample approval checklist for the individual release decisions.
A worked matrix example with explicit exceptions
Consider an illustrative range containing a lotion, a serum and a travel lotion. Give all three different SKU references even if they share a brand colour. The retail lotion and travel lotion may use related bottle shapes while requiring different closures or artwork panels. The serum may need a different dispensing assembly. Record the actual approved combination for each row instead of starting with the assumption that every product must share a pump.
| Illustrative SKU | Record separately | Sharing question |
|---|---|---|
| Retail lotion | Formula, bottle, pump and artwork revisions | Which exact parts are approved elsewhere? |
| Serum | Formula and dispensing approval | Does the shared appearance hide a different assembly? |
| Travel lotion | Smaller pack, closure and print area | Which checks need repeating at this capacity? |
This is a recordkeeping example, not a tested product specification or recommendation for a particular formula. Use the pump and formula matching guide to frame the dispensing questions, then retain the result for the actual formula-pack combination. A component can be visually shared while its performance approval remains specific to one use.
Add approval gates and named owners
A useful status field distinguishes proposed, sample review, approved, blocked and superseded references. Attach the evidence for each approval instead of filling the whole column with yes. Purchasing should be able to identify the current released row, while quality can see unresolved checks and the filling team can find the relevant assembly instructions.
Assign a record owner and a review route for changes. The owner maintains the matrix; that does not mean the owner personally approves formula compatibility or artwork content. Identify the responsible reviewer for each decision and retain the approval date. Where information is missing, mark the row incomplete and explain the dependency before an order is released.
Trace a shared-component change through the range
If a pump reference changes, filter the matrix for every row using the old reference. Review mating fit, formula performance, decoration and filling implications for those rows. An unaffected jar SKU need not acquire unrelated checks, but every affected pump SKU needs a documented decision. This targeted review is more reliable than approving the entire collection from the most convenient sample.
Link the replacement component to current stock, purchase orders and artwork revisions. Keep old and new codes distinct during the transition. At the next family review, compare physical samples together and update the reference set. The matrix then serves as a practical release record, not just a presentation showing that the collection looks consistent.
Frequently Asked Questions
Can one pump be shared across all lotions?
Only if each intended formula and assembly performs acceptably. A shared appearance is not sufficient.
Who should maintain the matrix?
Assign one controlled record owner and a review route connecting brand, purchasing, quality and filling teams.
Send the component brief and required checks through the packaging enquiry page.