How to Write a Candy Product Specification After Sample Approval

13 min read

Short Answer

After a candy sample is approved, do not send the factory a message saying only "make mass production exactly the same as this sample." Convert the approval into a controlled product specification that identifies the reference sample and records every attribute that must be reproducible, measurable or legally/commercially consistent in mass production.

A strong candy specification normally defines: product identity; approved sample code and sample type; production route; formulation and claim requirements; sensory profile; shape, dimensions and unit weight; texture; coating, filling or layer structure; relevant stability controls; net content; packaging material and seal requirements; carton configuration; artwork and coding versions; defect definitions; test methods; acceptance limits; retained-sample rules; change control; and the evidence required before shipment release.

The physical sample and the written specification perform different jobs. The sample is best for sensory and visual attributes such as flavor character, chew, appearance and coating feel. The specification is best for attributes that require controlled numbers, versions, documents and procedures. Neither should replace the other.

This approach is consistent with formal food-quality systems. IFS Food Version 8 requires finished-product specifications to be documented, current and unambiguous, and requires a controlled process for their creation, approval and amendment. Codex CXC 1-1969 likewise treats product description, relevant specifications and product characteristics such as water activity or pH, where applicable, as part of effective operational control.

Why "Same as Approved Sample" Is Not a Complete Specification

A physical sample is very good at communicating many things. The buyer can taste the flavor, feel the chew, observe color distribution, compare sour coating, and cut a filled product to see the internal structure.

But a single sample usually cannot answer:

The physical reference and the written specification must therefore be explicitly linked.

Freeze Sample Identity Before Writing the Specification

The most common specification-management error happens before the specification is written: a few weeks later, neither party can prove which sample was approved.

Give the reference sample a controlled identity. Record at minimum:

Identify the Sample Type

Do not assume every sample represents mass production equally.

Sample type What it may prove Main limitation
Stock sample Existing factory capability, baseline texture/flavor and general quality May not contain the final formula, color, coating, shape or packaging.
Benchmark sample The buyer's sensory/market target May have been produced by another factory or technology.
Laboratory/custom development sample Formula direction and sensory target May be hand-made or produced under conditions that do not represent line speed.
Pilot or line-trial sample Better evidence of process feasibility May still differ from normal commercial run size, conditioning or packing conditions.
Pre-production sample Near-final product before the full order Useful only if formula, line, packaging and process are the same as the planned production.
Mass-production sample Actual production output Strongest confirmation of the produced lot, but it arrives after commercial commitments have already increased.

Buyer takeaway: A "golden sample" is useful only if it has an identity, storage control and a written specification explaining what it controls.

Establish the Document Hierarchy Before a Conflict Happens

Private-label projects often contain multiple documents and message threads: buyer brief; quotation; approved sample comments; product specification; packaging specification; artwork files; purchase order; sales contract; inspection instruction; later amendments.

If these conflict, a possible operational hierarchy:

  1. signed amendment or latest formally approved change order;
  2. contract / purchase order;
  3. controlled product specification;
  4. controlled packaging specification and approved artwork;
  5. identified physical reference sample;
  6. earlier development briefs and chat messages.

This is an illustrative hierarchy, not universal legal advice. A chat message saying "make it slightly softer" should not quietly override a signed specification.

Build the Specification in Layers

A useful candy specification separates different types of requirements.

Layer 1 — Product identity: defines exactly what SKU is being manufactured.

Layer 2 — Sensory and physical target: defines what the candy should look, taste and feel like and which measurable characteristics support that target.

Layer 3 — Food-safety, formulation and claim information: defines composition-related requirements, allergens, excluded ingredients and evidence needed for claims.

Layer 4 — Packaging and coding: defines how the product is protected, filled, sealed, labeled and packed.

Layer 5 — Quality and acceptance: defines defects, tolerances, test methods, sampling, release evidence and corrective actions.

Layer 6 — Change control: defines which changes require written approval and whether a new sample or validation is required.

This layered structure makes the document usable by the factory's sales team, technologist, production manager, team, packing team and the buyer's inspector without forcing each person to interpret commercial chat history.

Section A: Product Identity and Intended Commercial Configuration

Start with the simplest questions that prevent the wrong product from being made. Include:

Avoid descriptions such as "premium gummy," "European style," "very sour" or "same quality as brand X" as the only production definition.

Section B: Formula, Ingredients, Allergens and Claims

The buyer does not always need the factory's confidential recipe percentages. But the specification should control the parts of formulation that materially affect the product, label, claims or commercial promise.

Depending on the project, record:

Codex CXC 80-2020 provides allergen management principles for food business operators. Even when the factory is not audited against a formal standard, the specification should record how allergen statements are substantiated and how raw-material changes affecting allergen status are controlled.

Section C: Sensory and Physical Target

The sensory section should describe the intended product character, supported wherever possible by measurable reference points. Separate what will be compared with the reference sample from what will be measured numerically.

Sensory attributes to define:

Physical targets to define:

Section D: Stability and Shelf Life

Record:

IFS Food Version 8 requires finished-product shelf-life claims to be validated. Even for buyers working with factories not subject to IFS certification, the principle applies: a shelf-life claim that is copied from a different SKU or packaging without supporting data creates commercial and regulatory risk.

Section E: Defect Definitions and Acceptance Criteria

Define before production what level of variation is acceptable and what constitutes a defect requiring action. Separate defects by category:

Class Meaning Candy examples
Critical Potential safety, legal or regulatory risk Foreign matter, allergen mislabeling, prohibited substance
Major Likely to cause customer rejection or non-compliance Wrong flavor/color, systematic leakage, out-of-range fill weight, missing lot code
Minor Noticeable but within commercially acceptable limits at the agreed threshold Minor color variation, surface marks within tolerance, minor weight variation

For each defect class, define: the defect description, how it is identified, the sampling/measurement method, the acceptance limit, and what action is required when the limit is exceeded (rework, segregation, re-inspection, rejection).

Section F: Test Methods and Measurement

For measurable attributes, define how they will be measured. Avoiding ambiguity in test methods prevents disputes about whether a result "passes."

Specify:

Section G: Packaging and Seal Requirements

Packaging must be controlled separately but linked to the product specification. Record:

AXTIMES operational experience: Changing from bulk packing to small individual units is not "the same candy with a different bag." It can change line time, weight control, breakage, material consumption, sealing behavior, carton configuration and price. The specification must reflect the final commercial pack.

Section H: Net Content, Count and Packing Configuration

Define the complete packing architecture: piece → retail pack → inner/display box → master carton → pallet.

Record:

Section I: Change Control

Define which changes require prior written approval and which can be implemented with notification only.

Changes that should require buyer reapproval:

Changes that may be managed with notification only (depending on the project):

Common Mistakes

  1. Approving a sample without a sample code or approval record.
  2. Treating "same as sample" as the entire quality clause.
  3. Writing subjective words with no shared physical reference.
  4. Copying tolerances from another SKU.
  5. Specifying only the candy and ignoring the packaging.
  6. Approving artwork before formula/allergen/claim information is stable.
  7. Assuming a laboratory sample proves full-line production.
  8. Failing to define which attributes require first-run approval.
  9. Using a shelf-life claim from a different SKU or package.
  10. Allowing changes through chat without revision control.
  11. Inspecting against criteria that were written only after production finished.
  12. Failing to define defect severity and corrective action.
  13. Keeping no retained sample from the accepted batch.

Implementation Workflow

  1. Identify the approved sample. Assign sample code, revision, date, photos and storage record.
  2. Map what the sample proves. Separate sensory/visual from unproven technical, packaging and regulatory attributes.
  3. Confirm the production route. Establish whether the same formula, process, line and packing route will be used.
  4. Draft the product specification. Convert critical attributes into controlled fields.
  5. Ask the factory for capability limits. Do not invent impossible tolerances.
  6. Create/attach the packaging specification. Confirm materials, dimensions, net content, seal and carton architecture.
  7. Reconcile ingredients, claims and artwork. Ensure all documents describe the same SKU.
  8. Define test methods and defects. State how conformity will be measured and what causes rejection.
  9. Agree change control. Define changes requiring notification, sample or reapproval.
  10. Approve the controlled revision. Buyer, export company and factory acknowledge the same version.
  11. Run first-production verification where needed. Confirm line-dependent attributes before uninterrupted production.
  12. Use the same specification for pre-shipment inspection. Do not create new quality rules after the lot is finished.
  13. Retain evidence. Keep the approved spec, sample record, production/batch sample and inspection results for repeat orders and claims.

Technical References