Mandatory FSSAI License/Registration number to be printed on invoices effective from 1st October, 2021

Section 31 of Food Safety and Standard Act, 2006 requires that every company supplying food products are required to obtain FSSAI license or registration prior to commencement of business. The implementation of the FSSAI Act 2006 and the Rules and Regulations made thereunder depends upon the FSSAI License and Registration number. FSSAI- Order dated 8th June 2021.

Presently, FSSAI number is compulsory to be displayed on packaged food labels. In the case of establishments such as restaurants, sweet Shops, caterers, retail stores, Food Safety Standards (FSS) regulations are being amended to mandate the display of ‘Food Safety Display Boards’ at all times at prominent places in the case of Restaurants. However, there is absence of effective mechanism to know the FSSAl number of the service/ product providers.

So, with the approval of Food Authority, it has been decided to mandatorily mention the declaration of a 14-digit FSSAI License or Registration number on cash receipts/ purchase invoices/cash memo /bills, etc. by all food suppliers effective from 1st October, 2021. When any supplier issues documents such as in the case of transporters issuing transport challan/ Bill etc. and an invoice, then FSSAI number needs to be mentioned on all the documents. Also, Consumers can visit the FSSAI’s portal and ‘Food Safety Connect’ app for accessing information about FSSAI License or Registration by inserting 14 digit FSSAI License/Registration number.

The only exemption from the aforesaid requirements of mentioning 14 digits FSSAI license has been granted to e-way bills underated under GST and such other documents generated from government portals. 

Disclaimer: The purpose of this blog is for education purpose and should not be construed as professional advice. Views expressed herein are the personal views of the author. Government or judicial authorities may or may not subscribe to the views expressed herein. The author of the blog is not liable for any implications arising out of actions taken based on the views expressed herein.