10-01-2019 11:56
10-01-2019 11:56
There are some products which, when scanned with FITBIT FOOD LOG UPC CODE READER, returns improper data - wrong product; incorrect calorie count per serving.
Is there anyway to have these issues fixed?
For instance, in the current database, a scan of SEALTEST 4% COTTAGE CHEESE returns the calorie count for the 1% product.
I imagine that someone must be responsible for assuring that these scan results return the proper information? (Or, am I dreaming in technicolor ?)
10-02-2019 10:57
10-02-2019 10:57
Welcome to the Community @ElwyAli. Thanks for the details mentioned.
Note that at this time, barcode scanning is only available for customers using the United States food database. If you use another food database, the barcode scanning option won't work.
Let me know how it goes.
Want to get more active? Visit Get Moving in the Lifestyle Discussion Forum.
10-03-2019 12:28
10-03-2019 12:28
This response does not address the issue that I raised. The point is that there is incorrect data in the fitbit food upc scan database regarding certain foods. My question was : How to fix the errors in FITBIT food database ?
10-04-2019 08:45
10-04-2019 08:45
@ElwyAli Thanks for getting back.
I appreciate your feedback regarding Fitbit database. In this case, you might want to manually add it in our database as mentioned above or as an alternative solution, you could link Fitbit and MyFitnessPal and once your accounts are linked your food will transfer automatically to Fitbit.
You can learn more about it by checking this article in how to link them and this for MyFitnessPal.
I'll be around if you need further assistance. Your understanding is appreciated.
Want to get more active? Visit Get Moving in the Lifestyle Discussion Forum.