Skip to main content

Service specification 4 sections Platform first, custom when needed

Ecommerce Website
Development

01

Most shops should use Shopify or WooCommerce

Most online shops should use Shopify or WooCommerce. BigCommerce is another good choice. A platform is faster and cheaper when the products, payments and delivery rules are standard. Build from scratch only when your sales rules will not fit the platform.

Use the simple answer

A platform gives a normal shop a tested catalogue, checkout and order area. It also gets regular updates. Paying to rebuild those parts makes no sense when they fit.

Large catalogues with trade rules may need Magento web design. Most shops do not.

Start with standard products, checkout and delivery. If all three fit, use the platform and spend the budget on the shop itself.

What a platform hands you, and what it takes back

Renting a shop platform is the right call for most people. It is still renting, and the terms are worth reading first.

The 2% figure is Shopify's own published third-party transaction fee, from shopify.com/uk/pricing, checked 9 September 2026.
What to weigh What the platform handles What it takes back
Getting started You can be selling within days, with hosting, security and updates all handled. You fit the business to the platform, rather than the other way round.
What you pay A predictable monthly fee, and no server of your own to run. That fee, plus a slice of every sale, for as long as you keep selling.
Taking payment The built-in payment tools are quick to switch on and well tested. Shopify adds 2% on top when you take payment through anyone else.
Changing how it works An app covers most ordinary needs, and installing one takes minutes. Anything unusual becomes an app, then three apps, then a workaround.
What you own Nothing to maintain, and the shop keeps running if you change agency. You are renting. The fees, the rules and the roadmap are not yours.
Outgrowing it Most shops never do, and that is a good outcome rather than a failure. The ones that do tend to find out in their busiest month.
02

Four things the platforms will not do

The platform stops fitting when a core sales rule needs a pile of workarounds. These four needs come from live stores.

What you need

Filter one catalogue several ways at once

Easy Care Solutions lets shoppers filter by use, product, brand, size and absorbency.

Why the platform struggles

A simple menu cannot handle all five filters. The shop needs filters that match how people buy.

What you need

Run repeat subscriptions beside one-off orders

Easy Care Solutions sells one-off goods and repeat plans in the same shop.

Why the platform struggles

Repeat orders and one-off orders run on different dates and different payment rules. The same basket has to keep both clear.

What you need

Count down against the real delivery cut-off

Easy Care Solutions and BlowMotion use real delivery cut-off times.

Why the platform struggles

A fixed delivery message is not enough. The promise has to follow the courier slot and the current time.

What you need

Run trade accounts beside retail

Easy Care Solutions includes trade accounts as part of the store.

Why the platform struggles

A standard shop treats most buyers alike. Trade access and order rules can need a separate path after sign-in.

Shipping, delivery and collection

Delivery charges can depend on parcel weight, size or zone. Product type may change the rule too. A long item may need a different courier from a small box.

Order cut-off times decide which delivery dates the shop can promise. They are the part that most often goes wrong. The shop must check the time against the courier's last collection.

Click and collect needs its own stock point and message. The shop can pass the order to a courier automatically. The courier can then send the tracking number back to the shop.

Moving an existing shop across

Most of this work is a migration rather than a new shop. You already have products, customers, orders and search rankings, and all four have to survive the move.

The catalogue goes first. We map every product, variant, image and price, and agree what is retired rather than moved. Customer accounts and order history follow, so nobody loses their receipts. Old product URLs get redirected to the new ones, which is the step that protects the rankings you already have.

The old shop keeps trading while the new one is checked. We switch when the two agree on stock, prices and orders.

Retailer and developer checking an online order at a packing bench
The shop does not stop at checkout

Orders must reach stock, packing and delivery. Nobody should type them twice.

03

Three we have built, and what a build costs

All three stores are live. Their screenshots show the real work, so this page does not need a drawn shop or a mockup.

Easy Care Solutions

Continence care ecommerce with a catalogue that has to be filtered five different ways - by user, product, brand, size and absorbency - alongside repeat subscriptions and a delivery cut-off that counts down against the courier.

Built
Faceted search, Subscriptions, Delivery cut-offs, Trade accounts
The Easy Care Solutions ecommerce website
easycaresolutions.co.uk, as it runs today

BlowMotion

Hand dryer ecommerce for a UK market leader trading since 2012. Filtering by colour, sector and feature, a price match promise, and an order countdown wired to the next delivery slot.

Built
Product filtering, Price matching, Order cut-offs, Reviews
The BlowMotion ecommerce website
blowmotion.co.uk, as it runs today

Military Signature Archive

Mounted display prints of WWII aviation art signed by the aircrew who flew, sold to collectors in the UK and abroad. The catalogue is browsed by force and squadron, while the shop switches between pounds and dollars for overseas buyers.

Built
Catalogue by squadron, Multi-currency, International checkout
The Military Signature Archive ecommerce website
militarysignaturearchive.co.uk, as it runs today

What drives the cost

The difficult sales rules set the cost. A product count on its own tells us very little.

  1. 03.1

    How many products and variants

    Each product type needs the right options, stock record, images and order data.

  2. 03.2

    How the catalogue is filtered

    Each filter needs clean product data. It must also work with the other filters.

  3. 03.3

    Pricing rules and trade accounts

    Account types, access and special order rules must be clear before checkout.

  4. 03.4

    What the accounts package needs

    Orders, tax, payments and refunds need an agreed hand-off to the finance record.

How the number gets set
  • The catalogue mapped
  • Every selling rule written down
  • Accounts hand-offs agreed
  • A fixed price against that scope

Payments, hosting and life after launch

A shop needs a payment provider. Stripe and PayPal cover most UK stores, and both handle cards, Apple Pay and Google Pay. Klarna is worth adding where customers expect to pay later. Each provider takes a percentage of every sale. The right choice therefore depends on your order values and your margins, not on which one is easiest to fit.

A built shop needs somewhere to run. We can host it or set it up on hosting you already pay for. Either way the shop stays yours, and moving it later does not need our permission.

After launch we can maintain the shop, fix faults and add to it. The handover lists what you own, what is licensed and what support covers. Handover does not create an unlimited support promise, so what is included is set out in the agreement.

04

Common questions

For Xero, Sage and other system links, see API development.

How much does an ecommerce website cost?
The scope sets the cost. Product count and options matter, but the hard rules matter more. Filters, trade accounts, repeat orders, delivery cut-offs and accounts links all add work. We write those rules down first and fix a price. Two shops with the same product count can need very different builds. One may use a standard checkout. The other may need contract prices, courier rules and stock from another system. Those are the details that set the work.
Should I use Shopify or have something built?
Use Shopify first for most online shops. WooCommerce and BigCommerce are also good choices when they fit the business. These platforms handle standard products, payments and delivery well. Choose a custom build when a core sales rule will not fit. That rule should matter enough to justify owning and supporting software. Try the closest platform before you decide. The limits you find will show if custom work has a clear job, or if a normal shop is enough.
What is custom ecommerce development?
A custom online shop is built around one seller. Its products, checkout and order flow follow the seller's own rules. This route is for rules a standard platform cannot support well. Those rules may cover trade prices, repeat orders or stock held in another system. They may also control which courier can take a product. The point is not to rebuild a normal shop. It is to support a sales rule that matters and has no sound platform option.
Can a custom store handle trade and retail pricing?
Yes. A trade account can have its own prices, products, order rules and payment terms. Other buyers can use the main shop and checkout. The scope states which rules change for each type of account. It also says how a buyer gets trade access and who can approve it. Some firms need set prices for each customer. Others use price bands or discounts. The basket, tax and delivery rules must stay clear before the order is placed.
Can it connect to Xero or Sage?
Yes. Orders, customers, payments and stock records can pass to Xero or Sage through an agreed link. Each field and hand-off needs a clear owner. The scope should say when data moves and what happens if a record fails. It should also state which system owns tax, stock and payment status. That keeps staff from fixing two copies by hand. Read more on our API development page for how these links are planned and checked.
Can AI build me an ecommerce website?
AI tools can produce a working shop front quickly, and for a simple catalogue that may be enough. They are weakest at the parts that make a shop yours: trade pricing, stock rules, delivery cut-offs and the link to your accounts package. Those need someone who understands the rules and can be held to them when an order goes wrong. Payment flows and stock changes also need careful tests. AI may help write code, but it does not own the result or support the shop.
Can you move our existing shop without losing our Google rankings?
That is the aim, and it is mostly about URLs. Every old product and category address gets redirected to its new one. Search engines and links pointing at you then still reach a real page. Products, customer accounts and order history move across too. The old shop keeps trading until the new one matches it. We also keep page titles, product copy and image details where they are still right. Search traffic should be checked after the switch so any missed URL is found.
Which payment providers can we take money through?
Stripe and PayPal cover most UK shops, and both handle cards, Apple Pay and Google Pay. Klarna suits shops where customers expect to pay later. Each provider charges a share of every sale, so the right one depends on your order values and margins. It also depends on refunds, trade payments and the places you sell. The shop should record the payment result without storing the card details. Failed payments need a clear path back to the basket so the customer can try again.
Will the shop be built so it can rank in search?
Yes. Products and categories get readable URLs that can stay in place. Page speed shapes the build from the start. It is not an extra added after launch. Product structured data gives search engines the price and availability for each item. That can help listings show those details in search results. The copy matters as much as the code. A shop with thin or duplicate product text will struggle to rank, no matter how well it is built.
How is card data kept safe?
Every page uses HTTPS. That includes the basket and checkout. The payment provider handles the card details. The shop receives the payment result, but it does not store card numbers. Keeping those numbers out of your own system is the main protection. It keeps most businesses out of scope for the card-security duties that apply when they hold or process card data themselves. Admin access and payment settings still need careful controls. The link to the provider also needs regular updates.

Every question we get asked, in one place

Next step

Show us where the platform stops

Bring the catalogue, account and delivery rules that do not fit. We will tell you whether to change the platform, extend it or build.

  • Pontefract, West Yorkshire
  • Building for businesses across the UK
  • Reply within 1 working day
Five clear questions

Start with the rough version

No finished spec needed. Tell us what is getting in the way.

Question 1 of 5
What are we building?

Choose the closest fit. It does not lock you into anything.

What needs to work better?

Describe what happens now and what you want to change.

One or two clear sentences are enough.
Who will use it?

A rough answer helps us judge access, training and support.

What must it connect to?

Name any software, website, payment service or database that needs to stay.

Leave this blank if there are none or you are unsure.
Where should we reply?

A developer will read the brief and reply within one working day.

We use these details to reply to your enquiry. Read our privacy policy.