Short answer: A whole Cordyceps sinensis lot is meaningfully traceable when its identifier connects the received material to the supplier, exact product and grade, relevant batch documents, packaging records and the businesses that received it. A mock recall tests whether those links work in practice. Select one lot, set a time window, reconstruct its path and record every missing or conflicting link.
For Jian'an enquiries, the product description should remain explicit: whole cultivated Ophiocordyceps sinensis raw material, not wild-harvested material and not Cordyceps militaris. Traceability records should preserve that identity rather than shortening it to an ambiguous “Cordyceps” label.
What should a Cordyceps lot record connect?
| Record group | Useful data fields | Traceability question |
|---|---|---|
| Supplier and source | Supplier legal name, contact, purchase order and supplier lot/reference | Who supplied the material and under which transaction? |
| Product identity | Scientific name, cultivated status, whole-material format and grade | What exactly is the lot? |
| Internal lot identity | Unique lot code, receipt/packing date and quantity | How is the material distinguished from other lots? |
| Specification and sample | Specification version and approved-sample reference, where used | Which acceptance basis applied? |
| Documents and tests | Document identifiers, dates, lot references and review status | Which evidence belongs to this lot? |
| Packaging | Pack format, label version, pack count and any sub-lot or carton codes | How can affected physical units be located? |
| Storage and movement | Locations, transfers, dates and quantities | Where has the material been held or moved? |
| Onward supply | Customer/business recipient, shipment reference, date and quantity | Which businesses received material from the lot? |
| Reconciliation | Received, used, held, lost/damaged and shipped quantities | Can the total quantity be accounted for? |
How do you run a simple mock recall?
- Define the exercise: choose one real lot, a simulated issue and the records to be tested.
- Start the clock: record when the exercise begins and who coordinates it.
- Trace backward: identify the supplier, purchase record, product identity, specification and incoming documents.
- Trace internally: locate all remaining stock, repacked units, transfers, samples and quantity adjustments.
- Trace forward: identify every business recipient, shipment reference, date and quantity linked to the lot.
- Reconcile quantities: compare the quantity received with quantities held, used, sampled, damaged and shipped.
- Test communication: verify that current supplier, internal and customer contacts are available.
- Close the gaps: document missing records, inconsistent codes and corrective actions with owners and dates.
The exercise should use a defined scenario, but it must not be represented publicly as a real safety incident. Its purpose is to test record retrieval and decision readiness.
What does a useful mock-recall report look like?
| Report item | Record |
|---|---|
| Exercise scope | Selected lot, simulated reason, start/end time and team |
| Identification result | Exact product, grade, lot and affected pack range |
| Backward result | Supplier and incoming records found or missing |
| Internal result | Locations, status and quantities found |
| Forward result | Business recipients and shipment records found or missing |
| Reconciliation result | Quantity accounted for and any unexplained difference |
| Communication result | Contact lists and notification templates tested |
| Corrective actions | Gap, responsible person, target date and completion evidence |
Which lot-code problems commonly break traceability?
- The same code is reused for different products, grades or packing events.
- A supplier code is replaced internally without keeping the link between both codes.
- Repacked cartons lose the original lot reference.
- Batch reports use a code that does not match the physical label.
- Broken pieces or downgraded material are moved without a documented lot relationship.
- Stock adjustments are made without a reason or record.
- Sales or shipment records identify only the product name, not the lot.
What do international and market-specific rules say?
ISO 22005:2007 provides principles and basic requirements for designing and implementing traceability systems in the feed and food chain. ISO states that the standard can apply to organizations at any step of the chain and that traceability can help determine the history or location of a product or relevant components. The ISO page provides the publication status and review history; buyers should check the current status when applying the standard.
Codex's General Principles of Food Hygiene include traceability/product tracing and recall-related principles within food hygiene systems. They provide a framework rather than a Cordyceps-specific legal approval.
For the European Union, Article 18 of Regulation (EC) No 178/2002 requires traceability through production, processing and distribution and requires food businesses to identify suppliers and business customers. Article 19 addresses withdrawal, authority notification and, where necessary, consumer recall. The EUR-Lex regulation page provides access to the original act and current consolidated version. This is a market-specific legal reference; buyers outside its scope must check their own applicable law.
Buyer questions to ask a supplier
- Which code identifies the commercial lot, and where does it appear?
- How does that code connect to product identity, grade and batch documents?
- What happens to the lot reference when material is sorted, repacked or downgraded?
- Can the supplier identify the quantities and business recipients associated with an affected lot?
- Who receives urgent quality or traceability notifications?
- How are corrections to lot records controlled?
Important limitations
A successful mock recall shows that selected records could be retrieved under the chosen scenario; it does not prove that the product is safe, legally permitted or compliant in every market. Recall duties, notification timelines, record-retention periods and authority contacts vary by jurisdiction and business role. Buyers should establish procedures with qualified legal and food-safety advisers for their intended destination and use.
Request Lot and Traceability Information
Related Jian'an resources
- Whole Cultivated Ophiocordyceps sinensis Product
- Four-Grade Guide
- Quality and Batch Information
- Buyer FAQ
- B2B Enquiry
Jian'an Cordyceps