Soy Phosphatidylserine and EUDR: A Scope Review for European Buyers

European buyers sourcing soy-derived phosphatidylserine are increasingly being asked whether the ingredient is covered by the EU Deforestation Regulation, commonly called the EUDR. The question sounds as if it should have a simple yes-or-no answer because soya is one of the seven commodities named in Regulation (EU) 2023/1115. That shortcut is not reliable for a processed ingredient.

The direct answer is: soy origin alone does not make every soy-derived phosphatidylserine grade an EUDR relevant product. Start with the exact CN classification of the imported commercial product and compare that classification with Annex I. If the product is not listed in Annex I, the Commission's current FAQ says it is not directly subject to the Regulation even when it contains or was made from a covered commodity. If the exact grade falls within an Annex I entry, the importer must then determine its role and complete the applicable EUDR workflow before placing it on the Union market.

A European customer may still need upstream soy information for policy, contract, or customer requirements. The useful response is therefore a controlled file separating classification, legal scope, upstream evidence, and voluntary requirements.

This resource explains that workflow for soy phosphatidylserine buyers. It does not assign a CN code or provide legal advice. Classification and operator responsibility should be confirmed for the exact composition, concentration, carrier, manufacturing route, presentation, importer, and transaction.

The Short Answer Buyers Need First

Use this four-question screen before requesting a broad sustainability dossier:

Do not reverse this sequence: premature geolocation requests create unnecessary work, while an unsupported out-of-scope declaration creates the opposite risk.

As of 2 August 2026, the main EUDR obligations are scheduled to apply from 30 December 2026 for large and medium operators and for the specified timber-related micro and small operators. Other qualifying micro and small operators established by 31 December 2024 have a later date of 30 June 2027. The Commission also adopted a product-scope Delegated Act on 13 July 2026, including a proposal to remove soybeans for sowing, but stated that the act still had to pass European Parliament and Council scrutiny before entering into force. Buyers should therefore date every scope review and re-check the current legal text before import.

Why "Made from Soy" Is Not the Legal Scope Test

The Regulation names commodities and listed products

Regulation (EU) 2023/1115 covers relevant products listed in Annex I that contain, have been fed with, or have been made using one of the named relevant commodities. Under the soya heading, the current base Annex lists specific product codes: soya beans, soya-bean flour and meal, soya-bean oil and its fractions that are not chemically modified, and oilcake or other solid residues from extracting soya-bean oil.

That is a closed product list, not a rule that captures every later derivative merely because its history begins with soybeans. The Commission's April 2026 FAQ makes the distinction explicit: a product whose HS code is not in Annex I is not subject to the EUDR even if it includes a component derived from a covered commodity.

For a soy PS buyer, this means the words "soy-derived," "soy lecithin," or "phospholipid" cannot close the scope decision. The team must classify the commercial ingredient that is actually being imported. A supplier's description is useful input, but it is not a binding EU classification decision.

CN classification must match the exact grade

The EU Combined Nomenclature uses eight-digit CN codes for customs declarations and trade statistics. At import, a CN code can be further subdivided into a ten-digit TARIC code. The Commission FAQ instructs supply-chain members to classify their products against Annex I to establish whether the Regulation applies.

The classification review should use the same product facts that procurement and quality control use:

• source route, including soy or sunflower
• declared ingredients and carrier system
• phosphatidylserine concentration and broader composition
• manufacturing and transformation description
• physical form and packaging presentation
• intended commercial use where classification rules make it relevant

Do not borrow a code from soy oil, lecithin, another PS concentration, or a previous supplier. Where uncertainty is material, the importer should discuss the file with its customs representative or competent authority and consider Binding Tariff Information. The EU customs-clearance checklist explains that route.

Three Commercial Scenarios to Keep Separate

Scenario 1: the imported PS grade is not listed in Annex I

If the supported CN classification for the exact imported soy PS grade is outside the product codes listed in Annex I, the current Commission FAQ indicates that the finished PS product is not directly subject to EUDR requirements. The importer would not create a due diligence statement for a non-relevant product merely because soy appears upstream.

The buyer should still retain the scope memo. It should identify the grade reviewed, classification rationale, Annex version and review date, people approving the decision, and events that require re-review. That is much stronger than an email saying "not applicable."

Upstream traceability requests can still be commercially valid, but the contract should label them as customer policy, supply-chain risk management, or evidence for a separate in-scope product—not proof that the finished PS grade is subject to EUDR.

Scenario 2: the exact imported product falls within an Annex I soya entry

If the confirmed classification is within a listed soya entry, the scope conclusion changes. The EU entity first placing that relevant product on the market will generally need to determine its operator role and satisfy the applicable requirements when the law applies.

The EUDR's core conditions are cumulative: the relevant product must be deforestation-free, produced in accordance with the relevant legislation of the country of production, and covered by the required due diligence statement or simplified declaration. Information collection can include product description and quantity, country of production, supplier and customer information, and geolocation of the plots where the relevant commodity was produced. The operator must assess risk and mitigate any risk that is not negligible before placing the product on the market.

For imports, the Commission states that the applicable due diligence must be completed and the statement reference or declaration identifier obtained before the customs declaration for release into free circulation is lodged. This is why a last-minute request after the goods arrive is not a workable control.

Scenario 3: the finished PS is out of scope, but the buyer wants an upstream soy file

Many procurement teams will choose to request an upstream information pack even where the finished grade is classified outside Annex I. Reasons may include group sustainability rules, retailer expectations, lender requirements, customer questionnaires, or preparation for future scope changes.

This is a legitimate commercial choice if it is stated clearly. The request should define:

• which upstream material is being traced
• how far back in the manufacturing route the request reaches
• whether plot geolocation is required or a country-and-supplier statement is sufficient
• how the information must link to the supplied PS lot
• confidentiality and data-access rules
• whether certification is supporting evidence or a contractual condition

The distinction protects both parties. It prevents the buyer from treating voluntary evidence as a statutory due diligence statement, and it prevents the supplier from answering a detailed request with a generic sustainability sentence.

Build a Seven-Part EUDR Scope and Evidence File

1. Lock commercial product identity

Record the supplier legal entity, product name and code, soy source, PS concentration, carrier or other declared ingredients, physical form, specification revision, packaging unit, and intended import route. Attach the current specification rather than relying on a sales description.

Nutranexa makes current specification and COA evidence available for PS buyer review. Its public site also verifies a 25 kg MOQ and 25 kg per drum for phosphatidylserine. Those facts help identify the proposed commercial unit, but they do not determine customs or EUDR scope.

2. Document the classification rationale

Create a short classification memo that connects product facts to the proposed CN code. Include the source of the proposal, the date it was checked, related TARIC research, and any customs advice or Binding Tariff Information used. Keep this work aligned with the product master data and commercial invoice.

3. Compare with the current Annex I

Record the exact Annex I version reviewed and whether the code appears under the soya commodity. Do not use a cached list without a date. The Commission can amend the product list through delegated acts, and its July 2026 announcement shows that the scope is actively maintained.

4. Map the transaction and responsible entity

Identify the non-EU supplier, EU importer, customs declarant, first customer, downstream operator, and trader where relevant. The Commission explains that non-EU producers generally do not have direct obligations unless they directly place products on the EU market, but EU customers may ask them for legality and geolocation information so the EU operator can do its work.

5. Request evidence proportionate to the conclusion

For an in-scope product, the operator needs information capable of supporting the statutory due-diligence process. For an out-of-scope product, ask only for the upstream evidence justified by policy or contract. A useful request may include origin countries, upstream material identity, traceability method, lot linkage, change notification, and the supplier contact responsible for maintaining the file.

6. Link the conclusion to purchase and lot controls

Add the approved scope status to the purchase specification or supplier-approval record. If an in-scope product is involved, define how due diligence statement references or declaration identifiers will be linked to purchase orders, shipments, customs entries, and received lots. If the product is out of scope, keep the approved rationale accessible to customs, regulatory, and quality colleagues.

7. Create re-review triggers

Re-open the decision when any of these changes:

• source changes from soy to sunflower or the reverse
• PS concentration, carrier, or composition changes
• manufacturing route or supplier legal entity changes
• the proposed CN or TARIC classification changes
• Annex I or Commission guidance is updated
• the importer, declarant, or transaction structure changes
• a customer adds a contractual traceability requirement

This connects EUDR preparation with the repeat-order document review rather than treating it as a one-time questionnaire.

Need a Source-Specific PS File for European Review?

Nutranexa was founded in 2013, operates a 110,000+ m2 campus, primarily serves Europe and North America, and supports R&D cooperation. European teams comparing soy and sunflower routes can request the current soy PS specification, available COA evidence, manufacturing context, and source-related files for their own classification and EUDR review. Share the exact grade, destination country, importer, and document checklist so the response can be matched to the transaction.

Buyer Request Matrix

Keep this matrix separate from the certificate of origin review. A customs origin document and an EUDR evidence set answer different questions. The same is true of a GMO statement or allergen statement: each can be important, but none determines EUDR Annex I scope.

Common Buyer Mistakes

1. Treating the word "soy" as proof that every processed derivative is in scope.
2. Accepting a supplier's proposed customs code without matching it to the exact grade.
3. Asking for a due diligence statement before identifying the EU operator and the relevant product.
4. Using a generic sustainability certificate as a substitute for classification and due diligence.
5. Combining EUDR, GMO, allergen, customs origin, and food-law approval into one yes-or-no declaration.
6. Failing to date the review even though application dates, guidance, and Annex I can change.
7. Collecting upstream data without a method to connect it to the purchased lot.

Источники

• Regulation (EU) 2023/1115 on deforestation-free products, consolidated text and Annex I
• Regulation (EU) 2025/2650 amending EUDR obligations and application dates
• European Commission: FAQ on EUDR Implementation, Version 5
• European Commission: EUDR implementation resources and product-scope guidance
• European Commission: Understanding EUDR due diligence
• European Commission: July 2026 update on EUDR product scope and implementation tools

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

Is soy phosphatidylserine automatically covered by the EUDR?

No. Soy is a relevant commodity, but the Commission's current guidance says the Regulation applies only to products listed in Annex I. Buyers must classify the exact imported PS grade and compare its CN code with the current Annex instead of deciding from soy origin alone.

Which soy products are listed in the EUDR Annex I?

The base Annex I lists soya beans, soya-bean flour and meal, soya-bean oil and its fractions that are not chemically modified, and oilcake or other solid residues from extracting soya-bean oil. Buyers should check the current legal text because the Commission adopted a scope update in July 2026 that was still awaiting scrutiny at the time of this article.

Does an out-of-scope soy PS grade need a due diligence statement?

Not solely because it is soy-derived. If the exact product is not listed in Annex I, the current Commission FAQ says it is not directly subject to EUDR requirements. A customer may still request upstream evidence under contract or company policy, but that should be distinguished from a statutory due diligence statement.

Can a sustainability certification replace EUDR due diligence?

No. The Commission says certification or verification schemes may support risk assessment when they cover relevant information, but the operator must still exercise due diligence and remains responsible for compliance.

What should a European buyer send when requesting an EUDR review from a PS supplier?

Send the exact product code, composition or specification, proposed CN classification, destination, importer and declarant details, intended transaction, and a clear evidence checklist. State whether the request supports legal EUDR scope, upstream risk management, or a voluntary customer policy.

Conclusion

The correct EUDR question is not "Does this ingredient come from soy?" It is "Is this exact commercial product, under its supported CN classification, listed in the current Annex I, and who is placing it on the EU market?" Once that answer is controlled, the buyer can request proportionate evidence, connect it to the imported lot, and avoid confusing statutory due diligence with a voluntary sustainability file.

For soy phosphatidylserine procurement, keep classification, EUDR scope, upstream traceability, customs origin, allergen, and GMO decisions in separate but connected records. Re-check the file whenever the grade, route, supplier, classification, law, or customer requirement changes.

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

Preparing a European soy PS qualification file? Contact Nutranexa sales with the exact grade, destination, expected annual quantity, importer details, and document checklist. The team can provide current product and COA information for your customs, regulatory, procurement, and Качество и НИОКР review.

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

• Просмотрите Phosphatidylserine страница продукта.
• Сравнить Soy PS и Sunflower PS.
• Проверять производственное доказательство и Качество и НИОКР.