A price rise from a US cloud or software supplier should not automatically be described as a tariff increase. UK tariff guidance and the Trade Tariff concern goods and their commodity codes. Cloud hosting and software subscriptions are services, with separate tax, contract and trade considerations.

Tariffs on physical equipment may affect parts of a provider’s supply chain, yet a customer cannot infer that a particular renewal increase was caused by them without evidence from the supplier. Currency, energy, product bundling, market power, new features, discount expiry and the vendor’s pricing strategy may all be relevant.

For a UK business, the useful response is a broader exposure review: understand contractual pricing, tax treatment, service location, data transfers, switching barriers and concentration before a renewal creates urgency.

Separate direct obligations from indirect pressure

The UK Trade Tariff is the official service for commodity codes, duty and VAT rates on goods. It is relevant when a business imports hardware or other physical products. It does not establish a customs duty on an ordinary cloud subscription.

Services bought from outside the UK may engage the VAT reverse charge. HMRC’s current guidance on VAT for services from abroad explains the mechanism and notes separate rules for electronically supplied services. Finance or tax advisers should confirm treatment for the actual supply and the business’s VAT position.

Indirect cost pressure is harder to attribute. A provider may face changing equipment, energy, labour, tax or regulatory costs across several countries. It may pass some cost to customers, absorb it or change packaging. Ask the supplier to explain a material increase and the contractual basis. Avoid presenting speculation about its internal costs as fact.

Build a complete supplier exposure view

Cloud dependence is distributed across infrastructure, CMS, CRM, email, collaboration, identity, analytics, security and specialist SaaS. Procurement records may miss products bought on expenses or bundled through an implementation partner.

Create an inventory containing:

  • legal supplier and contracting entity;
  • service, users and business process supported;
  • annual and forecast cost, currency and discount;
  • renewal, notice and termination dates;
  • price-adjustment and pass-through clauses;
  • data and service hosting regions;
  • sub-processors and critical technical dependencies;
  • export, egress and transition conditions;
  • operational owner and accountable sponsor;
  • consequence and recovery route if service is unavailable.

Distinguish company headquarters, contracting entity, billing currency, infrastructure location and data-processing location. A UK vendor may depend on US infrastructure; a US supplier may provide a UK-hosted region. These facts create different commercial, operational and legal questions.

Read the contract before the renewal window

Identify indexation, notice, minimum commitment, consumption tiers, exchange-rate treatment, discount expiry and the supplier’s right to vary features or price. Examine whether a committed spend can move between services and what happens when usage exceeds it.

Check total cost rather than headline unit price. Support, premium security, test environments, API calls, storage, egress, backup, implementation and mandatory partner services may change the comparison.

Start supplier discussion while alternatives still exist. Ask for:

  • the basis and effective date of the proposed change;
  • usage and forecast assumptions;
  • available commitment or consumption options;
  • products or features whose removal could reduce cost;
  • technical help with optimisation;
  • exit data, format, timing and charges;
  • the service and price implications of changing region.

Record promises in an agreed commercial document. A general assurance from an account manager is weak protection against later terms.

Account for currency separately

A dollar-denominated agreement exposes a UK buyer to exchange-rate movement even if the supplier’s list price does not change. Establish which rate and date are used for billing, who bears conversion fees and whether the contract can move to sterling.

Finance can model plausible ranges rather than predicting one rate. Hedging may be appropriate for material, predictable exposure and requires suitable treasury advice. Do not mix currency effect, vendor increase and usage growth into one unexplained percentage.

Separating them improves the renewal conversation and the internal forecast.

Examine switching and concentration

Price risk is more serious when exit is technically or operationally difficult. The UK Competition and Markets Authority reported barriers concerning egress fees, interoperability and licensing in its cloud-services work. Its March 2026 announcement on business software and cloud services also described continuing attention to switching and multi-cloud.

For each critical service, test:

  • whether data can be exported in a usable form;
  • how long a realistic transition would take;
  • which integrations or proprietary services must be replaced;
  • whether licences behave differently on another cloud;
  • internal skills and supplier capacity;
  • continuity during migration;
  • archive, retention and deletion obligations;
  • the true cost of running old and new services in parallel.

Multi-cloud is not automatically cheaper or more resilient. It can duplicate skills and controls while leaving application-level dependence untouched. Use it where the service and risk case support the additional operating complexity.

Treat hosting and data location as distinct questions

The physical or contractual location of a service affects resilience, latency, client commitments and regulation. The location of personal-data processing adds international-transfer and transparency questions.

The Data (Use and Access) Act 2025 amended parts of the UK transfer regime, with transitional provisions described in the Act’s official explanatory notes. Application depends on commencement, the organisation’s processing and the transfer mechanism. Obtain current data-protection advice rather than relying on a cloud region label.

Ask suppliers where primary, backup, support and telemetry data are processed, which sub-processors are involved and how location changes are notified. A “UK region” does not by itself answer every access or onward-transfer question.

For regulated financial services, resilience scrutiny has also intensified. In July 2026 the UK government announced Critical Third Party designations for four major cloud and technology providers. Regulated firms should interpret the regime with their compliance and operational-resilience specialists; designation does not transfer the firm’s own accountability to the provider.

Compare alternatives without using geography as a shortcut

UK or European suppliers may offer useful options for particular services. Geography alone does not establish lower price, easier compliance, resilience or portability. Compare capability, total cost, support, security, financial viability, integrations and exit on equivalent evidence.

Likewise, an established US platform may remain the best option after review. The purpose of the exercise is optionality and informed negotiation, rather than a predetermined migration.

Include hosting region, data processing, currency, price variation and transition in future platform criteria. Test the hardest dependency before signing a long commitment. A proof of concept or contractual schedule may be needed where documentation cannot settle it.

Put the board decision in commercial terms

Present current spend, drivers of forecast change, service criticality, contractual options, switching cost and risk. Distinguish facts, supplier statements and internal assumptions.

Provide options such as optimise the current service, renegotiate commitment, reduce unused scope, prepare an exit, phase a migration or consciously accept exposure. Show the cost and risk of each, including internal capacity.

If tariff changes are making you think about platform costs more seriously, there's a framework we use for assessing total cost of ownership that covers not just hosting and licensing, but the maintenance burden, the integration complexity, and the opportunity cost of being on a platform that limits what you can do next. Tariffs are the latest addition to that equation, but they're rarely the only cost that's been quietly compounding.

And if you're heading into a board conversation about digital investment or a platform review in the next quarter, that kind of analysis is what turns "we need to spend money on technology" into something the finance director can actually engage with. Worth reading alongside this, particularly if tariff exposure gives you the urgency to have a conversation that's been sitting on the backburner for a while.