Create a "solver" recipe importer that converts a food label using NCCDB entries.
The biggest conundrum in my Cronometer use for tracking micros is that if you don't track every calorie using NCCDB or USDA db entries, you don't actually know if you've hit your micros, since commercial food labels only have 10-15 micros listed. But if you're not making all your food from raw ingredients, you are forced to use the incomplete food labels.
I've solved this partially by creating my own recipes for foods I consume by using solver functions (or trial and error) based on food labels and the ingredient listings, since ingredient listings are in descending order by weight. With this info, you can reverse-engineer approximate recipes using NCCDB entries and get all 80+ micros in the NCCDB.
The problem is this takes a ton of time for each unique store-bought (or restaurant) item.
Sure would be nice if this feature would be offered natively! I can understand if Cronometer would be hesitant to do this by default since the reverse-engineering is a guess and could be off on actual micros - but by allowing users to click a button (perhaps with a disclaimer that it's just estimated), this would be great - a solver can get very close to matching a food label if it has the food label and the ingredients list.