When a barcode result shows a different food: build a mismatch record

If a barcode lookup displays a product that does not match the package in your hand, pause the import. You have a lookup result and a physical package, but you have not yet established that they describe the same item. A convincing photograph or familiar brand name is insufficient on its own.

Compare identity before nutrients

Write down the package's product name, flavor, net quantity, market and printed barcode digits. Next, copy whatever identifying fields the result actually displays. Mark absent fields as unavailable instead of assuming they match. Preserve a screenshot of the result so later corrections can be checked against what you originally saw.

For a fictional example, you scan a 180 g tomato-flavored cracker box and receive a plain 200 g cracker listing. Two identity fields disagree. Do not borrow the plain product's nutrition table just because both packages use the same brand artwork.

Use three match states

A practical note can use confirmed match, confirmed mismatch, and unresolved. Confirmed match means the visible identifying fields agree sufficiently for your specific task; it does not certify the database. Confirmed mismatch records a concrete disagreement. Unresolved means essential identification is missing, even if nothing visibly conflicts.

For the cracker example, write: flavor and pack weight differ; database quantities excluded. If the tool allows manual entry, copy readable quantities directly from the package with that source identified. The FDA overview of the Nutrition Facts label identifies the principal parts of a US nutrition panel; use the appropriate panel as your reference.

Do not silently repair the identity

A manual correction should keep two separate records: the returned database entry and your package transcription. Renaming the database result to the expected flavor without verifying its other fields creates a convincing hybrid that no source actually supports.

If the service provides a correction route, prepare the barcode digits, mismatch description and relevant package images. Send them only through a route you choose to use. Avoid posting a claim that the entire service is inaccurate based on one mismatch; the evidence concerns this result at this time.

When the correct entry becomes available, compare it with your saved package transcription before replacing anything. Retain the earlier mismatch note and a correction date. That makes the update reversible and explains why an old comparison used a different source.