Active/Inactive Restaurant (Group Landing Page)

Release Target: After DIY release (Sept 4) → Start Sept 5, completion by Sept 12

Feature Overview

This feature introduces the ability to display inactive restaurants on a group landing page. By default, only active restaurants are shown. With this enhancement, Admins and certain flows can view inactive restaurants for operational purposes, with clear filtering and UI controls to avoid ambiguity.

Problem Statement

Currently, HungryHub’s Group Landing Page only displays active restaurants. Inactive restaurants are completely hidden and non-searchable. This creates issues when:

• Admins or partners need to reference or manage inactive restaurants within group landing page → e.g. Katsu Midori Restaurant.

Goals and Objectives

• Clarity: Provide a clear and unambiguous way to filter active vs inactive restaurants.
• Flexibility: Support business requirements for displaying limited inactive restaurants.
• Consistency: Ensure Group Landing Page filtering matches HH-search logic (with extended support for inactive data).
• Efficiency: Deliver feature within 4–5 days development cycle, balancing parallel workstreams (e.g., "free refund guarantee" task delay if needed).

User Stories, Scope, and Design

• As an Admin, I want to show the Group Landing Page by Active Restaurant Only (default) or Inactive Restaurant Only, so that I can easily manage restaurants based on their status.
• As an Admin, I want explicit dropdown options instead of a vague checkbox, so that filtering feels intuitive and avoids confusion.
• As a Customer, I should never encounter inactive restaurants in the search flow, ensuring no broken booking experiences. Implementation Scope:
• Must-have:
  • Dropdown filter with clear options:
    • Active Restaurants Only (Default)
    • Inactive Restaurants Only
    • All Restaurants (Active + Inactive)
  • Group Landing Page fetches inactive restaurant data from HH-search → Need BE
  • Inactive restaurants remain non-searchable.
  • Show inactive restaurants but with some active settings here (would be faster performance if can narrow down the restaurant list). one of this setting must be active:
    • Allow booking
    • Allow booking without package Design Considerations:
• Use Show Restaurant List dropdown for clarity instead of using Show Inactive Restaurant Only checkbox → Avoid ambiguous language
  • The checkbox option Show Inactive Restaurant Only (unticked by default) introduces bias/ambiguity for users and creates confusion in filtering logic. A checkbox suggests adding or removing something from the current view, but here it’s actually being used as a mode switch. This mismatch leads to uncertainty:
    • When Unticked (default): The label implies inactive restaurants are hidden, but users might still wonder:
      • Does unticking mean displaying only active restaurants?
      • Or does it mean displaying both (active restaurant + inactive restaurant)?
• Default option = Active Restaurant Only.

• Ensure accessibility: keyboard and screen reader support.

Timeline / Duration

• Start Date: Sept 5 (post DIY release, Sept 4). But, ideally will start in the next week (just in case QA has found any issue or feedback)
• BE: 2–3 days
• FE: 1 day
• HH-search: 1 day
• Total Duration: 4–5 days
• Target Completion: Sept 12 (Week 2 of sprint).

Dependencies / Notes

• HH-search currently only contains active restaurants. Must extend schema/index to include inactive restaurants.
• Free Refund Guarantee rollout may be deprioritized/delayed.