Skip to content

Settings and activity

3 results found

  1. 16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Rayan Daroowalla supported this idea  · 
  2. 20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Rayan Daroowalla supported this idea  · 
  3. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Rayan Daroowalla commented  · 

    Clover Dining prompts servers to enter a guest count every time a new table is opened, and this data is confirmed to be collected and stored by Clover. However, this information is completely inaccessible — it does not appear in any dashboard report, CSV export, or REST API response, making it impossible for restaurant operators to track covers served, calculate average check per cover, or use this data in any meaningful way. For a foundational restaurant metric that Clover is actively collecting, the total absence of any way to retrieve it is a significant gap that directly impacts our ability to run our business. Cover count / guest count is something that needs to be implemented in the reporting end; it is just frustrating as this is not that complex.

    Rayan Daroowalla supported this idea  ·