Shopify Retainer Scope: What Ongoing Development Should Cover in 2026

Most Shopify retainer proposals list hours and “updates included.” This guide scopes ongoing development around what your store actually runs and how Shopify changed in 2026: the end of Shopify Scripts, the Thank you page upgrade, quarterly API versions, theme updates, performance monitoring, and the terms to agree in writing.

Yuval Tsabari עודכן ב- 20 באוק׳ 2026

Most Shopify retainer proposals read like a menu: bug fixes, theme updates, app updates, priority support, a block of hours. That tells you what a vendor sells. It doesn't tell you what your store needs to keep working, and improving, while Shopify keeps changing underneath it.

2026 made that gap hard to ignore. Shopify Scripts stopped running on June 30. The deadline to upgrade Thank you and Order status pages passed on August 26, and stores that hadn't upgraded were upgraded automatically. Shopify's Spring '26 Edition shipped more than 150 updates on June 17. And Shopify's API schedule lists October 16, 2026 as the last day version 2025-10 is accessible. None of these is a reason to panic. All of them are reasons to define what ongoing development actually covers.

This guide is for ecommerce decision-makers, and for agencies, scoping a Shopify development retainer. It covers what to include, what to keep out, and which terms to agree in writing before you sign.

Short answer: A useful Shopify retainer covers six things. (1) An inventory of the store's theme, apps, custom code, integrations, and tracking. (2) A watch on Shopify's platform changes: quarterly API versions, deprecations, and Editions. (3) Theme and app upkeep, tested in a draft theme before anything goes live. (4) Monitoring of performance and tracking, with changes logged so you can tell what happened when. (5) A prioritized improvement backlog for UX and CRO work, not only fixes. (6) Written terms for hours, response times, coverage, access, reporting, and exit.

1. Start with an inventory, not a number of hours

The first question in most retainer conversations is "how many hours a month?" It's the wrong place to start. You can't size ongoing work until someone has documented what is actually running on the store. A first-month inventory should cover:

Theme: which theme it is, where it came from (Shopify Theme Store, a third-party designer, or a custom build), its version, and whether its code has been edited.
Apps: every installed app, what it does, whether it injects code into the theme, and whether anyone still uses it.
Custom apps and integrations: ERP, inventory, reviews, subscriptions, or anything else connected through the Admin API, plus which API version each one requests.
Checkout and post-purchase: checkout extensions, Shopify Functions, and any discount, shipping, or payment logic that used to live in Shopify Scripts.
Tracking: analytics, ad pixels, and conversion events, including what fires on the Thank you and Order status pages.
Access: who has staff or collaborator accounts and why.

The inventory should also explain why each customization exists. A theme edit might support an important buying decision, or it might be a workaround nobody needs anymore. Before changing or removing anything, document its purpose, dependencies, and owner. This gives the team enough context to maintain the store without accidentally undoing something the business relies on.

2. Put Shopify's change calendar in scope

Shopify changes on a schedule, and several of the changes below were announced months before they took effect. A retainer should name who watches those changes and checks whether they affect your store. These are the dated changes from the last 12 months that show why:

Date	What Shopify changed	What a retainer should check
January 1, 2026	New custom apps can no longer be created in the Shopify admin. Existing ones keep working; new ones are built in the Dev Dashboard.	Where future custom integrations will be built, and who owns them.
April 15, 2026	Shopify Scripts could no longer be edited or published.	Which discount, shipping, or payment rules depended on Scripts.
June 17, 2026	The Spring '26 Edition announced 150+ updates.	Which updates are relevant to the store, and which can safely be ignored.
June 30, 2026	Shopify Scripts stopped executing. Published scripts were deactivated.	That each rule still needed was rebuilt with Shopify Functions or an app, and tested.
August 26, 2026	Deadline to upgrade Thank you and Order status pages. Stores not upgraded were upgraded automatically.	That post-purchase tracking and customizations still work on the upgraded pages.
October 16, 2026	Last day Admin API version 2025-10 is accessible, according to Shopify's schedule.	Which integrations request that version or older ones.

The API schedule deserves a closer look because it repeats every quarter. According to Shopify's API versioning documentation, a new version is released every three months, and each stable version is supported for at least 12 months. When an app targets a version that is no longer accessible, Shopify "falls forward" and answers with the oldest accessible stable version. In practice, an old integration may not fail loudly. It may simply start receiving responses from a newer version than it was built for. Shopify recommends updating to the latest stable version each quarter.

That makes a quarterly check a reasonable retainer line item: list every custom integration, the API version it uses, and any deprecation notices for it. Shopify notes that deprecations are announced in the developer changelog, and for app developers, as alerts in the Dev Dashboard.

Scripts are a good example of a change that needed active work. Shopify's Help Center guide to transitioning to Shopify Functions points merchants to a Shopify Scripts customizations report in the admin. It lists the customizations that were active before the deprecation, along with recommended apps or Function APIs to recreate them. If nobody has reviewed that report for your store, that is a concrete first task.

3. Define how theme and app updates are handled

"Theme updates included" can mean very different things. Shopify's guide to updating themes explains some details that should shape the scope:

Updates in the admin are only available for themes installed from the Shopify Theme Store. Themes bought elsewhere get updates from their designer, and vintage themes are no longer updated.
An update is added as a draft theme, so it can be reviewed before it's published.
Theme editor customizations are copied over. Code edits are only included if they don't conflict with the update. If they can't be included, they have to be copied into the new version by hand.
Some apps might not be compatible with a new theme version.

So a heavily customized theme can turn a "free" update into real development work. The retainer should say who decides whether an update is worth applying, how it's tested, and how custom code is preserved.

Apps need the same treatment. Each app that writes to the theme or runs on checkout is another dependency that can change. A periodic app review, covering what's installed, what's still used, and what could be removed, can be a better use of retainer hours than adding more.

4. Monitor performance and tracking, and log every change

Shopify's web performance reports use real user data to show how a store performs on Core Web Vitals: loading speed, interactivity, and visual stability. The over-time reports add annotation tags for potential changes in your store, and Shopify says they show how changes such as app installs, theme updates, and new code affected each metric. Two limits matter for a retainer: Shopify says the data can be delayed by up to 36 hours, and it's only available for the last 90 days. That makes the reports a useful free baseline, but not a long-term record.

Two habits make this monitoring useful:

Keep your own change log. Every release, app install, theme update, and campaign launch gets a date. When a metric moves, you have a list of what changed around the same time, even after the report's 90-day window has passed.
Separate the observation from the diagnosis. "Mobile loading speed got worse after June 20" is an observation. "The new reviews app slowed the product page" is a diagnosis, and it needs evidence before anyone acts on it. Traffic mix, campaigns, seasonality, and several releases can all overlap in the same week.

Tracking deserves its own check after each platform change. The Thank you page upgrade is a good example: if conversion events were set up through additional scripts, someone should confirm that each event still fires after the upgrade, rather than assuming it does.

For practical speed and UX fixes, see our guide to Shopify store speed and UX.

5. Reserve capacity for improvement, not just maintenance

A retainer that only reacts keeps the store running. It doesn't make the store better. Many teams distinguish between a maintenance retainer and a growth retainer. Whichever you choose, the scope should say how much capacity goes to each kind of work:

Maintenance: fixes, platform-change work, theme and app upkeep, monitoring.
Improvement: UX and CRO work such as product page changes, navigation, collection merchandising, cart and checkout friction, and landing pages for campaigns.

Improvement work should come from a prioritized backlog, and each item should record the evidence behind it. That evidence could be analytics, session recordings, customer feedback, or a usability review. Each item should also say what will be measured after release. That's what separates a roadmap from a list of opinions. Our Shopify conversion rate optimization guide covers how to find and prioritize those opportunities.

A practical way to prioritize is to address problems that prevent purchases or undermine reliable measurement, then assess improvements by customer impact, supporting evidence, and implementation effort. Analytics can show where shoppers drop off; a UX review helps identify what might be confusing or missing at that point. Consumer psychology provides hypotheses about hesitation, trust, and decision-making, which should be tested against customer behavior. Each task should connect a specific problem to a change and a measurable outcome.

6. Plan releases around your calendar

In 2026, Black Friday falls on November 27 and Cyber Monday on November 30. If your retainer starts in the fall, agree early on two things: the last date for significant changes before the peak season, and what counts as an emergency fix during it. The right lead time depends on the store, the size of the change, and how it's tested, so set it with your development partner rather than copying someone else's.

The same applies all year. Ask how releases are prepared and checked before they go live, how they're scheduled around campaigns, and how a change can be reversed if something goes wrong. Get the answers in writing as part of the engagement.

Before BFCM, separate changes needed for the campaign from experiments that can wait. Prioritize testing promotional pricing, discount combinations, inventory behavior, shipping options, payment methods, and purchase tracking. Schedule larger changes early enough to allow a full review and a rollback if needed. As the campaign approaches, keep releases focused and make sure everyone knows who handles urgent issues and who can approve a production change.

7. Agree the terms in writing

There's no standard Shopify retainer. Terms vary by provider and by engagement, which is why they belong in writing. Before signing, confirm:

Capacity: what's included each month, how unused time is handled, and how extra work is approved and billed.
Response times and coverage: how quickly different types of issue get a response, which days and hours are covered, and how much working-hour overlap you'll have with the team.
Access: which accounts and permissions the developer needs. Shopify Partners usually work through collaborator accounts, with permissions the merchant approves. According to Shopify, collaborator access expires automatically if the collaborator hasn't logged in for 90 days, which can matter in a quiet month.
Reporting: what you'll see each month, such as work completed, time used, open issues, and upcoming platform changes.
Scope boundaries: what is quoted as a separate project. Redesigns, new builds, and platform migrations such as a WooCommerce to Shopify migration usually need their own scope.
Exit and handoff: how access is removed, and how code, documentation, and the change log are handed over if the engagement ends.

For agencies: if you're bringing in a white-label partner to cover retainer work for your clients, add confidentiality, client communication, and subcontracting to the list, and agree them per engagement.

Retainer, project, or hourly?

A project fits work with a clear finish: a new build, a redesign, or a migration.
Hourly or ad hoc work can suit a stable store with occasional, predictable requests.
A retainer fits when work keeps arriving: regular campaigns, ongoing UX and CRO testing, custom integrations that need quarterly checks, or a team that wants the same developers to keep context on its store.

Many stores combine them: a retainer for ongoing work, with larger initiatives scoped as separate projects.

Shopify retainer scope checklist

Inventory of theme, apps, custom apps, integrations, checkout customizations, tracking, and access
Named owner for watching Shopify's changelog, API versions, deprecations, and Editions
Quarterly check of the API versions used by custom integrations
Review of the Shopify Scripts customizations report, if the store used Scripts
Post-purchase tracking checked on the upgraded Thank you and Order status pages
Theme update process: draft theme, review, custom code preserved
Periodic app review
Scheduled review of web performance reports, plus a dated change log
Prioritized UX/CRO backlog with evidence and success measures for each item
Agreed release timing around campaigns and BFCM
Written terms for capacity, response times, coverage, access, reporting, scope boundaries, and exit

FAQ

What should a Shopify retainer include?

At minimum: maintenance of the theme, apps, and integrations; monitoring of performance and tracking; and someone responsible for Shopify's platform changes. A growth-focused retainer also reserves capacity for UX and CRO improvements from a prioritized backlog. The exact scope should come from an inventory of your store.

Is a Shopify retainer worth it for a smaller store?

It depends on how often work comes up. If requests are rare and the store is simple, ad hoc work may be enough. If you run regular campaigns, rely on custom integrations, or want continuous UX and CRO work, a retainer gives you continuity with people who already know the store.

What isn't usually included in a Shopify retainer?

Large projects with a defined finish, such as redesigns, new builds, and migrations, are usually scoped separately. Third-party app fees are often excluded as well. Confirm the boundaries in writing for your engagement.

Why do Shopify API versions matter for a retainer?

Shopify releases a new API version every quarter and supports each stable version for at least 12 months. Custom integrations need to be checked and updated over time, and someone has to own that work.

Need ongoing Shopify development?

Dominatecom is a Shopify Select Partner. We provide Shopify and Shopify Plus development and ongoing support, alongside UX/UI design and CRO, so ongoing work can cover both upkeep and improving the buying experience. Dominatecom is led by Yuval Tsabari, a UX designer who combines analytics and consumer psychology.

Engagements can be project-based or ongoing, for merchants and, on a white-label basis, for agencies. Scope, response times, support coverage, and working-hour overlap are agreed as part of each engagement.

Talk to us about ongoing Shopify development →