When an item in the database lacks a specific nutritional value (e.g., Vitamin C or Potassium), Chomp strictly prohibits data imputation.
The system does not attempt to estimate or fill in a food item's missing information using data from a "similar" food item.
Operating under the principle that accurate, sparse data is significantly safer than complete, estimated data, this policy prevents the spread of misinformation and ensures that all values returned by the API are explicitly verified against the product's actual nutritional profile.
If your application requires a fallback for missing values, that logic must be implemented locally within your codebase.