Choosing a provider
Ecommerce website development services
An ecommerce developer becomes closely involved in how your business sells. The right one asks about products, margins, fulfilment and the people who will run the store day to day, recommends a platform for good reasons, and tests the whole buying journey before launch. The wrong one builds a beautiful shopfront that is hard to run.
This page explains how to choose an ecommerce development provider and what the engagement should include.
Illustrative diagram
- Discovery
- Platform choice
- Design and build
- Product data
- Journey testing
- Launch and training
Questions to ask a developer
Platform
- Why do you recommend this platform for us?
- What will it cost to run each month?
- Which apps or extensions will we need?
Build
- Who imports and checks product data?
- How are payments, shipping and emails tested?
- How is the store made fast on phones?
After launch
- What training is included?
- How is support provided?
- Who owns the store account and data?
What a store build should deliver
| Deliverable | Why it matters |
|---|---|
| Store specification | Agreed scope for products, payments, shipping and integrations |
| Configured store | Catalogue, checkout, emails and policies set up |
| Imported products | Data checked for prices, variants, images and stock |
| Test record | Evidence orders, payments and emails work |
| Training | Your team can add products and process orders |
| Handover notes | Apps, settings and accounts documented |
Product data is often the biggest task
Getting products into the store accurately, with correct prices, variants, images, descriptions and stock, often takes longer than designing the store. A good developer asks early how product data exists today, perhaps in a spreadsheet, another platform or an inventory system, and plans how it will be cleaned, imported and checked. Errors in product data are expensive after launch, causing wrong orders and refunds.
Agree who is responsible for supplying, checking and approving product information.
Warning signs
One platform for everyone
May reflect the developer's habits rather than your needs.
No mention of running costs
Monthly fees and apps can surprise you later.
Store account in their name
Leaving becomes difficult.
No test orders
Checkout problems found by customers.
A typical engagement
Discovery
Products, fulfilment, payments and team understood.
Output: Specification and platform choice
Design and build
Templates, catalogue and checkout configured.
Output: Staging store
Data and testing
Products imported; full journeys tested.
Output: Launch-ready store
Launch and handover
Go live, training and support period.
Output: Your team running the store
Ownership of the store
The store account, domain, payment provider account and customer data should belong to your business. Developers can be given staff or collaborator access. This matters for security and continuity, and for your obligations as the business holding customer data.
Experience with your kind of store
Ask for examples of stores similar to yours in size, product type or complexity. A developer used to small catalogues may find a store with thousands of variants challenging; one used to large retailers may over-engineer a simple shop. Ask what problems arose in those projects and how they were solved; honest answers are a good sign.
Experience with your preferred payment and shipping providers also helps.
Connecting to your systems
If you use inventory, accounting or order management software, ask how the developer would connect the store to it, what happens when the connection fails and who maintains it. Integrations save time but add moving parts; they should be tested as thoroughly as the checkout.
Policies and required information
A developer should build in the information online sellers must provide, such as business details, total prices, delivery arrangements and cancellation rights, though the wording of terms and policies remains your responsibility and may need legal review.
Training your team
Ask what training is included: adding products, processing orders and refunds, creating discount codes, and checking reports. Short recorded sessions are useful for new staff later.
Realistic timelines
Store builds often slip while waiting for product data, photographs or decisions. Ask the developer which inputs they need from you and when, and plan your team's time accordingly. A timeline that shows dependencies on both sides is more reliable than a single launch date.
Speed and mobile
Ask how the developer will keep product and collection pages fast on phones, including image handling and the number of apps or extensions. Fast, mobile-friendly pages matter for both shoppers and search visibility.
Questions about ecommerce website development services
How do we choose an ecommerce developer?
Look for platform reasoning, data handling, testing, training and clear ownership.
Who should own the store account?
Your business, with developer access.
Who loads the products?
Agree responsibility for supplying, importing and checking product data.
Are running costs explained?
They should be, including platform, apps and payment fees.
Is training included?
Ask; your team needs to add products and process orders.
How is the checkout tested?
With test orders for each payment method and email.
Will the developer write our policies?
They build in the structure; wording is your responsibility and may need legal review.
What slows store builds down?
Usually waiting for product data, photographs or decisions.
Request a Custom Quote
Ask about Ecommerce website development services
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.