Waitbusters LLC v. Oracle Corp

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: WaitBusters LLC (Virginia)
  • Defendant: Oracle Corporation (Delaware)
  • Plaintiff's Counsel: Yarbrough Wilcox, PLLC
• Case Identification: 1:26-cv-01955, W.D. Tex., 07/15/2026
• Venue Allegations: Venue is alleged to be proper in the Western District of Texas because Defendant Oracle Corporation maintains its "World Headquarters" and a place of business in Austin, Texas.
• Core Dispute: Plaintiff alleges that Defendant's Simphony Point-of-Sale (POS) systems, which integrate with third-party food ordering platforms, infringe a patent related to aggregating and processing electronic requests from multiple sources.
• Technical Context: The technology addresses the operational challenge in the restaurant industry known as "tablet turmoil," where merchants must use multiple, incompatible devices to manage orders from various online delivery services.
• Key Procedural History: The complaint alleges that Plaintiff provided Defendant with pre-suit notice of infringement via a letter dated March 4, 2026, which was received on March 10, 2026, and to which Defendant allegedly did not respond.

Case Timeline

Date	Event
2016-06-01	WaitBusters LLC founded
2019-04-10	U.S. Patent No. 11,367,125 Priority Date
2022-06-21	U.S. Patent No. 11,367,125 Issued
2026-03-04	Plaintiff sends infringement notice letter to Defendant
2026-03-10	Defendant receives infringement notice letter
2026-07-15	Complaint Filed

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

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

• Patent Identification: U.S. Patent No. 11,367,125, Systems and Methods for Processing Electronic Requests, issued on June 21, 2022.

The Invention Explained

• Problem Addressed: The patent's background section describes the problem of restaurants needing to manage a high volume of electronic orders from multiple, disparate third-party platforms (e.g., food delivery apps) Compl. ¶11 '125 Patent, col. 1:18-43 This requires merchants to own and operate multiple hardware devices, often tablets, each specific to a single platform, creating inefficiencies and wasting computing resources '125 Patent, col. 2:8-16
• The Patented Solution: The invention proposes a centralized "analytic server" that intercepts electronic messages (such as order confirmation emails) from a plurality of service provider computers '125 Patent, abstract The server then executes an "extraction protocol" to parse these messages, extract key order data, 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 consolidated format '125 Patent, col. 2:32-43 '125 Patent, Fig. 1B
• Technical Importance: This approach aims to eliminate the need for multiple dedicated hardware devices at the merchant's location, thereby streamlining order management, reducing costs, and improving operational efficiency Compl. ¶29

Key Claims at a Glance

• The complaint asserts at least independent claim 1 Compl. ¶35
• The essential elements of independent claim 1, a method claim, include:
  • Receiving, by a server from multiple service provider computers, a plurality of electronic messages corresponding to requests, where each message contains order data (including a requested item, user ID, service provider ID, and merchant ID).
  • Executing, by the server, an "extraction protocol" to extract the order data from each message.
  • Identifying, by the server, a client computing device associated with the merchant.
  • Generating, by the server, a "machine-readable file" containing the extracted order data.
  • Transmitting the machine-readable file to the identified client device, causing it to populate a GUI that includes an indicator for the requested item and an indicator for the service provider.
• The complaint reserves the right to assert other claims Compl. Prayer for Relief ¶a

III. The Accused Instrumentality

Product Identification

• The Accused Instrumentalities are "Oracle's Simphony POS and Kitchen Display System (KDS), and integrations" Compl. ¶36

Functionality and Market Context

• The complaint alleges that Oracle's Simphony system is a cloud-based POS solution that provides direct integrations with various third-party delivery platforms, including DoorDash and Uber Eats Compl. ¶36 Oracle allegedly advertises that its system is built on a "cloud-based open API framework with more than 200 integration partners," giving restaurants the ability to tailor the platform Compl. ¶38 This functionality is alleged to enable a single Oracle system to manage orders from multiple, otherwise incompatible, third-party services, addressing the "tablet turmoil" problem depicted in the complaint's explanatory graphic Compl. ¶21 The graphic illustrates the problem of "#TabletTurmoil," showing multiple tablets from services like Grubhub, DoorDash, and Uber Eats, and presents "WAITBUSTERS" as the alternative single-tablet solution Compl. ¶21

IV. Analysis of Infringement Allegations

The complaint references a claim chart in Exhibit 2, which was not attached to the filed document Compl. ¶37 Therefore, the infringement allegations are summarized below in prose based on the narrative of the complaint.

The complaint alleges that Oracle's Simphony POS system directly infringes at least claim 1 of the '125 Patent Compl. ¶36 The theory of infringement suggests that the Simphony system, when integrated with third-party ordering platforms, performs the patented method. The Simphony server allegedly "receives" data from multiple platforms like DoorDash and Uber Eats (the "plurality of service provider computers") Compl. ¶36 It is alleged to then process this data, which corresponds to the patented step of "executing an extraction protocol", to create a unified data set Compl. ¶¶24-25 This unified data is then allegedly used to "generate" a "machine-readable file" that is "transmitted" to the restaurant's Simphony POS terminal (the "client computing device") to "populate a graphical user interface" with order details from all integrated sources Compl. ¶26

• Identified Points of Contention:
  • Scope Questions: A central dispute may concern the scope of the term "extraction protocol." The patent describes this protocol in the context of parsing text from electronic messages like emails to extract data '125 Patent, col. 8:59-67 The question will be whether this term can be construed to cover the accused system's alleged use of a modern "open API framework" Compl. ¶38, which typically involves structured data exchange rather than parsing unstructured text.
  • Technical Questions: The infringement analysis may turn on the specific technical operation of the Simphony system. What evidence demonstrates that it sequentially "generates" and then "transmits" a discrete "machine-readable file" as recited in the claim, as opposed to using a continuous data stream or another API-based data handling method that may not map to the claim's specific steps? The complaint does not detail the inner workings of Oracle's system.

V. Key Claim Terms for Construction

• The Term: "extraction protocol"

• Context and Importance: This term is central to how the patented system processes data from disparate sources. Its definition will be critical for determining whether Oracle's API-based integration method infringes. Practitioners may focus on this term because the patent's primary embodiment describes parsing text from emails, which may be argued to be technically distinct from an API call.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: Parties advocating for a broader meaning might point to the general description of the protocol's function-"to extract the order data corresponding to each request within each electronic message" '125 Patent, cl. 1-arguing that this functional language is not limited to a specific implementation like email parsing.
  • Evidence for a Narrower Interpretation: Parties advocating for a narrower meaning may cite the specification's detailed description, which states the server may "execute the extraction protocol by parsing the text of electronic messages (e.g., emails) and extract the order data details" '125 Patent, col. 5:56-61 '125 Patent, col. 8:65-67 This may support an argument that the term is limited to methods involving text parsing, not structured API data exchange.

• The Term: "machine-readable file"

• Context and Importance: The claim requires "generating" this file and then "transmitting" it. Whether the accused system creates a distinct "file" as understood in the art, or simply processes a data stream, will be a key infringement question.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: A broader view could argue that any structured collection of data transmitted between systems, even if transient, constitutes a "machine-readable file." The patent's focus is on data normalization, not a specific file format.
  • Evidence for a Narrower Interpretation: The sequential claim language-"generating... a machine-readable file" and then "transmitting... the machine-readable file"-suggests a two-step process involving the creation of a discrete data object before its transmission. This could be used to argue against infringement by systems that process and forward data in a continuous stream without creating an intermediate, standalone file.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement, stating that Oracle actively encourages infringement by providing customers with detailed instructions on how to connect the Simphony system to third-party platforms like DoorDash and Uber Eats Compl. ¶38 Compl. ¶42 It also alleges contributory infringement, asserting the accused components are material to the invention, not staple articles of commerce, and are known by Oracle to be especially adapted for infringement Compl. ¶43
• Willful Infringement: The willfulness allegation is based on alleged pre-suit knowledge. The complaint states that Plaintiff sent a notice letter detailing the infringement on March 4, 2026, which Oracle received on March 10, 2026, giving Oracle knowledge of the patent and its alleged infringement prior to the lawsuit's filing Compl. ¶41 Compl. ¶45

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

This dispute appears to center on the intersection of claim language drafted around an earlier technological context (e.g., email parsing) and the functionality of a modern, API-driven system. The key questions for the court are likely to be:

• A core issue will be one of definitional scope: Can the claim term "extraction protocol," described in the patent with examples of parsing text from emails, be construed broadly enough to encompass the structured data exchange performed by the accused system's "open API framework"?
• A key evidentiary question will be one of technical implementation: Does the Oracle Simphony system in fact perform the discrete, sequential method steps of "generating" a "machine-readable file" and then "transmitting" it, as required by Claim 1, or does its API-based architecture operate in a way that is technically distinct from the claimed method?
• A third question concerns willfulness: Assuming infringement is found, did Oracle's alleged failure to respond to the pre-suit notice letter, combined with its continued alleged infringement, constitute the kind of egregious conduct necessary to support an enhancement of damages?