Private Label & OEM1 min read

Coating Product Tables: Keep Approved, Not Approved and Not Evaluated Distinct

A compatibility table should distinguish an approved use, an excluded use and a use that has not been evaluated. A blank cell should not silently imply either approval or failure.

Updated · NANOLAB Knowledge

The key distinction

Define the statuses and their evidence requirements. This helps sales and support teams communicate the actual scope without forcing incomplete information into a misleading yes-or-no answer.

Practical checks

  1. Use explicit status labels in the table.
  2. Link approvals and exclusions to their source documents.
  3. Route unevaluated uses for technical assessment.

Example

Illustrative example: a new substrate has no entry, and a salesperson assumes that absence means permission. An explicit not evaluated status would identify the need for review before a recommendation.

Scope and limits

Do not use the table to override product instructions or surface-manufacturer restrictions. Keep its revision and scope current, and avoid implying that every possible surface has been tested.

Related guidance

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

Private Label & OEM1 min read

Coating Support Templates: Keep Product-Specific Fields Explicit

A response template can improve consistency if its product-specific fields are completed and checked. It becomes risky when staff send generic timing or compatibility statements that belong to another coating.