FSSAI complaint register requirements for Indian restaurants

The Food Safety and Standards Authority of India (FSSAI) requires food business operators to maintain a consumer complaint register as part of their food safety management system. Under the Food Safety and Standards (Food Safety Management System) Regulations, licensed food businesses are required to have a documented procedure for handling consumer complaints and to maintain records of all complaints received.

The complaint register must be available for inspection by FSSAI food safety officers during scheduled and surprise inspections. For food safety complaints specifically — complaints involving foreign objects in food, allergic reactions, or suspected food contamination — FSSAI guidelines require that the incident be documented with full details and that the root cause investigation be completed and recorded.

The four severity levels and what they require

• Critical — food safety incidents. Foreign objects in food (glass, metal, plastic, insect), suspected food poisoning, allergic reaction to undeclared allergens, food contamination. These require: immediate escalation to senior management, isolation of the affected batch if it is still in service, documentation of the full incident, and FSSAI notification if health impact is confirmed. Do not attempt to resolve critical food safety incidents at the waiter level.
• High — significant quality or service failures. Severely undercooked or overcooked food, major billing errors, aggressive or inappropriate staff behaviour, serious cleanliness complaints. Require manager intervention during the same visit, likely compensation, and a follow-up with the guest. All high-severity complaints must be investigated for root cause within 24 hours.
• Medium — general dissatisfaction. Cold food, long wait times, incorrect order, below-expectation quality. Can often be resolved with prompt service recovery — a remake, a discount, or a sincere apology from the floor captain. Document the complaint and the service recovery action taken.
• Low — minor feedback. Preference-based feedback (“slightly too spicy”), ambiance feedback, minor suggestions. These are valuable for continuous improvement and should be logged, but do not require formal escalation. Review these monthly to identify patterns.

How to use complaint patterns to improve operations

The most valuable output of a complaint register is not the resolution of individual complaints — it is the pattern that emerges across complaints over time. A restaurant that receives three complaints about slow service on Friday evenings has identified a staffing or kitchen throughput problem. A restaurant that receives repeated complaints about a specific dish has identified a recipe or training problem. A restaurant that receives complaints primarily from online orders has identified an aggregator packaging or temperature retention problem.

Review the complaint register in your monthly management meeting. Look for: the top three complaint types by volume, any complaints of High or Critical severity that remain unresolved, any complaint type that has increased month on month, and any complaint with a root cause and corrective action that has not yet been implemented. The corrective action column is only useful if someone is accountable for implementation and if implementation is verified.

Where this fits

• Food safety checklist — daily FSSAI hygiene log; complement the complaint register with proactive safety checks
• Incident & accident report — for critical food safety incidents that require a detailed separate record
• Refrigeration temperature log — food safety complaints often trace back to temperature control failures
• Allergen menu matrix — allergen complaints are critical severity; a complete allergen declaration prevents them
• Compliance calendar 2026 — track FSSAI inspection dates and renewal deadlines alongside complaint records
• P5 — Compliance pillar — complete guide to FSSAI licence, food safety regulations, and compliance for Indian restaurants