What Documents Support Market Entry?

Entering a new market involves much more than shipping a product across a border.

For an importer or distributor evaluating an oral-care brand, one of the first practical questions is:

"What documentation supports this product and its market entry"

The answer is rarely one certificate.

Different documents answer different questions.

Some relate to regulatory status. Some concern manufacturing and quality systems. Others address specific standards, product characteristics or requirements of a particular country.

Understanding those differences is important because a document should only be used to demonstrate what it actually verifies.

For Fulgent, this principle follows directly from the Claim & Evidence Framework: regulatory approvals, certificates, compliance documentation, manufacturing quality systems and verified quality-control records can all constitute evidence—but the strength and scope of any public statement must match the evidence behind it.

Market entry is a documentation system—not a badge collection

A common way of presenting an international brand is to place a row of logos or certification names on a website.

CPNP.

ISO.

Halal.

Vegan.

Health Canada.

And so on.

Visually, this may suggest credibility.

But professionally, it can create confusion if the visitor is not told what each document means, what it applies to, and in which market it is relevant.

A better approach is to organize documentation according to the question it answers:

Can this product be placed on the relevant market

What quality system supports its manufacture

Does it meet a particular certification standard

What technical documentation supports the product itself

Which documents can an importer or distributor review

That turns certifications from marketing decoration into useful business information.

1. Regulatory documentation: market-specific by nature

The first distinction is between regulatory documentation and general quality certification.

A product entering a market may be subject to notification, registration, authorization, labelling or other compliance requirements depending on its classification and jurisdiction.

These requirements are not globally interchangeable.

For example, CPNP belongs specifically to the European cosmetics regulatory framework. The European Commission describes the Cosmetic Products Notification Portal as the online notification system used in implementation of the EU Cosmetics Regulation. Once a cosmetic product has been notified through CPNP, no further national notification is required within the EU.

Health Canada operates under a different framework. For cosmetics sold in Canada, manufacturers and importers must submit a Cosmetic Notification Form to Health Canada within 10 days after the product is first sold in Canada; Health Canada also makes clear that submission of the form does not constitute product approval or support compliance.

That last distinction is especially important.

Terms such as registered, notified, authorized, certified and approved should not be treated as synonyms.

If a product has been notified, Fulgent should say it has been notified—not automatically call it "government approved."

2. ISO: ask which standard and what scope

"ISO certified" can sound reassuring.

But by itself it is incomplete information.

ISO publishes many different standards, and certification normally relates to a defined management system, facility, process or scope—not an undefined statement that "the product is ISO certified."

For cosmetics manufacturing, ISO 22716 is particularly relevant because it provides Good Manufacturing Practices guidelines covering production, control, storage and shipment of cosmetic products. ISO itself describes the standard as guidance for GMP in the cosmetics industry.

For a professional distributor page, the useful information is therefore not simply:

ISO Certified

but, where supported:

Which ISO standard Which legal entity or manufacturing site is certified What activities are within the certificate's scope Is the certificate current Who issued it

This level of precision fits Fulgent much better than displaying a certification logo without context.

The brand's own Evidence Framework categorizes quality-management systems, manufacturing procedures, internal audits, certificates and compliance documentation as corporate documentation, requiring Quality Assurance and corporate approval before being translated into public claims.

3. Halal certification: communicate the certification, not assumptions around it

Halal documentation belongs to a different category.

Where a Fulgent product or manufacturing process has a valid Halal certificate from the relevant certification body, that certificate can provide useful information for distributors and markets where Halal status matters.

But the communication should stay within the certificate's scope.

A Halal certificate should not be stretched into unrelated claims about clinical efficacy, overall product quality or regulatory approval.

The useful distributor questions are practical:

Which products are covered

Which manufacturing location is covered

Which certification body issued the certificate

What is its validity period

For which markets is that certification recognized or commercially relevant

This approach reflects Fulgent's evidence rule: evidence should support the specific type of claim being made, and lower-level evidence should never be presented as if it establishes something broader.

4. Vegan documentation: define exactly what is being verified

"Vegan" also needs precision.

Depending on the documentation available, the statement might concern ingredients, manufacturing criteria or certification against the requirements of a specific external organization.

These are not automatically equivalent.

Therefore, a professional Fulgent download page should ideally allow a distributor to identify:

the certification or declaration,

the products it covers,

the issuing organization where applicable,

the validity or version date,

and the precise scope of the statement.

The website should avoid turning "Vegan" into broader implications such as "safer," "healthier" or "more effective."

Those are separate claims requiring separate evidence.

5. Product technical documentation answers another question

Certificates do not replace product documentation.

A distributor evaluating a product may also require technical information concerning the formulation, specifications, packaging, ingredients, usage instructions, stability, safety or other product-specific characteristics.

Within Fulgent's Evidence Framework, product specifications, formulation documentation, laboratory testing, stability studies, approved packaging claims and internal technical documentation belong specifically to product-level evidence.

This distinction matters because a certificate about a manufacturing system does not prove every product-performance claim.

Likewise, an ingredient specification does not prove the performance of the finished toothpaste or mouthwash.

The documentation should answer the question it was created to answer.

Nothing more.

6. Quality documentation supports trust—but only when it is specific

Importers and distributors also need confidence that quality is managed systematically.

Relevant documentation can include quality-management records, manufacturing procedures, audit documentation, certificates, compliance documentation and verified quality-control records. These are all recognized evidence categories within Fulgent's internal framework.

This allows Fulgent to communicate something more meaningful than:

"High quality."

A stronger professional approach is to show how quality is documented.

For example, instead of a generic quality claim, a distributor may be given access to the relevant current certificate, technical specification or approved quality document.

That shifts trust from assertion to verification.

7. Not every document should necessarily be public

Transparency does not mean publishing every technical file on an unrestricted website.

Some documents are appropriate for public download.

Others may contain confidential formulation, manufacturing or commercially sensitive information and should be available only through a controlled distributor or regulatory request process.

A useful Fulgent documentation architecture could therefore distinguish between:

Public documents — certifications and declarations suitable for open verification.

Partner documents — market-entry and commercial documentation supplied to qualified distributors or importers.

Controlled technical documents — product or manufacturing documentation provided when legitimately required and subject to appropriate controls.

This approach is consistent with Fulgent's philosophy that consumers and partners do not need every technical document in front of them; they need confidence that important statements have been evaluated responsibly and can be supported when appropriate.

What a distributor should check

A certificate name alone is not enough.

Before relying on any document, a professional partner should be able to establish:

Who issued it

What exactly does it cover

Which company, facility or products are named

Which market or regulatory framework does it relate to

Is it currently valid

Does the document actually support the claim being made about it

These questions protect both sides.

The distributor receives clearer information.

Fulgent avoids turning legitimate documentation into misleading marketing claims.

Where Fulgent documentation fits

For Fulgent, the purpose of a documentation section should not be to create a wall of certification logos.

It should reduce uncertainty for professional partners.

A distributor considering market entry should be able to identify which documents are relevant to regulatory requirements, which describe manufacturing or quality systems, which support particular product characteristics and which can be supplied for further assessment.

This also means that documentation should be presented with basic metadata whenever possible:

Document nameDocument typeScopeApplicable products/entityIssuing authority or certification bodyIssue/version dateExpiry date, where applicableMarket relevanceDownload or request access

That would turn the Fulgent Downloads area into a practical due-diligence resource, rather than a promotional certification gallery.

Documentation does not replace local regulatory assessment

One final point is essential.

Having documentation from one market does not automatically establish eligibility for another.

CPNP notification is relevant to the EU cosmetics framework. Canadian cosmetic notification follows Canada's own requirements. Halal or Vegan certification addresses different criteria again. ISO documentation relates to the scope of the particular standard and certificate.

Therefore, distributors and importers remain responsible for determining the requirements applicable to the specific product classification and destination market, together with the appropriate regulatory specialists.

The responsible Fulgent position is not:

"We have certificates, therefore we can enter every market."

It is:

"We maintain documented evidence relevant to product, quality and market requirements, and provide the appropriate documentation for professional evaluation."

That difference is fundamental to credible international expansion.

Important note

This article provides general information about documentation relevant to market-entry assessment and does not constitute regulatory or legal advice. Requirements vary according to jurisdiction, product classification, formulation, claims and other factors. Importers and distributors should verify current requirements with qualified regulatory professionals and the competent authorities of the intended market.

Frequently Asked Questions

Does CPNP notification mean a cosmetic product is EU-approved No. CPNP is the EU's notification portal under the Cosmetics Regulation. Notification and regulatory approval are not interchangeable concepts. The correct terminology should reflect the actual regulatory status.

Does Health Canada "approve" every cosmetic that is notified No. Health Canada explicitly states that submission of a Cosmetic Notification Form does not constitute approval for sale and does not confirm compliance with all legislative requirements.

What does ISO certification tell a distributor That depends on the specific ISO standard, certificate holder and scope. For example, ISO 22716 concerns Good Manufacturing Practices guidelines for cosmetic production, control, storage and shipment. A generic "ISO certified" statement is therefore less informative than identifying the exact standard and scope.

Are Halal and Vegan certifications proof that a product is more effective No. They address specific certification criteria. Clinical or product-performance claims require their own appropriate evidence.

Can manufacturing certification prove a toothpaste or mouthwash performance claim No. Fulgent's Evidence Framework separates corporate/manufacturing documentation from product-performance evidence. Finished-product performance requires appropriate product-specific evidence.

Can distributors request additional Fulgent documentation The intended website architecture should allow relevant public documents to be downloaded and controlled or market-specific documentation to be requested where appropriate. The exact files available should only be listed after the current Terahealth/Fulgent document set has been verified.

Responsible Use Note

Market-entry content should be framed as document readiness, not an assurance of approval in any country.