Food Lot Identity Gap Tool

Description

Count literal lot mismatches, product mismatches and records matching both.

Food-safety records connect lots, samples, tests, labels and handling events. Consistent identifiers and reconciled quantities support record review, but do not establish safe food, complete traceability or valid regulatory approval.

Count literal lot mismatches, product mismatches and records matching both.

When to use this tool

Use Food Lot Identity Gap when you need a specified food-handling record or traceability diagnostic.

How to use the tool and how it works

Enter lotIds, sourceLotIds, productIds, sourceProductIds. Keep parallel arrays aligned. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read lotMismatches, productMismatches, jointMatches. Use the output convention below.

Require aligned lot/product and source-ID arrays. Count literal lot mismatches, product mismatches and records matching both.^[1]

Input field	Meaning and units	Accepted input
lotIds	Lot Ids	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
sourceLotIds	Source Lot Ids	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
productIds	Product Ids	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
sourceProductIds	Source Product Ids	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.

Output field	Interpretation	Returned shape
lotMismatches	Lot Mismatches	Required. Safe integer.
productMismatches	Product Mismatches	Required. Safe integer.
jointMatches	Joint Matches	Required. Safe integer.

json

{
  "input": {
    "lotIds": [
      "L1",
      "L2"
    ],
    "sourceLotIds": [
      "L1",
      "L1"
    ],
    "productIds": [
      "P1",
      "P2"
    ],
    "sourceProductIds": [
      "P1",
      "P2"
    ]
  },
  "output": {
    "lotMismatches": 1,
    "productMismatches": 0,
    "jointMatches": 1
  }
}

Limitations and assumptions

Rows are counted without deduplication or source authentication. Matching identifiers alone do not establish physical identity, traceability or safety.
Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Review the complete controlled records, actual product condition and applicable validated procedures. Authenticate sources and approvals rather than treating one matching token or balance as a safety verdict.

References

Calculation and input contract: food-safety/food-lot-identity-gap — tool.io

Similar or alternative tools

Food Sample Parent Batch Identifier
Compare parents literally and serialize source, recorded parent and sample as a JSON-array provenance key.
Food Package Seal Test Record Code
Test code membership and serialize source/code as a JSON-array key.