Shopify for Service Businesses: When It Makes Sense, When It Absolutely Doesn't

Every few months I audit a service business running on Shopify, and the story is the same. "My developer recommended it." Or "my buddy who has an online store said Shopify is the best." The site itself usually looks fine. Hero image, service list, About, Contact, and a single product called "Service Call" priced at $1 so the cart and checkout don't break. Five static pages and a fake product. They're paying $39 a month for an e-commerce platform to host a brochure.

I want to be careful here. Shopify is a genuinely great product. For SKU-based businesses (SKU is short for stock keeping unit, the unique code for each product variant), it's hard to beat. The platform handles inventory, variants, taxes, shipping zones, and global checkout in a way that would cost a custom build six figures to replicate. The question is whether any of that helps a plumber, HVAC company, or roofing contractor who doesn't sell physical products. Most of the time the answer is no, and the real cost shows up in places nobody warned the owner about.

What Shopify is genuinely great at

Crediting the platform first. Shopify has spent a decade becoming the best e-commerce operating system on the planet. Per Halothemes' 2026 platform comparison, it's moved beyond being a "store builder" into a full commerce platform built for high-volume transactions and global expansion. If you sell t-shirts, coffee, supplements, or physical SKUs, Shopify is the safest bet you can make.

What the platform does at a level no other builder matches: inventory across multiple warehouses, real product variants with their own prices and stock counts, checkout that handles tax in 50 states plus international VAT, fraud analysis on every order, multi-currency, shipping labels, abandoned-cart recovery. Shopify Plus serves brands doing nine figures a year on the same engine that runs a one-person Etsy refugee's $39-a-month store. Real engineering achievement.

None of that helps a service business. Plumbers don't have inventory. HVAC contractors don't ship. Roofers don't have product variants. The features that make Shopify the right answer for a $5 million Plus brand are precisely the ones a service business will never use.

Why do service businesses end up on Shopify in the first place?

Three reasons, in order of how often they show up in audits. A developer who only builds Shopify sites recommended it. A friend with an e-commerce store endorsed the platform. Or the owner heard "everyone uses Shopify" and assumed it was a generic website builder. None of those are dumb reasons. They're just not the right reasons for a service business.

The first pattern is developer momentum. There's a large community of Shopify-only freelancers and agencies who build Shopify themes, install Shopify apps, and write Shopify Liquid (the templating language Shopify uses for theme code). When a service-business owner walks into that community asking for a website, the answer is going to be Shopify, because that's what the developer can build. Not malicious. Just the wrong tool getting reached for.

The second pattern is social-proof drift. The owner has a friend who runs a successful product business on Shopify and says "Shopify is amazing, you should use Shopify." The advice is correct for the friend. It does not transfer to a service business, and neither person has the context to spot that.

The third pattern is theme marketplace gravity. Shopify's theme store has a few thousand templates, many of them beautiful. An owner falls in love with a design and assumes the platform underneath will work for any business type. The theme is a skin. The engine underneath is built for selling products, and the friction shows up the moment you try to make it do anything else.

What does Shopify do badly for a service business?

Five specific places where the platform fights you. Booking and scheduling, recurring service contracts, quote and estimate flows, location and service-area pages, and the basic cost-per-feature math when you're not selling SKUs. Each one is a workaround away from working. The workarounds add up.

Booking versus cart. A service business doesn't sell a thing the customer puts in a cart. They sell a time slot for a person to come do a job. Shopify has no native scheduling product. Per Shopify's own roundup of appointment-booking apps, the workaround is a third-party app like Easy Appointment Booking, Appointo, or Sesami, each running $7 to $50 a month on top of the subscription. These apps inject a scheduling widget onto a "product" page (because in Shopify everything is a product), then funnel the booking through checkout. It works. It also feels like exactly what it is, an e-commerce checkout pretending to be a service appointment.

Recurring service contracts. Maintenance plans, lawn care subscriptions, HVAC tune-up memberships. Not products with shipping addresses. Recurring service relationships. Shopify's subscription tooling was built for monthly boxes (snacks, coffee, beauty kits) where a physical thing ships every month. Bending it to handle a quarterly HVAC tune-up needs custom Liquid code or another app layer. Shopify's own CEO has publicly said the platform isn't ideal for subscription products.

Quote and estimate flows. Most home-services jobs need a custom quote. A roof, a remodel, an HVAC install. Shopify has no native quote-to-cash workflow. The available paths are a third-party "request a quote" app, an embedded form that bypasses Shopify entirely, or a hacky workaround where the customer adds a $0 placeholder to cart and writes their request in the order notes. None of these feel professional.

Service-area and multi-location pages. A growing home-services business eventually wants city pages or service-area landing pages for local SEO. Shopify is built around a product catalog, not a content sitemap. URL structure, internal linking, and schema (the structured data that tells Google what each page is about) are all optimized for products and collections. Pulling clean LocalBusiness schema across multiple service areas is a fight, the same kind covered in the Squarespace teardown.

The cost math. Shopify Basic is $39 a month, or $29 with annual billing, per Shopify's 2026 published pricing. Grow runs $105. Plus starts at $2,300. If you're a seven-figure e-commerce business, the math works. If you're five static pages and a $1 fake product, you're paying $39 to $105 a month for an e-commerce platform to host a brochure. A clean Next.js site on Vercel's free tier with Supabase free costs essentially nothing at local-business traffic levels.

How fast is a typical Shopify site, really?

Most Shopify stores score 30 to 60 on mobile Lighthouse, in the same band as Wix and Squarespace. Per a benchmark study of 1,000 Shopify stores by Shero, only 48% passed all three Core Web Vitals on mobile. Median LCP (Largest Contentful Paint, how long the biggest visible thing on the page takes to finish loading) was 2.26 seconds, right at the edge of Google's "good" 2.5-second threshold with half of stores worse. Median INP (Interaction to Next Paint, how long the page takes to visibly respond to a tap) was 153 ms.

The reason is the same as every hosted-runtime platform: Shopify ships its own framework on every page, themes add megabytes of JavaScript, and the typical store loads four to seven third-party apps each shipping their own bundles. We covered the pattern in why most local business websites are slower than they should be. The same architecture that makes Shopify reliable for 10,000 orders a minute on Black Friday is the one that ships a megabyte of JavaScript before your service site's home page can paint.

Receipts from my own rebuild. I rebuilt my permanent-lighting site (TruLight SLC) on Next.js to fix the mobile-speed gap. Old total mobile load: 4,155 ms. New: 745 ms. Old TTFB (Time to First Byte, the wait before the first byte comes back): 585 ms. New: 37 ms. Old page weight: 35.3 MB. New: 10 MB. Full breakdown at the TruLight SLC case study. The old site wasn't on Shopify, but the architectural pattern (hosted runtime, client-side hydration) is the same, and the gap to a static stack is similar.

When does Shopify actually make sense for a service business?

One specific case. You sell physical products alongside the service. A plumber selling branded repair kits. An HVAC company with a parts store. A landscape company that ships seed mixes. In those hybrid models, Shopify legitimately earns its keep on the product side.

My own business is a real example. TruLight SLC and TruLight Austin are both permanent-lighting businesses. The core offer is install: a crew installs a $2,500 to $3,500 system on a customer's house, and we own the warranty. We also sell the hardware itself: replacement clips, controllers, accessories. If I wanted to spin up a parts store for existing customers and DIY buyers, Shopify would be a defensible answer for that store. Cart, checkout, inventory, shipping all map to what Shopify was built for.

What I would not do is run the install business itself on Shopify. Service-area pages, booking flow, case studies, quote process, LocalBusiness schema. None of that fits. A clean separation works better: a modern static site at trulightslc.com for the service side, a Shopify store at parts.trulightslc.com if and when the parts business is real enough to justify the recurring cost.

The other narrow case is a productized service. Fixed-scope, fixed-price, transactional. A $99 home-inspection report. A flat-rate $299 drain cleaning. If the entire offer fits on a product page and there's no quote involved, Shopify can work. Small slice of the home-services category, but it exists.

What's the better answer for a service business that doesn't sell SKUs?

A modern static stack. Next.js on Vercel for the front end, with content in a managed database like Supabase or flat files in the repo. That combination produces sub-second mobile load, costs $0 to $20 a month at small-business traffic levels, and gives you full control over schema, internal linking, and integrations.

The trade is real. You give up the all-in-one-dashboard convenience that Shopify, Wix, and Squarespace sell. In exchange, your performance ceiling is 5 to 10 times higher than any hosted builder, you own your code in a Git repository (Git is the version-control system that lets you take the site to any host), and you get per-page flexibility.

For booking, wire in Calendly, Acuity, or GoHighLevel. For quotes, a custom intake form that posts to your CRM. For payments on the rare productized service, a Stripe Checkout link. Each integration is its own small piece chosen for its job, instead of being bent through a Shopify app that wasn't built for it.

How do you tell if you're on Shopify by mistake?

Three checks. Open your site source and search for "shopify" or "myshopify.com" in the HTML. If you find it, you're on Shopify. Next, count the actual products. If you have one called "Service Call" priced at $1, or a $0 placeholder just to keep the cart from erroring, the platform is being used as a brochure and you're paying for an engine you're not running.

Third, run your home page through Google's free PageSpeed Insights on mobile. If your LCP is over 2.5 seconds and your top three local competitors are under 1.8 seconds, that gap is showing up in your local pack rankings. The 2025 Web Almanac shows only 62% of mobile pages hit a good LCP, so a sub-1.8-second LCP is a real differentiator.

If all three checks show you're using Shopify as a brochure with a fake product and a slow front end, the rebuild conversation is on the table. Not because Shopify is bad. Because it isn't built for this.

Frequently asked questions

How much does Shopify actually cost for a service business?

Shopify Basic is $39 a month, or $29 with annual billing. Grow is $105, Advanced $399, Plus starts at $2,300. Most service businesses also pay $7 to $50 a month for a booking app plus $10 to $40 for other apps. Realistic all-in on Shopify Basic with a booking app is $50 to $90 a month, before custom development.

Can a Shopify site rank well in local search?

Yes for branded searches and low-competition category terms. Less reliably for competitive local-pack rankings. Shopify's URL structure, schema, and internal linking are optimized for product catalogs, not LocalBusiness multi-location sites. You can engineer around it with custom Liquid, but the platform's defaults work against you the same way Squarespace's do, covered in the Squarespace post.

If I'm on Shopify and it's working, should I leave?

Probably not, especially if you have a genuine product side and the booking side is working. Switching for the sake of switching is how owners burn three months on a project that didn't need to happen. Run an audit first. The conversation changes if you're paying for ads and the landing page isn't converting, or if your mobile LCP is over three seconds and the local pack is filling up with faster competitors.

What's the right call for a hybrid business with both products and services?

Run two sites on the same brand. A modern static site for the service business at the main domain, optimized for local SEO and lead capture. A Shopify store at a subdomain (parts.yourbrand.com) for the actual product side, where Shopify's e-commerce strengths matter. The common mistake is cramming both into a single Shopify site, where the service side ends up grafted onto an e-commerce template that wasn't designed for it.

If you're on Shopify reading this, you probably already know which version of the story is yours. Either you have a real product business that should stay put, or you have five static pages and a $1 fake product and the rent is buying you nothing your business uses. The free Front Door Score will tell you the size of the gap.