Phosphatidylserine Allergen Statement Checklist for US and EU Ingredient Buyers

Ingredient buyers often reach the same problem from different directions. A US supplement brand wants a route that can move through its contract manufacturer without allergen confusion. A European distributor wants the source path documented before artwork or dossier review starts. Procurement has a phosphatidylserine quotation, QA has a specification, and regulatory has one short supplier email that says the product is "from sunflower" or "from soy." Everyone is using the same words, but not the same controlled file.

The short answer is that buyers should request a source-specific allergen statement and source declaration before approving phosphatidylserine for US and EU use. A generic COA, quotation, or "PS powder" description is not enough when the project could move through soy-sensitive or non-soy review paths. For dual-market work, the clean file should show the exact phosphatidylserine route under review, whether soy is part of the ingredient source, and how that source should be routed into downstream label and QA review.

This matters because soy is a regulated allergen topic in both markets. FDA lists soybeans among the major food allergens in the United States, and the EU's food-information regulation includes soybeans and products thereof in Annex II. That does not mean every phosphatidylserine review ends the same way. It means buyers should stop treating source identity as an informal commercial note and start treating it as a controlled approval document.

This article is written for importers, distributors, supplement manufacturers, private-label brands, procurement managers, QA teams, and regulatory reviewers working across North America and Europe. It focuses on B2B source control, allergen-document review, and handoff discipline. 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, with a 110,000+ m2 campus and a primary export focus on Europe and North America. It provides separate buyer paths for Phosphatidylserine, Soy Phosphatidylserine, and Sunflower Phosphatidylserine, plus visible document-request support through Quality & R&D and Contact Sales. Final approval should still depend on the current controlled files for the exact route and market being reviewed.

The Short Answer Buyers Need First

If your phosphatidylserine project may serve both US and EU customers, the minimum safe workflow is:

1. Fix the exact route first: general PS, soy PS, or sunflower PS.
2. Request a current source declaration and a current allergen statement tied to that route.
3. Check that those files align with the specification, COA pathway, and bulk product naming.
4. Route the source statement into regulatory and artwork review before the first commercial PO moves too far.
5. Record a clear go, hold, or escalation decision for the market combination you are serving.

The operational point is simple. A phosphatidylserine allergen statement is not just paperwork. It is the control that prevents a soy-route file, a sunflower-route quotation, and a generic internal product code from being treated as the same commercial item.

Why This Buyer Question Matters Across the US and Europe

Soy is a regulated allergen topic in both markets

This is the core reason the document matters. In the United States, FDA identifies soybeans as one of the major food allergens. In the EU, Regulation (EU) No 1169/2011 requires allergen information for listed substances and includes soybeans and products thereof in Annex II. For phosphatidylserine buyers, the commercial meaning is direct: when the route is soy-derived, the source cannot be handled as a casual background note.

That does not create the same file outcome for every product route. A sunflower phosphatidylserine route is a different source path from a soy phosphatidylserine route, and buyers should not collapse those paths into one generic "PS" approval folder. It also does not mean a buyer should make unsupported claims such as "allergen-free" based only on the absence of soy in a product nickname. The buyer still needs the supplier's current source-specific statement, plus internal review of how that information will be used downstream.

One practical advantage of a disciplined source statement is that it reduces rework across regions. The same basic file can support a US QA review, an EU dossier or artwork handoff, a distributor questionnaire, and a customer technical-pack request, provided the route is fixed and the statement remains current.

Bulk ingredient approval starts before finished label copy

Many teams wait too long to ask for allergen-support files because they think allergen questions only matter when retail label text is being written. That is too late for a clean B2B process.

FDA's allergen guidance explains that packaged foods, including bulk ingredients and ingredients used to make dietary supplements, still have allergen-labeling obligations. On the EU side, the regulation is aimed at food information supplied to the final consumer, but the operational burden for B2B buyers starts earlier because source identity drives technical review, artwork routing, distributor communication, and change-control decisions.

That is why the most useful buyer question is not "What will the final label say?" The better first question is: What source-specific file tells our teams whether this phosphatidylserine route should be treated as soy-derived or sunflower-derived in the first place?

The Five-Part Review Workflow

Lock the exact phosphatidylserine route before asking for statements

Before a buyer requests any allergen or source file, the project team should lock the route in writing. Is the product path general phosphatidylserine for open comparison, a soy route for an established formula, or a sunflower route for a non-soy position? Is the review for importer qualification, distributor resale, contract-manufacturer onboarding, or finished-brand dossier prep?

If that route is not fixed first, the team will collect documents that cannot be compared cleanly. A common failure is to request a "PS allergen statement," receive a soy-derived file, and later continue the quotation on a sunflower route because the commercial discussion shifted. By the time artwork or customer QA questions arrive, no one is sure which file belongs to which offer.

The route note should usually contain:

• product route
• market scope
• internal item code or quotation reference
• order stage
• responsible QA or regulatory owner

That one control note keeps source review attached to the actual buying decision.

Ask for a source declaration and an allergen statement, not one vague email

The second step is to request the right files in the right form. Buyers often ask a supplier, "Is this soy free?" and receive a short answer that is commercially helpful but not controlled enough for internal approval. A better workflow is to request two linked items:

1. A source declaration identifying the ingredient route under review.
2. An allergen statement showing how that route should be handled in customer, QA, or labeling review.

Those two documents may appear on one controlled file or on separate files depending on the supplier workflow, but the buyer should not accept an unstructured answer if the project will move across US and EU teams.

The table below helps separate what buyers should be checking.

Check the statement against the specification, COA, and product path

Once the supplier file arrives, buyers should compare it against the rest of the document set. The most important question is not whether the statement sounds reasonable. It is whether the statement belongs to the same commercial route as the specification, quotation, and COA process being discussed.

The fastest review is usually:

1. Check the product name and route on the specification.
2. Check whether the source statement uses the same route logic.
3. Confirm the COA path is attached to that same route, even if the COA itself is not the allergen file.
4. Match the route to the correct internal folder, customer file, or artwork workflow.

A COA can support batch identity and agreed specifications, but it is not a substitute for a source statement. That distinction is especially important if your team already uses Phosphatidylserine COA Review: Specification and Certificate Checks Before Approval or Phosphatidylserine Supplier Onboarding: Document Control Checklist for First Orders as internal references. Those pages help organize the wider approval packet. This article answers the narrower question of how the source and allergen file should be reviewed inside that packet.

Keep bulk-label review separate from finished-label approval

The fourth step is procedural and it prevents a lot of confusion. A bulk ingredient statement is not the same thing as final supplement label approval. The supplier's file supports the buyer's process. It does not replace the buyer's own regulatory, legal, or artwork decision.

In the US, this matters because bulk ingredients and dietary-supplement ingredients still need clear allergen handling within the supply chain. In the EU, this matters because the source path affects how teams prepare consumer-facing food information later. In both regions, the buyer should treat the supplier statement as an upstream control document, then run the finished label review under its own brand or manufacturer process.

This separation is also the best protection against overclaiming. If a sunflower route is not listed among the major allergens FDA names or among the Annex II allergens in the EU regulation, that does not automatically justify marketing language such as "allergen-free." It simply means the buyer should route the source file correctly and let its downstream teams decide the final compliant wording.

Record a market-specific go, hold, or escalation decision

The last step is to close the file with a decision that matches the market scope:

• approved for the current route and markets
• approved for one market but held for another pending clarification
• held pending source-statement correction
• escalated because the route changed or the file set conflicts

This is where dual-market discipline becomes real. A buyer may be comfortable with a sunflower route for a US quotation but still need a separate EU artwork handoff note. Another buyer may discover that a soy route is acceptable commercially, but only after the statement is corrected to match the current specification and customer-facing technical pack.

Without that closeout record, teams tend to reuse old source statements on new quotations. That is how preventable labeling and QA confusion enters a project that was otherwise technically straightforward.

A Mid-Process CTA for Buyers Missing Source-Specific Files

If your team is still debating whether a phosphatidylserine route is soy-derived or sunflower-derived, stop the approval flow and request the current source-specific file set before moving further. Nutranexa's contact page can be used to request the current specification, source declaration, COA support path, packaging references, and route-specific document handling for the exact phosphatidylserine item under review.

The fastest requests usually include the route, intended market, supplement format, order stage, and whether the question is for internal QA approval, distributor resale support, or artwork preparation.

Common Mistakes in Phosphatidylserine Allergen Review

The mistakes here are usually operational.

1. Asking whether the product is "soy free" instead of requesting a controlled source-specific statement.
2. Letting procurement use one route name while QA reviews another route file.
3. Treating a COA or quotation as if it replaces an allergen or source declaration.
4. Assuming a sunflower route can be marketed with broad claims that were never internally approved.
5. Reusing an old source statement after the route, market, or customer changed.

These errors slow projects because they force regulatory or QA teams to reconstruct the source history after the commercial path has already moved ahead.

How Verified Nutranexa Facts Fit This Workflow

For buyers evaluating Nutranexa, the current site supports this review in several practical ways. It provides separate product paths for general PS, soy PS, and sunflower PS, which is exactly how a disciplined allergen-review workflow should begin. It also provides visible document-request pathways through Quality & R&D, Manufacturing, and Contact Sales, plus public references to COA and specification support.

The site also confirms verified commercial baseline facts that help the file stay grounded: the company was founded in 2013, operates from a 110,000+ m2 campus, focuses exports on Europe and North America, and uses 25 kg MOQ with 25 kg net per drum for PS. Those details do not answer the allergen question by themselves, but they help buyers request the right route-specific file, packaging context, and commercial approval packet without inventing unsupported assumptions.

If a project may shift from soy to sunflower or vice versa, buyers should also keep Soya Phosphatidylserine Labeling and Regulatory Prep for European Supplement Buyers and Can Sunflower Phosphatidylserine Replace Soya Phosphatidylserine in Europe? in view. Those pages address adjacent issues. This article stays focused on the earlier control point: the source-specific statement that should be reviewed before those downstream questions expand.

Sources

• FDA: Food Allergies
• FDA Guidance for Industry: Questions and Answers Regarding Food Allergens, Including the Food Allergen Labeling Requirements of the Federal Food, Drug, and Cosmetic Act (Edition 5)
• Regulation (EU) No 1169/2011 on the provision of food information to consumers

FAQ

Can a phosphatidylserine COA replace an allergen statement?

No. A COA can support batch review and agreed analytical items, but it is not the same as a controlled source or allergen statement. Buyers should compare the COA pathway with the source statement, not use one to replace the other.

Does sunflower phosphatidylserine automatically mean I can make allergen-free claims?

No. A sunflower route is different from a soy route, but buyers should not jump from source identity to marketing claims. Final wording should be reviewed in the buyer's own regulatory and artwork process for the target market.

Should importers and contract manufacturers use the same source statement?

They should use the same current controlled route-specific file, even if each party records it in a different approval packet. The important point is that procurement, QA, and manufacturing are not working from conflicting source assumptions.

What is the first file I should request if my quotation only says PS powder?

Request the current specification and a route-specific source declaration first. Once the route is fixed, ask for the allergen statement, COA support path, and any packaging or customer-facing document references that belong to that same item.

How often should buyers refresh a phosphatidylserine source statement?

At minimum, refresh it whenever the route changes, the supplier issues a new controlled file, the customer or market changes, or the buyer is moving from sample or quotation stage into first commercial approval. Do not assume an old soy or sunflower statement still matches the current item.

Conclusion

Phosphatidylserine allergen review becomes manageable when buyers treat it as a route-control question instead of a late-stage artwork problem. The strongest US and EU workflow is to lock the exact source path, request a current source declaration and allergen statement, compare those files against the specification and COA path, and then close the file with a market-specific approval decision.

That process is practical, not bureaucratic. It prevents a soy-route file from being used on a sunflower quotation, keeps regulatory and QA teams aligned earlier, and reduces avoidable confusion before the first PO, artwork handoff, or customer technical review.

Recommended next steps

• Review the Phosphatidylserine product page.
• Compare Soy PS and Sunflower PS.
• Check manufacturing proof and Quality & R&D.