Using scanned-package data vs Generic Database -- Which one's more correct?

So I am trying to log some chicken drumstick I got from Costco. I used the barcode scanner (mobile app) on the package and it listed "Kirkland Signature, Fresh Chicken Drumsticks"

  1. Do the macros in the entry above pertain to cooked or raw?
  2. When weighing the package, the result includes the packaging itself as well as the juices. Obviously after cooking it, the weight would change. How can I plan out my meals if I can't accurately weigh the ingredients beforehand?
  3. Does the value include the bone as well?
  4. When comparing the generic "Chicken Drumsticks, Skin Eaten" from the NCCDB, I get different values for the same weight. Why does this happen?

Not really complaining here because I love cronometer but I am confused about the issues above. If anybody could clarify, I'd really appreciate it.

Thank you!


  • Options

    Hi there,

    It's not always clear whether packages list nutrition values for raw or cooked meat - they can choose which they would like to show on the label. I usually compare it with a generic version from NCCDB or USDA to see if the package matches cooked or raw values. NCCDB will always list cooked values for meat, whereas USDA foods will usually have raw or cooked in the name. Based on the comparison, the Kirkland Drumstick nutrition values are for raw chicken.

    The weight of the meat will change after you cook it due to water losses, and there are pros and cons of recording the raw or cooked weight in your diary. For bone-in meats, I prefer to weigh it after it's cooked and use the NCCDB version because nutrient values are given for the edible portion only, and I find it easier to remove the bone after it's cooked to weigh my portion. Vickie has a great suggestion for using the raw weight here:

    When you weigh your food, put the empty container on your food scale, then tare the scale before you put the meat on to weigh it to make sure you are not counting the weight of the package!

    I hope that makes things easier for you! Check out this blog if you want to learn more about getting accurate nutrition data using Cronometer: https://cronometer.com/blog/6-tips-getting-nutrition-data/


    Karen Stark
    As always, any and all postings here are covered by our T&Cs:

  • Options

    @Karen_Cronometer Thank you! It's all clear now. Seems like using NCCDB would be the best option in cases like this.

  • Options

    Thanks for the link to Vickie's tip. I hadn't realized that you could adjust the amount of an entry by calorie count. So much easier than tinkering with the weight until you get calories to match. Alas, the time I'm most interested in raw weight is in recipes, but this trick only works in the diary.

Sign In or Register to comment.