Lead Opinion
OPINION
Plaintiffs Crystal and Brian Byrd bring this interlocutory appeal under Rule 23(f) of the Federal Rules of Civil Procedure. The Byrds brought a putative class action against Aaron’s, Inc. and its franchisee store Aspen Way Enterprises, Inc. (collectively “Defendants”), who they allege violated the Electronic Communications Privacy Act of 1986 (“ECPA”), 18 U.S.C. § 2511. Concluding that the Byrds’ proposed classes were not ascertainable, the District Court denied their motion for class certification. Because the District
I.
Aaron’s operates company-owned stores and also oversees independently-owned franchise stores that sell and lease residential and office furniture, consumer electronics, home appliances, and accessories. On July 30, 2010, Crystal Byrd entered into a lease agreement to rent a laptop computer from Aspen Way, an Aaron’s franchisee. Although Ms. Byrd asserts that she made full payments according to that agreement, on December 22, 2010, an agent of Aspen Way came to the Byrds’ home to repossess the laptop on the grounds that the lease payments had not been made. The agent allegedly presented a screenshot of a poker website Mr. Byrd had visited as well as a picture taken of him by the laptop’s camera as he played. The Byrds were troubled and surprised by what they considered a significant and unauthorized invasion of their privacy.
Aspen Way obtained the picture and screenshot through spyware — a type of computer software — designed by DesignerWare, LLC and named “PC Rental Agent.” This spyware had an optional function called “Detective Mode,” which could collect screenshots, keystrokes, and webcam images from the computer and its users. Between November 16, 2010 and December 20, 2010, the Byrds alleged that this spyware secretly accessed their laptop 347 times on eleven different days.
The Byrds’ operative class-action complaint asserts claims against Aaron’s, Aspen Way, more than 50 other independent Aaron’s franchisees, and DesignerWare, LLC.
In the meantime, the Byrds moved to certify the class under Federal Rules of
Class I — All persons who leased and/or purchased one or more computers from Aaron’s, Inc., and their household members,' on whose computers Designer-Ware’s Detective Mode was installed and activated without such person’s consent on or after January 1, 2007.
Class II — All persons who leased and/or purchased one or more computers from Aaron’s, Inc. or an Aaron’s, Inc. franchisee, and their household members, on whose computers DesignerWare’s Detective Mode was installed and activated without such person’s consent on or after January 1, 2007.
Byrd,
The Magistrate Judge recommended denying the Byrds’ motion for certification because the proposed classes were not ascertainable. Regarding owner and lessee class members, the Magistrate Judge concluded that the proposed classes were underinclusive because they did “not encompass all those individuals whose information [was] surreptitiously gathered by Aaron’s franchisees.” Id. The Magistrate Judge also determined that the classes were “overly broad” because not “every computer upon which Detective Mode was activated will state a claim under the ECPA for the interception of an electronic communication.” Id. Regarding “household members,” the Magistrate Judge took issue with the fact that the Byrds did not define the phrase. Id. Further, although the Byrds stated that the identity of household members could be gleaned from “public records,” the Magistrate Judge, citing to Carrera v. Bayer Corp.,
II.
The District Court had federal question jurisdiction under 28 U.S.C. § 1331. We have jurisdiction under 28 U.S.C. § 1292(e) and Federal Rule of Civil Procedure 23(f). ‘We review a class certification order for abuse of discretion, which occurs if the district court’s decision rests upon a clearly erroneous finding of fact, an errant conclusion of law or an improper application of law to fact.” Grandalski v. Quest Diagnostics Inc.,
III.
The central question in this appeal is whether the District Court erred in determining that the Byrds’ proposed classes were not ascertainable. Because the District Court confused ascertainability with other relevant inquiries under Rule 23, we conclude it abused its discretion and will vacate and remand.
Before discussing these errors, however, we believe it is necessary to address the scope and source of the ascertainability requirement that our cases have articulated. Our ascertainability decisions have been consistent and reflect a relatively simple requirement. Yet there has been apparent confusion in the invocation and application of ascertainability in this Circuit. (Whether that is because, for example, the courts of appeals have discussed ascertainability in varying and distinct ways,
We seek here to dispel any confusion. The source of, or basis for, the ascertainability requirement as to a Rule 23(b)(3) class is grounded in the nature of the class-action device itself. In endeavoring to further explain this concept, we adhere to the precise boundaries of ascertainability previously iterated in the quartet of cases we discuss below. The ascertainability requirement as to a Rule 23(b)(3) class is consistent with the general understanding that the class-action device deviates from the normal course of litigation in large part to achieve judicial economy. See Comcast,
The class-action device is an exception to the rule that litigation is usually “ ‘conducted by and on behalf of the individual named parties only.’ ” Comcast Corp. v. Behrend, — U.S. —,
The ascertainability inquiry is two-fold, requiring a plaintiff to show that: (1) the class is “defined with reference to objective criteria”; and (2) there is “a reliable and administratively feasible mechanism for determining whether putative class members fall within the class definition.” Id. at 355 (citing Marcus v. BMW of N. Am., LLC,
We have on four occasions addressed the requirement that a Rule 23(b)(3) class be “ascertainable” in order to be certified. Our quartet of cases began with Marcus v. BMW of North America, LLC, in which we adopted this implicit ascertainability requirement.
As to the use of affidavits, we began by explaining that in Marcus, “[w]e cautioned ‘against approving a method that would amount to no more than ascertaining by potential class members’ say so.’ ” Id. at 306 (quoting Marcus,
We were careful to specify in Carrera that “[although some evidence used to satisfy ascertainability, such as corporate records, will actually identify class members at the certification stage, ascertainability only requires the plaintiff to show that class members can be identified.” Id. at 308 n. 2 (emphasis added). Accordingly, there is no records requirement. Carrera stands for the proposition that a party cannot merely provide assurances to the district court that it will later meet Rule 23’s requirements. Id. at 306. Nor may a party “merely propose a method of ascertaining a class without any evidentiary support that the method will be successful.” Id. at 306, 307, 311.
Following the Marcus-Hayes-Carrera trilogy, we again considered the issue of ascertainability in Grandalski v. Quest Diagnostics Inc.,
Ascertainability is closely tied to the other relevant preliminary inquiry we addressed in Marcus,
And after certification, a trial court is tasked with providing “the best notice that is practicable” to the class members under Rule 23(c)(2)(B), “ ‘including individual notice to all class members who can be identified through reasonable effort.’ ” Larson v. AT & T Mobility LLC,
The ascertainability inquiry is narrow. If defendants intend to challenge ascertainability, they must be exacting in their analysis and not infuse the ascertainability inquiry with other class-certification requirements. As we said in Carrera, “ascertainability only requires the plaintiff to show that class members can be identified.”
B.
With this explanation of ascertain-ability in mind, we will reverse the District Court for four reasons. First, the District Court abused its discretion by misstating the rule governing ascertainability. Second, the District Court engrafted an “underinclusive” requirement that is foreign to our ascertainability standard. Third, the District Court made an errant conclusion of law in finding that an “overly broad” class was not ascertainable. And fourth, the District Court improperly applied the legal principles from Carrera to the issue of whether “household members” could be ascertainable.
1.
The District Court misstated the. law governing ascertainability by conflating our standards governing class definition
“As an ‘essential prerequisite’ to the Rule 23 analysis, the Court must consider 1) whether there is a precisely defined class and 2) whether the named Plaintiffs are members of the class. Marcus v. BMW of North America,687 F.3d 583 , 596 (3d Cir.2012). ... At the first step of the analysis, determining whether there is a precisely defined class entails two separate and important elements: ‘first, the class must be defined with reference to objective criteria’ and ‘second, there must be a reliable and administratively feasible mechanism for determining whether putative class members fall within the class definition.’ Hayes v. Wal-Mart Stores, Inc.,725 F.3d 349 , 355 (3d Cir.2013).”
Byrd,
Although the District Court is correct that the class definition requirements are applicable to a class-certification order, Wachtel,
Also troubling is the District Court’s discussion of class membership. Byrd,
2.
The District Court also abused its discretion in determining that the proposed classes were not ascertainable because they were underinclusive. The District Court reasoned that although the records provided by Aaron’s “may reveal the computers upon which Detective Mode was activated and the owner/lessee of that computer,” the Byrds did “not provide an administratively feasible way to determine whose information was surreptitiously gathered.” Byrd,
Defendants contend that “underinelusiveness” was an appropriate consideration in support of the denial of class certification. They rely on a district court decision, Bright v. Asset Acceptance, LLC,
We decline to engraft an “underinclusivity” standard onto the ascertainability requirement. Individuals who are injured by a defendant but are excluded from a class are simply not bound by the outcome of that particular action. Cf. e.g., Taylor v. Sturgell,
3.
Similarly, the District Court also abused its. discretion in determining that the proposed classes were not ascertain
Defendants also rely on Bright for the proposition that a class is not “ascertainable if it is decoupled from the underlying allegations of harm rendering it ... over-broad.” See Bright,
Defendants’ reliance on authority outside this Circuit does nothing to bolster their argument. For example, they extensively discuss Oshana v. Coca-Cola Co.,
The “definiteness” standard from Oshana is distinguishable from our Circuit’s ascertainability requirement. The standard applied in the Seventh Circuit is based on the premise that because “[i]t is axiomatic that for a class action to be certified a ‘class’ must exist,” Simer v. Rios,
Defendants also argue that a proposed class is overbroad “where putative class members lack standing or have not been injured.” Defendants’ argument conflates the issues of ascertainability, overbreadth (or predominance), and Article III standing. We have explained that the issue of
The Byrds’ proposed classes consisting of “owners” and “lessees” are ascertainable. There are “objective records” that can “readily identify” these class members, cf. Grandalski,
4.
The District Court again abused its discretion in determining that “household members” were not ascertainable. The District Court concluded that the inclusion of the phrase “household members” in the Byrds’ revised class definitions was vague and not ascertainable. In the Byrds’ reply brief on the motion for class-action certification, they asserted in a footnote that “[hjousehold members can easily be objectively verified through personal and public records. And their usage of the owner/lessee’s computers can also be easily objectively established.” The Magistrate Judge recommended denying class certification because the Byrds did not define “household members” or prove by a preponderance of the evidence how “ ‘household members’ can be verified through personal and public records.”
In their objections to the Magistrate Judge’s Report and Recommendation, the Byrds argued that they intended “the plain meaning of ‘household members.’ ” On appeal, the Byrds continue to argue that they intended the plain meaning of “household members” to be “all of the people, related or unrelated, who occupy a housing unit.” By way of example, the Byrds cite to multiple definitions used in government documents for census, taxation, and immigration purposes. With these definitions, they contend that the simple act of confirming membership would mean matching addresses in public records with that of an owner or lessee that had already been identified.
The “household members” of owners or lessees are ascertainable. Although the government documents cited by the Byrds do contain slight variations on the definition of a household member (as noted by Defendants), the Byrds presented the District Court with various ways in which “household members” could be defined and how relevant records could be used to verify the identity of household members.
The parties also dispute whether the phrase “household members” is often used in class definitions. Although it is true that the phrase “household members” has been used in other class definitions,
We also conclude that Defendants’ and the District Court’s reliance on Carrera is misplaced. In Carrera, we concluded that the plaintiffs’ proposed reliance on affidavits alone, without any objective records to identify class members or a method to weed out unreliable affidavits, could not satisfy the ascertainability requirement.
The Byrds’ proposed method to ascertain “household members” is neither administratively infeasible nor a violation of Defendants’ due process rights. Because the location of household members is already known (a shared address with one of the 895 owners and lessees identified by the Byrds), there are unlikely to be “serious administrative burdens that are incongruous with the efficiencies expected in a class action.” Marcus,
Certainly, Carrera does not suggest that no level of inquiry as to the identity of class members can ever be undertaken. If that were the case, no Rule 23(b)(3) class could ever be certified. We are not alone in concluding that “the size of a potential class and the need to review individual files to identify its members are not reasons to deny class certification.” See Young v. Nationwide Mut. Ins. Co.,
As to Defendants’ contention that their due process rights would be violated, Carr-era counsels that this due process right relates to the ability to “challenge the proof used to demonstrate class membership.”
In sum, the District Court erred in its application of Carrera and in concluding that the phrase “household members” was inherently vague.
C.
In light of the errors discussed above, we will remand to the District Court to consider the remaining Rule 23 certification requirements in the first instance. At oral argument and in their briefs, Defendants urged us to read the District Court’s ruling as one on predominance, independently review the record in this case, and conclude that the Byrds’ proposed classes fail to satisfy Rule 23(b)(3)’s predominance requirement. Defendants contend that the elements of an ECPA claim, particularly that each plaintiff must show the interception of the “contents” of an “electronic communication,” create insurmountable barriers to proving predominance. See 18 U.S.C. § 2511(1)(a), (c), (d). Formidable though these barriers may be, they are not for us to address in the first instance.
Beginning in General Telephone Co. of Southwest v. Falcon,
What is more, a close reading of Defendants’ response briefs demonstrates how they continue to conflate ascertainability with the other relevant requirements of Rule 23. We write again to emphasize that at class certification, Rule 23’s explicit requirements go beyond and are separate from the ascertainability inquiry. Precise analysis of relevant Rule 23 requirements will always be necessary. We therefore decline to go beyond the scope of the District Court’s opinion.
IV.
The District Court erred both in relying on an errant conclusion of law and improperly applying law to fact. Accordingly, we will reverse and remand for further consideration in light of this opinion.
Notes
. The spyware allegedly captured a wide array of personal information: “credit and debit card numbers, expiration dates, security codes, pin numbers, passwords, social security numbers, birth dates, identity of children and the children’s personal school records, tax returns, personal health information, employment records, bank account records, email addresses, login credentials, answers to security questions and private communications with health care providers, therapists, attorneys, and other confidants.” The record also reveals what appear to be screenshots of adult-oriented and active webcam transmissions and conversations of an intimate nature.
The spyware, as described in the Byrds’ complaint, was Orwellian-like in that it guaranteed that “[t]here was of course no way of knowing whether you were being watched at any given moment,” George Orwell, 1984, at 3 (Signet Classics 1950), because Aspen Way's corporate intranet (and Aaron’s corporate server by proxy) apparently activated the PC Rental Agent's Detective Mode “whenever they wanted to.” Id.
. On March 20, 2012, the District Court issued an order noting that DesignerWare filed for bankruptcy in the U.S. Bankruptcy Court for the Western District of Pennsylvania. Accordingly, the District Court ordered that no action be taken against DesignerWare and that the case be administratively closed as to that defendant.
. In the motion for class certification, the Byrds proposed the following classes:
Class I (against Aaron's Inc. for direct liability under ECPA)—
All persons residing in the United States, who have purchased, leased, rented or rented to own, Aaron's computers and individuals who used said computers whose personal information, electronic communications and/or images were intercepted, used, disclosed, accessed, monitored and/or transmitted via PC Rental Agent or other devices or software without the customers [sic] authorization.
Class II (against Aaron's Inc., Aspen Way, and all other Franchisee Defendants for direct liability under ECPA, invasion of privacy, conspiracy, and aiding and abetting) — •
All customers of the Aaron’s Defendants who reside in the United States, who have purchased, leased, rented or rented to own, Aaron’s computers and individuals who used said computers whose personal information, electronic communications and/or images were intercepted, used, disclosed, accessed, monitored and/or transmitted by the Aaron’s Defendants via PC Rental Agent or other devices or software without the customers [sic] authorization.
Byrd,
Class II (against Aaron's Inc., and Aspen Way for direct liability under the ECPA, invasion of privacy, conspiracy, and aiding and abetting (under Wyoming law))'—
All persons residing in the United States, who have purchased, leased, rented or rented to own, Aaron's computers from Aspen Way Enterprises, Inc., d/b/a Aarons Sales and Leasing, and individuals] who used said computers whose personal information, electronic communications and/or images were intercepted, used, disclosed, accessed, monitored and/or transmitted by Aspen Way and/or Aaron's via PC Rental Agent or other devices or software without the customers [sic] authorization.
Id. It is worth noting that the Byrds' revised proposed class definitions did not expressly require an electronic communication to be "intercepted,” although that is a necessary element in successfully proving their ECPA claims. See 18 U.S.C. §§ 2511, 2520(a).
. For example, some of our sister courts of appeals have interspersed their analysis of ascertainability, or "identifiability,” with explicit Rule 23 requirements. See, e.g., Colo. Cross Disability Coal. v. Abercrombie & Fitch Co.,
Conversely, others have framed ascertainability as requiring that there be an "objective standard” to determine whether class members are included in or excluded from the class without reference to any particular portion of Rule 23. See, e.g., EQT Prod. Co. v. Adair,
Even the citations we relied upon in Marcus v. BMW of North America, LLC, to discuss the policy rationales behind ascertainability,
. Ascertainability is an "essential prerequisite,” or an implied requirement, of Rule 23, “at least with respect to actions under Rule 23(b)(3).” Marcus,
. See, e.g., Class Action Reporter, Courts Scrutinize Class Certification "Ascertainability,” Vol. 17, Feb. 6, 2015, (explaining that "courts across the country are increasingly scrutinizing ‘ascertainability’ at the class certification stage”); Melody E. Aldravan, Ascertainability Challenge Is Viable Weapon for Defense, Law360, Nov. 26, 2014, http://www.law360. com/articles/599335/ascertainabilitychallenge-is-viable-weapon-for-defense ("Courts’ focus on ascertainability has become an increasingly useful tool for defendants fighting class certification.”); Alida Kass, Third Circuit Case Could Limit Consumer Class Actions, N.J. Law Journal, June 25, 2014 (“[T]he Third Circuit will be a fertile ground for exploring the boundaries of ascertainability.”).
. In Shelton v. Bledsoe, we held that ascertainability is not a requisite of a Rule 23(b)(2) class.
. An additional post-certification concern relates to the argument by some that the class-action device fails in its purpose if a judgment or settlement cannot be executed without resulting in a largely cy pres fund. E.g., Marek v. Lane, — U.S. —,
. The ECPA permits any person to bring a civil action "whose wire, oral, or electronic communication is intercepted, disclosed, or intentionally used in violation of this chapter.” 18 U.S.C. § 2520(a); see also id. § 2511. The Byrds’ operative complaint alleges that the PC Rental Agent "allows its installer (here, the rent-to-own store) to remotely and surreptitiously build and activate the 'Detective Mode' function on the laptop over the Internet and through the Aaron's Inc. and DesignerWare websites.” Byrd,
. See, e.g., Ortiz,
Concurrence Opinion
concurring:
I agree with the majority that, under our current jurisprudence, the class members here are clearly ascertainable. Indeed, as Judge Smith points out, “Aaron’s own records reveal the computers upon which Detective Mode was activated, as well as the full identity of the customer who leased or purchased each of those computers.” (Maj. Op. at 169) (quoting Byrd v. Aaron’s, Inc., No. 11-cv-101,
Historically, the ascertainability inquiry related to whether the court will be able to determine who fits within the class definition for purposes of award or settlement distribution and the preclusion of the relitigation of claims.
In 2012 we adopted a second element, namely, requiring district courts to make certain that there is “a reliable, administratively feasible” method of determining who fits into the class, thereby imposing a heightened evidentiary burden. Marcus,
Records are not the only way to prove that someone is in a class. It is the trial
This puts the class action cart before the horse and confuses the class certification process, as this case makes manifest. The irony of this result is that it thwarts “[t]he policy at the very core of the class action mechanism,” i.e., “to overcome the problem that small recoveries do not provide the incentive for any individual to bring a solo action prosecuting his or her rights.” Amchem Prods., Inc. v. Windsor,
The policy rationales that we cite in support of our expanded ascertainability requirement are relatively weak when compared to the significant policy justifications that motivate the class action mechanism. We have noted three rationales for our ascertainability requirement: (1) eliminating administrative burdens “incongruous” with the efficiencies of a class action, (2) protecting absent class members’ rights to opt out by facilitating the best notice practicable, and (3) protecting the due process rights of defendants to challenge plaintiffs’ proffered evidence of harm. Marcus,
Eliminating “administrative burdens” really means short-circuiting the claims process by assuming that when individuals file claims, they burden the court. But claims administration is part of every class action. Imposing a proof-of-purchase requirement does nothing to ensure the manageability of a class or the “efficiencies” of the class action mechanism; rather, it obstructs certification by assuming that hypothetical roadblocks will exist at the claims administration stage of the proceedings.
Denying class certification due to concerns about providing notice to class members makes little sense. Rule 23 requires the “best notice that is practicable under the circumstances” to potential class members after a class has been certified.
The concerns regarding the due process rights of defendants are unwarranted as well, because there is no evidence that, in small-claims class actions, fabricated claims impose a significant harm on defendants. The chances that someone would, under penalty of perjury, sign a false affidavit stating that he or she bought Bayer aspirin for the sake of receiving a windfall of $1.59 are far-fetched at best. On the other hand, while most injured individuals will find that it is not worth the effort to claim the few dollars in damages that the class action can provide, in the aggregate, this sum. is significant enough to deter corporate misconduct. Our ascertainability doctrine, by focusing on making abso
The concerns about defendants’ due process rights are also overblown because damages liability under Rule 23 is determined in the aggregate: courts determine the extent of a defendant’s monetary liability to the entire class. Therefore, whether an individual can establish membership in that class does not affect the rights of defendants not to pay in excess of their liability. Carrera’s concern that allowing undeserving individuals to claim damages will dilute deserving class members’ recoveries is unrealistic in modern day class action practice, and it makes little sense when used to justify the wholesale dooming of the small-value class action such that no injured plaintiff can recover at all. Moreover, this is an issue to be dealt with in the implementation of a class action settlement, not in conjunction with ascertaining the class for purposes of certification. Concerns about claims processing should not be used to scuttle these types of class actions altogether.
The policy concerns animating our ascertainability doctrine boil down to ensuring that there is a surefire way to get damages into the hands of only those individuals who we can be 100% certain have suffered injury, and out of the hands of those who may not have. However, by disabling plaintiffs from bringing small-value claims as a class, we have ensured that other policy goals of class actions— compensation of at least some of the injured and deterrence of wrongdoing, for example — have been lost. In small-claims class actions like Carrera, the real choice for courts is between compensating a few of the injured, on the one hand, versus compensating none while allowing corporate malfeasance to go unchecked, on the other. As such, where there are small-value claims, class actions offer the only means for achieving individual redress. As the Supreme Court stated in Eisen, when individual damages are so low, “[ejconomic reality dictates that petitioner’s suit proceed as a class action or not at all.”
[T]he class action device, at its very core, is designed for cases like this where a large number of consumers have been defrauded but no one consumer has suffered an injury sufficiently large as to justify bringing an individual lawsuit. Against this background, the ascertainability difficulties, while formidable, should not be made into a device for defeating the action.
Ebin v. Kangadis Food Inc.,
Therefore, while I concur in the judgment, I suggest that it is time to retreat from our heightened ascertainability requirement in favor of following the historical meaning of ascertainability under Rule 23. I would therefore reverse the District Court’s ruling, and hold that (1) hereafter, our ascertainability analysis will focus on class definition only, and (2) the District Court’s analysis regarding the second prong of our ascertainability test was unnecessary. We thus would instruct the District Court to proceed to determine whether the class can be certified under the traditional mandates of Rule 23. Until we revisit this issue as a full Court or it is addressed by the Supreme Court or the Advisory Committee on Civil Rules, we will continue to administer the ascertainability requirement in a way that contravenes the purpose of Rule 23 and, in my view, disserves the public.
. See Manual for Complex Litigation (Fourth) § 21.222 (2004) ("An identifiable class exists if its members can be ascertained by reference to objective criteria.”); Joseph M. McLaughlin, McLaughlin on Class Actions § 4:2 (11th ed.2014) ("[C]lass members need to be able to determine with certainty from a class notice whether they are in the class.... If the class definition is amorphous, persons may not recognize that they are in the class, and thus may be deprived of the opportunity to object or opt out.”); 5 James Wm. Moore et al., Moore’s Federal Practice ¶ 23.21 [1] (3d ed.1999) (noting that a class must be "susceptible to precise definition”).
. Courts have found classes to be ascertainable when the class definition is sufficiently specific. Compare Parkinson v. Hyundai Motor Am.,
. Several courts have denied class certification on ascertainability grounds similar to our current ascertainability test. See, e.g., Randolph v. J.M. Smucker Co.,
. While the majority cites a footnote in Carrera as standing for the proposition that we have no "records requirement,” the class in Carrera failed the ascertainability test because there were no records from which the class members could be ascertained with certainty. (Maj. Op. at 164 (citing Carrera,
. See, e.g., McCrary v. Elations Co., LLC, No. 13-cv-242,
. Small-value consumer class actions certified by district courts nationwide would not pass muster in our Circuit because of our heightened ascertainability requirement. See, e.g., Hughes v. Kore of Ind. Enter., Inc.,
. See Carnegie v. Household Int’l, Inc.,
. Fed.R.Civ.P. 23(c)(2)(B).
. See also Girsh v. Jepson,
. As one court has noted,
[a]dopting the Carrera approach would have significant negative ramifications for the ability to obtain redress for consumer injuries. New people retain receipts for low-priced goods, since there is little possibility they will need to later verify that they made the purchase. Yet it is precisely in circumstances like these, where the injury to any individual consumer is small, but the cumulative injury to consumers as a group is substantial, that the class action mechanism provides one of its most important social benefits.
Lilly,
. Myriam Gilíes, Class Dismissed: Contemporary Judicial Hostility to Small-Claims Consumer Class Actions, 59 DePaul L.Rev. 305, 308 (2010).
