Product Development

From Product Idea to Physical Sample: A Practical OEM/ODM Guide

A structured way for brand and sourcing teams to define the starting model, requested changes, packaging inputs and physical-sample approval record before production planning.

Knowledge GuideUpdated October 23, 202611 minute read
Guide scope

This guide teaches buyers how to assemble an input brief. It does not promise feasibility, a fixed MOQ, a fixed lead time, tooling terms, exclusivity or a production result. Those points require project-specific review and written confirmation.

Why the input brief matters

A product idea becomes easier to quote when the supplier can separate what is already defined from what still needs to be tested. “Custom nipple covers” might mean a catalog model in a selected color and retail box, or it might mean a new profile, construction or development path. Those scopes should not be priced or approved as if they were equivalent.

OEM commonly begins with a buyer-defined specification; ODM often begins with a supplier-developed design. In practice, the useful question is not the label alone. It is whether the project starts from an existing model, which elements change, who supplies each input and what physical sample becomes the approval reference.

Build the brief in eight controlled steps

  1. Choose the product family and starting model

    Identify standard nipple covers, lift covers or adhesive bras, then name the catalog model. Include the exact product name and listed size format. A model reference provides a shared starting point; a broad keyword does not.

  2. Separate standard construction from requested changes

    Create two lists: confirmed catalog facts and requested changes. Put color, shape, closure, surface, logo, instructions and packaging on separate lines. Do not describe an idea as standard until feasibility is confirmed.

  3. Prepare usable color and design references

    Record the selected catalog color reference and attach any separate target reference. Explain whether the target is for the product, protective component, packaging or printed material. A screen color alone is not a physical approval standard.

  4. List packaging and instruction requirements

    Describe the pack structure, product count, protective components, artwork files, instructions, barcode or label requirements and destination-language needs. Mark any proposed logo placement for eligibility review rather than assuming it is available.

  5. State commercial context without inventing commitments

    Provide estimated quantity, unit of measure, destination market, target channel and desired schedule. Treat these as planning inputs. MOQ, sampling cost, tooling, production timing and shipping terms remain quotation-specific until confirmed.

  6. Define what the physical sample must confirm

    List the model, dimensions or listed size, color reference, profile, closure where applicable, pack components and artwork revision. Agree how observations will be recorded. Avoid unsupported universal wear, reuse or performance criteria.

  7. Record approval, revision or hold

    Keep the sample identifier, specification revision, photographs, observed differences and decision together. If a substitution changes the approved product or packaging, request a revised reference and written agreement.

  8. Build the final RFQ package

    Combine the product brief, quantity basis, packaging scope, artwork status, sample requirements and open questions. Ask each supplier to identify inclusions, exclusions and unresolved feasibility items so quotations can be compared on equivalent scope.

Minimum information for the first supplier review

  • Product family, catalog model and current reference name.
  • Selected size or size format and catalog color reference.
  • Requested product changes, each labeled for feasibility confirmation.
  • Logo, artwork and instruction assets currently available.
  • Packaging structure, pack count and protective component requirements.
  • Estimated quantity with an explicit unit of measure.
  • Destination market and retail or distribution context.
  • Sample checkpoints, decision owner and approval-record format.
  • Questions about cost, timing, tooling and responsibilities.

Make sample approval traceable

The approved sample should be connected to a written specification, not remembered as “the good one.” Assign a sample identifier and revision. Record which product and pack components were reviewed, which criteria were observed and which items remain open. If only color or packaging is approved, say so; do not imply approval of untested product behavior.

Supporting documents also need scope. A material report may concern a specified material grade without certifying the finished adhesive product or shipment. Match each document to the actual model, material or test subject it covers, and place unresolved gaps on hold rather than filling them with assumptions.

Common shortcuts that create sourcing risk

  • Using “custom” without stating what changes from the catalog model.
  • Combining product, packaging and tooling costs without a scope breakdown.
  • Approving a rendering when a physical product sample is still required.
  • Assuming all logo placements, printing methods or embellishments are available.
  • Assuming a fixed MOQ, lead time, wear time or reuse count from a category page.
  • Comparing quotations that use different quantities, pack counts or approval duties.

Reference basis and limits

The workflow consolidates TD’s current OEM/ODM development scope, public product tables, Quality sample-comparison guidance and wholesale RFQ checklist. It is procurement education, not a confirmed quotation or a promise of capability for every requested change.