FSMA204 Required Attributes Discrepancies

[nancyVigo]

Good morning team!

I was updating an item in 1WS to include the new FSMA204 requirements and noticed that there are differences from the chart provided after the webinar on March 13th, 2025 to what I currently see in 1WS.  The attributes not mentioned during the webinar that I now see on the website are:  Regulatory Agency, Regulatory Act Compliance Level Code (where I picked "Exempt") and Regulation Community Level Code.

The one I cannot find on the website, which was mentioned during the webinar is:  Regulation Restrictions and Descriptors (NOT_COVERED_BY_FTL or KILL_STEP_APPLIED).

Thanks in advance for your guidance in this matter.

[Val_P]

Hello @Ginny, thank you for the follow-up and information provided.

GTIN 10011140101691 is currently successfully syncing with Sysco Corporation 0074865000000:

If the issue persists on the retailer side, we recommend contacting them for more information, as there does not seem to be an issue with the submitted information from Item Management. Thank you. 

[Ginny]

Thanks for confirming synchronization, we will work with our trading partner to resolve.

Ginny

[Val_P]

Thank you, @Ginny, it is always our pleasure. Just in case they advise you to edit anything and you are unsure how to proceed in our systems, please let us know and we would be delighted to assist where needed. 🙂

[nancyVigo]

@Val_P, good afternoon!

We were able to upload all the FSMA204 attributes using FUSE, except for our Feta (Gtin 10071072008055) because this item is on the FTL list.  As we uploaded the FUSE, it got rejected because we left the Regulation Restrictions and Descriptors Code Value blank.

Can you tell us what is the value that needs to be added so that our customers see it whenever they look at this particular item?

Thanks in advance!

[ana_neamtu]

Hello @nancyVigo,

Thank you for continuing the use of our community!

If the product is subject to the rule, there is no value that should be provided for the Regulation Restrictions and Descriptors field, so both this column and the language column for it (named Regulation Restrictions and Descriptors LANG) should be left blank.

If the item may contain a U.S. FDA Food Traceability List ingredient, but is not subject to the rule, then the Regulation Restrictions and Descriptors values can be:
KILL_STEP_APPLIED
NOT_COVERED_BY_FTL

• For the FUSE file, the following columns would have to be provided for an All Attributes export:
  NYX: Regulation Restrictions and Descriptors > with one of the two codes above
  NYY: Regulation Restrictions and Descriptors LANG > with value "en"

Please don't hesitate to let us know if you have additional questions.

[nancyVigo]

@ana_neamtu, good morning!

We did leave the Regulation Restrictions and Descriptors field, as well as the Language column blank.

This is what caused the FUSE rejection. 

That's why I was reaching out to see what we had to fill out for this particular attribute. 

We are thinking of not using the FUSE if the item is on FTL list. 😉

[Maria]

Hello @nancyVigo. We checked the Item Management but could not find any Fuse File validation error related to this. Also, GTIN 10071072008055 is published to UNFI only, and it is successfully synchronised; on the other hand, there is no Sysco publication. Can you please advise where the Fuse attempt failed? Also, if there is only one GTIN in question that is causing that we suggest not using the FUSE if the item is on the FTL list.

Thank you!

[nancyVigo]

@Maria, please see attached screen shot showing the FUSE rejection because of the FSMA204 attributes for the Feta.  Thanks!

[Val_P · Accepted solution]

Hello @nancyVigo, thank you for the reply and update.

In this case the easier update method would be to add the information in Item Management directly, save, and then publish it to Sysco as needed. Thank you and please let us kow if this helps to synchronize the item with them as intended or if any related issue persists.

[nancyVigo]

@Val_P,  @Maria and @ana_neamtu thanks again for all your help and suggestions!  As always, they are truly appreciated! 🙂