Softgel Sample Approval: An OEM/ODM Checklist for Brand Teams

Identify what the sample represents

A softgel sample can serve several purposes: exploring capsule appearance, reviewing a formula concept, checking packaging fit, or evaluating a production trial. Before the team reviews it, label its purpose, sample identifier, preparation date, formula version, shell version, and package version. State any differences from the intended commercial product. A sample with a temporary color or a substitute bottle can still be useful when its limits are explicit.

Avoid an approval email that simply says the sample looks good. That message does not identify what was evaluated or which changes remain open. Use a decision form that connects the physical sample to the documents and observations used in its review.

Review the capsule and the complete package separately

For the capsule review, record relevant appearance observations such as shape, color, surface condition, and visible variation. Compare against the agreed specification or reference, using consistent lighting where color matters. For packaging, evaluate bottle dimensions, closure fit, label placement, readability, seal configuration, and the intended capsule count. Keep the capsule decision separate from artwork approval.

A larger capsule may look acceptable on a tray yet change how the planned bottle fills. A label that reads well on screen may become difficult to read after wrapping around the bottle. Review those interactions with a physical assembled sample when feasible, rather than approving every component in isolation and discovering the mismatch at packing.

Build a small, specific approval document set

Organize the review packet around decisions the brand actually needs to make. The following documents can support a clear approval trail; the appropriate level of detail depends on the sample stage. Technical records can be shared through agreed confidentiality arrangements without making the commercial approval ambiguous.

Give each file a revision, owner, and approval status. If a document is pending, identify the unresolved question and the person responsible for closing it. Keep the signed packet together so the purchasing team does not issue a production order against an outdated attachment.

• Sample identification sheet with the purpose and known differences from production.
• Formula, shell, and finished-product specification versions covered by the review.
• Appearance reference or photographs with an agreed comparison method.
• Packaging component list, assembly details, and approved artwork revision.
• Relevant sample results, open issues, and a signed decision with conditions.

Separate brand acceptance from commercial batch release

Brand approval of a development sample is not quality release of a commercial batch. Commercial batch release requires the relevant quality-control approval, as FDA's CGMP guide explains. A sample review should not be presented as replacing that process.

Define how the first commercial batch will be connected to the approved version and what information accompanies release. A brand may accept the proposed appearance while laboratory work or process evaluation remains open. Record that as a limited approval, with the outstanding work clearly identified. The purchasing and scheduling teams should understand whether a decision authorizes more development, packaging procurement, or a specific production step.

Control changes after the signatures are collected

List the events that require another review, such as changes to the shell, capsule dimensions, artwork, closure, or fill formula. A corrected typo and a new capsule size should not follow the same approval path. Agree on a practical change procedure that describes the information needed and the people responsible for evaluating each type of change.

Retain a reference sample when appropriate and record how it is stored and used. If the first production delivery differs from the approved sample, compare the actual identifiers and revisions before debating appearance. This document trail turns a vague disagreement into a specific question about what changed, whether it was authorized, and what action is needed.

Common questions