Phosphatidylserine buyers often clear the familiar technical questions first: source, assay, MOQ, packaging, COA, allergen position, GMO route, and destination-market document pack. Then a customer questionnaire or internal QA checklist raises a narrower but important question: has the phosphatidylserine route been irradiated, and if not, do we have a controlled non-irradiation statement strong enough for Europe and North America?

The short answer is that buyers should review irradiation status as a route-specific supplier document-control task, not as a casual side note on a quotation. A COA is not the same thing as an irradiation declaration, and a finished-label rule is not the same thing as an upstream B2B approval file. If your project may move across US and EU review paths, the irradiation question should be closed before the route is handed to a distributor, contract manufacturer, or customer technical team.

This matters because the EU and the United States regulate food irradiation differently. The European Commission's irradiation legislation page points buyers to Directive 1999/2/EC and Directive 1999/3/EC, explains that EU countries must use validated methods to detect irradiated foods, and lists the categories currently authorised for irradiation in the EU framework and Member State authorisations. Phosphatidylserine does not appear on that public overview list. In the United States, FDA regulates irradiation through specific food-additive authorisations in 21 CFR Part 179. Section 179.26 authorises ionising radiation only for defined food uses and categories, not as a blanket option for any ingredient. FDA also explains that retail labeling rules for irradiated foods are separate from the question of how ingredient buyers keep upstream supplier records. The practical implication is an inference from those primary sources: a buyer should not assume an irradiated or non-irradiated PS route is commercially fine just because a supplier gave a short email answer.

This article is written for ingredient importers, distributors, supplement manufacturers, procurement managers, QA teams, and regulatory reviewers serving Europe and North America. It focuses on supplier qualification, route-specific document review, and commercial readiness. It does not provide legal advice and it does not make medical treatment claims.

Where Nutranexa is mentioned, only verified site facts are used. The current site identifies the operating company as Shandong Baianrui Biopharmaceutical Co., Ltd., founded in 2013, operating a 110,000+ m2 campus, and primarily serving Europe and North America. It keeps Phosphatidylserine, Соя Phosphatidylserine, and Подсолнух Phosphatidylserine on separate buyer paths, with request routes through Качество и НИОКР, Производство, and Свяжитесь с отделом продаж for current controlled files. Final approval should still depend on the exact route, the current irradiation-status file, and the buyer's own market-specific review path.

The Short Answer Buyers Need First

If your team is reviewing phosphatidylserine for both US and EU projects, the simplest workable irradiation-status process is:

  1. Lock the exact route first: general PS, soy PS, or sunflower PS.
  2. Confirm whether the buyer needs an irradiation statement, a non-irradiation statement, or a route-acceptability review for a specific market.
  3. Review that file together with the specification, intended use, and downstream questionnaire or customer request.
  4. Keep supplier-file review separate from retail labeling, consumer wording, and generic marketing claims.
  5. Record a clear go, hold, or escalation decision before the route moves into customer handoff or first commercial order.

That is the operational distinction buyers often miss. A customer may ask, "Is this ingredient irradiated?" while QA is really trying to answer three different questions at once:

Buyer questionWhat the team is really trying to confirm
Do you have a non-irradiation statement?Is there a current controlled supplier file for this exact route?
Can this route be used for an EU project if a customer rejects irradiation?Does the team understand the market-specific review path before making a promise?
Is the COA enough?No, because batch data is not the same as a treatment-status declaration
Does US labeling settle the matter?No, because retail labeling is different from B2B supplier approval

Why Irradiation Status Review Is Its Own Buyer Task

EU irradiation rules are authorization- and labeling-specific

The EU side of the issue is stricter than many buyers expect. The Commission's irradiation pages describe a legal framework built around Directive 1999/2/EC and Directive 1999/3/EC. The public legislation overview says foods and food ingredients authorised for irradiation currently include a limited set of categories, and it separately links the list of Member State authorisations and approved facilities.

For phosphatidylserine buyers, that does not mean every supplier must automatically provide a dramatic irradiation dossier. It means something narrower and more practical: if the route is intended for Europe, the team should not improvise the irradiation answer from generic product knowledge. If the route is presented as non-irradiated, the file should say so clearly enough for procurement, QA, and customer-facing teams to use the same answer. If a route has been irradiated or may have been treated in a way that raises the question, the buyer should escalate immediately rather than assuming the ingredient fits EU expectations.

That is why irradiation review should sit beside, not inside, other compliance files. Allergen statement review, GMO statement review, and Packaging declaration review answer different buyer questions. Irradiation review asks: what controlled file explains the irradiation status of this exact PS route, and is that answer usable for the target market?

US irradiation rules are use-specific and not the same as a supplier questionnaire

The U.S. side is different, but buyers still need discipline. FDA's irradiation overview and 21 CFR 179.26 make clear that ionising radiation is authorised only for specified foods and uses. The regulation lists categories such as dry or dehydrated enzyme preparations, certain aromatic vegetable substances, meat, poultry, shell eggs, seeds for sprouting, shellfish, and a small number of other defined uses. It is not a blanket approval that can be assumed for any imported food ingredient.

FDA also explains a second distinction that matters in B2B trade: if a whole food has been irradiated, retail labeling must carry the Radura symbol and the phrase "treated with radiation" or "treated by irradiation." But if an irradiated ingredient is added to a food that has not itself been irradiated, FDA says no special retail labeling is required on that retail package. For ingredient buyers, the business implication is important. A customer questionnaire asking for an irradiation or non-irradiation statement is not the same thing as a final U.S. label review. The buyer still needs one controlled upstream answer for supplier approval even when the retail labeling analysis will happen later and elsewhere.

That is why U.S. buyers should avoid two weak assumptions: that no upstream supplier file is needed if no special retail label is required, and that a short supplier email automatically closes the market review. Both assumptions create avoidable risk because they collapse a route-specific supplier question into a much broader finished-product discussion.

The Six-Part Workflow for Reviewing a PS Irradiation Statement

Lock the exact phosphatidylserine route and commercial stage first

Before requesting any irradiation-status file, record the exact product route in writing. Is the team reviewing general phosphatidylserine during early comparison, or one source-specific route such as soy PS or sunflower PS? Is the file needed for importer qualification, contract-manufacturer onboarding, a distributor questionnaire, or a customer technical pack?

This matters because irradiation questions become vague when teams keep saying "PS powder" while the actual quoted route keeps moving. If the route was never fixed, the statement review becomes a filing exercise instead of a control exercise.

The opening note should usually record:

  • exact product route
  • destination market
  • commercial stage
  • documents already in hand
  • whether the buyer is asking about irradiated status, non-irradiated status, or market acceptability

Define whether the file must answer irradiated status, non-irradiated status, or market acceptability

The second step is to identify what the downstream party is really asking. These questions sound similar but they are not identical:

Question typeWhat the buyer needs to know
Irradiated statusWhether the quoted route has been treated with ionising radiation
Non-irradiated statusWhether the supplier is formally declaring the route has not been irradiated
Market acceptabilityWhether the route and its treatment status fit the intended US or EU project pathway
Customer questionnaire supportWhether the current file is controlled enough for downstream use

This separation matters because a buyer can have a commercially useful answer without yet having a market-usable answer. A short statement may be enough for shortlist qualification, but not enough for a Europe-facing customer questionnaire or a U.S. finished-product team that needs a cleaner regulatory handoff.

Review the statement together with the specification and intended market path

Once the file arrives, review it against the rest of the route documentation. The fastest check is usually:

  1. Confirm the statement belongs to the same route as the specification.
  2. Confirm the route is the same one being quoted commercially.
  3. Confirm the intended destination market is known.
  4. Confirm the downstream team understands whether the file is being used for internal approval, customer support, or retail-label review.

A useful buyer table looks like this:

CheckpointBuyer question
Route matchDoes the statement clearly belong to general PS, soy PS, or sunflower PS?
Statement scopeDoes it answer treatment status, non-treatment status, or only a broad commercial note?
Specification matchDoes the current specification describe the same route as the statement?
Market pathIs this file being used for US review, EU review, or both?
Downstream useIs the file strong enough for QA, customer questionnaire, or distributor handoff?

This step keeps irradiation review from drifting into guesswork and prevents a common failure pattern: answering the customer's irradiation question with whichever file was easiest to find, not the one that actually belongs to the quoted route.

Separate supplier irradiation files from retail labeling and marketing claims

This is where many approvals become messy. Supplier-file review is upstream document control. Retail-label review is downstream market execution. Marketing claims are a third question again.

For example:

  • A supplier non-irradiation statement may help QA approve a route for customer questionnaires.
  • A U.S. retail labeling team may still need its own analysis if irradiation status affected the downstream product.
  • A Europe-facing distributor may still need a separate escalation if the route status is unclear or if the project assumptions changed.

That is why buyers should not let one answer do three jobs. Keep the supplier statement in the technical file, and let the downstream labeling or regulatory owner decide what it means for the final packaged product or market claim.

Escalate immediately if the route, treatment status, or approval basis is unclear

Escalation is appropriate when:

  • the supplier statement is generic and does not clearly identify the route
  • the commercial route changed after the original file was collected
  • the buyer is being asked whether an irradiated route is acceptable in Europe without a proper market review
  • the customer wants a non-irradiation statement but the file in hand only speaks indirectly
  • the team is trying to answer a retail-label question with a supplier approval file

The escalation note does not need to be complicated. It should say which route is under review, what irradiation-status question remains open, which market is affected, and which controlled file is missing or unclear. That is safer than allowing sales, procurement, or customer service to turn a partial answer into a specific promise.

Close with a go, hold, or escalation decision

The final step is to record an outcome another team can actually use:

  • Go: the route, statement, and intended market path are aligned well enough for the current stage.
  • Hold: the commercial route may still be attractive, but the irradiation-status file is not controlled enough yet.
  • Escalate: the question goes beyond the current file and needs regulatory, quality, or customer-specific review.

That closeout note matters because irradiation questions often reappear late. The customer wants the tech pack. The contract manufacturer asks for one more declaration. The EU distributor wants a clearer answer than the original quote file contained. One short decision note prevents that loop from reopening.

Need a Current Irradiation or Non-Irradiation Support File?

If your team is still relying on one generic supplier email while comparing soy and sunflower phosphatidylserine routes for Europe or North America, stop before the answer becomes a customer-facing promise. Use Nutranexa's contact page to request the current route-specific statement path, specification path, and related source-support files for the exact phosphatidylserine route under review.

The fastest inquiries usually include the route, intended market, order stage, expected quantity, and whether the request is being raised by procurement, QA, a distributor, or a downstream customer.

Common Mistakes in Phosphatidylserine Irradiation Review

Most failures here are document-control failures, not scientific failures.

  1. Asking for a "PS irradiation statement" before the team has fixed whether it is approving general PS, soy PS, or sunflower PS.
  2. Treating a COA or generic product page as if it automatically answers irradiation status.
  3. Assuming a route is acceptable for Europe or the U.S. without checking the actual regulatory framework and intended use.
  4. Letting a downstream label or claim question dictate a supplier answer that the controlled file does not actually support.
  5. Reusing a shortlist-stage commercial answer as if it were a customer-ready technical declaration.

The practical fix is narrow: keep one question at the center of the review. What controlled file explains the irradiation status of this exact phosphatidylserine route for this exact market stage?

How Verified Nutranexa Facts Fit This Workflow

For buyers evaluating Nutranexa, several verified site facts support a cleaner irradiation-status workflow.

First, the site already separates Phosphatidylserine, Соя Phosphatidylserine, and Подсолнух Phosphatidylserine into distinct buyer paths. It also confirms useful baseline facts for qualification: the company was founded in 2013, operates a 110,000+ m2 campus, and primarily serves Europe and North America.

Second, Nutranexa's public site routes buyers through Качество и НИОКР, Производство, and Свяжитесь с отделом продаж rather than implying that one marketing page answers every controlled question. That is the right operating pattern for irradiation review too.

Third, the site provides verified commercial handling facts for PS, including 25 kg MOQ и 25 кг нетто на барабан packaging, together with visible specification and COA evidence plus factory, packaging, and dispatch imagery. Those facts help first-order planning, but they do not replace irradiation-status review.

Источники

Часто задаваемые вопросы

Do buyers need a phosphatidylserine irradiation or non-irradiation statement?

Often yes, especially when a customer questionnaire, distributor file, or QA approval process asks the team to confirm treatment status for a specific route. The key is to request a current controlled file tied to the quoted route.

Can a phosphatidylserine COA replace an irradiation declaration?

No. A COA may show batch-specific analytical information, but it is not the same as a controlled irradiation-status statement.

Is an irradiated phosphatidylserine route automatically acceptable in the US and EU?

No. The U.S. and the EU each regulate irradiation through specific legal frameworks and defined uses. Buyers should not assume cross-market acceptability without a route-specific review.

Why is this different from final labeling?

Because supplier-file review is an upstream B2B control task, while final labeling is a downstream market-execution task. The same project may need both reviews, but they do not answer the same question.

What should a buyer request from Nutranexa if irradiation status is still unclear?

Request the exact route-specific statement path, the current specification path, and any related source-support files for the phosphatidylserine route under review, then align them to the destination market and commercial stage before approval.

Conclusion

Phosphatidylserine irradiation review becomes manageable when buyers stop treating it as a vague compliance side note and start treating it as a route-specific document-control task.

The strongest US and EU workflow is practical: lock the route first, identify whether the file must answer irradiated status, non-irradiated status, or market acceptability, review the statement together with the specification and intended market path, separate supplier records from downstream labeling questions, and close with one explicit decision. That process helps ingredient buyers avoid a common failure pattern: the project is moving, the customer question has arrived, but nobody can show that the irradiation-status answer in the file belongs to the exact phosphatidylserine route being approved.

Рекомендуемые дальнейшие действия

Свяжитесь с отделом продаж для получения документации по продукту

Поделитесь предпочтениями источника, приложением, страной и годовым количеством.

Свяжитесь с отделом продаж