How to Verify a Nutrition Manufacturer's Certificates and Credentials

Match the contracting entity, the manufacturing entity and the address

Start with the party that will actually carry the work. Write down three names: the company you will sign with, the company that will physically produce the product, and the production address. Check whether they are the same. If they are not, ask what each one does, how they are related, and make sure the relationship appears in the project documents.

A brand name on a website is not the legal entity on a certificate. A licence held by one company in the same group is not evidence about a different company, and it should not be used as such unless the relationship is explained. Map the promotional pages, the certificates and the project paperwork against each other field by field, rather than concluding that everything belongs to "the same brand".

Whether a production licence applies to your project depends on the rules where the product is made, on the category the product falls into and on the scope of the licence. A product that looks like a softgel is not one regulatory category everywhere, and a softgel licence should not be assumed to cover every softgel you might buy.

Six fields on every certificate

Keep a verification ledger. For each document, record:

• The certified entity — the legal name, and whether it is the party that will make your product.
• The covered site or address — whether the location where your batch will be produced appears in scope.
• What the document actually is — a management system certificate, a production licence, a facility registration or something else. Each answers a different question.
• The scope — the activities, product categories or processes covered, in the words of the document.
• The certificate number and the issuing body — enough to find the corresponding record or to ask for confirmation.
• Validity and current status — the dates, the date you checked, and any suspension, withdrawal or change information.

An expiry date printed on a document is not the only test, and a certificate that is still in date is not automatically in good standing. If a public register does not return a result, record it as "pending verification" and follow up with the issuing body. "Not found" is not the same conclusion as "invalid", and treating it as one either wastes a good supplier or buys a bad one.

What an ISO certificate does and does not tell you

In general terms, an ISO management system certificate is evidence about a management system, at a named site, written by a certification body against a standard that ISO publishes. The standard and the certificate are two different things: the body named on the certificate is the one that issued it, and the one you contact for status. The scope statement on the certificate is the part that tells you what it actually covers, and it is more informative than the logo or the design of the document. Check the issuing body's own current description of how it certifies and how its records can be confirmed.

In practice this means the following. A food safety management system certificate tells you that an organisation has been audited against a documented system for controlling food safety hazards at the site in scope. It does not tell you the active content of any batch, the result of a test on your product, the stability of a formula, or the outcome for any consumer. A management system certificate and a set of batch records answer different questions, and a purchase decision needs both — see how the two connect below.

Which regulatory regime applies alongside that system depends on how the product is classified in the destination market. Where a nutrition product is treated as a food rather than as a supplement, human food current good manufacturing practice requirements apply rather than a supplement-specific regime; check the current text in the eCFR for which set applies to your product category rather than assuming. ATXA's public quality page lists its own systems and certificates, and each certificate names the body that issued it, so you can verify with that body directly — see R&D and Quality.

Connect the system documents to this project's records

Within whatever confidentiality boundary works for both sides, agree in writing what the factory will provide for your project: incoming material inspection, in-process records, finished-product release and traceability. Different products and markets need different documents, so set the scope in the quality agreement or the delivery schedule rather than assuming a standard pack.

When you receive a test report, check the sample name, the specification, the batch number, how the sample was drawn or submitted, the test date, the method and the criteria against which results are judged. A report that says "pass" speaks to the sample on that report, the items listed on it and the criteria applied to it. It does not extend to every batch, every item or every risk.

Incoming material certificates, the manufacturer's own finished-product release records and a third-party laboratory report play different roles. They can corroborate one another, and they should not be substituted for one another without saying so explicitly. Where a regulation treats production records as a distinct category of evidence — as the US rules for dietary supplements do in 21 CFR Part 111, Subpart P — a management system document is not a stand-in for that record set.

Record the conclusion and who owns the update

Verification is not a folder of screenshots. Each line in the ledger should carry a status — verified, information still outstanding, or not applicable to this project — together with the evidence source, the date checked and the open question. Then the file still works when the project changes, a certificate is renewed or the production site moves.

Agree who updates the ledger and when. A change of raw material supplier, specification, production site or a significant process change should trigger a conversation about whether earlier conclusions still stand. How exception reports, recall support and traceability information will be provided are also worth settling before you need them.

The practical steps are on the R&D and Quality page. To discuss a specific project, use the OEM/ODM project enquiry form with the product and target market, and agree which documents apply. Once a factory is chosen, how to check batch records and release documentation covers the second half of the question, and the four checking lines for a multi-market formula covers whether one formula can travel.