Private Label & OEM2 min read

Coating Development Sample Names: Avoid Reusing Informal Labels

Informal names such as new sample or latest version become ambiguous as a project grows. Use unique sample references that remain stable across application notes, photographs and supplier discussions.

Updated · NANOLAB Knowledge

The key distinction

The reference should identify the sample without revealing confidential formulation details unnecessarily. Keep the supplier's code and the buyer's internal code mapped where both are used. A clear naming system prevents observations from different versions being merged into a product history that no single sample actually represents.

Practical checks

  1. Assign a unique reference at receipt and preserve the supplier identifier.
  2. Put that reference on the evaluation record and associated media.
  3. Reconcile references before comparing results or approving the next development step.

Example

Illustrative example: two bottles are both described as sample B in separate email threads, but they contain different revisions. An installer prefers one while purchasing approves the other. Unique references and a verified mapping would prevent the misunderstanding before it reaches a production decision.

Scope and limits

Do not reconstruct identity from smell, colour or expected behaviour. If a reference is missing, resolve it with the supplier before testing. This guide does not authorize relabelling that removes required product information; it concerns additional project traceability within the approved handling process.

Related guidance

Discuss bulk supply and private-label requirements with NANOLAB. Use the current product documentation for formulation-specific instructions.