Phosphatidylserine TSE/BSE Statement Review for European Buyers

European phosphatidylserine buyers often clear the obvious commercial questions first: source, assay, MOQ, packaging, specification, COA path, and novel-food fit. Then a downstream quality or customer questionnaire raises a narrower but very real issue: do we have a usable TSE/BSE statement for this exact phosphatidylserine route, and is it strong enough for the stage we are trying to approve?

The short answer is that a phosphatidylserine TSE/BSE review should be handled as a route-specific animal-origin and document-control task, not as a vague reassurance. The European Commission explains that TSEs include diseases such as BSE in cattle and scrapie in small ruminants, and that Regulation (EC) No 999/2001 forms the legal basis for almost all EU legislative action on TSEs. The Commission also explains that public-health requirements for the entry into the Union of products of animal origin include Regulation (EC) No 999/2001, while imported products of animal origin present a high level of risk and undergo specific checks at EU border control. The practical implication is an inference from those primary sources: if a phosphatidylserine route is being presented as plant-derived and outside an animal-origin import-control path, the buyer still needs a controlled statement that matches the exact route under quotation rather than a casual email.

That distinction matters because European buyers do not ask for a TSE/BSE statement only when they suspect a problem. They ask because customer files, internal QA questionnaires, distributor approval packs, and contract-manufacturer reviews often require a clear answer on animal-origin risk and statement scope. A generic note saying "plant source" may help early commercial discussion. It does not automatically answer whether the exact route under review has been documented clearly enough for a Europe-facing supplier file.

This article is written for ingredient importers, distributors, supplement manufacturers, private-label brands, procurement managers, quality teams, and regulatory reviewers serving Europe. It focuses on supplier qualification, controlled statement review, and first-order 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 also keeps Phosphatidylserine, Soja Phosphatidylserine, and Girasol Phosphatidylserine on separate buyer paths, alongside Calidad e I+D, Fabricación, and Contactar con Ventas pages for current document requests. Final approval should still depend on the exact route, the current controlled statement, and the buyer’s own Europe-facing review path.

The Short Answer Buyers Need First

If your team is reviewing a phosphatidylserine TSE/BSE statement for Europe, the minimum workable process is:

1. Lock the exact route first: general PS, soy PS, or sunflower PS.
2. Confirm whether the question is about animal-origin status, customer questionnaire support, or first-order supplier approval.
3. Review the current TSE/BSE statement together with the route description, current specification, and source file.
4. Escalate anything that goes beyond a simple route declaration before the answer becomes a customer-facing promise.
5. Record a clear go, hold, or escalation decision.

That is the practical distinction buyers often miss. A statement can be commercially useful without being complete for every stage. A general product page can help orient the route. A sample COA can show batch-reporting style. None of those items, by itself, proves that the exact phosphatidylserine route has a controlled TSE/BSE answer that matches the current Europe-facing file.

Why TSE/BSE Statement Review Is Its Own Buyer Task

EU TSE controls focus on animal-origin risk, not casual product nicknames

The official EU sources frame TSE/BSE controls around animal-origin risk. The Commission’s TSE page explains that Regulation (EC) No 999/2001 is the legal basis for almost all legislative actions on TSEs and that the rules cover trade in live animals and products of animal origin. The Commission’s page on products of animal origin for human consumption separately lists Regulation (EC) No 999/2001 among the public-health requirements that apply to entry into the Union for those products. Another Commission page on official controls states that imported products of animal origin present a high level of risk and therefore undergo specific checks.

For phosphatidylserine buyers, that does not mean every route automatically falls into an animal-origin import framework. It means the buyer should stop answering TSE/BSE questions with a nickname such as "PS powder" or "sunflower route" and start answering them with a controlled route-specific document. If the commercial file is presenting a route as plant-derived, the statement should make that route clear enough that procurement, QA, and customer-facing teams are not forced to infer the answer.

The business lesson is simple: a TSE/BSE statement is not usually requested because the buyer believes phosphatidylserine is an animal-origin product. It is requested because the buyer needs a formal answer showing how the route should be classified and reviewed inside the approval file.

Plant-derived commercial routes still need controlled document answers

This is where many teams become careless. They correctly understand that a soy-derived or sunflower-derived route is not the same thing as a bovine or ovine product. Then they assume no further statement control is needed.

That shortcut causes downstream friction because European approval files often ask a more exact question:

That is why TSE/BSE review belongs beside, not inside, the other statement reviews. Allergen statement review answers a source and allergen-control question. GMO statement review answers a traceability and declaration question. Novel-food review for EU buyers answers a route authorization question. TSE/BSE review answers a narrower but separate question: how should the animal-origin risk position for this exact phosphatidylserine route be documented?

The Six-Part Buyer Workflow for Phosphatidylserine TSE/BSE Review

Lock the exact phosphatidylserine route and commercial stage first

Before requesting or approving any TSE/BSE statement, fix the commercial route in writing. Is the team reviewing general phosphatidylserine as an early comparison, or one source-specific route such as soy PS or sunflower PS? Is the statement needed for shortlist qualification, quotation approval, contract-manufacturer onboarding, distributor resale, or first bulk order?

This matters because TSE/BSE questions quickly become vague when the route is moving. A salesperson may send a general PS document. QA may be reviewing a soy-route file. The customer may be asking about sunflower because the non-soy position is commercially attractive. If the route is not fixed first, the statement review becomes a filing exercise instead of a control exercise.

The opening note should usually record:

• exact product route
• intended Europe-facing use
• commercial stage
• documents already in hand
• specific TSE/BSE or animal-origin question still open

That note prevents the team from asking for one statement and applying it to several different route discussions.

Separate route identity from the customer’s animal-origin concern

The second step is to identify what the downstream party is actually asking.

Sometimes the customer wants a simple animal-origin declaration for supplier qualification. Sometimes QA needs a controlled TSE/BSE-free statement in the technical file. Sometimes a contract manufacturer wants confirmation that the route under review is plant-derived before it aligns the broader compliance pack.

Those are related questions, but they are not identical. The buyer should separate:

1. the route being quoted
2. the document type being requested
3. the commercial stage at which the answer will be used

That separation keeps the review practical. A shortlist-stage distributor may only need confirmation that the supplier can issue the right route-specific statement. A first-order or customer-dossier stage may require a current formal statement plus matching source and specification files. Without that distinction, teams overpromise early and underdocument later.

Review the TSE/BSE statement, specification, and source file together

This is the control point that saves time later. Buyers should not review the TSE/BSE statement in isolation. They should compare it directly against the route description, current specification, and related source file.

At minimum, the review should ask:

That comparison matters because a TSE/BSE statement often fails for one simple reason: it belongs to a broader product family while the commercial file has already narrowed into a specific route. A buyer should not assume the route match is obvious. It should be checked deliberately.

This is also where the current Nutranexa structure helps. Buyers can compare Phosphatidylserine, Soja Phosphatidylserine, and Girasol Phosphatidylserine separately, then align the statement request with ¿Qué documentos deben solicitar los compradores para los ingredientes PS? y Phosphatidylserine Supplier Onboarding so the route and file set stay synchronized.

Escalate route or process questions before they become customer promises

Not every TSE/BSE question can be closed at procurement level. Some should be escalated immediately.

Escalation is usually appropriate when:

• the commercial route changed after the original statement was collected
• the statement is generic while the customer is asking for a route-specific answer
• the file does not clearly distinguish between a general plant-source claim and a formal TSE/BSE declaration
• the buyer is being asked to answer process or material questions not covered by the current controlled file
• a downstream customer wants to reuse the statement in a way that exceeds the current approval stage

The right escalation note does not need to be dramatic. It should simply state:

1. which route is under review
2. what question remains open
3. which file is missing or unclear
4. who owns the next answer

That is far safer than letting sales or procurement translate a generic statement into a more specific customer promise than the file actually supports.

Keep TSE/BSE review separate from novel-food, allergen, and GMO files

One reason these files drift is that teams treat every compliance question as if it were interchangeable. It is not.

That separation is commercially useful because it prevents a customer questionnaire from being answered with whichever file happens to be easiest to find. The stronger workflow is to map each question to one controlled document type, then close it clearly.

Close with a go, hold, or escalation decision

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

• Go: the route, statement, and supporting file are aligned well enough for the current stage.
• Hold: the route may still be commercially attractive, but the current statement or route match is not controlled enough yet.
• Escalate: the question goes beyond the current file and needs technical, quality, or customer-specific review.

This final note matters because TSE/BSE questions often resurface late. The quote is moving, the customer wants a document pack, and QA realizes nobody wrote down whether the current statement actually belongs to the route under approval. One short closeout note prevents that avoidable loop.

Need a Current TSE/BSE Support File for a Europe Project?

If your team is still relying on one generic animal-origin email while comparing soy and sunflower phosphatidylserine routes, pause before the quotation becomes a customer-facing commitment. 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 Europe use, order stage, expected quantity, and whether the question is being raised by procurement, QA, a contract manufacturer, or a downstream customer.

Common Mistakes in Phosphatidylserine TSE/BSE Review

Most failures come from file-control mistakes rather than from the existence of the question itself.

1. Asking for a general TSE/BSE statement before the team has fixed whether it is approving soy PS, sunflower PS, or only a general PS benchmark.
2. Treating a plant-source product nickname as if it automatically answers a controlled animal-origin question.
3. Using a COA or product page in place of a current route-specific statement.
4. Letting a customer questionnaire turn a generic statement into a more specific promise than the controlled file supports.
5. Mixing TSE/BSE review with allergen, GMO, or novel-food files and assuming one of them can stand in for the others.
6. Closing the commercial file without recording a go, hold, or escalation decision.

The practical fix is narrow and repeatable: keep one question at the center of the review. What controlled TSE/BSE or animal-origin statement do we need for this exact phosphatidylserine route at this exact Europe-facing stage?

How Verified Nutranexa Facts Fit This Workflow

For buyers evaluating Nutranexa, several verified site facts support a cleaner TSE/BSE statement workflow.

First, the site already separates Phosphatidylserine, Soja Phosphatidylserine, and Girasol Phosphatidylserine into distinct buyer paths. That helps teams keep the statement attached to one stable commercial route instead of one vague “PS” category.

Second, the site confirms usable supplier baseline facts for qualification: the company was founded in 2013, operates a 110,000+ m2 campus, and primarily serves Europe and North America. Those facts help orient the supplier file before the buyer requests route-specific statements.

Third, Nutranexa’s public site provides request paths through Calidad e I+D, Fabricación, and Contactar con Ventas rather than implying that one public marketing file answers every controlled question. That is the right operating pattern for TSE/BSE review as well: the buyer should request the current route-specific statement file and align it with the commercial stage.

Fourth, the site provides verified baseline handling facts for phosphatidylserine, including 25 kg MOQ y 25 kg netos por bidón packaging, together with visible COA/specification evidence and factory, packaging, and dispatch context. Those facts help first-order planning, but they do not replace the route-specific statement review described in this article.

Fuentes

• European Commission: Control of TSEs (including BSE and scrapie)
• European Commission: Products of Animal Origin for Human Consumption
• European Commission: Animals and Products of Animal Origin
• Regulation (EC) No 999/2001
• European Commission: Animal By-Products
• Regulation (EC) No 1069/2009

Preguntas frecuentes

Do European buyers need a TSE/BSE statement for phosphatidylserine?

Often yes, as a supplier-qualification or customer-file document. The practical need is usually not because buyers think phosphatidylserine is automatically an animal-origin product, but because they need a controlled statement showing how the exact route should be documented.

Is a phosphatidylserine COA enough for TSE/BSE review?

No. A COA can show reporting style or batch information, but it does not replace a route-specific TSE/BSE or animal-origin statement.

Should a soy phosphatidylserine statement and a sunflower phosphatidylserine statement be treated as interchangeable?

No. Buyers should match the statement to the exact route under quotation and not assume one route document automatically covers another route.

What is the most common TSE/BSE workflow mistake?

Approving a generic statement before fixing the exact route and commercial stage. That usually leads to a mismatch between the statement, the specification, and the customer question being answered.

What should buyers request from Nutranexa if the TSE/BSE file is still unclear?

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

Conclusion

Phosphatidylserine TSE/BSE review becomes manageable when buyers stop treating it as a vague reassurance and start treating it as a route-specific document-control task.

The strongest Europe-facing workflow is practical: lock the route first, identify what the downstream party is really asking, review the statement together with the specification and source file, escalate anything that exceeds the current controlled answer, and close with a clear commercial decision. That approach helps ingredient buyers avoid a common qualification failure: the project is moving, the customer question has arrived, but no one can clearly show that the TSE/BSE statement in the file belongs to the exact phosphatidylserine route being approved.

Próximos pasos recomendados

• Revisa el Phosphatidylserine página del producto.
• Comparar Soy PS y Sunflower PS.
• Verificar prueba de fabricación y Calidad e I+D.