Research ordinary Uber Eats group-order completion tracking

[CCOSTAN]

Problem

A meeting coordinator uses ordinary Uber Eats group orders for in-person meetings. After selecting a restaurant and sharing the standard group-order link, the coordinator repeatedly opens the organizer view to determine who has submitted an order and manually reminds anyone still pending.

This is repetitive, time-sensitive work that should be reduced if a supported and privacy-safe data source exists.

Constraints

• The workflow uses ordinary Uber Eats group orders, not Uber for Business meal planning.
• Participants must not be asked to self-report completion, visit another page, or take any action beyond the normal Uber Eats ordering flow.
• Do not store or publish client names, attendee identities, email addresses, restaurant choices, order contents, group-order URLs, or payment information.
• Do not store authenticated browser cookies or credentials in a workstation session or a privileged automation runtime.
• Do not scrape or automate the authenticated Uber Eats UI unless a separately approved, isolated browser design and applicable service terms permit it.
• This repository is only the public research tracker. No Home Assistant dashboard, automation, or configuration change is proposed.

Goal

Determine whether ordinary Uber Eats group orders expose a reliable, supported signal for pre-checkout participant completion. If they do, design a private dashboard status such as:

• Lunch setup needed
• Waiting on orders
• Reminder due
• All orders submitted / lunch complete

A private assistant could then summarize the status and prepare or send reminders through an authorized business mailbox, subject to explicit outbound-email policy and audit logging.

Research questions

• Does Uber expose a supported API, webhook, organizer notification, or email signal showing which invited participants have submitted an order before checkout?
• Can organizer emails provide enough structured information without accessing order contents or payment data?
• If the only source is an authenticated organizer page, is there a compliant isolated-browser approach with human takeover and no credentials in the privileged runtime?
• How should a group order be matched to a meeting without storing sensitive order or attendee data?
• What reminder schedule and approval policy would avoid duplicate or premature messages?
• What is the correct fail-closed behavior when status cannot be verified?

Acceptance criteria

• Document the supported data sources and their limitations for ordinary group orders.
• Record a clear go/no-go decision for automatic completion tracking.
• Define the minimum private data model and retention policy.
• Define mailbox authorization, preview/send policy, idempotency, and audit requirements.
• Produce a dashboard and assistant design that does not require additional participant actions.
• If no supported source exists, document that the feature remains manual rather than introducing brittle scraping or participant friction.