PCS Software, Inc v. Dispatch Services, Inc.

CourtDistrict Court, S.D. Texas
DecidedMay 6, 2024
Docket4:23-cv-00108
StatusUnknown

This text of PCS Software, Inc v. Dispatch Services, Inc. (PCS Software, Inc v. Dispatch Services, Inc.) is published on Counsel Stack Legal Research, covering District Court, S.D. Texas primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
PCS Software, Inc v. Dispatch Services, Inc., (S.D. Tex. 2024).

Opinion

FOR THE SOUTHERN DISTRICT OF TEXAS May 06, 2024 HOUSTON DIVISION Nathan Ochsner, Clerk

§ PCS SOFTWARE, INC., § § Plaintiff, § v. § CIVIL ACTION NO. H-23-108 § DISPATCH SERVICES, INC., § § Defendant. §

MEMORANDUM AND OPINION Dispatch Services, Inc., contracted with PCS Software, Inc. for a software license. Dispatch quickly learned that the software did not meet its needs, so it stopped paying PCS the contractual setup and subscription fees. PCS sued for breach of contract. Dispatch counterclaimed, alleging fraudulent inducement. This opinion grants in part and denies in part PCS’s motion to dismiss Dispatch’s counterclaims. The reasons are set out below. I. Background PCS Software, Inc. provides “cloud-based transportation management software.” (Docket Entry No. 6 at ¶ 7). Dispatch Services, Inc, is a “third-party logistics provider and freight brokerage company.” (Id. at ¶ 8; Docket Entry No. 28 at 6). Dispatch “connects clients with truck owner-operators and manages the transportation of freight across the United States and Canada.” (Docket Entry No. 6 at ¶ 8). To do so, Dispatch depends on “Transportation Management Software.” (Docket Entry No. 28 at 6). Russia’s invasion of Ukraine created “logistical issues” for Dispatch’s transportation management software service. (Id.). Dispatch entered into discussions with PCS in an effort to “find a suitable replacement” for Dispatch’s software “capable of meeting all its specific transportation management needs.” (Id. at 6–7). In those discussions, Dispatch alleges that PCS alternative, but also meet various specifications that Dispatch’s current system allows and which Dispatch relies upon in its ordinary course of business.” (Id. at 7). PCS also allegedly “represented the Software had functions that Dispatch communicated were crucial to its decision to replace its current management system.” (Id.). A. The Agreement In June 2022, relying on PCS’s representations that its software would meet Dispatch’s specific needs, Dispatch executed a software licensing agreement with PCS (the “Agreement”). Under the Agreement, PCS promised to “grant[] to [Dispatch] during [] [an initial three-year term] a personal, non-exclusive, non-transferable, and royalty-free license to access and use [PCS’s

software] for [Dispatch]’s internal business purposes and not for the benefit of any third party.” (Docket Entry No. 6-1 at 5). In exchange, Dispatch agreed to pay “applicable fees and charges,” including a $108,639 “setup fee” and a monthly subscription fee “[c]ommencing upon [Dispatch]’s initial use of the [software].” (Id. at 3, 5, 18). The Agreement contained the following “as is” clause: EXCEPT FOR THE EXPRESS WARRANTIES SET FORTH IN SECTION 6.1, THE SERVICE AND ALL PRODUCTS ARE PROVIDED “AS IS”. PROVIDER SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT, AND ALL WARRANTIES ARISING FROM COURSE OF DEALING, USAGE OR TRADE PRACTICE. WITHOUT LIMITING THE FOREGOING, PROVIDER MAKES NO WARRANTY OF ANY KIND THAT THE SERVICE OR PRODUCTS, OR ANY OUTPUT OR RESULTS OF THE USE THEREOF, WILL MEET CLIENT’S OR ANY OTHER PERSON’S REQUIREMENTS, OPERATE WITHOUT INTERRUPTION, ACHIEVE ANY INTENDED RESULT, BE COMPATIBLE OR WORK WITH ANY SOFTWARE, SYSTEM, OR OTHER SERVICES, OR BE SECURE, ACCURATE, COMPLETE, FREE OF HARMFUL CODE, OR ERROR FREE. ALL THIRD-PARTY MATERIALS ARE PROVIDED “AS IS”, AND ANY REPRESENTATION OR WARRANTY OF OR CONCERNING ANY THIRD- PARTY MATERIALS IS STRICTLY BETWEEN CLIENT AND THE THIRD- PARTY OWNER OR DISTRIBUTOR OF SUCH THIRD-PARTY MATERIALS. The Agreement also contained the following integration clause: This Agreement and any relevant license agreement(s), constitute the entire agreement between [Dispatch] and PCS, and supersedes any and all prior agreements, negotiations and communications (whether written, oral or electronic) with respect to the Service. No change, modification, or waiver of the terms and conditions of this Agreement, shall be binding on PCS unless made in writing by PCS. However, Client acknowledges that applicable FCC rules and regulations are subject to change and that PCS may freely and without liability to [Dispatch], modify this Agreement to the extent necessary to comply with such FCC rules. (Id. at 14). B. PCS’s Allegations of Contract Breach Shortly after the parties executed the Agreement, PCS alleges that Dispatch ceased paying its subscription fees and setup fee installments. (Docket Entry No. 6 at ¶ 14). PCS alleges that Dispatch never paid the overdue fees and, since November 2022, has ignored PCS’s requests for payment. (Id. at ¶ 16). In November 2022, PCS gave Dispatch written notice that it was in breach “by failing to pay its outstanding invoice balance, and that failure to cure the breach by bringing its account current would result in suspension of services.” (Id. at ¶ 17). A few days after sending this notice, PCS suspended Dispatch’s access to the software. (Id.). In December 2022, PCS sent Dispatch a formal demand letter, invoking the Agreement’s acceleration clause for immediate payment of “all fees that would have become payable had the [Agreement] remained in effect until expiration of the Term.” (Id. at ¶ 18). PCS notified Dispatch of PCS’s termination of the Agreement and demanded payment for the full contract amount of $1,437,426. (Id.). C. This Lawsuit In January 2023, PCS filed this action against Dispatch, asserting causes of action for breach of contract and quantum meruit. (Docket Entry Nos. 1, 6). Dispatch answered and asserted misrepresentation; (4) fraudulent inducement; (5) breach of warranty; (6) violation of the Texas Deceptive Trade Practices Act, TEX. BUS. & COM. CODE § 17.46 et seq.; and (7) breach of the implied duty of good faith and fair dealing. (Docket Entry No. 28). PCS moved to dismiss Dispatch’s counterclaims under Federal Rule of Civil Procedure 12(b)(6). (Docket Entry No. 32). Dispatch responded, (Docket Entry No. 43), and PCS replied, (Docket Entry No. 44). Based on the pleadings, the briefs, and the applicable law, the motion to dismiss is granted in part and denied in part. The following claims are dismissed without prejudice: fraudulent misrepresentation, fraudulent inducement, unconscionability, and breach of warranty. The DTPA claim and claim for breach of the implied duty of good faith and fair dealing are dismissed with

prejudice. The negligent misrepresentation claim withstands the motion to dismiss. The reasons for these rulings are set out below. II. The Legal Standards Rule 12(b)(6) allows dismissal if a plaintiff fails “to state a claim upon which relief can be granted.” FED. R. CIV. P. 12(b)(6). Rule 12(b)(6) must be read in conjunction with Rule 8(a), which requires “a short and plain statement of the claim showing that the pleader is entitled to relief.” FED. R. CIV. P. 8(a)(2). “[A] complaint must contain sufficient factual matter, accepted as true, to ‘state a claim to relief that is plausible on its face.’” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009) (quoting Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007)). Rule 8 “does not require ‘detailed factual allegations,’ but it demands more than an unadorned, the-defendant-unlawfully-

harmed-me accusation.” Id. at 678 (quoting Twombly, 550 U.S. at 555). “A claim has facial plausibility when the plaintiff pleads factual content that allows the court to draw the reasonable inference that the defendant is liable for the misconduct alleged.” Id. (citing Twombly, 550 U.S. at 556). “The plausibility standard is not akin to a ‘probability requirement,’ but it asks for more at 556).

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Williams v. WMX Technologies, Inc.
112 F.3d 175 (Fifth Circuit, 1997)
Cuvillier v. Taylor
503 F.3d 397 (Fifth Circuit, 2007)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
In Re Poly-America, L.P.
262 S.W.3d 337 (Texas Supreme Court, 2008)
Williams v. Glash
789 S.W.2d 261 (Texas Supreme Court, 1990)
English v. Fischer
660 S.W.2d 521 (Texas Supreme Court, 1983)
Arnold v. National County Mutual Fire Insurance Co.
725 S.W.2d 165 (Texas Supreme Court, 1987)
Transport Insurance Co. v. Faircloth
898 S.W.2d 269 (Texas Supreme Court, 1995)
Berry v. Indianapolis Life Insurance
608 F. Supp. 2d 785 (N.D. Texas, 2009)
Abraham Shakeri v. ADT Security Services, I
816 F.3d 283 (Fifth Circuit, 2016)
Daniel Hux v. Southern Methodist University
819 F.3d 776 (Fifth Circuit, 2016)
Dewey Clark v. Mustang MacHinery Company, Ltd. D/B/A Mustang Cat
571 S.W.3d 305 (Court of Appeals of Texas, 2018)
Inclusive Cmtys. Project, Inc. v. Lincoln Prop. Co.
920 F.3d 890 (Fifth Circuit, 2019)
Luca Cicalese v. Univ of Texas Medical Bran
924 F.3d 762 (Fifth Circuit, 2019)

Cite This Page — Counsel Stack

Bluebook (online)
PCS Software, Inc v. Dispatch Services, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/pcs-software-inc-v-dispatch-services-inc-txsd-2024.