Hiring ecommerce developers without being sold a demo

Operations and cost 9 min read

Two people talking across a table over a printed requirements list
Four questions separate experience from portfolio.

Ecommerce suppliers are hard to tell apart from their portfolios, because a portfolio shows finished storefronts and every finished storefront looks competent.

What distinguishes a team that has run stores from one that has only built them is visible in four answers, and none of them is about design.

Four questions that decide it#

  1. "Walk me through a data migration you did and what went wrong." Everyone who has done one has a story; nobody who has not can invent a convincing one.
  2. "What happens in your checkout when the payment fails at 3-D Secure?" The answer reveals whether they built for the bad day.
  3. "What admin tooling did you build for the client's own team?" Teams who have operated stores always build something here.
  4. "What broke in the first month after your last launch?" An honest, specific answer is the strongest signal available.

Deliverables to require in the contract#

Hiring ecommerce developers without being sold a demo — Deliverables to require in the contract
DeliverableWhy it matters
Repository and deployment instructionsYou must be able to change supplier
Data migration plan and mappingThe largest risk in the project, written down
Admin tooling and documentationYour team runs the store, not the agency
Runbook for payment and fulfilment failuresIncidents will happen
Post-launch support terms in writingMonth one is when you need them most

Warning signs#

  1. A quote produced without asking about your product data or your ERP.
  2. Timeline promises with no mention of payment provider onboarding.
  3. No question about who owns the store after launch.
  4. Reluctance to hand over the repository.
  5. A fixed price with no defined scope for edge cases and migrations.

The shape of the engagement#

Start with a paid two-to-three week discovery that produces a data migration plan, a technical approach and a working slice — usually catalogue import plus one product page. It costs little and reveals everything about how the team works.

Frequently asked questions

Freelancer, agency or in-house?

Freelancer for a scoped build, agency when integrations are broad, in-house when the store is your main revenue channel.

How do I judge quality without a technical person?

Ask for the migration story and the admin tooling. Both are hard to fake.

How long to a first version?

Two to four weeks hosted and simple; two to five months with real integrations.

hire ecommerce developersecommerce agency selectionwebshop developerproject discoverysupplier evaluation

All guides

Last updated 2026-08-05 by ecommercedevelopment.info · About us

Written by builders

Every guide is written by developers who ship and maintain real stores, not spun from other sites.

Reviewed on a schedule

Platforms and payment rules change. Each guide carries the date of its last review, and we publish the date even when nothing changed.

No paid placements

No platform, theme shop, app vendor or agency can buy a mention, a ranking or a link here.

Twelve languages

Every guide is translated, not machine-popped — each language has its own URL and its own review date.

Limits named

We say plainly when a hosted platform or a marketplace listing would be cheaper and more reliable than a custom build.