Shopify Web Development Is Usually a Cleanup Job

You paid for the store once. It looks fine. The logo is right, the photos are decent, and orders come in. But your office manager still retypes addresses into a spreadsheet, the wrong shipping rate shows up on half the checkouts, and nobody can find the product that a customer swears they bought last spring.

That's the normal case. A storefront that looks good with plumbing that doesn't work. Most Shopify web development we get called into is cleanup, not construction — the theme is fine, the back end was never set up to match how the business actually runs.

So before you sign off on a rebuild, it's worth knowing which parts of your store are genuinely broken and which ones just need to be wired up properly. By the end of this page you'll be able to tell the difference.

Most Shopify stores don't need to be rebuilt

A rebuild is the easiest thing for an agency to sell. It's a clean scope, a big number, and a nice screenshot at the end. It also throws away a storefront that was probably fine and replaces it with a new one that has the same problems underneath, because nobody touched the parts that were actually failing.

The theme is rarely the issue. Products are tagged three different ways by three different people. Collections were set up once and never revisited. Shipping rules were guessed at during launch week. An app got installed for a holiday promo two years ago and still loads on every page. A new design won't fix any of that. It follows you into the new build.

When we look at a store with an owner, we go through nine areas in the same order every time:

• Product structure and tagging
• Collections and navigation logic
• Metafields and custom product data
• Shopify Flow automations
• Klaviyo and abandoned cart email
• Shipping and fulfillment routing
• App audit and page performance
• Analytics and tracking
• Staff workflows and training

Most stores have real problems in four or five of them. Almost none need a new custom store built from scratch. The work is closer to what an electrician does on an older house: the walls stay, the wiring gets pulled and run correctly.

If you're already paying for a custom website that looks the way you want, the question worth asking is which of those nine areas is costing you orders right now. The rest of this page goes through them one at a time.

What a Shopify web developer actually does

A designer decides what your store looks like. A developer makes the store do things.

Those are different jobs, and mixing them up is how owners end up paying for a new look when the problem was never the look.

Shopify stores run on a theme, and themes are built with a template language called Liquid. Liquid is what decides that a product page shows a size chart, or that a collection page hides items you're out of. Editing it is code work. The theme editor in your admin will get you part of the way, then stop.

Past the theme, development work on a Shopify web store usually means one of four things:

• Installing, configuring or removing apps, and making them work together instead of fighting each other
• Connecting Shopify to something else through an API — your accounting software, an inventory system, a supplier feed
• Changing the checkout, which on Shopify is locked down and has to be done through the tools Shopify allows
• Fixing the back end: how products are structured, tagged, routed and reported on

The front-end is what a customer sees. The back end is everything that decides what they see, what they get charged for shipping, and what email arrives after they buy.

Most of the money problems live in the back end.

Theme edits you can do yourself, and the work you shouldn't

The real test is what happens if you get it wrong. Price comes second.

Work you can safely do yourself in the theme editor:

• Swapping images, headlines and button text
• Reordering sections on a page
• Adding or editing pages, blog posts and product descriptions
• Changing colors, fonts and the logo
• Building a collection and adding products to it

All of that is reversible. Shopify keeps your published theme separate from your drafts, so you can duplicate a theme, make a mess in the copy, and publish it only when it looks right.

Work that needs a developer:

• Anything that touches checkout, tax or shipping rates
• Connecting Shopify to your accounting or inventory system
• Custom code in the theme files, including code an app asked you to paste in
• Rebuilding how products are tagged or structured across your whole catalog
• Automations that move real orders around

The line is risk to orders and money. A bad headline costs you nothing. A shipping rule that quotes the wrong price on heavy items costs you on every order until someone notices, and in ecommerce nobody notices for weeks.

One more rule worth keeping: if an app's setup instructions tell you to edit a file, stop and get help. Pasted code is the most common cause of development work we get called in to undo.

How to hire and vet a Shopify developer without knowing code

You don't need to read code to tell whether someone can do the work. You need to ask about process.

Start here:

• Ask what they'd look at first. A good answer is boring: give me read-only staff access and I'll tell you what's broken before I quote. A bad answer is a rebuild pitch before they've seen the store.
• Ask how they test changes. The answer you want involves a duplicate theme or a development store, not edits made live on a Friday afternoon. Serious shops work with Shopify CLI and version control so a change can be rolled back.
• Check the Shopify Partners directory. Anyone doing this work regularly has a Partner account. A listing proves nothing about skill on its own. Still, if a developer claims years of Shopify experience and has no listing at all, ask about it.
• Ask who owns the code. You should. Get it in writing.

Have them show you one store they fixed and explain what was wrong in plain words. If they can't say what the problem was without jargon, they probably inherited the job and guessed.

Red flags: a flat quote before anyone has logged in, pressure to move to a new theme, no written scope, and no answer on what happens if something breaks after they're paid.

Messy tags break your ecommerce filters and reports

Tags are where good stores go sideways. One product is tagged stainless, another Stainless Steel, a third ss-finish. To Shopify those are three different tags, so a filter on the collection page shows a third of your inventory and the customer assumes you don't carry the rest.

The same thing happens with product types and vendors. If half your catalog was loaded by hand and half came in on a CSV from a supplier, you have two naming systems fighting each other. Search misses items. Filters return short lists. Your reports split one product line into four rows that don't add up.

Your theme is fine. The fix is a tag cleanup: export the product CSV, sort the tag column, and decide on one name for each thing. Then reimport. On most ecommerce catalogs this is a few hours of careful work, not a redesign.

Do it in that order, too. Collections, filters, and automations all read tags. Cleaning tags first means the rest lands right the first time. And it holds whether you're on a stock theme or a custom store someone built for you three years ago.

Your front-end navigation doesn't match how customers shop

Most menus are a map of the warehouse. Brand, then supplier, then whatever got added last. Customers think in problems. A part that failed, a size they need, a job they're doing this weekend.

So they land on the storefront, open the menu, and see six brand names they've never heard of. Then they leave. No error message, no support ticket, nothing in your inbox. That's why it stays broken for years.

Here's a check you can run today. Open your own site on a phone and try to find one specific product the way a first-time customer would. Count the taps. If it takes more than three, your navigation is working against you.

Then look at your site search terms in the Shopify admin. Those words are customers telling you what the menu should have said. If people keep searching for a category that isn't in your navigation, build a collection for it. Smart collections let you do this off tags, which is why we cleaned the tags first.

Good ecommerce navigation names things the way the customer names them, not the way your supplier catalog does.

Metafields are why a custom store beats a stock theme

A metafield is an extra box you add to a product in Shopify to hold one specific piece of information. Warranty length. Voltage. Filter size. Required clearance for install. Whether the unit ships freight. Each one gets its own field instead of being mashed into a paragraph of description text.

Most stores type that information into the description, or worse, leave it in a supplier PDF nobody clicks. So a customer looking at a replacement blower motor can't tell if it fits their unit without calling you. Some of them call. Most just leave.

Once the data sits in metafields, you can print it on the page in a spec table, filter collections by it, and pull it into a quote. One place to update, every page stays right.

This is the part where a custom store earns its keep. Off-the-shelf themes give you a title, a price and a description box, which is fine for t-shirts and useless for equipment. A custom website built on Shopify can show a spec table under every product because the data is structured, not typed.

Pick your five most-called-about specs and start there.

Shopify Flow can do the busywork your staff does by hand

Somebody in your office opens every order and decides what to do with it. Is this a contractor or a homeowner? Does this item ship by freight or in a box? Is this a repeat customer who gets the trade price? That decision takes ten seconds and happens forty times a day.

Shopify Flow is a free app from Shopify that makes those decisions for you. It watches for something happening — an order comes in, stock drops, a new customer signs up — and then does what you told it to do. Tag the order. Email the warehouse. Hold it for review. Post it in the channel your crew already watches.

Useful setups we see:

• Orders containing an oversized item get tagged for freight and flagged to whoever books the truck
• Orders shipping to a PO box get held before someone ships a pallet to a mailbox
• New wholesale signups get tagged and routed to the office for approval instead of buying at retail
• Low stock on a fast mover sends a note to the person who reorders

Write down the three checks your office does by hand every morning. Those are your first three flows.

Check the app sending your abandoned cart emails

Almost every store we open has an abandoned cart email somewhere in it. Half the time it's the default one Shopify ships, still saying whatever it said the day the store went live. The other half it's a Klaviyo flow that got built during setup, never finished, and has been sitting in draft ever since.

So the carts pile up and nobody hears from them.

Log into Klaviyo and check three things. Is the flow live, or in draft? Does the email pull in the actual item the customer left behind, with its picture and price, or does it just say "you left something in your cart"? And does it go out more than once — a reminder a few hours later, then another a day or two on?

Then check the connection itself. If Klaviyo isn't properly linked to the store, the data it needs never arrives, and the flow either sends nothing or sends the wrong thing. This is the most common break we find in ecommerce email, and it's a settings problem, not a writing problem.

One more thing worth doing: turn off any other app still sending its own cart emails. Customers shouldn't get two.

Shipping rules that quote the right price at checkout

Shipping settings tend to be set once, on the day the store opened, and then never touched again. The business changes. The rates don't. So a customer in another state gets quoted a price that made sense two years ago, and someone in the office fixes it by hand after the order lands.

Watch for the signs. Staff editing shipping charges on orders after the fact. Customers emailing to ask why a small item costs so much to send. Free shipping that applies to things you can't afford to send free, like anything heavy or oversized.

Open your shipping profiles and compare them to how you actually ship today. Does every product have a weight on it? If not, weight-based rates are guessing. Are heavy or bulky items in their own profile with their own rates? If you ship from more than one place, or use a third party for part of your catalog, does the store know which location handles what?

Fulfillment routing is the other half. Orders should land at the right location without a person deciding. Every manual override at checkout is a rule that was never written, and in ecommerce those add up fast.

An app audit finds what's slowing your storefront down

Apps get installed in a hurry and almost never get removed. A review widget from two years ago. An upsell app someone tested for a week. A currency switcher for a market you stopped selling to. The subscription shows up on the bill, so owners notice that part. What they don't see is that most apps drop their own HTML, CSS and JavaScript into every page load, and some leave that code behind in the theme even after you uninstall them.

The result is a storefront that takes a beat too long to open on a phone, for features nobody uses.

An audit is a checklist you can start this week. Open your app list and write down, next to each one, what it does and who asked for it. Anything you can't answer is a candidate for removal. Then check whether uninstalling left leftover code in the theme files, because that's the part that usually gets missed.

Fewer apps also means less risk. Every app has access to your store data and can break when Shopify updates. The ones earning their keep are worth that. The rest are just sitting there.

Analytics and tracking: knowing what's actually happening on your site

Broken tracking looks exactly like working tracking. The dashboard loads. There are numbers in it. Nobody notices the numbers are wrong until someone tries to make a decision with them.

The usual causes are boring. A Google Analytics property was set up years ago and never migrated. A Meta pixel fires on page views but not on purchases, so ad reporting shows traffic and no sales. Shopify's own ecommerce tracking settings were never switched on. Two tags got installed by two different people and every order counts twice.

Here's a check you can run in ten minutes. Place a real test order on your storefront, then open your analytics and your ad platform and see whether that one order shows up once, in both, with the right dollar amount. If it doesn't, everything you've been reading is a guess.

Do this before you spend another dollar on ads. Bad data doesn't just leave you uninformed, it points you the wrong way — you cut the channel that's working because it isn't reporting, and feed the one that's double counting.

Fix the measurement first. Then decide.

Staff workflows and training: the fix that outlasts any developer

A clean tagging structure lasts about six weeks if nobody tells the person adding products what the tags mean. Then someone types "Outdoor" instead of "outdoor", the collection stops filling, and everyone decides the new setup is broken.

That's not a development problem. That's a handoff problem.

Whoever does the Shopify web development work should leave behind a short written page for each thing your office actually touches. How to add a product so it lands in the right collections. What the metafield fields are for and which ones are required. What happens when a Flow fires and what the staff member is supposed to do next. One page each, plain words, saved where the team can find it without asking.

Then walk one person through each workflow while they do it, not while they watch.

Ask any developer you hire whether training and written steps are included before you agree on a price. If the answer is vague, the answer is no, and you'll be paying again in three months to fix drift that never had to happen.

The setup is only worth what your team can keep running without you.

Start with the Free Store Checkup

You can't price a fix you haven't looked at. So we look first.

It works like this. You give us read-only staff access to your Shopify store today. Read-only means we can see everything and change nothing, so there's no risk to your live storefront while we go through it. We walk the nine areas covered above: product structure and tagging, collections and navigation, metafields, Flow, Klaviyo and cart recovery, shipping rules, installed apps and speed, analytics, and how your staff actually work the admin.

Tomorrow you get a written list. Every problem we found, in plain words, with a fixed price beside each fix. Not a range. Not an hourly estimate that grows. A number you can say yes or no to, line by line, in whatever order makes sense for your business.

Some of those lines you'll hand to your own team. Some you'll skip because the payoff isn't there yet. That's fine. The list is yours either way, whether you hire us for any of it or none of it. No retainer, no discovery fee, nothing to sign before you see it.

If it turns out you genuinely need a custom store built from scratch, we'll tell you that too. It's rarer than the people selling rebuilds would like you to believe. Most of the time the custom website you paid for is fine on the front and tangled underneath, and the cleanup costs a fraction of starting over.

Book a time and we'll get you the list.

New Project Consultation

Common questions about Shopify web development

Is Shopify still worth it?

For a trade or product business selling online, yes. The hosting, the checkout, the payment handling and the security updates are handled for you, which is most of what makes ecommerce expensive to run yourself. The platform isn't the reason stores underperform. Tagging, collections and shipping rules are.

How is Shopify Plus development different from standard Shopify?

Plus opens up parts of the platform the standard plans keep closed, including deeper control over the checkout, more automation workflows, and multiple storefronts under one account. The build work looks similar on the surface. The difference is that a Plus developer can change things that would otherwise need an app or a workaround. Most shops on a standard plan don't need Plus. If you're being told you do, ask which specific feature you're missing and what it would fix.

What does Shopify take from each sale?

There are two pieces: the monthly plan fee and the payment processing rate on each order. Third-party payment gateways add a transaction fee on top, which is why Shopify Payments usually costs less. The rates change and vary by plan and country, so check Shopify's own pricing page rather than any figure quoted in an article, including this one.

Still have a question about your own store? New Project Consultation