SPICE COMPLIANCE PLANNING

Codex Alimentarius & EU Spice Compliance Guide

Codex texts and European Union food law are different reference systems. The applicable requirement depends on the exact spice, form, residue or contaminant, destination and decision date. Use this guide to plan the evidence; it is not a certificate of compliance or legal advice.

By Fu Yang Updated

06 Spice Testing Documents Card

PRACTICAL TIPS

Separate the Codex baseline from the EU legal check

Separate the Codex baseline from the EU legal check
RequirementCodex baselineEU requirement
Legal roleInternational food standards, codes of practice and recommendations used as reference points.EU legislation applies to food placed on the EU market; the current legal text controls.
Pesticide MRL lookupSearch the Codex pesticide-residue database for the commodity and pesticide combination.Search the EU pesticides database by food product and active substance, then confirm the current legal text.
When no specific pesticide MRL is listedDo not assume that one universal fallback applies; confirm whether Codex has adopted an MRL for the exact combination.Regulation (EC) No 396/2005 generally uses a 0.01 mg/kg default where no specific MRL is set, subject to the regulation and its exceptions.
Mycotoxin controlUse the Codex code of practice for preventing and reducing mycotoxins in spices together with the General Standard for Contaminants and Toxins.Match the product category to the current maximum levels in Regulation (EU) 2023/915 and its amendments.
Shipment evidenceKeep prevention, sampling, methods and identified results connected to the material assessed.Keep the agreed specification, identified lot or sample, relevant laboratory result, packing record and destination documents connected.

Pesticide residues (MRLs)

An MRL is not one number for every spice or every pesticide.

Define the product before selecting the test scope

Record the botanical and commercial identity, whole or ground form, intended destination and the pesticide or residue definition being checked. Query the official database for that exact combination rather than copying a limit from another spice.

EU MRLs apply to imported products as well as products produced within the EU. A limit found in Codex does not automatically replace the applicable EU limit.

Confirm the rule on the decision date

MRL entries and legislation can change. The buyer or importer should confirm the current requirement and the laboratory scope before sampling, ordering or releasing a shipment.

Record the database or legal text consulted, the date, the commodity mapping, the analyte and the limit of quantification needed for the decision.

Mycotoxin prevention and testing

A laboratory result is one part of control; prevention begins earlier in the supply chain.

Connect prevention to sourcing and handling

Codex CXC 78-2017 describes good agricultural, manufacturing and storage practices for reducing mycotoxins in spices. Drying, cleaning, moisture control, storage and transport conditions should therefore be considered before the test plan is finalised.

Match the plan to the regulated category

Regulation (EU) 2023/915 sets contaminant maximum levels by food category. Confirm how the exact product is classified, which contaminant applies, and which consolidated version or amendment is in force before stating that a lot meets an EU limit.

Export documentation

Evidence is useful only when every record points to the same product and decision.

Build one traceable evidence chain

Connect the agreed specification and version to the identified sample or lot, sampling date, requested methods, laboratory report or COA, packing record and shipment references. A generic certificate without that connection does not establish the condition of a future lot.

State each party’s role precisely

Yang Squared Spices can coordinate product information, requested checks and order records. The buyer or importer should confirm destination-law requirements, and an appropriately qualified laboratory or authority should issue the evidence within its own scope. Avoid blanket claims such as “EU compliant” without product- and lot-specific support.

QUICK CHECK

Compliance brief to confirm before quotation

  • Exact product, botanical identity and form
  • Destination market and intended use
  • Pesticides, residue definitions and applicable limits
  • Contaminants and product-category mapping
  • Sampling plan, methods and required quantification limits
  • Lot or sample identity and record dates
  • Packing, labelling and destination documents
  • Rule version, review date and responsible reviewer

Regulations and database entries change. Confirm the current official source and the buyer or importer’s requirements for each order; this page does not certify any product or shipment.

BUYER QUESTIONS

Frequently asked questions

Does meeting a Codex limit automatically prove EU compliance?

No. Codex texts and EU legislation are different reference systems. Confirm the rule that applies to the exact product, substance, destination and date.

Is one EU pesticide MRL valid for every spice?

No. The result depends on the active substance, residue definition and food-product category. The EU default is relevant only when no specific MRL is set and the regulation's conditions are met.

Which document proves that a spice shipment meets the requirement?

There is no single generic document for every order. Use an agreed specification connected to an identified sample or lot, relevant laboratory evidence, packing records and the required destination documents.