Agriculture & Food: Organize Batch Traceability Records
Link harvest, inbound, and outbound records into a batch flow table, flagging quantity or source gaps.
Fictional batch: AG-105, category: apples Harvest record: plot P-3, 2026-09-12, 500 kg Inbound: 480 kg; outbound: 300 kg, destination store S-2 The 20 kg difference from harvest to inbound has no recorded reason.
Read both input and output
Input
Fictional batch: AG-105, category: apples Harvest record: plot P-3, 2026-09-12, 500 kg Inbound: 480 kg; outbound: 300 kg, destination store S-2 The 20 kg difference from harvest to inbound has no recorded reason.
Output
Preset traceability summary Batch AG-105: plot P-3 → warehouse → store S-2. Harvest 500 kg, inbound 480 kg: 20 kg difference to be explained. Book balance calculated from the given inbound/outbound records: 480-300=180 kg; not a physical inventory count result. To be supplemented: transport loss or sorting records, signed receipt documents. Cannot confirm food safety, certification status, or compliance conclusions based on this.
Applicable Scenarios
Link harvest, inbound, and outbound records into a batch flow table, flagging quantity or source gaps.
This demo uses fictional business data and pre-prepared outputs to show a customizable workflow; it is not a client case, live AI execution, or actual business result.
Work Steps
- Standardize batch numbers, weight units, and transfer nodes.
- Link records and calculate book quantity differences.
- Generate the traceability chain and a list of supporting documents to be supplied.
Human Review and Boundaries
Warehouse and quality personnel verify supporting documents, physical inventory, and inspection records; do not infer missing reasons as normal loss.
Customizable Content
Customize batch fields, traceability QR code materials, and supplier ledgers; can import agricultural or food ERP data.
How to Validate
Test separately with normal inputs, missing fields, and conflicting materials; check that key fields can be traced back to inputs, missing content is clearly marked, and numerical calculations are completed by reviewable rules. The samples and delivery scope agreed by both parties shall prevail.
Platform and Delivery
Instructions, templates, auxiliary scripts, and review steps can be customized for Codex or Claude. Specific product versions, tool permissions, and system interfaces are confirmed during the requirements phase and tested separately. Source files, test samples, and usage documentation can be delivered; this page does not connect to external systems, send notifications, or execute business operations.