Technical · 5 min read
A Shopify Liquid theme handoff checklist for agencies
What a custom Shopify theme handoff should include: store access, theme settings, sections, app list, redirects, testing and documentation.
November 4, 2026
Key takeaways
- A handoff is the moment someone else becomes responsible for the store; make it a checklist, not an email.
- The store belongs to the client from day one, so handoff means closing access, not transferring a store.
- Make every section editable in the theme editor and write a one- or two-page guide for non-developers.
- Agree who handles fixes after launch before the first request arrives.
A handoff is not the moment the build ends. It is the moment someone else becomes responsible for the store. If you are the agency, that someone is you and then your client. Here is the checklist we use to make sure a custom Shopify theme can be run by people who did not write it.
1. The store belongs to the client
The store should live in the client’s own Shopify account from day one, with the build partner working through staff or collaborator access. Handoff then means closing that access, not transferring a store. Confirm who is the account owner, who else has access, and that ours ends at launch. Shopify’s help pages on staff accounts and collaborator access show how access is granted and removed.
2. The theme code
- The live theme is the finished theme, and the version in the admin matches what was approved.
- The theme is written in Liquid with clear section and snippet names that describe what they do.
- You hold a copy of the final theme files, so the code does not exist only in one account.
- Anything unusual (custom logic, workarounds) is commented where it happens.
3. Editing without a developer
- Every section the client will want to change is available in the theme editor, with sensible labels.
- Default content is replaced with real content or deliberately blank.
- Settings for colours, fonts and key layout choices are exposed where it makes sense, not hard-coded.
4. Apps and integrations
- A list of every installed app: what it does, which account holds the subscription, and where its settings live. See who pays for Shopify apps.
- Any app that adds code to the theme is noted, so removing it later is not a surprise.
- Shipping, tax, payments and email settings are confirmed with the client, not assumed.
5. Testing before the client sees it
- Product pages with each type of variant, cart, checkout and a real test order.
- Mobile first, then desktop; the main browsers.
- Forms, newsletter signup and emails arrive where they should.
- Page speed checked on key pages, with the numbers saved as a baseline.
6. Redirects and SEO
- If URLs changed, redirects are in place and tested; see Shopify’s guide to URL redirects.
- Titles and descriptions for key pages are set; the sitemap and analytics are connected.
- Nothing that should be hidden from search is accidentally live.
A one-page handoff sign-off
| Item | Done | Notes |
|---|---|---|
| Store ownership and access confirmed | Who is owner, who has access | |
| Final theme matches approved version | ||
| Copy of theme files delivered | ||
| Sections editable in the theme editor | ||
| App list with subscription holders | ||
| Test order completed | ||
| Redirects tested | ||
| Speed baseline saved | ||
| Guide for the client delivered | ||
| Post-launch support agreed |
7. Documentation your client can use
A short document, written for a non-developer: how to add a product, change the homepage, edit a section, where the apps are managed, who to call. One or two pages is enough, and it is the part clients actually appreciate.
8. What happens after launch
Agree who handles fixes and changes next, and how. Without it, the first small request becomes an argument. Our guide to scoping a Shopify build shows how to define the boundary. To choose the right foundation in the first place, read custom Shopify theme vs template.
How we hand off
We build custom-coded Shopify themes under your brand, close our access at launch, and let you review the build before your client sees it. See white label Shopify development, the white label Shopify agency page and how we work. If you want a build handled this way, get in touch.
Frequently asked questions
Who should own the Shopify store?
Do we need the theme files if the theme is live?
How long should handoff take?
Who fixes things after launch?
Sources and further reading
- Shopify: Liquid reference — the template language Shopify themes use.
- Shopify: theme architecture — how layouts, templates, sections and snippets fit together.
- Shopify: sections — making content editable in the theme editor.
- Shopify: themes — the official overview of themes.
- Shopify: theme performance best practices — what to measure at handoff.
- Google: 301 redirects — how redirects work for search.
Ready to talk?
Looking for a white label web partner you can actually rely on?