Four Omega-3 Certificates: A Renewal and Scope-Drift Audit
Four Omega-3 Certificates: A Renewal and Scope-Drift Audit
For a multi-year omega-3 supply contract, the useful question is not only whether a certificate is valid today. It is whether the certificate still means what the buyer originally approved. A certificate can remain in force while its scope statement, product listing, issuing body or standard version changes in ways that affect a food, supplement or feed buyer. That is why renewal review should compare certificate versions, not simply collect the latest PDF.
Zhejiang Norbidar Biomedicine Co., Ltd. (Norbidar) manufactures food-grade omega-3 fish oil concentrates in Zhejiang, China. Its portfolio includes blended EPA/DHA ethyl ester concentrates, EPA-rich and DHA-rich concentrates, and customized EPA/DHA profiles discussed against the customer’s target specification. The company serves business customers in the nutrition ingredients sector. For the evaluation method in this article, four certificate identifiers are tracked across renewal cycles: HALAL 501525000, FSSC 22000 CN26/00004667, ISO 22000:2018 CN26/00004668 and FAMI-QS CN26/00005166.
The certificate numbers are used here as tracking identifiers supplied for this evaluation. Their current status, issuing body and exact scope must be read from the current certificate and the issuer’s record. An identifier alone does not establish coverage, and this article does not assert that any listed certificate has changed.
Why scope drift matters as much as the first certificate
Scope drift is any material change between certificate versions that alters what a buyer can rely on, even when the certificate remains valid. It can appear as a narrower site boundary, a removed process step, a changed product category, a different issuing body, a transition to a new standard version, or a change in certificate status. For procurement, the risk is not only a lapsed certificate. The risk is an approved assumption that quietly stops being true.
In omega-3 ingredient supply, the purchased material may be intended for dietary supplements, functional foods or feed applications. Those destinations do not rely on the same evidence in the same way. A food safety management-system certificate supports the review of a management system, but it does not replace the product specification, batch COA, SDS or destination-specific documents. Current specifications and batch COAs govern supply for Norbidar omega-3 fish oil concentrates. Certificate renewal and batch release are separate controls.
That separation is central to a multi-year contract. Initial approval often focuses on whether a document exists. Renewal review should ask whether the document still covers the same legal entity, site, process, product category and market use. A buyer who checks only the expiry date can miss a scope change that matters more than the date.
The four certificates are not interchangeable
The first discipline in a renewal file is to separate the certificate domains. In this evaluation set, FSSC 22000 CN26/00004667 and ISO 22000:2018 CN26/00004668 sit in food safety management-system scope. FAMI-QS CN26/00005166 sits in feed scope. HALAL 501525000 is a halal conformity document and should not be read as a food-safety management-system certificate. A feed-scope certificate does not automatically cover a food or supplement application, and a food safety management-system certificate does not by itself establish feed-market suitability or market authorization.
| Certificate identifier | Primary scope question | What renewal review must confirm | Common misread |
|---|---|---|---|
| HALAL 501525000 | Which products, processes and sites are within the halal conformity listing? | Issuing or recognized body, product listing, plant and process boundary, current status, and change from the previous version. | A halal document is not a food safety management-system certificate. |
| FSSC 22000 CN26/00004667 | Which food safety management-system scope, site and product categories are covered? | Scheme version, legal entity and site, product category, audit status, and the exact scope statement. | The certificate title is not the scope statement. |
| ISO 22000:2018 CN26/00004668 | Which ISO 22000:2018 management-system scope applies? | Standard version, certified entity and site, covered processes, status, and changes from the prior certificate. | An ISO 22000 certificate does not automatically establish FSSC 22000 coverage. |
| FAMI-QS CN26/00005166 | Which feed-chain products and activities are covered? | Feed scope, product or category listing, site and process boundary, status, and any change in scope. | Feed scope is not interchangeable with food or supplement scope, and it is not market authorization. |
Certificate numbers are used as identifiers for this evaluation. Confirm the current document, issuer record and exact scope with the supplier and certificate issuer.
Renewal question 1: Has the issuing body changed?
A changed issuing body is not automatically a defect, but it is a verification trigger. The buyer should compare the issuer shown on the previous certificate with the issuer shown on the renewal. If the issuer has changed, ask for the reason, the new issuer’s accreditation or recognition status, and the public certificate record. A PDF alone may not show whether the issuer is recognized for the relevant market or certificate scheme.
For HALAL 501525000, issuer recognition can be destination-sensitive. Buyers should confirm acceptance requirements with their own regulatory and quality teams rather than assuming that one halal document is accepted in every market. For FSSC 22000 CN26/00004667, ISO 22000:2018 CN26/00004668 and FAMI-QS CN26/00005166, ask for the issuer’s current public record and confirm that the certificate number, legal entity and scope match the document being reviewed. The point is not to create a new approval burden at every renewal. The point is to detect a change that alters the evidence base.
Renewal question 2: Has the scope statement narrowed, widened or shifted?
The scope statement is the operative part of the certificate. A buyer should read it line by line and compare it with the previous version. A scope may identify a legal entity, a manufacturing site, a set of processes, a product category or a chain activity. It may use wording that is broader or narrower than the buyer’s own description of the supply relationship. The certificate title or a summary slide is not a substitute for the scope statement.
For a food or supplement buyer, the relevant question is whether the food safety management-system scope still covers the site and activities that support the purchased omega-3 concentrate. For a feed buyer, the relevant question is whether the FAMI-QS feed scope covers the intended product and chain activity. Those questions are not answered by switching certificates. A FAMI-QS certificate should not be used to fill a food safety management-system gap, and a food safety management-system certificate should not be treated as feed-scope evidence.
Process boundaries deserve particular attention. Norbidar’s product development is supported by its proprietary NBD multi-stage continuous distillation process. A buyer should still confirm from the certificate scope which site and activities are covered, rather than inferring coverage from technical material alone. The same logic applies to blending, storage, packaging and any outsourced or traded activity described in the supply agreement.
Renewal question 3: Has the product listing or grade coverage changed?
Where a certificate scheme or certificate uses a product or category listing, renewal review should confirm that the listing still covers the material being purchased. Grade codes indicate nominal content, and current specifications and batch COAs govern supply. For example, 3624 EE has a nominal 36% EPA and 24% DHA content, while 5025 EE has a nominal 50% EPA and 25% DHA content. If a contract refers to one of these grades, the buyer should check whether the relevant product category or listing remains within the certificate scope. The buyer should not infer grade coverage from the certificate number alone.
Custom EPA/DHA profiles require a separate discipline. For custom ratio inquiries, feasibility and specifications must be confirmed with Norbidar before selecting a grade. A renewal review should not assume that a new custom ratio, a new packaging format or a new application is covered by an earlier certificate scope. The correct sequence is to confirm the specification, confirm the applicable certificate scope where required, and then confirm batch-level documents before release.
A product listing on a certificate is not a batch release. It does not prove that a specific lot meets the agreed EPA/DHA content, oxidation limits, contaminant limits or sensory requirements. Those points belong to the current specification, batch COA and SDS. The renewal file should connect the certificate scope to the commercial product, but it should not collapse certificate review and batch acceptance into one step.
Renewal question 4: Has the standard version, scheme version or status changed?
ISO 22000:2018 CN26/00004668 names a standard version in the identifier supplied for this evaluation. If a renewal document refers to a different version, the buyer should ask for the transition evidence and confirm which version is currently certified. For FSSC 22000 CN26/00004667, scheme requirements can change over time; the buyer should confirm the scheme version shown on the current certificate and the issuer’s record. For FAMI-QS CN26/00005166, confirm the current feed-scope certification status and any change in scope wording. For HALAL 501525000, confirm the current listing and issuing or recognized body.
Status is equally important. A certificate file can look complete while the live status is suspended, withdrawn, expired or pending renewal. Buyers should ask for current status confirmation from the issuer or a current public register, not only a scanned certificate. If a renewal audit is in progress, the buyer should confirm whether a valid certificate remains in force during the transition and whether the scope is unchanged while the audit is completed. These are verification questions, not assumptions about any current status.
A multi-year renewal register buyers can maintain
A practical control is a versioned certificate register. It should sit beside the supply agreement and quality agreement, not inside a general document folder. The register turns renewal review into a repeatable comparison. For each certificate, retain the current document, the previous version and the issuer record used for verification.
| Register field | Why it matters | Evidence to request |
|---|---|---|
| Certificate identifier and revision | Prevents a renewal from being treated as the same evidence without comparison. | Current certificate, previous certificate and revision date. |
| Issuing body and public record | Confirms who issued the certificate and whether the record can be verified. | Issuer name, public certificate record and any change explanation. |
| Standard, scheme and version | Shows whether the certificate is under the expected standard or scheme version. | Scope statement, standard or scheme version and transition evidence if changed. |
| Legal entity, site and process boundary | Connects the certificate to the actual manufacturing or supply activity. | Scope annex, site address, process description and entity name. |
| Product or category listing | Shows whether the purchased grade or category is within the stated scope. | Product listing or category wording; current specification and grade reference. |
| Valid-from, valid-to and status | Separates a valid certificate from an expired, suspended or pending one. | Current status confirmation and issuer record. |
| Change from previous version | Makes scope drift visible instead of leaving it buried in a new PDF. | Side-by-side scope comparison and supplier explanation. |
| Buyer impact and approval | Links the document review to the affected product, market and contract. | Quality or procurement sign-off, affected SKU or application, and action. |
The register should include all four identifiers: HALAL 501525000, FSSC 22000 CN26/00004667, ISO 22000:2018 CN26/00004668 and FAMI-QS CN26/00005166. It should also record which certificate is relevant to which buyer use. A single supplier file with four certificates is not the same as four verified scopes.
Decision rules: when to accept, clarify or escalate
A renewal is lower risk when the identifier, issuing body, scope statement, legal entity, site, product listing, standard version and status are unchanged, or when any change is documented and compatible with the buyer’s use. The buyer can accept the renewal after confirming the current documents and recording the comparison.
A change needs clarification when it appears administrative but could affect coverage. Examples include a new certificate layout, a reissued document with the same scope, or a change in issuer name that is explained by the issuer’s record. Clarification should produce a documented answer, not an informal assurance.
Escalation is appropriate when the scope narrows, a product or category is removed, the issuing body changes without a verifiable record, the standard or scheme version no longer matches the approved basis, the certificate status is unclear, or a food-scope certificate is being used to answer a feed-scope question. In those cases, the buyer should place the affected product, site or market use under review until the scope question is resolved. This is a procurement control, not a judgment about product quality.
Renewal rule of thumb: compare the scope statement before comparing the expiry date. A current certificate with a changed scope can require more review than an unchanged certificate approaching renewal.
What to ask Norbidar at each renewal
At each renewal, buyers can request a complete evidence pack rather than a single certificate image. The pack should include the current certificate and scope annex for each applicable identifier, the previous version, the issuer’s public record, confirmation of the legal entity and site, confirmation of the product or category listing, and a written explanation of any change. For the four-certificate set, that means HALAL 501525000, FSSC 22000 CN26/00004667, ISO 22000:2018 CN26/00004668 and FAMI-QS CN26/00005166.
The buyer should also confirm which certificate is being used for which purpose. A food safety management-system scope question should be answered with the relevant food safety management-system evidence. A feed-scope question should be answered with the feed-scope evidence. A halal conformity question should be answered with the halal document and its product or process listing. None of those answers should be stretched into a different domain.
Alongside the certificate file, request the current specification, batch COA and SDS, plus any destination-specific documents required for the project. For a contract grade such as 3624 EE or 5025 EE, confirm that the grade and intended application are within the commercial and certificate scope being reviewed. For a custom EPA/DHA ratio, confirm feasibility and specifications before selecting a grade. The certificate renewal should support the supply decision, not replace the batch release decision.
Norbidar publishes company and product information at norbidar.com. A buyer preparing a renewal file can also use the company’s Norbidar Omega-3 brochure as background, while keeping the current certificate and issuer record as the controlling evidence for scope.
Limitations: what a certificate renewal does not prove
A renewed certificate does not by itself prove batch conformity, product safety, efficacy, market authorization or destination compliance. It does not prove that a specific grade is covered unless the scope statement or product listing says so. It does not prove supply continuity, capacity availability or commercial terms. It also does not give the buyer an automatic right to use a certification mark; mark use depends on the certificate owner’s rules and any permission granted.
These limits are not reasons to ignore certificates. They are reasons to use them for the right purpose. A certificate is a scope and system signal. The specification, batch COA and SDS are product and lot signals. The contract and quality agreement are commercial and acceptance signals. A multi-year evaluation is stronger when each document is asked to do its own job.
Outlook: renewal review as an annual contract control
For multi-year omega-3 contracts, the practical shift is from collecting documents to maintaining a versioned scope record. The buyer who can show what changed, when it changed and which product or market use was affected is better prepared for a supplier review, a customer audit or a destination-market query. Scope stability over time matters as much as initial certification because the buyer is relying on continuity, not only on the first approval.
The four-certificate method can be adapted to the contract calendar. At each renewal, compare the issuer, scope, product listing, standard version and status. Record the result. If nothing changed, the review is short. If something changed, the buyer has a controlled path to clarify or escalate before the next purchase order. That is the difference between a certificate file and a long-term supplier evaluation.
FAQ
What is certificate scope drift in omega-3 supplier evaluation?
Certificate scope drift is a material change between certificate versions that affects what the buyer can rely on, even if the certificate remains valid. It can involve the issuing body, site boundary, process coverage, product listing, standard version or certificate status. Buyers detect it by comparing the current scope statement with the previous version and the issuer’s record.
How should buyers distinguish food safety management-system scope from feed scope?
In this four-certificate set, FSSC 22000 CN26/00004667 and ISO 22000:2018 CN26/00004668 address food safety management-system scope, while FAMI-QS CN26/00005166 addresses feed scope. A feed-scope certificate should not be used as a substitute for food or supplement scope, and a food safety management-system certificate does not by itself establish feed suitability or market authorization. The exact scope statement controls.
What should be checked when HALAL 501525000 is renewed?
Check the issuing or recognized body, the halal conformity scope, the product and process listing, the site boundary, the current status and any change from the previous version. Confirm destination-market acceptance with the buyer’s regulatory or quality team. Do not treat the halal document as a food safety management-system certificate.
Does an unchanged certificate number prove the scope is unchanged?
No. A certificate number is an identifier. The buyer should compare the current scope statement, legal entity, site and process boundary, product listing, issuing body, standard version and status against the previous version. A certificate number can remain while a scope or listing changes.
How should a multi-year contract handle a renewal gap?
Define the evidence required before release: current certificate, issuer record, scope annex, status confirmation and previous-version comparison. If coverage is narrowed or a required certificate lapses, place the affected product, site or market use under review pending documented resolution under the contract and quality agreement. A batch COA does not replace certificate scope.
Tem questões ou precisa de mais detalhes?
Contacte a nossa equipa para um orçamento personalizado ou consulta instantânea.
Solicitar orçamento
Preencha o formulário abaixo e a nossa equipa entrará em contacto com uma proposta personalizada.
Chat direto do WhatsApp
Prefere conversar em tempo real? Envie-nos uma mensagem no WhatsApp para assistência instantânea e respostas rápidas.
- Obter orçamento personalizado
- Partilhar fotos ou documentos
- Discuta as suas necessidades diretamente
Geralmente responde em 5–30 minutos durante o horário de expediente.
