4:26-cv-00381
Ecomm Innovations LLC v. Levi Strauss & Co
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: eComm Innovations, LLC (Georgia)
- Defendant: Levi Strauss & Co. (Delaware)
- Plaintiff's Counsel: DAIGNAULT IYER LLP
- Case Identification: 4:26-cv-00381, E.D. Tex., 04/14/2026
- Venue Allegations: Venue is alleged to be proper in the Eastern District of Texas because Defendant Levi Strauss & Co. maintains multiple regular and established places of business (retail stores) in the district, transacts business in the district, and has committed alleged acts of patent infringement in the district.
- Core Dispute: Plaintiff alleges that Defendant's e-commerce websites and mobile applications infringe a portfolio of eight patents related to dynamic web page layout and social network-enabled systems for collecting and syndicating user reviews.
- Technical Context: The patents address foundational e-commerce technologies for creating responsive web layouts that adapt to different screen sizes and for managing the authenticity and relevance of user-generated product reviews.
- Key Procedural History: Plaintiff alleges it sent Defendant a notice letter and draft complaint on September 22, 2025, followed by subsequent communications on October 14, 2025, and January 14, 2026, putting Defendant on notice of the alleged infringement.
Case Timeline
| Date | Event |
|---|---|
| 2004-11-16 | Priority Date for U.S. Patent Nos. 7,409,635 and 7,765,470 |
| 2004-12-23 | Priority Date for U.S. Patent Nos. 7,657,458; 7,752,081; 7,761,343; 7,822,646; 7,881,975; and 8,266,007 |
| 2008-08-05 | U.S. Patent No. 7,409,635 Issued |
| 2010-02-02 | U.S. Patent No. 7,657,458 Issued |
| 2010-07-06 | U.S. Patent No. 7,752,081 Issued |
| 2010-07-20 | U.S. Patent No. 7,761,343 Issued |
| 2010-07-27 | U.S. Patent No. 7,765,470 Issued |
| 2010-10-26 | U.S. Patent No. 7,822,646 Issued |
| 2011-02-01 | U.S. Patent No. 7,881,975 Issued |
| 2012-09-11 | U.S. Patent No. 8,266,007 Issued |
| 2025-09-22 | Plaintiff sends notice letter and draft complaint to Defendant |
| 2025-10-14 | Plaintiff sends follow-up email to Defendant |
| 2026-01-14 | Plaintiff sends second follow-up email to Defendant |
| 2026-04-14 | Complaint Filed |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 7,409,635 - "Display/Layout Methods and Apparatuses Including Content Items and Display Containers," Issued Aug. 5, 2008
- The Invention Explained:
- Problem Addressed: The patent's background section describes how conventional web publishing technologies struggled to dynamically lay out content of different sizes on web pages without causing "unacceptable layout effects, such as overlapping of content items, internal wasted space, unreadable text, and so forth" '635 Patent, col. 1:25-33 Fixed-width designs also failed to use the full "real estate" of larger browser windows, while scrolling mechanisms for overflow content were clumsy '635 Patent, col. 1:34-59
- The Patented Solution: The invention is a processor-implemented method for generating a web layout automatically. It operates by iteratively forming an "inner-outer display entity pair"-pairing a content item with a potential display container-and then evaluating that placement against "layout placement criteria" (e.g., rules for fit and space utilization) '635 Patent, col. 16:20-35 This rule-driven, generative process builds the layout step-by-step, avoiding the rigidity of predefined templates and allowing flexible accommodation of different-sized content '635 Patent, col. 5:43-49
- Technical Importance: This approach provided a method for creating responsive web designs that could automatically adapt to various screen sizes and dynamic content, a key challenge in the evolution of web development.
- Key Claims at a Glance:
- The complaint asserts infringement of at least independent Claim 1 Compl. ¶122
- Claim 1 of the '635 Patent breaks down into the following essential elements:
- A processor implemented method for automated layout of a plurality of content items, comprising:
- forming by a layout generator operated by a processor, an inner-outer display entity pair having an inner display entity and an outer display entity, the outer display entity being a display container, and the inner display entity being a selected one of one of said content items and another display container;
- accepting or rejecting placement by the layout generator of the inner display entity into the outer display entity based at least in part on one or more layout placement criteria; and
- repeating said forming and said accepting or rejecting at least one other time if layout of the content items is incomplete and another inner-outer display entity pair can be formed.
- The complaint does not explicitly reserve the right to assert dependent claims.
U.S. Patent No. 7,657,458 - "Vendor-Driven, Social-Network Enabled Review Collection System and Method," Issued Feb. 2, 2010
- The Invention Explained:
- Problem Addressed: The patent addresses the lack of trustworthiness in online review platforms, noting that "many internet reviews cannot be fully trusted because sellers or affiliated persons often post biased or fake reviews" '458 Patent, col. 1:37-41 This "status quo" of accepting unverified reviews "invites fraudulent negative reviews by competing merchants, as well as fraudulent positive reviews" '458 Patent, col. 10:17-25
- The Patented Solution: The patent proposes a "vendor-driven, social-network enabled review collection system" that uses a unique "locator code" to verify that a review corresponds to a real transaction '458 Patent, cl. 1 This code, stored in a database, acts as an authenticity token. When a customer uses the code on the review system's website, the system retrieves transaction-level information and presents a specific review form, ensuring only bona-fide customers can submit reviews tied to actual purchases '458 Patent, col. 7:60-67 '458 Patent, col. 16:1-17 The system also integrates a social network to help filter and rank reviews based on the reader's social connections '458 Patent, Fig. 1
- Technical Importance: This system provided a technical framework for verifying the authenticity of user-generated reviews, a foundational problem for establishing trust in e-commerce and online communities.
- Key Claims at a Glance:
- The complaint asserts infringement of at least independent Claim 1 Compl. ¶130
- Claim 1 of the '458 Patent breaks down into the following essential elements:
- An apparatus, comprising:
- a database that contains reviews and reviews information, locator code information, subject information, and user information; and
- a computer system configured to instantiate a review engine server that provides a first information to a user and receives a second information from said user and stores at least some of the second information in the database, wherein said first information includes at least a review form, and said second information includes at least a locator code, and further wherein said locator code references a unique transaction.
- The complaint does not explicitly reserve the right to assert dependent claims.
Multi-Patent Capsules
U.S. Patent No. 7,752,081, "Social-Network Enabled Review System with Subject-Owner Controlled Syndication," Issued July 6, 2010
- Technology Synopsis: This patent, a continuation of the '458 Patent, addresses the challenge of allowing merchants ("subject-owners") to control how their product reviews are selected and presented on third-party sites while preserving credibility Compl. ¶68 The solution is a computer-controlled method where a review-provider server applies subject-owner-controlled functions and filters to reviews before syndicating them Compl. ¶¶69-70
- Asserted Claims: At least Claim 1 Compl. ¶136
- Accused Features: The Levi's review system, allegedly operated by Levi's as the subject-owner to select, control, and send reviews for presentation to users Compl. ¶¶137-141
U.S. Patent No. 7,761,343, "Social-Network Enabled Review System with Subject Identification Review Authoring Form Creation," Issued July 20, 2010
- Technology Synopsis: This patent, also a continuation of the '458 Patent, claims a detailed method for verifying review authenticity by linking reviews to transactions Compl. ¶76 The claimed method involves receiving a locator code, determining the product ("subject") from the code, preparing and sending a customized review form, and then receiving, creating, marking, and storing the review in a database Compl. ¶77
- Asserted Claims: At least Claim 1 Compl. ¶145
- Accused Features: The Levi's review submission system, which is alleged to receive a locator code (e.g., an order ID), identify the product, prepare a review form, and process the submitted review by creating, marking, and storing it Compl. ¶¶146-153
U.S. Patent No. 7,765,470, "Display/Layout Methods and Apparatuses Including Content Items and Display Containers," Issued July 27, 2010
- Technology Synopsis: This patent, a continuation of the '635 Patent, claims a specific apparatus architecture for automated web layout, rather than a method Compl. ¶84 The invention comprises a processor with distinct modules: a "display pair formation module" for pairing content items with containers, and an "acceptance or rejection module" for evaluating those placements against layout criteria, thus avoiding rigid templates Compl. ¶¶84-85
- Asserted Claims: At least Claim 1 Compl. ¶157
- Accused Features: The Levi's System, alleged to comprise a processor and modules (e.g., CSS layout and rendering engines) that form display pairs (e.g., HTML blocks) and accept or reject placements based on layout criteria like aspect ratio and media rules Compl. ¶¶158-160
U.S. Patent No. 7,822,646, "Social-Network Enabled Review System with Subject-Owner Controlled Syndication Management," Issued Oct. 26, 2010
- Technology Synopsis: This patent, a continuation of the '458 Patent, addresses the challenge of syndicating review content to third-party websites while preserving authenticity Compl. ¶91 The solution is a multi-server architecture where a third-party server delivers a client-side script to a user's computer, which then triggers a separate request to a review-provider server that selects and returns the appropriate reviews Compl. ¶92
- Asserted Claims: At least Claim 1 Compl. ¶164
- Accused Features: The Levi's system, which allegedly uses a review-provider server (Bazaarvoice) that receives review requests triggered by a client-side script delivered from a third-party server (Levi's own website) Compl. ¶¶165-168
U.S. Patent No. 7,881,975, "Methods and System Using Client-Side Scripts for Review Requests," Issued Feb. 1, 2011
- Technology Synopsis: This patent, also a continuation of the '458 Patent, discloses a networked architecture for delivering personalized, third-party review content (Compl. ¶¶98; Compl. ¶102). A primary web server delivers page content along with an embedded client-side script; this script then initiates a separate data fetch from a review-provider's server, which can use data from the request (e.g., a cookie) to personalize the reviews returned '975 Patent, col. 13:15-32
- Asserted Claims: At least Claim 1 Compl. ¶172
- Accused Features: The Levi's System, which allegedly employs a networked server (levi.com) that provides content and a client-side script to a user's computer, which then executes the script to request reviews from a separate review-provider server (Bazaarvoice) Compl. ¶¶173-178
U.S. Patent No. 8,266,007, "Methods and Systems for Delivering Customized Advertisements," Issued Sept. 11, 2012
- Technology Synopsis: This patent claims a method for improving the trust and relevance of online advertisements by tailoring them to a user's social network Compl. ¶114 The claimed method involves a server selecting a member of the user's social network who is "socially 'close'" to the user and visibly associating that member with the advertisement, thereby increasing the ad's perceived trustworthiness '007 Patent, cl. 1 '007 Patent, col. 7:19-27
- Asserted Claims: At least Claim 1 Compl. ¶182
- Accused Features: The Levi's "AS SEEN ON YOU" community feature, which allegedly functions as a social network where the server selects a member of the network to visibly associate with an advertisement based on social distance to the user Compl. ¶¶183-185
III. The Accused Instrumentality
- Product Identification: The accused instrumentalities are the "Levi's Products and Services," which include Levi's Mobile Apps, the Levi's website (levi.com), online shopping services, the "Levi's Rewards" program, and the "Levi's Community ('AS SEEN ON YOU')" feature Compl. ¶8 These services are supported by the underlying "Levi's System" of servers, software, and networked components Compl. ¶9
- Functionality and Market Context: The complaint focuses on two main functionalities of the accused products. The first is the responsive web layout of the Levi's website, which allegedly uses a layout engine to dynamically arrange content blocks (e.g., product images, text) to fit different browser and device screen sizes (Compl. ¶123; Compl. ¶124; Compl. ¶125; Compl. ¶126). A screenshot from the complaint shows a desktop browser view of the Levi's homepage Compl. ¶123 The second is the customer review system, which the complaint alleges is provided by Bazaarvoice and integrated into the Levi's website to collect, manage, and display product reviews, including marking certain reviews as coming from a "verified" purchaser (Compl. ¶¶131; Compl. ¶152). A screenshot of the Levi's website displays a review section managed by Bazaarvoice, showing an overall rating and customer images Compl. ¶131 The complaint alleges these products and services are offered for sale throughout the United States Compl. ¶6
IV. Analysis of Infringement Allegations
'635 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| forming by a layout generator operated by a processor, an inner-outer display entity pair having an inner display entity and an outer display entity, the outer display entity being a display container, and the inner display entity being a selected one of one of said content items and another display container; | The Levi's System's layout generator forms pairs by placing content items (e.g., and and |
¶124 | col. 16:22-29 |
| accepting or rejecting placement by the layout generator of the inner display entity into the outer display entity based at least in part on one or more layout placement criteria; | The Levi's System accepts or rejects placements based on layout placement criteria defined in its code, such as aspect ratio, min-width, height, and CSS @media rules. | ¶125 | col. 16:29-32 |
| and repeating said forming and said accepting or rejecting at least one other time if layout of the content items is incomplete and another inner-outer display entity pair can be formed. | The Levi's System repeatedly forms and places display entity pairs to construct the full page layout, as shown by the existence of multiple, different product displays on the same page. | ¶126 | col. 16:32-35 |
- Identified Points of Contention:
- Scope Questions: A potential issue is whether the accused system's use of standard, albeit complex, HTML/CSS for responsive design constitutes the specific "layout generator" performing the claimed iterative "forming," "accepting or rejecting" process. The defense may argue that modern web browsers and CSS engines operate differently from the claimed method. A screenshot of the website's source code shows the use of
<section>and<div>elements for layout Compl. ¶124 Another screenshot shows the use of CSS media queries and aspect ratios as layout criteria Compl. ¶125 - Technical Questions: A key question for the court will be whether the complaint provides sufficient evidence that the accused system performs an active, iterative "accepting or rejecting" step for each placement, as opposed to a more passive, declarative rendering based on a predefined set of CSS rules.
- Scope Questions: A potential issue is whether the accused system's use of standard, albeit complex, HTML/CSS for responsive design constitutes the specific "layout generator" performing the claimed iterative "forming," "accepting or rejecting" process. The defense may argue that modern web browsers and CSS engines operate differently from the claimed method. A screenshot of the website's source code shows the use of
'458 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| an apparatus, comprising: a database that contains reviews and reviews information, locator code information, subject information, and user information; | The Levi's System is alleged to comprise a database containing reviews, associated information (e.g., ratings), subject (product) information, user information (e.g., name, email), and "locator code" information (e.g., order/transaction ID). | ¶131 | col. 21:20-23 |
| and a computer system configured to instantiate a review engine server that provides a first information to a user and receives a second information from said user and stores at least some of the second information in the database, wherein said first information includes at least a review form, and said second information includes at least a locator code, and further wherein said locator code references a unique transaction. | The Levi's System provides a review form to a user and receives the submitted review information. The complaint alleges this submitted information includes a "locator code" (e.g., an order ID from a verified purchase) that references the unique transaction, thereby linking the review to an actual purchase. | ¶132 | col. 21:24-34 |
- Identified Points of Contention:
- Scope Questions: The central issue will be whether an "order number/ID, transaction number/ID, transaction record, token, etc." Compl. ¶131 as used by the Levi's system qualifies as the claimed "locator code." A screenshot of a review form from the Levi's website shows fields for the review content but does not explicitly show an order ID being entered, raising a question of how the linkage is made Compl. ¶132
- Technical Questions: The complaint alleges the Levi's review system is operated by Bazaarvoice (Compl. ¶¶55-56, Compl. ¶showing Bazaarvoice branding and scripts). A key question will be how eComm Innovations intends to prove that Levi's "makes" or "uses" the claimed apparatus. The analysis will likely focus on whether Levi's control and configuration of the Bazaarvoice platform is sufficient to constitute "use" under patent law. A screenshot of "verified" reviews on the Levi's site suggests a mechanism for linking reviews to purchases is in use Compl. ¶152
V. Key Claim Terms for Construction
For the '635 Patent
- The Term: "layout placement criteria"
- Context and Importance: This term is the core of the decision-making process in the claimed method. Its definition will determine whether the accused system's use of standard web technologies like CSS rules for responsive design falls within the scope of the claims. Practitioners may focus on this term because the infringement allegation hinges on equating CSS properties like
min-widthandaspect-ratiowith the claimed "criteria" Compl. ¶125 - Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification is not highly specific, stating the criteria may relate to "fit, space utilization, etc." and are "explicit rules or constraints" Compl. ¶40, language which may support a broad reading that includes CSS rules.
- Evidence for a Narrower Interpretation: The patent distinguishes its "search-based algorithm" from "prior art deterministic approaches" '635 Patent, col. 13:37-14:20 This could support an argument that the "criteria" must be part of an active, procedural search algorithm, not the declarative rules of standard CSS.
For the '458 Patent
- The Term: "locator code"
- Context and Importance: This term is the central element for achieving the patent's goal of review authenticity. The infringement case depends on whether an internal identifier used by the accused system (allegedly an order or transaction ID) to link a review to a verified purchase constitutes a "locator code" as claimed.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The claim itself is broad, only requiring that the "locator code references a unique transaction" '458 Patent, cl. 1 This could support reading the term on any unique identifier that links a review to a purchase, as alleged by the plaintiff Compl. ¶131
- Evidence for a Narrower Interpretation: The specification describes embodiments where a "unique locator code" is created and delivered to a merchant, who then issues it to a customer on a paper card or via email, and the customer then manually types the code into the review website '458 Patent, col. 7:37-67 '458 Patent, Fig. 7 This could support a narrower construction requiring an externally-provided, user-entered code, which may differ from how the accused system operates.
VI. Other Allegations
- Indirect Infringement: The complaint alleges that Levi's indirectly infringes by, inter alia, providing the accused Levi's Products and Services and Levi's System to third parties, thereby aiding and abetting their infringement Compl. ¶17 The specific facts alleged to support knowledge and intent are the pre-suit notice letters sent starting on September 22, 2025 Compl. ¶¶21-29
- Willful Infringement: Willfulness is alleged based on Defendant's purported knowledge of the patents-in-suit as of the September 22, 2025 notice letter Compl. ¶21 The complaint alleges that despite this notice, Levi's has continued its infringing activities, justifying a finding of willful infringement (Compl. ¶¶19; Compl. ¶114(k)).
VII. Analyst's Conclusion: Key Questions for the Case
- A core issue will be one of definitional scope: for the '635 patent family, can the claimed iterative, criteria-driven layout method be construed to cover the declarative rules and rendering processes of modern CSS-based responsive web design? For the '458 patent family, can an internal transaction ID used to verify a purchase be considered a "locator code" as described in the patent?
- A second key issue will be one of system liability: given that the accused review functionality is provided by a third-party vendor (Bazaarvoice), what level of control and direction must Plaintiff prove Levi's exercises over that system to be held liable for directly infringing the claimed apparatus and methods?
- An evidentiary question will be one of technical operation: what evidence will be presented to demonstrate that the accused systems perform the specific, ordered steps of the asserted method claims, particularly the "accepting or rejecting" step of the '635 patent and the explicit locator code handling steps of the '458 patent family, as opposed to functionally similar but technically distinct processes?