Purpose

This article walks through the HFSS Compliance feature for Spoonfed.
 

HFSS Feature  Overview

The HFSS Compliance feature enables 365 catering platform to comply with UK regulations restricting the advertising of foods high in fat, sugar, and salt (HFSS). (This feature is limited to UK customers only.)

HFSS information can be provided through supported nutrition integrations, such as Kafoodle or 365 Kitchen Management (KM) Nutritics, or via Nutritiics if the infromation is provided from the Nutritics side or maintained manually when external HFSS information is unavailable.

365 Catering displays the HFSS information provided by the caterer or integrated nutrition system. It does not calculate, determine, or enforce HFSS compliance.

This allows catering teams to consider HFSS information when managing menus, promotions, and marketing content while keeping responsibility for compliance decisions with the customer.
 

This feature allows caterers to:

• classify menu items as HFSS or non-HFSS.
• give a disclaimer to restrict HFSS items in marketing campaigns.
   

Business value:

• Avoids fines and reputational risk for caterers.
• Provides safer menu experiences for end consumers.
• Positions the SaaS platform as compliance-ready and premium.
   

Important Considerations

HFSS information should be treated as customer-provided or source-system-provided information.

365 Catering does not independently validate, calculate, or determine HFSS status. Customers should therefore ensure that information received from integrated nutrition systems or entered manually is accurate and reflects their compliance requirements.

The HFSS information is advisory only and does not enforce compliance.
 

Scope

1. HFSS item identification: Menu-level, category-level, and item-level HFSS visibility controls.
    
2. The intent is to help a catering business position which menu items are HFSS (using the Government’s nutrient profile model), it can support compliance. The obligations fall on the businesses using the platform to sell, market, or present HFSS content.
    
3. Spoonfed publishes content to websites/online ordering platforms that function like online retail (e.g. menus with checkout or order pages), the caterer is responsible for compliance with HFSS placement and promotion rules when that content includes HFSS products.
    

Impacted Customers

Value to the User:

For the caterer, it avoids regulatory fines, maintains brand reputation, and confidently markets menus knowing HFSS items are correctly flagged and restricted. 
For the end consumer, it ensures safer menu choices, protects minors from unhealthy food advertising, and provides a transparent ordering experience.
 

Value to 365 Catering/Spoonfed:

Differentiates the platform as compliance-ready, attracts premium/corporate clients, reduces legal risk, and adds value by offering built-in regulatory tools that competitors may lack.
 

Key Requirements

HFSS Classification Engine

• Calculate HFSS score using UK Nutrient Profiling Model.
   
• Support:
  • Food HFSS threshold
  • Drink HFSS threshold
     
• Persist:
  • HFSS score
  • HFSS status (HFSS / Non-HFSS)
  • Source of classification (Auto / Manual)
     

Auto Classification (Nutrition Integration)

HFSS information can be received when a menu item is synchronized from a supported nutrition system (i.e., Kafoodle / 365 KM or Nutritics → Menu Item → 365 Catering). The exact HFSS information provided by the nutrition system may vary by integration.

• Ingest nutritional data from the integration source.
  • 365 Catering stores and displays the information as provided by the source.
     
• Trigger HFSS scoring automatically on import/update.
   
• Handle incomplete data gracefully:
  • Mark as Unclassified if required fields missing.
  • Prompt for manual classification.
     

Scenario 1: HFSS Items Only

If the nutrition system sends HFSS information only for items classified as HFSS:

• 365 Catering treats the presence of HFSS information as an indication that the item is HFSS.

• The received HFSS status and score are stored.

• The information is displayed to users.

365 Catering does not independently verify the classification.
 

Scenario 2: HFSS Information for All Items

If the nutrition system provides HFSS information for all menu items:

• 365 Catering displays the status provided by the source system.

• The provided score is displayed or stored as received.

• 365 Catering does not evaluate the score against HFSS thresholds.

• 365 Catering does not independently determine whether an item should be classified as HFSS.

In both scenarios, classification responsibility remains with the nutrition system and the customer.
 

Manual Classification

If HFSS information is not available through an integration, a customer can manually maintain the information on the menu item. The manually entered information is stored as provided by the user. 365 Catering does not calculate or validate the score.
 

• Allow users to:
  • override HFSS status.
  • enter HFSS score manually.
  • enter or adjust nutrient values.
     
• Manual overrides take precedence over auto-classification.
   
• UI must clearly show:
  • Auto vs Manual status.
  • last updated timestamp.
     

HFSS Visibility

• HFSS label visible on:
  • Item detail pages.
  • Menu item lists.
  • Promotion configuration screens.
     
• Clear visual distinction (e.g. badge or icon).
   

Banner & LTO HFSS Disclaimers

• Detect HFSS items included in banners/LTOs.
   
• For UK clients only:
  • Display a disclaimer message during creation.
  • Display disclaimer on published LTO page.
     
• Disclaimer must:
  • Be informational.
  • Not block publishing.
  • Reference HFSS advertising considerations.
     

Process

Caterer Setup

To set up HFSS compliance, the Caterer performs the following procedures in Back Office Admin.
 

Item Creation / Import

1. Caterer imports food items from Kafoodle. 
    
2. System ingests nutritional data.
    
3. System automatically:
   1. Provides HFSS score using UK Nutrient Profiling Model
   2. Labels item as HFSS or Non-HFSS
       
4. HFSS status is visible on the item detail page.
    

Manual Classification

1. Caterer views an item with missing or incorrect HFSS data.
    
2. Caterer selects Edit HFSS Classification.
    
3. Caterer:
   1. manually marks item as HFSS or Non-HFSS.
   2. optionally enters or edits HFSS score / nutrient values.
       
4. System:
   1. saves manual override.
   2. records source as Manual.
       
5. HFSS status updates across menus and promotions.
    

Banner / LTO Creation

1. Caterer creates a banner or LTO page.
    
2. Caterer selects products or menus to feature.
    
3. System checks HFSS status of included items.
    
4. If HFSS items are present:
   1. System displays a non-blocking HFSS disclaimer.
   2. Disclaimer appears on the banner/LTO creation screen. HFSS functionality is advisory and does not enforce compliance:
      This offer may include foods or drinks that are high in fat, sugar or salt. There are UK rules around promoting or discounting these items online. You can still publish this promotion, but please check the rules before using it in limited-time offers.
       
5. Caterer can proceed without restriction.
    

End Consumer/Client Journey

HFSS information is displayed when users manage menu items. Users can use the information to identify which products have been classified as HFSS.

For integrated menu items, the HFSS type and score reflect the information received from the nutrition system.

For manually maintained items, the information reflects the values entered by the customer.

365 Catering does not automatically recalculate or change the HFSS classification.
 

1. User visits the catering platform (web or mobile).
    
2. Browses menus:
   1. HFSS items may be hidden by the caterer for promotions/banners.
   2. Non-HFSS items visible with photos, descriptions, and pricing.
       
3. Adds items to cart and submits order.
    
4. Checks out normally, with HFSS restrictions enforced by the caterer.
    
5. Receives confirmation.