A $3,200 fixed quote for a Shopify build is rarely cheaper than a $14,000 one. It's smaller. Somebody sat down with your requirements, mentally deleted the four or five line items you can't see from the outside, and priced what was left. The most useful of the Shopify developer red flags isn't a bad portfolio or a typo in the proposal. It's a quote that has no line for QA, no line for redirect mapping, no line for tax and checkout testing, and no mention of accessibility. Those four omissions are worth more than the discount, and you pay for them in the eight weeks after launch instead of the eight weeks before it.
This is how we read a lowball estimate when a merchant forwards one to us for a second opinion.
A real scope has boring line items. A cheap one doesn't.
Design, theme development and app setup are the visible parts of a build. Every quote has them, because those are the things a founder knows to ask about. The variance between a $3,200 quote and a $14,000 quote is almost never in those rows. It's in the rows nobody asks for:
- Cross-browser and device QA with a written test matrix, plus a bug-fix window after handover
- URL inventory and 301 redirect mapping, if anything is migrating
- Checkout testing across the payment methods you actually accept, with real test orders
- Sales tax configuration: nexus states, product tax codes, shipping taxability
- WCAG 2.1 AA work on the templates, not just an overlay widget
- Analytics and conversion tracking validation after launch, not before
- A performance budget, so the theme doesn't ship at a 4-second LCP on mobile
Ask for the quote as a table with hours against each task. A developer who works this way will send it in a day. A developer who priced your project by feel will send you a paragraph, and that's your answer.
What each dropped line item costs a US merchant after launch
Take redirects, since it's the easiest one to price.
Say you're moving off BigCommerce or a WooCommerce install with 900 products and 40 collection pages. The URL patterns change. Your developer skips the mapping because it's tedious and it's the line item no client has ever queried. Now suppose you do 30,000 organic sessions a month, and 3,800 of them land on product and collection URLs that no longer exist. At a 2.1% conversion rate and a $68 average order value, that's 3,800 × 0.021 × 68 = $5,426 a month, gone, until someone rebuilds the map and Google recrawls. Call it six to ten weeks before it recovers, and it doesn't fully recover, because rankings that dropped don't always come back to the same position.
The redirect line on a proper quote for that store is maybe $900. You saved $900 and paid roughly $8,000 for the privilege, before counting the paid traffic you had to buy to cover the hole.
Tax is the same shape of problem with a different bill. Shopify Tax will calculate rates once it's configured, but somebody has to tell it which states you have economic nexus in, assign product tax codes, and decide whether shipping is taxable in each. Apparel is the classic trap: clothing under a price threshold is exempt in New York and treated differently again in Pennsylvania and Minnesota. A developer who never touched the tax settings leaves you collecting the wrong amount in a handful of states for a full quarter, and you can't retroactively charge customers. You eat it.
Accessibility is the omission with the longest tail. US merchants get ADA demand letters over storefronts that fail keyboard navigation, have unlabelled form inputs, or ship a color contrast ratio below 4.5:1 on the add-to-cart button. An overlay widget bolted on at the end does not make that go away, and plaintiff firms know which overlays are which. Building the templates to WCAG 2.1 AA during the build costs a fraction of remediating under a deadline while paying a lawyer.
And checkout. If nobody placed test orders through Shop Pay, Apple Pay, PayPal and a plain card, with a discount code applied, on a mobile device, then you find out on launch day. We've seen a subscription app conflict with a post-purchase upsell in a way that only shows up when both are live, and only for returning customers. That's a QA line item. It costs a few hours. Discovering it during your first big promotion costs considerably more.
Signs of a bad Shopify agency, before you've signed anything
The sales process tells you nearly everything. Watch for these:
- No discovery. A fixed price arrives within an hour of your first email, without anyone asking how many SKUs you have, whether you have variants with metafields, which apps you're carrying over, or whether you sell B2B. They've priced a template, and you have a store.
- The scope is a feature list, not a deliverable list. "Custom homepage design" is not a deliverable. "Homepage: 2 concepts, 2 rounds of revision, delivered as Figma, responsive at 375/768/1440" is.
- Revisions are "unlimited". Nobody offers unlimited revisions on a $3,200 project and means it. Either the price goes up later or the work stops early.
- They won't tell you who's doing the work. Ask for the name and role of each person on the project. If the answer is vague, your build is being subcontracted to someone the agency has also lowballed.
- No maintenance conversation. Shopify ships breaking-ish changes, apps update, themes drift. An agency that treats launch as the end is planning to be unreachable.
- The timeline ignores your season. Anyone proposing a go-live in the second week of November for a US consumer brand either doesn't understand BFCM or doesn't care. We refuse those dates. Launch in September or launch in January.
Shopify freelancer warning signs are slightly different
Plenty of excellent Shopify work is done by solo developers, and for a theme customization or a handful of Liquid changes a freelancer is usually the right call and a quarter of the cost of an agency. The failure modes are just specific.
Single point of failure is the obvious one: one person, one laptop, and if they get sick during your launch week there is no bench. Then there's scope drift, because a freelancer with no project manager will take a verbal "can you also..." and absorb it until the project quietly stalls. And access. A freelancer who insists on a full staff account with owner-level permissions, rather than requesting collaborator access through the Shopify Partner dashboard, is either not a Partner or is planning to hold something.
The one that costs real money: no version control. If the work happens by editing theme files directly in the Shopify admin with no Git repository, there is no rollback. Ask where the repo lives and whether it's in your GitHub organisation. It should be.
How to tell if a Shopify developer is legit
Checks that take fifteen minutes and are hard to fake:
- Find them in the Shopify Partner Directory and read the reviews, including the two-star ones. Partner status is verifiable; a logo on a website is not.
- Ask for three live store URLs and open the source. You can see the theme, the app scripts, whether it's a stock Dawn install with a new color scheme.
- Ask which of those stores they built versus maintained versus "contributed to". The wording in portfolios does a lot of quiet work.
- Ask for one reference you can email, ideally a store in your category and size.
- Check whether they've published anything on the Shopify App Store. Building and maintaining a public app means they've been through app review and know the platform's edges.
A ten-minute call where you ask them to explain, out loud, how they'd handle metafield migration for 900 products with three variant options is worth more than any of the above. Competence is audible.
Questions to ask before hiring a Shopify developer
- What's in scope and what's explicitly out? Send me both lists.
- Who owns the code and where does the repository live?
- What happens to redirects, and can I see your mapping process?
- How will you test checkout, and with which payment methods?
- What accessibility standard are you building to, and how are you verifying it?
- Who configures sales tax and nexus, me or you?
- What's the bug-fix window after launch, and what counts as a bug versus a change request?
- What's your hourly rate, and how many hours are in this quote?
- What is your process if we disagree about whether something was in scope?
- What happens on the Monday after Cyber Monday if something breaks at 2am?
Question 8 is the one that separates estimators from guessers. Any quote can be reverse-engineered into hours. If they resist, the number wasn't built on anything.
Is my Shopify developer overcharging me?
Sometimes, and the tell is not the total. It's the ratio of hours to output.
Blended rates vary enormously by geography. US and UK agencies commonly sit in the $120 to $200 per hour range; experienced offshore teams, including ours in Bengaluru, work at a fraction of that. Neither number is wrong. What's wrong is 60 hours billed for a homepage redesign on an existing theme, or a "custom app" invoice for something a $19/month listing on the App Store does better. If you want a sense of what specific pieces of work should cost before you negotiate, we publish our breakdown of Shopify development costs with the assumptions shown.
Three practical checks. Ask for a time log against tasks, not a monthly total. Ask what would happen to the price if you cut one feature; if nothing changes, the estimate was never itemised. And get a second quote for the same written scope, not a vague description, because two quotes for two different scopes tell you nothing.
The opposite problem is more common than overcharging, honestly. Most of the rescue work that reaches us came from a quote that was too low to include the work it needed.
Shopify developer scams and the deposit that disappeared
Outright fraud is rarer than incompetence, but it happens, and it follows a pattern. Large upfront deposit, usually 50% or more. Payment by wire, Zelle or crypto rather than card or an escrow platform. A portfolio of screenshots with no live URLs. Then progress updates that are screenshots of a design file, never a staging store you can click.
If your developer took a deposit and went quiet, act in this order:
- Lock down access first. Shopify admin, Staff accounts, remove their collaborator access, rotate the theme. Then your domain registrar, your email platform, your payment gateway. Do this before you send the angry email.
- Get the code. If there's a repo, export it. If the work lives only in an unpublished theme in your admin, duplicate and download it now.
- Dispute the payment. Credit card chargebacks for services not rendered are your fastest route, and the window is generous but not infinite. Wire transfers are usually unrecoverable, which is exactly why they were requested.
- File a Partner complaint if they're in the Shopify Partner Directory, and leave a factual review.
- Small claims is viable for amounts under your state's limit and doesn't need a lawyer. It's worth it more often than people assume.
The structural fix is milestone payments. 20% to start, then tranches released against demonstrable deliverables on a staging URL you can open yourself. Nobody reputable objects to this.
What a Shopify quote should include
Print this and hold the proposal against it. A quote that's fit to sign names the deliverables and the number of revisions per deliverable; lists the apps by name, with who pays the monthly fees; states the hours or the days per task; defines the testing scope, including browsers, devices and payment methods; says who handles redirects, tax configuration and analytics; sets an accessibility standard; carries a post-launch bug-fix window with a date on it; specifies code ownership and repository location; sets out milestone payments; and includes a change-request process with a rate attached.
Anything missing from that list is a thing you will pay for twice. If you're moving platforms, the redirect and data-integrity sections matter more than everything else combined, which is why our migration scope treats URL mapping as its own phase rather than a checkbox at the end.
A cheap quote is sometimes the right one
Not every project needs an agency. If you're on a stock theme, you do under $40k a month, and you want a better collection page and a faster homepage, hire a good freelancer for two weeks and spend the difference on email and SMS, where your returns are better anyway. Rising Meta CAC has made retention the cheaper growth lever for most US D2C brands, and a $14,000 rebuild rarely beats a properly segmented flow series in the same quarter.
The lowball quote becomes dangerous when the project has real surface area: a migration, a checkout change, a B2B catalogue, a subscription program, anything touching tax across multiple nexus states. That's when the missing line items have teeth.
If you've got a proposal in your inbox and you're not sure what's been left out of it, send it over with your store URL and we'll mark up what's missing. No obligation to use us. You can also start with a free store audit and take the findings to whichever developer you were already leaning towards.