The packaging audit guide.

01.What a packaging audit is — and what it is not

A packaging audit is a structured review of a packaging program against defined criteria, producing a written report with findings, severity ratings, and a prioritized action register. The scope can be a single SKU, a line family, or a full program. The dimensions covered can be any subset of the seven below, or all of them. The output is always the same: a document the brand can act on, share internally, and reference against future decisions.

What a packaging audit is not

• Not a QC inspection. QC confirms a production run matches a written spec. An audit asks whether the spec is the right one.
• Not a sales pitch. The report gets delivered whether or not the brand hires the auditor for execution.
• Not a design critique. The audit evaluates the pack against commercial, operational, regulatory, and system criteria — not against aesthetic preference.
• Not an open-ended conversation. The scope is defined in advance; the deliverable is defined in advance; the timeline is defined in advance.

02.The five triggers for an audit

Most packaging audits land in one of five situations. If any of these apply, the audit is almost always the right next step before committing to tooling, print, or production.

Trigger 1 — A new retailer PO is landing

First retail launches generate predictable chargebacks because the vendor-manual review, barcode grade testing, master-carton configuration, and EDI setup are easier to handle in parallel than reactively. An audit before the first PO ships catches these in time to prevent the deduction. See the Retail-Ready Beauty Packaging guide for the operational detail.

Trigger 2 — A compliance deadline is on the calendar

SB 54, EU PPWR, and MoCRA each have known compliance windows. The exposure is per-SKU and per-component — which means it is predictable only if you have mapped it. An audit does the mapping before an enforcement letter or retailer sustainability questionnaire forces it. See the Beauty Packaging Claims & Compliance guide for the framework overview.

Trigger 3 — Cost pressure is forcing a redesign discussion

When a CFO or ops lead starts asking why packaging cost is where it is, the common pattern is a reactive redesign that cuts the wrong things. An audit models landed cost per component (not just factory unit cost) and routinely surfaces 10–25% in savings through spec re-engineering, supplier reroute, freight-mode selection, or consolidation — without touching the brand look. See the Cost, MOQ & Landed-Cost Planning guide for the modeling framework.

Trigger 4 — A new SKU family or line extension is launching

Launches that extend an existing line often inherit only parts of the current design system — and formalize the drift. An audit catches the system drift and formalizes the design system before the new launch locks another one-off. See the Beauty Brand Packaging Design System guide for the system view.

Trigger 5 — A defect, reprint, or chargeback event

After a quality or compliance event, an audit does the root-cause analysis, writes the acceptance criteria that should have existed, and prevents the pattern from recurring. See the Packaging Testing & Quality Control guide for the written-spec and run-to-sample discipline the audit backfills into.

03.The seven audit dimensions

A full-scope audit covers seven dimensions. Most audits scope to the two or three driving the trigger. Each dimension produces its own findings list and severity rating, and each routes to a Logic Pac guide spoke for the deep operational detail.

A single-SKU audit (left) focuses on fit, function, and conformity for one pack; a program audit (right) reviews the full SKU family for cost, compliance, system coherence, and retail readiness.

04.Audit methodology — what we actually do, in order

The audit methodology is the same regardless of scope. The depth per dimension scales with the trigger. The order rarely changes.

Phase 1 — Scope & intake (Week 1)

• Scope conversation: which dimensions, which SKUs, which trigger, which deadline.
• Written scope document and audit plan — signed before any work begins.
• Access setup: supplier contact list, current spec documents, existing certifications, latest production samples, recent QC reports, invoice history for landed-cost modeling.

Phase 2 — Evidence gathering (Weeks 1–3)

• Physical sample pulls — current production run inspected against the written spec (or the retroactive spec reconstruction if no current spec exists).
• Supplier documentation review — CoAs, FSC chain-of-custody, PCR certifications, migration tests, Prop 65 letters, routing guides, vendor manuals.
• Measurement — critical dimensions, finishes, closure resistance, insert tolerances, barcode grade on the production substrate.
• Framework mapping — current pack against each regulatory framework in scope (SB 54, PPWR, FTC Green Guides, Prop 65, MoCRA, as applicable).
• Landed-cost modeling — unit cost, tooling, freight, duties, warehousing, defect reserve, over-order buffer.

Phase 3 — Findings synthesis (Weeks 3–4)

• Findings list per dimension with evidence citation (photos, documents, measurements).
• Severity rating per finding (critical / major / minor — same classification as the QC guide).
• Action register with ownership and effort estimate per action.
• Prioritization against the trigger’s deadline.

Phase 4 — Report delivery & walkthrough (Week 4+)

• Written report delivered as a PDF with embedded evidence.
• 60-minute walkthrough with the brand team to discuss findings, severity, and the action register.
• Quote for execution of the actions Logic Pac is positioned to run — separate from the audit, non-conditional.

05.The findings that recur across beauty audits

Different packs produce different findings, but the pattern of what recurs across audits is remarkably consistent. If you have not been audited recently, assume at least three of the below apply to your program.

• No current written specification exists. The brand knows what the pack looks like; the production floor has a verbal history of what to do; no one has a document that could be handed to a new supplier.
• Supplier documentation is scattered across email threads. CoAs, FSC letters, PCR verifications, migration tests. Each exists somewhere. None is in one versioned folder.
• Landed cost has never been modeled. Factory unit cost is known. Tooling amortization, freight-mode selection, warehousing, defect reserve, over-order carry — not modeled, often not even separately tracked.
• Compliance mapping is incomplete. SB 54 has been considered. PPWR might apply but is unmapped. Prop 65 was checked once at launch and has not been re-verified. MoCRA registration is current but no one is sure.
• Design system drift between SKUs. Hero SKU uses one carton weight, one finish stack, one insert. Line extensions each used a slightly different vendor and slightly different spec. The family no longer reads as one brand on shelf.
• Barcode grade has never been verified on production substrate. A proof was approved. No one scanned the actual production carton with a verifier.
• Insert tolerances have drifted. First-run molded trays held the pack firmly. Current-run trays are slightly loose because the mold was re-cut without updated specs.
• One supplier concentration is higher than the brand realized. A single-source component carries 100% of a critical SKU and no second source has been qualified.

06.Deliverables & report structure

Every audit produces the same artifact: a written report structured by the dimensions in scope. The depth per dimension scales with the trigger, but the structure holds.

Report structure

1. Executive summary. One page. The three to five most important findings and the recommended next steps.
2. Scope & methodology. What was audited, which dimensions, what evidence was gathered, what was explicitly out of scope.
3. Dimension findings. One section per dimension in scope. Each finding gets a plain-language summary, evidence citation (photo, document, or measurement), severity rating, and recommended action.
4. Prioritized action register. Every finding’s action rolled into one register, prioritized by severity and by the trigger’s deadline. Columns: finding ID, action, owner, effort estimate, by-when.
5. Logic Pac recommendation. The subset of actions Logic Pac is positioned to execute, with a scope-of-work pointer. Non-conditional on the brand hiring Logic Pac for implementation.
6. Appendices. Evidence photos, document references, measurement tables, framework-mapping worksheets, landed-cost model (if in scope).

Severity rating

Same three-class system as the QC guide:

• Critical. Will cause a chargeback, enforcement action, retail rejection, or production stop. Must be fixed before the next shipment or launch.
• Major. Material cost or risk exposure that should be fixed inside the current planning cycle.
• Minor. Improvement opportunity with limited immediate exposure — queue for the next planning cycle.

07.Timeline, scope & pricing framing

Timeline

Audit timeline scales with scope:

• Single-SKU audit, 1–2 dimensions: 2–3 weeks from brief to report.
• Single-SKU audit, full seven dimensions: 3–4 weeks.
• Multi-SKU program audit (3–10 SKUs): 4–6 weeks.
• Multi-SKU program audit (10+ SKUs or multi-market): 6–8 weeks.

Scope flexibility

Most audits scope to the two or three dimensions tied to the trigger. A compliance-driven audit might only touch Compliance & Claims and Sustainability Posture. A pre-retail audit scopes to Retail Readiness, Compliance, and QC. A cost-pressure audit scopes to Cost & Landed Economics, Structural & Material Integrity, and System Coherence. Full seven-dimension audits are common when the trigger is a new line launch, an investor diligence process, or a new ops lead taking ownership.

Pricing framing

Audits are quoted per scope — not per unit, not per hour. The quote reflects the number of dimensions, the number of SKUs, and the depth of evidence gathering required. Simple scopes are low four-figure engagements; full multi-SKU multi-dimension programs sit higher. The pricing framing matters because: (a) the audit is a defined deliverable with its own value, independent of execution; (b) the quote covers evidence gathering and report synthesis — not implementation; (c) implementation work surfaced in the audit is quoted separately, as a next-step scope the brand is free to accept or run elsewhere. Reach out to discuss scope and we will scope an audit against your trigger and timeline.

08.Should I request an audit? A 10-item scorecard

If three or more of the following apply, the audit is almost certainly the right next step. If five or more apply, request the audit now — the longer it waits, the smaller the actionable window becomes.