Wolverine Barcode IP LLC v. Walgreen Co

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Wolverine Barcode IP, LLC (Texas)
  • Defendant: Walgreen Co. (Illinois)
  • Plaintiff's Counsel: Ramey LLP
• Case Identification: 2:26-cv-00153, E.D. Tex., 06/11/2026
• Venue Allegations: Venue is alleged to be proper based on Defendant having a regular and established place of business within the Eastern District of Texas and having committed acts of infringement in the district.
• Core Dispute: Plaintiff alleges that Defendant's retail point-of-sale systems, including its "myWalgreens" mobile application and rewards program, infringe a patent related to conducting offline commerce transactions using a specialized user-identifying barcode.
• Technical Context: The technology addresses methods for enabling low-cost electronic payments at physical retail locations by leveraging existing barcode scanners rather than requiring specialized hardware like NFC readers.
• Key Procedural History: The complaint indicates Plaintiff is a non-practicing entity and that it and its predecessors-in-interest have previously entered into settlement licenses with other entities, none of which included an admission of infringement or a license to produce a patented article.

Case Timeline

Date	Event
2010-09-21	'689 Patent Priority Date
2016-03-08	'689 Patent Issue Date
2025-08-XX	Defendant acquired by Sycamore Partners
2026-06-11	Complaint Filing Date

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

• Patent Identification: U.S. Patent No. 9,280,689, "Method and Apparatus for Conducting Offline Commerce Transactions," issued March 8, 2016.

The Invention Explained

• Problem Addressed: The patent's background section describes the impracticality of using conventional payment methods for "micropayment-level purchases" Compl. ¶7 It notes that credit card transaction costs are too high for such small amounts, while systems like RFID or NFC require special non-contact readers that are not widely available at vendor locations '689 Patent, col. 1:24-31 '689 Patent, col. 2:21-31
• The Patented Solution: The invention proposes a system that uses a standard, ubiquitous barcode scanner to facilitate payments '689 Patent, col. 2:47-52 A user is identified by a "User ID Barcode," which is generated from a unique personal number (e.g., a cell phone number) and includes a "special character" that allows a vendor's server to distinguish it from a standard product barcode '689 Patent, abstract '689 Patent, col. 2:39-45 This information is then routed to a central "User Vendor Management Server" (UVM) that manages the user's account (either pre-paid or credit-based) and authorizes the transaction, as depicted in the system architecture of Figure 1(b) '689 Patent, Fig. 1(b) '689 Patent, col. 3:15-45
• Technical Importance: This approach was designed to enable low-cost, secure, and convenient electronic payments by leveraging existing retail infrastructure, thereby avoiding the significant investment and adoption hurdles associated with deploying new hardware like NFC readers '689 Patent, col. 7:1-9

Key Claims at a Glance

• The complaint asserts independent claim 1 and dependent claim 2 '689 Patent, col. 17:29-18:35 Compl. ¶6
• Independent claim 1 recites a multi-step method for conducting offline electronic commerce transactions, including the following essential elements:
  • Providing a personal code to a user.
  • Converting the code into a "User ID Barcode" that includes a "special character" to distinguish it from a product barcode.
  • Storing the personal code in a "User Vendor Management Server" (UVM Server).
  • Establishing a user account on the UVM Server.
  • Depositing funds into the account to establish a credit limit.
  • At a vendor, scanning both product barcodes and the User ID Barcode, and transmitting the data to a "vendor server."
  • The vendor server detecting the User ID Barcode and forwarding it with the purchase price to the UVM Server.
  • The UVM Server comparing the purchase price with the account funds and sending an approval signal back to the vendor server.
  • The vendor server forwarding the approval signal to the cash register.
  • Repeating the process for subsequent purchases.
• The complaint reserves the right to assert additional claims '689 Patent, col. 17:29-18:35 Compl. ¶6

III. The Accused Instrumentality

Product Identification

• The complaint identifies the "Accused Walgreens Systems" as the infringing instrumentality Compl. ¶11

Functionality and Market Context

• The Accused Walgreens Systems are described as encompassing Walgreens' retail point-of-sale (POS) systems, barcode scanners, cash registers, backend systems, mobile applications, and the "myWalgreens" loyalty program Compl. ¶11 According to the complaint, customers create a myWalgreens account, which is associated with a unique identifier Compl. ¶13 This identifier is converted into an "account-associated barcode" available within the Walgreens mobile application Compl. ¶14 Compl. ¶23 At checkout, a customer can have this barcode scanned, along with product barcodes, to identify their account, apply rewards such as "Walgreens Cash," and process the transaction Compl. ¶12 Compl. ¶18 The complaint alleges this entire infrastructure-from the mobile app to the POS scanner to the backend processing servers-collectively performs the steps of the patented method Compl. ¶¶11-12 No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

'689 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
(a) providing a personal code to a person for their use to purchase goods	Defendant provides a personal code by having a customer create a myWalgreens account with information like a phone number, which functions as a user-specific identifier.	¶13	col. 2:39-46
(b) converting said personal code into barcode format to form a User ID Barcode... including at least one special character to distinguish the barcode... from a product barcode	The user-specific identifier is converted into the myWalgreens account-associated barcode, which is alleged on "information and belief" to include encoded data or symbology that distinguishes it from product barcodes.	¶14	col. 2:40-45
(c) storing said personal code in said User ID Barcode format... and storing said personal code in a User Vendor Management Server	The barcode is stored in the Walgreens mobile app, and the corresponding account information is stored in Walgreens backend systems, which allegedly function as the UVM Server.	¶15	col. 7:21-36
(d) establishing a User Account in a User Vendor Management Server	Defendant establishes a myWalgreens account for the user in its backend systems.	¶16	col. 8:1-8
(e) depositing funds in said User Account to establish a credit limit	Defendant credits the myWalgreens account with "Walgreens Cash rewards or other stored-value balances," which allegedly establishes an available amount or spending limit.	¶17	col. 3:51-55
(f) conducting purchases at vendors... scanning product barcodes... and said User ID Barcode... and transmitting both product barcodes and User ID Barcode to said vendor server	At checkout, both product barcodes and the myWalgreens barcode are scanned, and the resulting information is transmitted to Walgreens backend systems, which allegedly function as the vendor server.	¶18	col. 9:53-10:18
(g) detecting the User ID Barcode at the vendor server and forwarding the ID Barcode and purchase price to said User Vendor Management Server	The point-of-sale system transmits the scanned barcode and purchase price to Walgreens backend systems, which allegedly route the information to other backend systems that manage the customer account (the UVM Server).	¶19	col. 10:9-18
(h) comparing the purchase price with the funds in said User Vendor Management Server... and... sending an approval signal	Walgreens backend systems allegedly compare the purchase price with available Walgreens Cash rewards and, if sufficient, authorize the transaction and send an approval response.	¶20	col. 10:19-31
(i) forwarding the approval signal to the vendor cash register	An approval, evidenced by a digital receipt or POS transaction information, is forwarded to the POS system (the vendor cash register).	¶21	col. 10:19-25
(j) repeating steps (f) through (i) for subsequent purchase transactions	The same myWalgreens barcode can be used repeatedly for subsequent transactions.	¶22	col. 18:28-29

Identified Points of Contention

• Scope Question: A central issue may be whether accruing loyalty points ("Walgreens Cash rewards") satisfies the claim limitation of "depositing funds... to establish a credit limit" Compl. ¶17 The patent specification describes this step in the context of a user making an "initial minimum deposit" of money or being granted a formal credit line, which may suggest a different mechanism than earning rewards through purchases '689 Patent, col. 7:26-34 '689 Patent, Fig. 5(a)
• Technical Question: The complaint alleges "on information and belief" that the myWalgreens barcode includes a "special character" or its equivalent to distinguish it from product barcodes Compl. ¶14 A key factual dispute may be whether the accused system actually uses such a distinguishing feature as required by the claim, or if it differentiates the barcodes using another method not covered by the patent's claims.
• Technical Question: The infringement theory maps different parts of "Walgreens backend systems" to both the "vendor server" and the "User Vendor Management Server" Compl. ¶¶18-20 The case may turn on whether the accused architecture genuinely performs the two-step routing from a vendor server to a separate UVM server as claimed, or if its operation is technically distinct.

V. Key Claim Terms for Construction

• The Term: "special character"

  • Context and Importance: This term is critical because it defines the core mechanism for how the system distinguishes a user barcode from a product barcode using a standard scanner. The complaint's allegation for this element rests on "information and belief," making its definition pivotal to the infringement analysis Compl. ¶14
  • Intrinsic Evidence for a Broader Interpretation: The specification suggests the character's purpose is functional, enabling the vendor server to "distinguish the barcode" '689 Patent, col. 5:64-6:6 This could support an argument that any encoded data, prefix, or change in symbology that performs this distinguishing function meets the limitation.
  • Intrinsic Evidence for a Narrower Interpretation: The abstract and summary of the invention explicitly provide an example of "prefixing a special character like '?'" '689 Patent, abstract '689 Patent, col. 2:43-45 This example may be used to argue for a narrower construction limited to an explicit, prefixed character.

• The Term: "depositing funds... to establish a credit limit"

  • Context and Importance: The viability of the infringement allegation may depend on whether accruing loyalty points falls within the scope of this term. Practitioners may focus on this term because it represents a potential mismatch between the patent's description of a funded account and the accused system's rewards-based functionality Compl. ¶17
  • Intrinsic Evidence for a Broader Interpretation: Plaintiff may argue that crediting an account with rewards is a form of "depositing" value ("funds") and that the total redeemable rewards constitute a "credit limit."
  • Intrinsic Evidence for a Narrower Interpretation: The patent's detailed description of the pre-paid mode involves a user making an "initial minimum amount of deposit" '689 Patent, col. 14:8-14 '689 Patent, Fig. 5(a) The post-pay mode involves establishing an "initial maximum credit limit" '689 Patent, col. 14:50-54 This language may support an interpretation that the term requires an explicit funding action by the user or a formal grant of credit, rather than the passive accumulation of loyalty points.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement, stating that Defendant instructs customers and employees to use the Accused Walgreens Systems in an infringing manner through its mobile app, account workflows, and checkout procedures Compl. ¶27 Contributory infringement is also pled, alleging that components like the myWalgreens digital wallet are especially made for this infringing use and are not staple articles of commerce Compl. ¶28
• Willful Infringement: The complaint alleges knowledge of the '689 patent at least from the filing date of the lawsuit and seeks a finding of willfulness should discovery reveal pre-suit knowledge of the patent and the infringing conduct Compl. ¶27 Compl. ¶VI.e

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

• A core issue will be one of definitional scope: can the claim term "depositing funds... to establish a credit limit," which the patent describes in the context of pre-paid cash accounts or formal credit lines, be construed to cover the accrual and redemption of loyalty points in the accused myWalgreens rewards program?
• A key evidentiary question will be one of technical proof: what evidence will emerge in discovery to substantiate the "information and belief" allegation that the myWalgreens barcode contains a "special character" or an equivalent functional mechanism to distinguish it from product barcodes, a specific technical requirement of the asserted claims?
• A third central question will concern architectural mapping: does the flow of data within the Accused Walgreens Systems align with the claimed two-tier structure of a "vendor server" forwarding information to a distinct "User Vendor Management Server," or is there a fundamental mismatch in technical operation that may place the accused system outside the scope of the claims?