Best Practices June 8, 2026 10 Min Read

How to price a packaging design project without underquoting

Packaging design gets underquoted for a predictable reason: the client thinks they are buying "a label" or "a box design," while you are actually being asked to price a small system with production constraints, approval risk, and often some amount of compliance pressure.

That gap matters.

A packaging job can look tiny in the first email. One carton. One pouch. One can label. Then the real shape appears. There are six SKUs, not one. The barcode needs usable space. Legal copy is still moving. The claims panel gets reviewed by marketing, then operations, then a printer, then a retailer, then maybe regulatory. Suddenly the project is not a front panel comp anymore. It is version control, layout discipline, production prep, review management, and risk.

Public sources back the shape of that work, even if they do not give you a neat freelance rate card. The U.S. Bureau of Labor Statistics notes that graphic designers work on commercial design applications including packaging, displays, and logos, and reported a median annual wage of $61,300 in May 2024 for graphic designers in the U.S. (BLS). That is not a quoting guide. It is a reminder that packaging design is skilled commercial work, not decoration around a printer file.

And the constraints are real. FDA guidance for foods and cosmetics lays out required label information and principal-display-panel rules. GS1 US gives barcode placement guidance and warns against placing codes near the edge without enough surrounding white space. TTB requires mandatory information on many malt beverage labels and reviews it through label approval where applicable. The FTC's Made in USA guidance adds another layer when origin claims show up on pack (FDA food labeling guide, FDA cosmetics labeling guide, GS1 US, TTB, FTC).

So the goal is not to find the magic price for "packaging design." There isn't one. The goal is to price the actual workload, the decision risk, and the production burden the brief is quietly carrying.

If the brief is still a mess, start with turning a messy brief into a clean quote and turning a creative brief into a scope of work and quote. This article starts one step later, when you already know the project is packaging work and need to price it without lying to yourself.

Packaging projects get underquoted when the job is defined too loosely

Most bad packaging quotes are not bad because the designer forgot to multiply their hours correctly. They are bad because the scope was described in client language instead of production language.

"We need packaging for a new skincare line."

"We need a label refresh for our canned drink."

"We need three pouch designs for launch."

Those are starting points, not usable scopes.

Packaging is especially sensitive to hidden complexity because the visible hero surface is only one part of the job. FDA's food labeling guide requires certain statements and placement rules on many food labels, including net quantity declarations on the principal display panel and required information elsewhere on pack (FDA food labeling guide). FDA's cosmetics guide does the same for cosmetic labels, including identity, net quantity, business information, and ingredient declaration requirements in the appropriate places (FDA cosmetics labeling guide). TTB says certain mandatory information must appear on malt beverage labels, and some labels require a COLA review (TTB). None of that automatically means your client needs formal regulatory consulting from you. It does mean packaging projects often carry layout and review consequences that poster design or social graphics do not.

That is why a packaging quote needs firmer boundaries than the brief usually gives you.

Start by pricing the package system, not the mockup

The fastest way to underquote packaging is to price the hero mockup and ignore the system around it.

That system usually has five moving parts.

1. Surface design versus structural design

Surface design means you are applying graphics, hierarchy, copy, and brand language to an existing format or dieline. Structural design means the pack format itself is being created or changed. New carton geometry, insert logic, shelf behavior, unboxing sequence, closure decisions, pack engineering coordination. That is a different project shape.

Even when you are "only" doing surface design, ask whether the dieline is final, who owns it, and whether you are expected to adapt it. A client-supplied approved dieline is very different from "the printer will send something later" or "can you clean this old file up a bit." The second version quietly drags you toward production problem-solving.

Practical guidance: quote structural work, or any meaningful structural coordination, as a separate phase unless it is truly minor.

2. SKU count and variant logic

A single SKU and a six-SKU family are not the same job. Everybody says they understand this. Plenty of quotes still ignore it.

The important question is not only how many SKUs there are. It is how much of the design logic repeats cleanly and how much of it needs real adaptation.

Three examples:

  • One front-panel concept rolled across six tea flavors with consistent hierarchy and light color swaps: moderate expansion.
  • Six supplement SKUs with different claims, ingredients, warning blocks, and panel density: larger expansion.
  • Three beverage labels now, then seasonal variants, retailer packs, and multi-can trays later: system design problem, not one label problem.

Do not let "it is basically the same design" do too much work in the conversation. "Basically" is where hours go to die.

3. Regulatory and claims complexity

FDA says cosmetic labels need required identity, net quantity, business information, and ingredient declarations in the proper places, with readability and prominence rules to consider (FDA cosmetics labeling guide). FDA's food labeling guide covers mandatory information and panel rules for many packaged foods (FDA food labeling guide). TTB reviews mandatory label information for many malt beverages and points producers toward label approval requirements (TTB checklist). The FTC says marketers making unqualified Made in USA claims need to comply with the Made in USA Labeling Rule, and it does not pre-approve those claims for you (FTC Made in USA standard).

That does not mean you should act like a lawyer or a regulator when you are not one. It means you should price for the review load and layout constraints that come with regulated or claim-heavy categories.

Practical guidance:

  • If the pack includes regulated panels or mandatory statements, assume more rounds and tighter copy handling.
  • If the client has not finalized claims or legal copy, treat that as a quoting risk, not a harmless detail.
  • If compliance review sits outside your role, say so clearly in the scope. You can still price the design work needed to accommodate reviewed copy.

4. Production readiness and printer coordination

Packaging work often becomes expensive after the design "looks done."

GS1 US advises avoiding the edge of the package and keeping enough white space around a barcode to support clean scanning (GS1 US). That sounds minor until you are squeezing marketing copy, ingredients, legal text, and claims onto a small label or narrow carton side. Printer constraints, color mode, bleed, panel folds, trapping expectations, and export requirements all sit in the same neighborhood.

This is why print-ready packaging artwork should not be priced as if it were only concept design plus a quick export.

Ask whether the quote includes:

  • final production artwork
  • prepress cleanup
  • printer liaison
  • one printer only or multiple vendors
  • one final file set or several localized / retailer / format versions

If you skip that distinction, the job will happily grow itself later.

5. Review load and decision risk

Packaging work tends to attract more opinion than people expect. Brand wants shelf impact. Sales wants more claims. Legal wants caution. Operations wants the barcode moved. A founder wants the pack to feel premium. Retail may want specific content hierarchy. Somebody always wants one more callout bubble.

That is not a personality problem. It is the nature of a surface carrying commercial, regulatory, and production meaning at the same time.

So review load needs to be estimated as real work:

  • concept presentation prep
  • revision rounds
  • version comparison
  • copy updates
  • final QA
  • last-mile approval churn

If the pack is going to a committee, price the committee.

A practical formula for packaging design pricing

Here is a clean starting formula:

packaging quote = discovery + concept work + production artwork + revision load + risk buffer + pass-through costs + profit

If you want the more mechanical internal version:

(hours by phase x internal rate) + external costs + risk adjustment

The key is to build by phase, not by vague asset label.

Discovery
Brief review, SKU audit, reference pull, copy audit, dieline review, production questions, kickoff, and assumptions.

Concept work
Hierarchy, visual routes, front-panel thinking, system logic, mockups, route presentation.

Production artwork
Applying the approved route across all panels, variants, claims blocks, barcode placement, legal text, exports, and print-ready files.

Revision load
Real time for client review, copy changes, layout adjustments, and final QA. This is not optional fluff. It is part of the job.

Risk buffer
A protection against visible uncertainty already in the brief: moving copy, unfixed claims, unclear SKU counts, missing dielines, new approvals, printer ambiguity.

Pass-through costs
Mockup assets, specialist illustration, structural partner costs, translator costs, proofing, or other third-party expenses if they are part of your arrangement.

One important caveat: public sources can help you explain why packaging projects widen in scope. They do not give you a trustworthy universal price card. So use public sources for workload logic, not for fake certainty about market-wide rates.

If you need help building the hours underneath the quote, how to estimate project hours before you send a quote is the right companion piece.

Should you charge per SKU, per phase, or fixed fee?

There is no single right answer. The right model depends on how stable the scope is.

Situation Usually safest model Why
One clear package, final dieline, stable copy Fixed project fee The scope is bounded enough to price cleanly
Several related SKUs with repeatable layout logic Base fee + per-SKU expansion fee Protects the system work and the variant work separately
Structural exploration or unclear launch requirements Paid discovery phase first Avoids fake precision while the pack format is still moving
Heavy production rollout across channels, retailers, or languages Phase pricing Lets you separate concept, artwork rollout, and production support
Long product pipeline with recurring pack updates Retainer or rolling capacity model Better for steady release cycles than re-quoting every tiny change

My bias:

  • Charge fixed fee for a clearly bounded single package.
  • Charge base-plus-SKU when the first pack carries the real thinking and later packs still carry meaningful rollout labor.
  • Charge in phases when structural, regulatory, or rollout uncertainty is still high.

Do not collapse six variants into one "package design" line item unless you enjoy surprise unpaid work.

Worked examples across different packaging jobs

These are practical estimate structures, not market guarantees.

Example 1: a single-SKU skincare carton and bottle

The brief: one facial oil launching direct-to-consumer. Existing bottle format. Existing carton dieline from printer. The client needs label and carton graphics, one visual direction, ingredient panel layout, and final print-ready files.

Phase Practical scope
Discovery brief review, competitor shelf scan, copy audit, dieline check, kickoff
Concept 1-2 front-panel directions, hierarchy proposal, mockups
Development selected route refined across bottle and carton
Production artwork all required panels, barcode placement, print-ready exports
Revisions two consolidated rounds before final artwork
Assumptions client provides final approved ingredient list and claims copy

What pushes price up:

  • claims copy still moving
  • several founders commenting separately
  • metallic or special-finish mockup expectations
  • retailer-specific secondary assets getting added later

Example 2: a six-variant craft beverage label series

The brief: a brewery wants a label family for six seasonal cans. The brand system exists, but naming, color differentiation, and some compliance copy will vary. TTB label review may apply depending on the product setup.

Phase Practical scope
Discovery existing brand review, flavor list, mandatory info review, format check
Concept one family system plus flavor differentiation logic
Development refine the chosen route and finalize the series rules
Variant rollout apply the system across all six labels
Production support final artwork package, export checks, revision to approved copy changes only
Assumptions client owns regulatory sign-off and provides final mandatory copy

What changes the quote shape here is not just quantity. It is variant control. One label shifts, five more often follow. If you want a nearby article that helps frame those add-ons and change lines, read how to prevent scope creep in creative projects.

Example 3: a three-SKU food pouch launch

The brief: a small food brand needs three stand-up pouches for launch, each with different nutrition panels, ingredients, and net contents. The visual system is new. Retail is possible later, but not confirmed.

Phase Practical scope
Discovery copy audit, SKU matrix, packaging references, dieline review
Concept one system direction with front-panel hierarchy and shelf logic
Development selected route refined, panel logic built out
Artwork rollout three separate production files with category-specific copy blocks
QA and exports barcode space checks, panel checks, final export package
Assumptions retailer adaptations, displays, and future size extensions are excluded

This is where many people underquote by treating three food pouches as one design plus two easy duplicates. If nutrition, ingredient, or claim blocks differ materially, they are not duplicates. They are controlled variants.

What to lock before you send the quote

If these points are soft, your price is probably soft too.

Item to lock Why it matters
Package formats and dimensions Different surfaces mean different layout burden
Final vs draft dielines Unapproved structure creates extra production risk
Number of SKUs and how they differ Quantity alone is not enough; variation complexity matters
Copy status Unapproved claims and ingredients create churn
Regulatory responsibility Design support is not the same as legal or regulatory sign-off
Barcode source and placement Small technical constraints can force major layout changes
Revision rounds Packaging review can sprawl fast
Output list Print-ready files, mockups, source files, retailer variants, localization
Printer or vendor coordination One printer handoff is not the same as ongoing production support
Exclusions Future variants, displays, shippers, secondary packs, new claims, retailer adaptations

One rule worth keeping: if the quote depends on client-provided copy, dimensions, claims, or regulatory review, write those as assumptions with consequences if they change.

Mistakes that quietly destroy margin on packaging work

  • Pricing only the visible design moment: Ignoring the downstream artwork and prepress details where true packaging projects often consume the most labor.
  • Treating every SKU like a simple duplicate: If nutrition panels, legal claims, ingredients, or localized copies differ between versions, you are designing individual variants, not cloning files.
  • Sloppy technical support boundaries: Squeezing printer support, proof adjustments, line modifications, and endless press-check loops into standard graphic pricing.
  • Underestimating regulatory or claims-heavy categories: FDA, FTC, GS1, and TTB naming or placement guides exist because minor label mistakes carry serious commercial liabilities.
  • Vague "reasonable revisions" statements: A recipe for unlimited design changes. Define consolidated revision loops explicitly.
  • Mixing basic concept design with complex rollout systems: Unnecessarily locking a fixed project fee before SKU extensions or structural variants are fully finalized.
  • Trading rights and licensing for nothing: Assuming standard freelance files include full product licensing, source files, and commercial distribution rights from day one.

FAQ

Should I price packaging design per SKU?

Sometimes. If the first SKU carries the strategic and system-building work, and later SKUs still require real adaptation, a base fee plus per-SKU expansion fee is usually cleaner than one flat number.

Is print-ready artwork a separate line item?

Often, yes. Concept design and print-ready production artwork are different phases. If you bundle them, at least separate them in your internal estimate so you can see where the workload really sits.

What if the client has not finalized claims or legal copy?

Treat that as scope risk. Either quote a discovery / cleanup phase first or write a clear assumption that the price depends on final approved copy being delivered before production artwork starts.

Do I need to price compliance review itself?

Only if you are actually providing that service. Many designers should not overclaim here. What you should price is the design and revision work that regulated or claim-heavy packaging tends to generate.

Should I include printer coordination?

Only if it is in scope. And if it is in scope, name it. A one-time printer handoff is different from iterative production support across several vendors or proof rounds.

When should I refuse a fixed fee?

When the structure is still moving, the SKU count is fuzzy, the copy is not approved, or the production route is too uncertain to estimate honestly. That is usually a discovery-phase problem, not a pricing-confidence problem.

If you already have the brief and the hard part is turning it into scope, phases, roles, estimate logic, assumptions, and a quote you can defend before packaging work starts, Roadbase is built for that stage. You still review the draft and make the judgment calls. After approval, the project can continue in a simple board with notes and per-user time tracking instead of getting rebuilt from scratch.

Sources

Ready to stop guessing on design proposals?

Roadbase parses client requirements and auto-predicts project breakdowns, role rates, contingency margins, and precise fee quotes in two clicks.