Understand the updated Classic food catalog

Learn why new and existing BeFit Tracker Classic 7.5 installations can show different food catalogs.

Version 7.5 includes a refreshed USDA-derived food catalog for new installations. Classic protects an existing local database instead of silently replacing it during an update.

For a new installation

When Classic does not find an existing database, it creates its local Application Support folder and installs the bundled 7.5 catalog. Search, charts, folders, and serving calculations then use that local copy.

A selected food in the Classic catalog with calorie, carbohydrate, and protein charts — The bundled catalog is copied locally so browsing, search, details, and charts remain available without a network lookup.

For an existing installation

If Classic finds a database already in use, it keeps that database. Your folders, personal foods, imported products, quantities, and relationships remain together in the existing store. The new bundled catalog is not copied over it automatically.

This difference is intentional.

Replacing the database would also replace customer-created information stored alongside the catalog. Do not delete your existing database merely to obtain a newer catalog.

If you have decided to leave the old library behind and rebuild with the refreshed catalog, follow the dedicated Move from an older BeFit Tracker to Classic guide. That procedure is a complete uninstall and clean start, not an in-place catalog upgrade.

What catalog accuracy means

Classic presents the nutrition values available in its source records. Some foods can have incomplete nutrients or limited serving descriptions. Missing information should not be interpreted as zero, and catalog coverage is not universal.

If you need a food that is missing

Create a food manually in the User Food Library.
Search Open Food Facts and import a compatible product.
Verify nutrition against a reliable label or source before relying on a personal entry.