I have signed agency contracts as a client, and I have written them as an agency owner. That dual perspective has given me an uncomfortable clarity about how the industry operates: most ecommerce agency contracts are written to protect the agency, not the client.
This is not necessarily malicious. Agencies use template contracts drafted by their lawyers, and lawyers default to protecting the party that pays them. But the result is the same: brand owners sign agreements containing clauses they do not fully understand, and those clauses come back to haunt them when things go wrong — or when they simply want to move on.
This article walks through the ten most common contract red flags I see in ecommerce agency agreements, explains why each one matters, and tells you what to negotiate instead.
Why the contract matters as much as the portfolio
Most brand owners spend weeks evaluating an agency's portfolio, references, and capabilities, then spend fifteen minutes reviewing the contract before signing. This is backwards. A great portfolio tells you what the agency can do. The contract tells you what they will do — and what happens when things do not go to plan.
I have seen brands trapped in twelve-month contracts with agencies delivering mediocre work. I have seen brands unable to take their own store's code to a new developer because the contract assigned IP ownership to the agency. I have seen brands pay £15,000 in "exit fees" for a store they already paid to build.
Every one of these situations was avoidable. The warning signs were in the contract. The brand owners just did not know what to look for.
If you are evaluating agencies now, read our guide on how to choose a Shopify agency in the UK alongside this article. Together, they cover both sides of the evaluation process: capabilities and contractual terms.
Red flag 1: You do not own the code
This is the single most important clause in any agency contract, and the one most frequently overlooked. Intellectual property (IP) ownership determines who owns the custom code, design assets, and content created during the project.
The red flag
The contract states that the agency retains ownership of all intellectual property created during the engagement, with a licence granted to the client for use of the deliverables. Some contracts use softer language — "the agency retains rights to reusable components" or "proprietary frameworks remain agency property" — but the effect is the same: you do not fully own what you paid for.
Why it matters
If you want to switch agencies, your new developer may not be able to work with the existing codebase without the original agency's permission. In extreme cases, agencies have threatened legal action against clients who took "their" code to a competitor. More commonly, the agency charges a "code release fee" or "handover fee" to provide access to files you thought you already owned.
What to negotiate
The contract should state that all custom code, design files, and content created specifically for your project are assigned to you upon final payment. The agency may reasonably retain rights to their pre-existing frameworks, libraries, and tools — but these should be explicitly listed, and you should receive a perpetual, irrevocable licence to use them within your project.
Red flag 2: Excessive lock-in periods
Lock-in periods are common in retainer and managed service agreements. They guarantee the agency a minimum revenue commitment. Some lock-in is reasonable — agencies invest time in onboarding and learning your business. But excessive lock-in periods shift the power balance entirely to the agency's side.
The red flag
Contracts requiring 12-24 month minimum commitments for ongoing services, particularly when combined with auto-renewal clauses that extend the term unless you provide notice 60-90 days before the end date. Some contracts include early termination penalties equal to the remaining contract value — meaning you pay for months of work that will never be delivered.
Why it matters
A twelve-month lock-in with a 90-day notice period means you effectively need to decide whether to continue at the nine-month mark. If the agency's work has been mediocre but not terrible, you are in a difficult position: commit to another year, or pay a penalty to leave. We have written extensively about this pattern in our article on how to tell if your ecommerce agency has locked you in.
What to negotiate
For project work, there should be no lock-in period beyond the project itself. For ongoing retainers, a three-month initial commitment is reasonable, rolling to monthly thereafter with 30 days' notice. If the agency insists on a longer commitment, the contract should include performance benchmarks that trigger a right to terminate without penalty if targets are consistently missed.
Red flag 3: No scope change process
Every ecommerce project involves scope changes. New requirements emerge during discovery. Stakeholders request additions. Market conditions shift. The question is not whether scope will change, but how those changes are handled contractually.
The red flag
The contract either does not address scope changes at all, or handles them with a vague statement like "additional work will be charged at the agency's standard rates." There is no defined process for requesting, estimating, approving, or documenting scope changes. This creates a situation where the agency can bill for additional work without your explicit approval, or where disputes arise because there is no record of what was agreed.
Why it matters
Without a clear scope change process, you lose budget control. I have seen projects where the final invoice was 40-60% higher than the original quote, with the agency pointing to emails and Slack messages as "approvals" for additional work. The brand owner had a different understanding of what was included in the original scope, and there was no clear documentation to resolve the dispute.
What to negotiate
The contract should include a formal change request process: any work outside the original scope must be documented in a written change order that specifies the additional work, the cost, the timeline impact, and requires your written approval before work begins. This protects both parties and eliminates the ambiguity that leads to disputes.
Red flag 4: Front-loaded payment terms
Payment structure reveals an agency's confidence in their own work. Agencies that deliver consistently are happy to tie payments to milestones. Agencies that do not want their payment tied to deliverable milestones — that should tell you something.
The red flag
The contract requires 50-100% payment upfront before any work begins, with no milestone-based payment structure. Alternatively, the payment schedule is heavily front-loaded: 50% deposit, 40% on design approval, 10% on launch — meaning you have paid 90% before the most complex and risk-heavy phase (development) begins.
Why it matters
If you have paid 90% of the project fee before development starts, you have very little leverage if the quality is poor, the timeline slips, or the agency becomes unresponsive. Your money is already spent. The agency's financial incentive to deliver promptly and to a high standard diminishes with every payment received before work is completed.
What to negotiate
A fair payment structure for a Shopify development project looks like this: 25-30% deposit to commence work, 25-30% on design approval, 25-30% on development completion and staging site approval, and 10-20% on launch. Each payment should be tied to a specific, verifiable deliverable. This keeps both parties aligned: you pay for work completed, and the agency has cash flow throughout the project.
Red flag 5: Vague deliverables
The scope of work is the most important section of the contract after IP ownership. It defines what you are paying for. Vagueness here benefits the agency, not you.
The red flag
Deliverables are described in broad terms: "custom Shopify theme development," "SEO optimisation," "email marketing setup." There are no specific page counts, functionality lists, integration specifications, or acceptance criteria. The contract might say "responsive design" without specifying which breakpoints, or "SEO setup" without defining what that includes.
Why it matters
When deliverables are vague, disputes are inevitable. You expected a custom product page with a size guide, ingredient list, and video gallery. The agency built a standard product page template and considers the job done. Both parties are right according to their own interpretation. The contract should have prevented this ambiguity.
What to negotiate
Insist on a detailed scope document as an appendix to the contract. This should list every page template, every custom feature, every integration, and every third-party service to be configured. Include wireframes or reference examples where possible. Specify acceptance criteria for each deliverable — measurable standards that determine whether the work is complete. For example: "Mobile PageSpeed score of 85+" is an acceptance criterion. "Good performance" is not.
When it comes to web design deliverables, specify the number of design concepts, revision rounds, and the formats in which design files will be delivered.
Red flag 6: Unreasonable liability caps
Liability clauses define who bears the financial risk if something goes wrong. They are the clauses that matter most when they are needed most — and they are the clauses most brand owners skip over.
The red flag
The agency's total liability is capped at the fees paid in the preceding month, or at a nominal amount like £1,000. This means that if the agency's negligence causes your store to go down for a week during peak trading, resulting in £50,000 in lost revenue, their maximum liability is the cost of one month's retainer — perhaps £2,000-£3,000.
Why it matters
A liability cap that is disproportionately low relative to the potential damage transfers all meaningful risk to you. While unlimited liability is unreasonable to expect from any agency, the cap should be proportionate to the size of the engagement and the potential consequences of failure.
What to negotiate
A reasonable liability cap for a project-based engagement is the total project fee (or 100-150% of the total fee). For ongoing retainers, liability capped at 12 months' fees is standard. The contract should also specify that this cap does not apply to certain categories of loss: data breaches, IP infringement, and wilful misconduct should typically be excluded from any cap.
Red flag 7: No service level agreement
For ongoing support and managed services, a service level agreement (SLA) defines the agency's response time and resolution time commitments. Without one, "support" means whatever the agency decides it means on any given day.
The red flag
The contract promises "ongoing support" or "priority access" without defining response times, resolution targets, support hours, or escalation procedures. There is no distinction between critical issues (store down, checkout broken) and minor requests (text change, image swap).
Why it matters
Without an SLA, a critical issue during Black Friday could sit unaddressed for 48 hours while the agency prioritises other clients. You have no contractual basis to demand faster resolution because "support" was never defined. For brands doing £250,000+ in annual revenue, every hour of downtime during peak trading costs real money.
What to negotiate
The SLA should define issue severity levels (Critical, High, Medium, Low), response time targets for each level (Critical: 1-2 hours, High: 4-8 hours, Medium: 1-2 business days, Low: 3-5 business days), resolution time targets, support hours (business hours, extended hours, or 24/7), and escalation procedures. It should also specify what happens if SLA targets are consistently missed — typically a right to terminate or a service credit.
Red flag 8: Data retention after termination
What happens to your data — customer records, order history, product information, analytics, email lists — when the relationship ends? This is one of the least discussed but most consequential aspects of agency contracts.
The red flag
The contract does not address data handover at all, or includes vague language about "reasonable assistance" with transition. Some contracts allow the agency to retain copies of your data indefinitely. Others specify a data handover process but charge a fee for it — sometimes substantial.
Why it matters
If your email marketing is managed through the agency's Klaviyo account, switching agencies means potentially losing your entire subscriber list, flow performance history, and segmentation data. If your store is on the agency's Shopify partner account, they control access to your admin. We have seen agencies hold data hostage during acrimonious separations, and the brand had no contractual recourse.
What to negotiate
The contract should mandate complete data transfer within 14-30 days of termination, at no additional cost. Specify that all accounts (Shopify, Klaviyo, Google Analytics, Search Console, social media, advertising) are owned by you and registered under your business email, not the agency's. If the agency insists on using their partner accounts, the contract must specify a zero-cost handover process with defined timelines.
Red flag 9: Silent auto-renewal
Auto-renewal clauses are common in subscription and retainer agreements. They serve a legitimate purpose: ensuring continuity of service without the administrative overhead of re-signing every period. But they can also trap you into extended commitments you did not intend to make.
The red flag
The contract auto-renews for the same term length (often 12 months) unless written notice is provided 60-90 days before the renewal date. The agency has no obligation to remind you of the upcoming renewal. Some contracts include price increase clauses that take effect on renewal — meaning your retainer fee increases automatically unless you actively terminate and renegotiate.
Why it matters
A twelve-month contract with 90-day notice and silent auto-renewal means you have a 90-day window to exit — starting nine months after you signed. Miss that window, and you are committed for another twelve months. Combined with early termination penalties, this creates a rolling trap that is difficult to escape.
What to negotiate
Either remove auto-renewal entirely (the contract continues on a rolling monthly basis after the initial term), or limit auto-renewal to monthly rolling periods with 30 days' notice. If the agency insists on term-based renewal, require written notification at least 30 days before the notice deadline. Any price increases should require your written agreement, not default to acceptance.
Red flag 10: Non-compete or exclusivity clauses
Some agency contracts include clauses restricting your ability to work with other providers, either during the engagement or for a period after termination. These range from reasonable (not hiring the agency's staff) to outrageous (not using any other digital service provider).
The red flag
The contract prevents you from engaging other agencies or freelancers for any digital work during the contract term. Alternatively, it includes a non-compete clause preventing you from hiring an agency that "competes" with the current one for 6-12 months after termination. Some contracts even restrict you from hiring freelancers who have worked for the agency.
Why it matters
Exclusivity clauses prevent you from getting the best provider for each aspect of your digital presence. Your SEO provider might be excellent, but their paid advertising capability might be weak. An exclusivity clause prevents you from hiring a specialist paid media agency without violating the contract.
What to negotiate
Remove exclusivity clauses entirely unless they are narrowly defined and genuinely necessary. A reasonable restriction is a mutual non-solicitation clause preventing either party from poaching the other's employees for 12 months after termination. Broader exclusivity has no place in a modern agency-client relationship.
What a fair contract looks like
After highlighting what to avoid, here is what a well-structured ecommerce agency contract should include. Use this as a checklist when reviewing any agreement.
Scope of work
- Detailed deliverables list with acceptance criteria
- Defined project phases with milestones
- Specific exclusions (what is not included)
- Formal change request process
Intellectual property
- Full IP assignment of custom work upon final payment
- Perpetual licence for pre-existing agency frameworks
- Clear definition of what constitutes "custom" vs "pre-existing"
Payment
- Milestone-based payment tied to deliverables
- Clear invoicing schedule with 14-30 day payment terms
- Defined process for scope change billing
- No hidden fees or undisclosed rate increases
Timeline
- Realistic project timeline with phase durations
- Client responsibilities and response time expectations
- Process for handling delays (from either party)
- Force majeure provisions
Support and SLA
- Defined support hours and channels
- Severity levels with response and resolution targets
- Escalation procedure
- Remedy for consistent SLA failures
Termination
- Reasonable notice periods (30 days for retainers)
- Right to terminate for cause without penalty
- Defined data handover process and timeline
- Payment for completed work only upon termination
- No punitive exit fees
Liability and indemnity
- Proportionate liability cap (total project fee minimum)
- Mutual indemnification for IP infringement
- Professional indemnity insurance confirmation
- Exclusions from cap for data breaches and wilful misconduct
Understanding what a fair contract looks like is particularly important when evaluating what a Shopify store build should cost. The cheapest quote often comes attached to the most restrictive contract, because the agency plans to make their margin on lock-in and change requests rather than on delivering excellent work.
When to walk away
If an agency refuses to negotiate on IP ownership, insists on punitive termination penalties, or will not provide a detailed scope document, walk away. These are not negotiating positions — they are business model choices. The agency has structured their operation around locking clients in and extracting maximum value from each relationship. No amount of portfolio quality or sales charm compensates for a contract designed to work against you.
Conversely, an agency that is transparent about their terms, willing to discuss and adjust clauses, and proactive about protecting your interests as well as their own is demonstrating how they will behave throughout the engagement. The contract negotiation is a preview of the working relationship.
I have a simple test for agency contracts: would I be comfortable if the roles were reversed? If a clause would frustrate me as the client, it has no place in our agreements. Contracts should create alignment, not leverage.
Agency contracts do not need to be adversarial. They should be clear, fair, and designed to create alignment between both parties. If your current or prospective agency's contract fails that test, use this article as your negotiation guide.
If you would like to discuss a project with an agency that puts transparency first, start a conversation with us. We will show you our standard terms upfront — no surprises.
