Do it yourself,
until this line.

01 · Solo

No developer needed for any of this.

• Setting up the store, products, collections, variants and inventory.
• Choosing and configuring a theme, including colours, fonts and homepage layout.
• Building pages from sections on any template, since Online Store 2.0.
• Payments, shipping rates, taxes and policies.
• Installing and configuring apps.
• Basic markets and currency setup.
• Writing the copy, which matters more than most design decisions.

If your store is products, collections, a homepage and a checkout, you are done. Hiring at this stage buys taste and time, not capability.

02 · The line

Four points where a developer pays for itself.

1. The store needs something no theme does. A configurator, a stockist map, pack tiers, a made-to-order flow. This is a section that does not exist yet, and no amount of settings will conjure it.

2. Speed has become a revenue problem. Diagnosing why a store is slow means reading what actually loads and in what order. It is measurable, unglamorous work, and it is not a setting.

3. You are moving platforms or restructuring URLs. Migrations are where irreversible mistakes live: lost redirects, broken product handles, orphaned collections. This is the cheapest place to buy expertise and the most expensive place to learn.

4. Apps are fighting each other. Three apps injecting into the same product page, each half-working. Untangling that requires reading the code they left behind, not toggling settings.

03 · Hard stops

Do not do these alone.

Editing theme code directly on the live theme, with no copy. It is the single most common way a store goes down, and the fix is free: duplicate first.

Pasting scripts from a blog post into theme.liquid. It works until it silently does not, and by then nobody remembers what was pasted or why. Tracking belongs in customer events, not in theme files.

Bulk-editing product data without an export first. There is no undo.

Changing URL structure without mapping redirects. Search rankings and existing links attach to addresses.

04 · Symptoms

You have crossed the line when...

• You have installed a third app to fix what the first two broke.
• A change you make in one place undoes a change somewhere else.
• You are pasting code you do not understand and hoping.
• The thing you need has no setting anywhere, and the theme documentation does not mention it.
• You are spending evenings on the store instead of on the business.

That last one is the real economics. The cost of doing it yourself is rarely the mistake; it is the fortnight.

05 · Hiring

Hire in bounded pieces.

The safest first engagement is small, specific and finishable: one section, one fix, one audit. It tells you how someone works before anything large is at stake, and a good developer will happily quote a bounded job. We publish fixed-scope prices from $299 for exactly this reason.

Ask three questions of anyone you are considering. What will I be able to change myself afterwards? What do I receive at handover? What happens if something breaks in a month? Vague answers to those three are more informative than any portfolio.

Quick check

Before you commit.

• The task is one of the four, not simply unfamiliar.
• The live theme is duplicated before anyone edits code.
• Product data is exported before any bulk edit.
• The first engagement is small and finishable.
• You know what you can change yourself afterwards.
• Handover includes documentation and source access.

Hire for the wall, not for the whole store.

Most merchants need a developer four times, not continuously. Knowing which four keeps the bill small and the store yours.

Questions

Questions people ask.