A Qadex supplier approval record is not lot-level receiving evidence
Qadex presents food-safety and supplier-quality software covering approval, specifications, complaints, audits, incidents, and traceability-related records. An approved supplier and current document set can govern who may supply a product, but each received lot still needs identity, source, date, quantity, condition, specification, and disposition evidence tied to the actual shipment.
Editorial figure by Food Traceability Ledger. Source context: Qadex.
Approval defines an allowed relationship
A supplier program can collect facility details, certifications, audits, questionnaires, specifications, corrective actions, and approval status. That record may determine whether purchasing can place an order for a defined product, facility, or risk category. It does not establish that every delivery came from the approved site, matched the approved specification, or remained within required conditions in transit.
The approval record should identify legal entity, producing and shipping sites, products and processes in scope, evidence versions, risk basis, restrictions, approval owner, effective and expiry dates, review cadence, and suspension triggers. A corporate-level approval should not automatically cover a new facility, broker, product form, ingredient source, or subcontractor without an explicit applicability decision.
Receiving creates lot-level facts
Each receipt should preserve purchase order and shipment identifiers, supplier and origin sites, item and form, supplier lot, internal lot, quantity and unit, production or harvest date where relevant, receipt time and location, carrier and seal information, temperature or condition evidence, certificates, inspection or sampling results, exceptions, and disposition. These facts belong to the received material, not only to the supplier profile.
Identity reconciliation matters when labels, advance shipping data, certificates, and physical quantities disagree. The system should hold the affected material, preserve the conflict, route investigation, and record any relabeling or split-lot action. A current supplier certificate cannot resolve a mismatched lot code or prove that this shipment met the agreed specification.
Genealogy should inherit evidence deliberately
When received material enters production, the traceability record should connect its lot identity and accepted quantity to transformations, work in process, rework, finished lots, storage, and shipments. Supplier and specification metadata can provide context, but only defined fields should propagate. A later supplier-status change should not rewrite historical receiving or production events.
If a supplier is suspended or a document expires, the organization needs a rule for stock already received, open purchase orders, material in production, and finished goods. The action may vary by hazard and evidence. The system should show affected lots and decisions rather than treat relationship status as an automatic recall or as proof that existing inventory is safe.
Test approval and receipt mismatches
A representative evaluation should receive product from an unapproved site under an approved parent, submit an expired certificate, change the specification after shipment, split one supplier lot into two internal lots, and discover a quantity mismatch. Reviewers should preserve source records, hold affected material, approve or reject at the correct scope, and trace accepted quantities into production without inventing missing events.
Qadex's official site supports the described supplier, specification, quality, incident, and traceability-related positioning. It does not establish external event completeness, internal genealogy depth, configured workflows, supplier performance, lot conformity, recall speed, or outcomes. Food businesses retain responsibility for hazard analysis, supplier controls, receiving, specifications, traceability, recall, regulatory applicability, food safety, and legal judgment.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Food Traceability Ledger will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.