6 November 2026International edition
Vol. I · No.
6 November 2026
AI IN FASHION
DAILY
The daily briefing on AI in the fashion business
Where fashion meets artificial intelligence.
Strategy, Data & Regulation · Stories

AI vendor M&A risk assessment: 10 questions before signing contracts

Fashion buyers need vendor financial health checks, data portability clauses and exit plans as M&A reshapes AI technology suppliers and bankruptcies surge.

four men looking to the paper on table
Photo: Sebastian Herrmann / Unsplash

KEY TAKEAWAYS Summary by the editors

  1. Three year contracts are becoming standard for enterprise software, locking fashion businesses into vendors vulnerable to acquisition or financial distress.
  2. Saks Global filed for Chapter 11 in January 2026 after months of delayed vendor payments, illustrating how retail bankruptcies cascade through supply chains.
  3. Data portability clauses must specify export formats, transition timelines and post termination access periods of at least 30 days.
  4. Due diligence checklists should assess vendor financial stability, ownership structure, subprocessor dependencies and concentration risk before contract signature.

Fashion technology buyers face elevated vendor risk as M&A activity accelerates and financial stress mounts across retail and software sectors. In June 2026, CommerceClarity acquired Katalogo.ai, whilst in January 2025, CLO Virtual Fashion acquired swatchbook. Meanwhile, on 14 January 2026, Saks Global announced it commenced voluntary Chapter 11 cases and in 2025, SSENSE filed for bankruptcy protection with 371 million dollars of debt, including over 93 million dollars owed to vendors. Three year contracts now standard for enterprise software expose buyers to vendor disruption, ownership changes and service continuity failures unless procurement teams conduct structured due diligence before signature.

Why does vendor ownership stability matter for three year contracts?

The average SaaS contract length grew from 19.2 months in 2025 to 22.3 months in 2026, with 51 per cent of contracts having a 36 month term. Enterprises are signing three and five year deals to defend against price increases, not to endorse a vendor's roadmap. Longer commitments amplify exposure to ownership changes that alter product roadmaps, support quality and commercial behaviour. The risks that matter most for enterprise software relationships often emerge years into a contract: financial deterioration, acquisition by a private equity firm that dramatically changes commercial behaviour, or growing concentration risk as a single vendor becomes embedded in more and more critical processes.

What financial health signals should buyers verify before signing?

Vendor due diligence checklists should evaluate vendor security, financial stability, and compliance with regulatory requirements, with vendors undergoing security, financial, and legal assessments before contracts are signed. Financial assessment should cover revenue trajectory, profitability, debt levels and investor composition. Moody's says around 2022, vulnerable retailers began having a tougher time with refinancing and other financial measures to avoid bankruptcy, and that continues in 2026. Examine whether the vendor is cash flow positive, holds sufficient runway or depends on additional funding rounds that may not materialise.

How do recent bankruptcies illustrate vendor payment risk?

Fashion retail bankruptcies reveal how payment delays signal deeper instability. Reports indicate that Saks is in need of a strong holiday shopping season to meet its 100 million dollar interest payment due on 30 December in order to remain current on its 2.2 billion dollars in debt, with relationships strained due to chronic issues with delayed vendor payments. Fashion rental technology company CaaStle filed for Chapter 7 bankruptcy, triggering a liquidation of its assets following substantial financial losses and leadership turmoil. Technology vendors serving fashion clients face analogous stress. Buyers should request recent financial statements, monitor payment behaviour with other partners and require credit insurance for material contracts.

What concentration and dependency risks require assessment?

Seventy per cent of TPRM programmes are understaffed, and organisations assess only 40 per cent of their vendors on average, whilst 4.5 per cent of all breaches now originate from fourth party compromises, creating cascading downstream failures. Assess which internal processes depend on the vendor, what alternatives exist and whether the vendor relies on subprocessors for hosting, analytics or customer communications. Material supplier changes can alter the risk profile after onboarding. Map the vendor's own supply chain, particularly infrastructure providers, payment processors and data centre operators whose failure would cascade to your operations.

What data portability and exit provisions must contracts guarantee?

A well drafted SaaS agreement from the customer's perspective will clearly state the customer owns its data and all intellectual property rights related to it, the customer has immediate data access without charge upon demand, upon termination the customer may exercise full data portability and take its data to a new provider, and the data export format in which the data will be returned is specified. Contracts must address the data and assets that can move, the procedure, assistance, timing and deletion after the process, with a separate retrieval period lasting at least 30 calendar days after the transition ends. Standard SaaS contract language provides 30 days post termination access; this is almost never sufficient for an enterprise scale data migration. Negotiate 90 day windows, specify machine readable formats and require vendor technical assistance during transition.

Which contractual safeguards reduce M&A and insolvency exposure?

Include change of control provisions requiring notification, consent rights and termination options if the vendor is acquired. In a bankruptcy proceeding, customer data may be treated as a business asset and included in the estate. Require vendors to maintain source code escrow arrangements, particularly for mission critical systems, that release code to customers if the vendor ceases operations or materially breaches support obligations. Add performance bonds or parent company guarantees where vendor financial strength is uncertain. Establish service level agreements with financial penalties, not just credits, to maintain leverage if ownership changes degrade support quality.

  • Does the contract specify your ownership of all input data, trained models and derivative outputs?
  • Are export formats documented, including APIs, database schemas and file specifications?
  • What notice period and transition assistance does the vendor provide upon termination?
  • Does a change of control clause grant you termination rights if the vendor is acquired?
  • Are post termination data access periods negotiated beyond standard 30 day windows?
  • Have you verified the vendor's financial stability through recent audited statements?
  • Does the vendor rely on subprocessors whose failure would disrupt your service?
  • What backup and disaster recovery arrangements protect your data if the vendor fails?
  • Are liability caps and indemnities adequate for your business criticality and data sensitivity?
  • Have you documented internal switching costs and alternative vendor options?

Frequently asked questions

How often should fashion buyers reassess vendor financial health?

Critical vendors warrant annual reassessment of financial statements, ownership structure and subprocessor dependencies. Trigger immediate reviews if the vendor reports security incidents, delays payments to partners, announces redundancies or faces credit rating downgrades. Quarterly monitoring of payment behaviour and service performance provides early warning of deterioration.

What data portability rights does EU law guarantee from September 2025?

Chapter VI of the EU Data Act, which applied from 12 September 2025, requires data processing service providers to remove obstacles to switching. Contracts must address data export procedures, vendor assistance and timing. The notice period before switching starts cannot exceed two months. The transition normally cannot exceed 30 calendar days, with a separate retrieval period of at least 30 calendar days after transition ends.

Should fashion businesses avoid vendors involved in M&A activity?

M&A activity is not inherently disqualifying but requires heightened due diligence. Assess whether the acquirer has fashion domain expertise, maintains comparable support quality and preserves product roadmaps. Recently acquired vendors may face integration disruption, support team turnover and strategic pivots that deprioritise fashion specific features. Negotiate change of control clauses granting termination rights if acquisition materially degrades service.

Stories