Waitbusters LLC v. Beehub Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: WaitBusters LLC (Virginia)
  • Defendant: BeeHub Inc. d/b/a/ Peppr (Delaware)
  • Plaintiff's Counsel: Yarbrough Wilcox, PLLC
• Case Identification: 2:26-cv-00255, E.D. Tex., 03/27/2026
• Venue Allegations: Venue is alleged to be proper based on Defendant maintaining a regular and established place of business within the Eastern District of Texas.
• Core Dispute: Plaintiff alleges that Defendant's restaurant point-of-sale (POS) systems and related integration services, which aggregate orders from multiple third-party delivery platforms, infringe a patent directed to systems for processing and normalizing disparate electronic order requests.
• Technical Context: The technology addresses operational inefficiencies for restaurants that must manage multiple, often incompatible, online ordering and delivery platforms, each historically requiring its own dedicated hardware.
• Key Procedural History: The complaint alleges that Defendant was notified of the patent-in-suit and its alleged infringement via a letter received on March 10, 2026, prior to the filing of the lawsuit.

Case Timeline

Date	Event
2019-04-10	Priority Date for U.S. Patent No. 11,367,125
2022-06-21	U.S. Patent No. 11,367,125 Issued
2026-03-10	Defendant allegedly received pre-suit notice letter
2026-03-27	Complaint Filed

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 11,367,125 - "Systems and Methods for Processing Electronic Requests"

The Invention Explained

• Problem Addressed: The patent's background section describes the technical problem of restaurants needing to use multiple, separate hardware devices (e.g., tablets) to receive orders from various third-party delivery platforms, which use different and sometimes incompatible data formats. This situation, which the complaint terms "tablet turmoil," is described as inefficient, costly, and a waste of computing resources '125 Patent, col. 1:30-40 Compl. ¶23
• The Patented Solution: The invention proposes a computer-implemented system centered on an "analytic server" that acts as an intermediary. This server is configured to receive a plurality of electronic messages (e.g., online orders) from the different service provider computers, execute an "extraction protocol" to parse and extract the order data from these disparate messages, and generate a single, normalized "machine-readable file." This file is then transmitted to a single merchant computing device, which populates a unified graphical user interface (GUI) displaying all orders in a consistent format '125 Patent, abstract '125 Patent, col. 2:32-43
• Technical Importance: This architecture is presented as a solution to hardware proliferation and data fragmentation at the merchant's location by centralizing the receipt and normalization of order data from heterogeneous sources Compl. ¶28

Key Claims at a Glance

• The complaint asserts at least independent claim 1 Compl. ¶35
• The essential elements of independent claim 1 include:
  • Receiving, by a server from a plurality of service provider computers, a plurality of electronic messages corresponding to a plurality of requests, where each message contains specific order data (e.g., requested item, user identifier, service provider identifier, merchant identifier).
  • Executing, by the server, an extraction protocol to extract the order data from each electronic message.
  • Identifying, by the server, a client computing device associated with the merchant.
  • Generating, by the server, a machine-readable file comprising the extracted order data.
  • Transmitting the machine-readable file to the identified client computing device, which then populates a GUI with the order information.
• The complaint reserves the right to assert additional claims Compl. ¶45

III. The Accused Instrumentality

Product Identification

The Accused Instrumentalities are identified as "Peppr's POS, Kitchen Display System (KDS), and integrations" Compl. ¶36

Functionality and Market Context

The complaint alleges that the accused Peppr system provides direct integrations with third-party delivery platforms, including DoorDash, Uber Eats, and GrubHub Compl. ¶36 This functionality allows restaurant clients to receive and manage orders originating from these multiple, distinct services through Peppr's own cloud-based POS system, rather than relying on separate hardware for each service Compl. ¶36 The complaint includes a screenshot of the Peppr software's "Integrations" dashboard, which displays logos and onboarding options for third-party services like DoorDash, Uber Eats, and GrubHub Compl. p. 12

IV. Analysis of Infringement Allegations

The complaint references a claim chart in "Exhibit 2," which was not provided Compl. ¶37 The following summary is based on the narrative allegations in the complaint.

'125 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving, by a server from a plurality of service provider computers, a plurality of electronic messages corresponding to a plurality of requests...	The Peppr system allegedly receives order data from multiple third-party delivery platforms such as DoorDash, Uber Eats, and GrubHub.	¶36	col. 8:12-16
executing, by the server, an extraction protocol to extract the order data corresponding to each request within each electronic message	The Peppr system is alleged to process incoming messages to extract pertinent order details.	¶24	col. 8:60-67
identifying, by the server, a client computing device associated with the merchant	The system allegedly identifies the specific restaurant's Peppr POS or KDS system to which the order data should be sent.	¶26	col. 9:12-20
generating, by the server, a machine-readable file comprising the extracted order data	Peppr's cloud-based system is alleged to generate a normalized file from the disparate incoming data for its own POS systems.	¶25	col. 9:36-44
transmitting, by the server, the machine-readable file to the identified client computing device, whereby the identified client computing device populates a graphical user interface...	The Peppr system allegedly transmits the processed order data to the restaurant's POS or KDS, which then displays the order details in a unified GUI.	¶26	col. 10:3-10

Identified Points of Contention

• Scope Questions: A central question may be whether the accused system's method for receiving data from partners like DoorDash qualifies as executing an "extraction protocol" on an "electronic message" as contemplated by the patent. The patent specification provides email parsing as an example of the protocol '125 Patent, col. 8:65-67, which may raise the question of whether modern, structured API (Application Programming Interface) data exchanges fall within the scope of this term.
• Technical Questions: The complaint does not specify the underlying architecture of the Peppr system. A key technical question will be whether the accused system actually generates a discrete, intermediate "machine-readable file" that is then transmitted to a client device, as required by the claim, or if it employs a different data-handling architecture, such as direct database writes or real-time data streaming, that might not map to the claimed steps.

V. Key Claim Terms for Construction

• The Term: "extraction protocol"

  • Context and Importance: This term is central to the infringement analysis, as it defines the core action performed by the claimed server on the incoming data. Practitioners may focus on this term because its scope will determine whether the patent covers modern integration methods (like APIs) or is limited to the specific text-parsing methods described in the specification.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The term is not explicitly defined in the patent, which could support an argument that it should be given its plain and ordinary meaning, encompassing any protocol used to extract data from a source.
    • Evidence for a Narrower Interpretation: The specification states that the server "may execute the extraction protocol by parsing the text of electronic messages (e.g., emails) and extracting the order data" '125 Patent, col. 8:65-67 This example could be used to argue that the term is limited to protocols that operate on unstructured or semi-structured text, as opposed to structured data received via a pre-defined API.

• The Term: "electronic message"

  • Context and Importance: The nature of the "electronic message" is a prerequisite for the "extraction protocol." The definition of this term will be critical in determining what kind of data inputs the patent's claims apply to.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The term could be interpreted broadly to mean any form of electronic data transmission between computer systems.
    • Evidence for a Narrower Interpretation: The patent repeatedly uses "emails" as a primary example of electronic messages that are received and parsed '125 Patent, col. 8:46-54 This repeated reference may support a narrower construction limited to file- or text-based communications rather than real-time, structured API calls.

VI. Other Allegations

• Indirect Infringement: The complaint alleges inducement by asserting that Defendant provides instructions and advertises its integration capabilities, thereby encouraging its restaurant customers to use the system in an infringing manner Compl. ¶38 Compl. ¶41 Contributory infringement is also alleged on the basis that the accused components are not staple articles of commerce and are known by Defendant to be especially adapted for use in an infringing system Compl. ¶42
• Willful Infringement: Willfulness is alleged based on Defendant's purported knowledge of the '125 Patent since receiving a letter on March 10, 2026 Compl. ¶40 The complaint further alleges that Defendant's subsequent action of taking down its main website while leaving technical support and login portals active constitutes an attempt to conceal infringement, supporting the willfulness claim Compl. ¶44

VII. Analyst's Conclusion: Key Questions for the Case

• A core issue will be one of definitional scope: can the term "extraction protocol," which is described in the patent with examples of parsing text from emails, be construed to cover the potentially more structured, API-based data exchanges that may be used by the accused modern POS integration system?
• A key evidentiary question will be one of architectural correspondence: does the accused Peppr system's technical implementation align with the specific, sequential steps of the patent's claims-particularly the generation and transmission of an intermediate "machine-readable file"-or does it operate using a fundamentally different data processing architecture that falls outside the literal claim scope?