topic USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code and a in Ask a Question for USDA & FNS

USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code and a

foodingredients — Tue, 12 Sep 2023 14:14:57 GMT

Hello,

I'm struggling with the following error (USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code and at least one instance of BY_MEASURE.) I've updated the case level to have nutritional information by 100 ml and I'm still getting the error. I'm hoping someone can point me in the right direction.

So far I've only done it at the EA level, do I need to do it at each level? Here is an example of a sku I'm struggling with 50027000737304.

Thanks

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

jcharles — Tue, 12 Sep 2023 15:44:17 GMT

Hi Melanie,

I can see the issue and you would need to address the issue on the EACH. The case would not provide that for the consumer unit. Pretty much anything that goes to the register to be scanned will need this information.

Have you corrected and submitted back to them with that correction?

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

hilld3 — Wed, 27 Sep 2023 13:55:07 GMT

We have the same issue with USDA, it will give you a warning as stated above but when you publish it, you get a validation error and will not let you publish to them.

I also have an issue with using by-measure just for USDA because on all of our products we use by-serving. Is there any way to do both in IM? I know I can add an extra panel for the nutrient basis type code but is there a way to enter the by-measure values for the nutrient code and percentage of daily value intake?

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

DanV — Wed, 27 Sep 2023 15:14:20 GMT

Hello hilld3,

You can add another set of Nutrition Facts in IM, simply click the + to the right of the Nutrient Basis Qty Type Unit of Measure (in the screenshot below)

This will add a second instance below the existing instance, so you'll need to scroll down a bit to see it but you will be able to enter values based on a Nutrient Basis Qty Type of By Measure

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

hilld3 — Wed, 27 Sep 2023 15:18:07 GMT

i got that, but wouldn't the nutrient type code and percentage of daily value intake will also have to be calculated by measure?

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

DanV — Wed, 27 Sep 2023 15:27:31 GMT

That is correct, all Nutrient values would need to be based on By Measure

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

hilld3 — Wed, 27 Sep 2023 15:42:20 GMT

but can I have by serving and by measure on the same GTIN with the appropriate values for the nutrient type code and the percentage of daily value intake? If so, how can this be done in 1WS? Other customers are using by serving and USDA wants by measure for the same product.

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

DanV — Wed, 27 Sep 2023 15:57:37 GMT

Yes you can have by serving and by measure on the same GTIN, you would just need to calculate appropriate values for each

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

foodingredients — Wed, 04 Oct 2023 20:39:06 GMT

Sorry, somehow I missed this response. I have it by serving and by measure on the EA and I'm still getting this error. Here is an example - 00027000690659. I'm guessing I'm still missing something.

Thanks

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

Julie — Wed, 04 Oct 2023 21:01:49 GMT

Hello @foodingredients and thank you for reaching out!

I have verified your item and you have at least one instance of BY_MEASURE for attribute Nutrient Basis Type Code. However, if I look at the dates from the Sync Status report I see that you have not received an updated CIC (last received on the 23rd of August) from USDA after the item was last modified (7th of September):

Current Status Date SENT TO SUBSCRIBER 07-SEP-2023 11:05:38

Last CIC State Date REVIEW---23-AUG-2023 11:04:3

I would recommend reaching out to them for additional information regarding an updated CIC. I have attached their implementation guide where you can find their contact information: USDA Implementation Guide. Please let me know if there is anything else I can help with.

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

hilld3 — Wed, 04 Oct 2023 21:06:01 GMT

thank you

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

foodingredients — Fri, 27 Oct 2023 19:50:46 GMT

Hello Julie,

I see that I've received an updated sync status from a few skus Oct 13th and yet I'm still getting those errors. I also tried emailing them and haven't heard back. Any other thoughts?

Does this GTIN look correct 00027000690659?

Thanks

Annette

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

CommunityJedi22 — Fri, 27 Oct 2023 20:52:43 GMT

Hello @foodingredients and thanks for reaching out. I see GTIN 00027000690659 is part of multiple hierarchies with varying parents. Can you tell me which hierarchy is encountering these errors?

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

foodingredients — Wed, 08 Nov 2023 16:45:55 GMT

Sorry - here is the hierarchy - 50027000690043.

Thanks

Re: USDA1355 WARNING For Consumer units, it is recommended to provide the Nutrient Basis Type Code a

JustinW — Wed, 08 Nov 2023 18:00:05 GMT

Hello, @foodingredients. I just wanted to reach out and let you know we are currently looking into the items sent on the 13th of October. We will be reaching out with an update shortly. Thanks.