Phosphatidylserine Gluten-Free Statement Review for US and EU Buyers

Phosphatidylserine buyers often clear the familiar questions first: source, assay, MOQ, packaging, COA, allergen position, and destination-market documents. Then a project moves into a gluten-free supplement, powder blend, or functional food brief and one narrower question starts delaying approval: what exactly should a phosphatidylserine gluten-free statement prove before procurement, QA, and downstream regulatory teams rely on it?

The short answer is that buyers should approve a route-specific gluten-free support file, not a casual assumption that soy phosphatidylserine or sunflower phosphatidylserine is automatically suitable for every gluten-free project. In the United States, FDA's gluten-free rule in 21 CFR 101.91 sets the voluntary claim standard at less than 20 parts per million gluten for foods that bear the claim. In the EU, Implementing Regulation (EU) No 828/2014 also uses 20 mg/kg as the condition for foods described as gluten-free, while separately allowing "very low gluten" under stricter defined conditions up to 100 mg/kg. For B2B ingredient buyers, the operational implication is an inference from those primary sources: the numeric threshold may align, but the supplier approval file still has to explain the route, support basis, and whether any gluten-related cross-contact question remains open.

This article is written for ingredient importers, distributors, supplement manufacturers, functional food brands, procurement managers, formulation teams, QA teams, and regulatory reviewers serving Europe and North America. It focuses on supplier qualification, source-route review, and commercial document control. It does not provide legal advice.

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, Soja Phosphatidylserine, and Girassol Phosphatidylserine on separate buyer paths, with request routes through Qualidade e P&D, Fabricação, and Contato de vendas for current controlled documents. Final gluten-free approval should still depend on the exact route, current support files, and the buyer's own finished-product review path.

The Short Answer Buyers Need First

If your team is reviewing a phosphatidylserine route for a US or EU gluten-free project, the minimum workable process is:

1. Lock the exact route first: general PS, soy PS, or sunflower PS.
2. Request a current gluten-free statement or equivalent controlled support file for that exact route.
3. Check whether the file explains source identity, gluten-containing grain exposure, and cross-contact or processing assumptions clearly enough for the intended project stage.
4. Keep the supplier support file separate from the final consumer claim decision on the finished supplement or food.
5. Record a clear go, hold, or escalation decision before the route moves into customer handoff or commercial artwork review.

That is the practical distinction buyers often miss. A phosphatidylserine route may look low-risk for gluten on paper, but a low-risk route is not the same thing as a controlled supplier answer.

Why a Gluten-Free Statement Is Its Own Buyer Task

US and EU gluten-free thresholds are similar, but the approval file is not automatic

The first reason this deserves its own workflow is that the regulatory headline looks simple while the commercial file does not. In the U.S., FDA says any food bearing a gluten-free claim must comply with 21 CFR 101.91. That rule defines the voluntary claim and sets the basic limit at less than 20 ppm gluten. FDA's gluten-free labeling materials also make clear that the rule applies to FDA-regulated foods, including dietary supplements. In the EU, Implementing Regulation (EU) No 828/2014 lays down the information requirements for foods that describe themselves as gluten-free or very low gluten, and the European Commission's guidance page repeats the same 20 mg/kg ceiling for gluten-free foods.

For buyers, that similarity is helpful, but it is not a shortcut. It does not mean that a supplier's commercial note saying "no gluten ingredients used" is automatically enough for a US supplement dossier, an EU distributor questionnaire, or a customer-facing technical pack. It means the buyer should know what target claim path is being discussed, then ask whether the supplier file actually supports that path.

On January 21, 2026, FDA announced that it was seeking information on gluten labeling and prevention of gluten cross-contact in packaged food, including issues involving rye, barley, and oats because of cross-contact with gluten-containing grains. That is not a new finished-product rule by itself, but it is a current signal that gluten-related transparency remains active.

Source identity helps, but cross-contact and downstream use still need control

Soy phosphatidylserine and sunflower phosphatidylserine are not wheat-, barley-, or rye-based ingredient routes. That is relevant. But buyers should not jump from that observation straight to a downstream promise. A stronger supplier review still asks:

• what the exact route is
• whether any gluten-containing grain is part of the raw-material or process chain
• whether the statement addresses cross-contact or facility-control questions
• whether the project needs only internal qualification support or a customer-facing technical answer

This is also why a gluten-free statement should stay separate from an allergen file. Phosphatidylserine Allergen Statement Checklist for US and EU Ingredient Buyers answers the soy-source question. A gluten-free statement answers a different one.

The Six-Part Workflow for Reviewing a PS Gluten-Free Statement

Lock the exact phosphatidylserine route and commercial stage first

Before requesting any gluten-free support file, write down the exact route in review. Is the project comparing general PS at shortlist stage, a soy route for an existing formulation, or a sunflower route for a non-soy product brief? Is the file needed for importer qualification, a distributor document pack, a co-manufacturer questionnaire, or a final customer technical review?

This matters because gluten-related questions drift quickly when teams keep using one generic internal label such as "PS powder." Procurement may still be negotiating one route while QA has already stored another route's document set.

The opening route note should usually record:

• exact product route
• intended market
• commercial stage
• current document set in hand
• who is asking the gluten question and why

Separate a gluten-free statement from a COA, allergen file, and marketing claim

The second step is to stop treating every supporting document as if it answers the same question. Many teams already have a specification, a COA sample, a source declaration, and perhaps an allergen file. Those documents matter, but the gluten-free question should still be isolated. A clean review typically separates four layers:

1. the route and source identity
2. the gluten-free support statement
3. the internal supplier-qualification decision
4. the final consumer-facing claim decision

If your team already uses Quais documentos os compradores devem solicitar para os ingredientes PS? or Phosphatidylserine Supplier Onboarding: Document Control Checklist for First Orders internally, keep this article in a narrower lane. The question here is not whether the buyer has a broad supplier packet. It is whether one controlled gluten-free support file is clearly attached to the right route.

Check what the statement says about source grains, processing, and cross-contact

Once the file arrives, review the content, not just the presence of the file. A buyer should be able to tell what the supplier is actually saying.

At minimum, the statement should help the buyer understand:

• which phosphatidylserine route the file covers
• whether wheat, barley, rye, or related gluten-containing grain exposure is part of the route
• whether oats or cross-contact concerns were considered where relevant
• whether the supplier is making a route-status statement, a batch-specific statement, or a broader commercial declaration

This is also the right place to identify what the file does not say. If the statement only says "product is gluten free" without identifying the route or support basis, it may be commercially helpful but technically weak.

Match the file to the intended US or EU claim pathway

The fourth step is where buyers often overreach. The supplier file should be reviewed against the intended market path, but it should not be mistaken for the final market decision. In the U.S., FDA's rule defines when a food can bear a gluten-free claim. In the EU, Regulation 828/2014 defines the information allowed for gluten-free and very low gluten foods. For ingredient buyers, the practical lesson is:

• supplier qualification is upstream
• finished-product claim use is downstream
• the same numeric threshold does not eliminate the need for document control

This distinction becomes important in multi-step supply chains. A brand may buy phosphatidylserine for a capsule line, then hand the route to a contract manufacturer with its own allergen and gluten controls. The supplier statement supports the process, but it does not collapse all later decisions into one.

Escalate early if the project is customer-facing or co-manufactured

Escalation is usually appropriate when:

• the file is generic and does not clearly identify the route
• the customer questionnaire asks for cross-contact or facility-control detail that the statement does not cover
• the route changed after the original file was collected
• the project involves a contract manufacturer or private-label customer with its own gluten-control program
• commercial teams are trying to use a sourcing statement as if it were a finished-label approval

Because FDA is actively seeking information on gluten labeling and prevention of gluten cross-contact, buyers should assume that weak wording will receive more scrutiny, not less.

Close with a go, hold, or escalation decision

The last step is to leave a decision another team can use.

• Go: the route is stable, the gluten-free support file is controlled enough for the current stage, and downstream teams know how to use it.
• Hold: the route may still be commercially acceptable, but the gluten-free file is too vague, too broad, or attached to the wrong route.
• Escalate: the project needs QA, regulatory, or customer-specific clarification before the route can be approved for the intended market stage.

Need a Current Gluten-Free Support File?

If your team is still relying on an assumption such as "sunflower is probably fine" or "soy is not a wheat ingredient" instead of one controlled route-specific file, stop before the answer becomes a customer-facing promise. Use Nutranexa's contact page to request the current specification path, route-specific gluten-related support file, COA-review path, and related document handling for the exact phosphatidylserine item under review.

Common Mistakes in Phosphatidylserine Gluten-Free Review

Most failures here are document-control failures, not ingredient-science failures.

1. Assuming soy or sunflower phosphatidylserine is automatically approved for gluten-free use without requesting a controlled support file.
2. Treating a COA, specification, or allergen statement as if it automatically answers the gluten-free question.
3. Reusing a route-specific file after the project has changed from one source path to another.
4. Letting sales or customer service make a finished-claim promise before QA and regulatory have aligned the supplier file to the downstream use.
5. Ignoring cross-contact wording because the raw material is not wheat-based on paper.
6. Forgetting that EU gluten-free and very low gluten are not the same information category.

The practical fix is narrow and repeatable: keep one question at the center of the review. What controlled gluten-related support file do we have for this exact phosphatidylserine route at this exact commercial stage?

How Verified Nutranexa Facts Fit This Workflow

For buyers evaluating Nutranexa, the current site supports this workflow in several practical ways.

First, it separates Phosphatidylserine, Soja Phosphatidylserine, and Girassol Phosphatidylserine into distinct buyer paths. That makes it easier to keep a gluten-free review attached to one stable route instead of one vague "PS" category.

Second, the site confirms reusable qualification facts that are safe to cite during supplier screening: Nutranexa was founded in 2013, operates a 110,000+ m2 campus, and primarily serves Europe and North America. It also shows visible request paths through Qualidade e P&D, Fabricação, and cases rather than implying that one public page answers every downstream customer question.

Third, the site provides verified commercial baseline details that help buyers frame the right request, including 25 kg MOQ, 25 kg líquidos por tambor packaging for PS, public specification and COA evidence, and visible factory, packaging, and dispatch imagery. Those facts help qualification and logistics planning, but they do not replace the gluten-free review described in this article.

Fontes

• FDA: Gluten-Free Labeling of Foods
• eCFR: 21 CFR 101.91 - Gluten-free labeling of foods
• FDA: Questions and Answers on the Gluten-Free Food Labeling Final Rule
• FDA: FDA Takes Steps to Improve Gluten Ingredient Disclosure in Foods
• European Commission: Gluten-free food
• EUR-Lex: Commission Implementing Regulation (EU) No 828/2014

Perguntas frequentes

Do buyers need a phosphatidylserine gluten-free statement if the route is soy or sunflower?

Often yes, especially when the project will support a gluten-free supplement or food brief, a customer questionnaire, or a co-manufacturer approval file. Source identity helps, but buyers still need a controlled supplier answer for the exact route.

Can a phosphatidylserine COA replace a gluten-free statement?

No. A COA can support route and batch review, but it is not the same as a controlled gluten-free statement or route-specific declaration.

Does the same 20 ppm threshold in the US and EU mean the supplier file can be reused without review?

No. The shared threshold is useful, but buyers should still check whether the supplier file matches the exact route, the intended commercial stage, and the downstream claim pathway.

Is soy phosphatidylserine automatically unsuitable for gluten-free projects because it is an allergen topic?

No. Soy allergen review and gluten-free review are different questions. Buyers should review both when needed, but they should not treat one file as a substitute for the other.

What should a buyer request from Nutranexa if the gluten-free file is still unclear?

Request the exact route-specific specification path, the current gluten-related support file, the COA-review path, and any relevant source or process clarification for the phosphatidylserine route under review, then align those files to the intended US or EU project stage before approval.

Conclusion

Phosphatidylserine gluten-free review becomes manageable when buyers stop treating it as an assumption and start treating it as a route-specific document-control task.

The strongest US and EU workflow is practical: lock the route first, separate the gluten-free support file from the COA and allergen file, check what the statement says about source and cross-contact, match it to the intended claim pathway, escalate customer-facing projects early, and close with one explicit decision.

That approach helps ingredient importers, supplement manufacturers, distributors, and QA teams avoid a common failure pattern: the route looks commercially easy, but nobody can show that the gluten-free answer in the file actually belongs to the exact phosphatidylserine item being approved.

Próximas etapas recomendadas

• Revise o Phosphatidylserine página do produto.
• Comparar Soy PS e Sunflower PS.
• Verifique prova de fabricação e Qualidade e P&D.