Buy and Sell

Ecommerce App Development Services

Ecommerce app development services, priced and dated before anybody starts. We build custom stores and shopping apps rather than configuring somebody else's: your catalogue, your checkout, your order management, and where you have a shop, the counter and the website holding the same stock. Most first releases go live in about 30 days.

Get a free costed plan WhatsApp us

Price: Fixed upfront
Launch date: In writing
First release: About 30 days
You get: Source code & docs

Why own it

Built for how you sell, not configured around it.

Every platform is opinionated, and those opinions are free until the day your business needs something the platform will not do. A custom build starts from what you sell and how you sell it, and the awkward parts of your business stop being workarounds.

Your rules, not the platform's
Trade pricing, deposits, bundles or hire periods, built rather than bolted on.
One stock figure
The shop and the website counting the same items, so nothing is sold twice.
No percentage of every sale
Gateway fees are unavoidable. A platform's cut of your revenue is not.
Yours to extend
The code is yours, so the next thing you need is a decision rather than a feature request.

A hosted platform

Time to a first store: Days
Monthly cost: A fee, plus a cut of sales
Your awkward requirement: An app, a workaround or no
Your data: Exportable, mostly
Your shop till: Whatever integrates
When you outgrow it: Migrate everything

A custom build

Time to a first store: Weeks
Monthly cost: Hosting, and what you choose to add
Your awkward requirement: Built
Your data: Yours, in your own database
Your shop till: Connected to the same stock
When you outgrow it: Add to what is there

What you get

What gets built.

Ecommerce application development is a storefront, an office and, where you have a shop, a till. Pick one to see what goes into it.

App 01 of 03

Storefront and app

The shopping experience, on the web and on both stores. The screens below are the full flow a first release ships with, which is a list you can check a quote against.

DiscoveryHome, categories, product listing and a search with filters people actually reach for.
Product pagesImages, detail, variants, stock and the information that answers the question before it is asked.
Wishlist and cartSaved for later and ready to buy, both surviving a closed app and a new device.
Checkout and paymentAddresses, delivery choice and payment, in as few screens as the order allows.
After the orderConfirmation, receipt, order tracking and notifications, which is where repeat custom is won or lost.
AccountsSign up, sign in, saved addresses, and past orders to reorder from rather than retype.

App 02 of 03

Admin panel

Your side of the store. Products in, orders out, and the answers when somebody phones about either.

Catalogue and PIMProducts, variants, images, attributes and descriptions, edited in bulk or imported from a spreadsheet.
Order management systemEvery order with a status, from pending to picked to sent, and the buttons that move it.
Inventory and fulfilmentStock by location, low-stock warnings, and what to pick for today's orders.
CustomersWho bought what, their addresses and their history, for whoever answers the phone.
Pricing and promotionsPrice lists, discounts, codes and scheduled offers, without a deploy.
ReportsSales, best sellers, stock turn and what is sitting still, exportable.

App 03 of 03

The shop counter

For businesses with a physical shop. The till and the website counting the same stock, so an item sold at the counter cannot also be sold online an hour later.

Point of sale integrationYour till connected to the same catalogue, stock and customer records, or built as part of the system.
One stock figureA sale on either side moves the same number. This is the reason for doing it at all.
One customerThe same account whether they bought in the shop, on the site or in the app.
Click and collectBought online, picked in the back, handed over at the counter.
Returns either wayAn online order refunded at the till, and a shop purchase returned by post.
Reporting across bothOne set of numbers for the business rather than two that need reconciling on a Friday.

Open slot · built to order

Content and loyalty

For brands where the catalogue is not the whole product. Articles, guides and recommendations sit beside the shop rather than on a separate blog nobody visits.

Content beside commerceGuides, routines and stories in the app, with the products they mention shoppable in place.
Product recommendationsBased on what somebody browsed and bought, rather than on what you want to shift.
Loyalty and pointsEarned on orders and spent at checkout, configured in the admin.
SubscriptionsRepeat orders on a schedule, paused and resumed by the customer.
ReviewsFrom verified buyers, which is the only kind worth showing.
Notifications worth openingBack in stock, order shipped, and the reminder timed to how often they actually reorder.

How it works

From a browse to a repeat order.

Six steps. The last two are where most stores stop trying, and they are where the margin is.

01
Customer
They find something
Category, search or a recommendation. Filters that match how your customers describe things rather than how you file them.
02
Customer
They decide
The product page answers size, fit, stock and delivery before they have to ask, because asking is where orders are lost.
03
Customer
They pay
Cart, address, delivery choice and payment, with as few screens as the order allows.
04
Your system
You see it
The order lands in the admin with a status, and stock moves whether the sale was online or at the counter.
05
You
It is picked and sent
Fulfilled from the shelf or the shop, with the customer told at each step rather than left guessing.
06
Your system
They come back
Past orders to reorder from, points earned, and a notification timed to when they usually need more.

Features

What a custom store is built from.

Your costed plan names which of these are in the first release. The catalogue and the order management are rarely worth deferring, because everything else reports into them.

Catalogue and PIMProducts, variants, attributes, images and descriptions, imported in bulk rather than typed one at a time.
Payment gateway integrationCards, wallets and local methods, set up per market, with the gateway your bank actually settles through.
Order management systemStatuses that match how you work, from pending through picked to sent, with the history behind each change.
Inventory and fulfilmentStock by location, low-stock alerts, reservations at checkout and picking lists for what goes out today.
Point of sale integrationFor businesses with a shop: the till and the site sharing one stock figure and one customer record.
ERP and back-office integrationWe connect to the system you already run where it has an API worth using, and say so plainly when it does not.
Headless commerce architectureThe store's data behind an API, so a website, an app and a till can all read it. Worth it when you have more than one front end, and overkill when you do not.
Product schema and feedsStructured data on product pages and a Google Merchant Center feed, so your catalogue is readable by the things that send you traffic.
Search, filters and wishlistThe three features shoppers use before they ever add to a cart, and the three most often left until later.
Accounts and order historySaved addresses and past orders to reorder from, which is most of what makes a second purchase easy.

Ways to earn

How a custom store pays for itself.

A platform takes a fee and a percentage forever. A build costs once. These are the places the difference usually shows up.

No revenue shareGateway fees remain. A platform's cut of every sale does not.
Your own pricing rulesTrade prices, volume breaks and account terms, without an app subscription for each.
Subscriptions and repeatsScheduled orders, which most platforms charge extra to support.
Selling in person tooThe counter on the same stock, instead of a second system and a nightly reconciliation.
Loyalty you ownPoints and tiers configured in your admin rather than rented per month.
Feeds and channelsYour catalogue pushed where buyers already search, from data you control.

Example month, $40,000 of sales

What a hosted platform costs that a build does not

Platform subscription: $79
Platform fee on sales, 1.5%: $600
Four paid apps for missing features: $116
Hosting your own build instead: −$60

Difference, every month$735

That is roughly $8,800 a year, which is the honest way to think about what a build costs: not whether it is cheaper than a plan, but how long it takes to overtake one. Gateway fees are paid either way. Figures are an example, and your own volume decides it.

Who it is for

Who we build stores for.

B2B ecommerce development, B2C ecommerce website development and D2C ecommerce platform development are three different builds rather than three names for one. Tell us which you are and the scope is designed from there.

Shops that also sell online
You have a counter, a stockroom and a website that does not know about either.
Built to fit
- Point of sale connected to the same stock and customers
- Click and collect, and returns accepted either way
- One set of numbers instead of two that need reconciling
D2C brands
You sell your own products and the brand is most of why anybody buys them.
Built to fit
- Content and guides beside the catalogue, shoppable in place
- Recommendations and loyalty built in rather than rented
- A branded app worth keeping on a home screen
B2B and wholesale
Your customers are businesses, and almost nothing about retail checkout suits them.
Built to fit
- Account pricing, volume breaks and negotiated terms
- Credit accounts, purchase orders and monthly invoicing
- Reordering from history, because they buy the same things
First stores
A catalogue, a cart and one payment method, live in weeks rather than months.
Built to fit
- Storefront first, then the admin, then payments
- One payment method properly rather than four badly
- Room to add the rest once something is selling
Multi-location retail
Several shops, different stock in each, one website over the top.
Built to fit
- Stock by branch, with orders routed to the one that can fill them
- Per-location pricing, hours and collection
- Group reporting across every site
Outgrowing a platform
The store works, and the workarounds now cost more than the platform does.
Built to fit
- An honest read on whether to rebuild or stay
- A migration that keeps your orders, customers and URLs
- The awkward requirement built rather than worked around

How it works

A price and a date, and milestones you can track.

01 · Before we start
Free costed plan
What you sell, how you sell it and where. You get the scope, a fixed price and a launch date in writing, free, whether you go ahead or not.
02 · Week 1
Catalogue and screens
How your products are structured, and a clickable storefront in your brand. Getting the catalogue right here saves more than any other week of the project.
03 · Weeks 2 to 4
Storefront, admin, payments
Built in that order, because each is testable on its own. A new build reaches you every week and you can see the store filling up.
04 · From about day 30
Launch and sell
Live, with the payment gateway in your name and the stock in your control. Then fixes, updates and whatever the orders tell you to build next.

Most first releases go live in about 30 days. A small first store is quicker, and a build with point of sale or an ERP behind it takes longer. Your costed plan fixes the scope and the exact date.

What goes live first, and what follows.

Your costed plan splits the build into releases with their own fixed prices and dates. A first store is smaller than most people expect, and the order below is the one clients keep suggesting themselves.

About 2 weeks
A first store
- Categories, product pages and cart
- Checkout with one payment method
- Admin: add products, see orders, mark them done
- Accounts with order history
About 30 days
First release
- The full sixteen-screen app flow
- Search, filters and wishlist
- Order tracking and notifications
- Stock, fulfilment and reporting
When you need it
As you grow
- Point of sale and click and collect
- ERP or accounting integration
- Subscriptions, loyalty and recommendations
- More languages, currencies and markets

Store launch

We publish your apps. It is in the price.

Every build ends with your apps live on the App Store and Google Play. Submission is part of the job, never an extra: we prepare everything, handle the review and fix whatever the stores ask for.

Included in every build

Store listings. Name, description, keywords, screenshots and preview images.
Privacy and compliance. Privacy details, data forms and content ratings each store requires.
Signed release builds. Built, signed and uploaded for iOS and Android.
Review and approval. We answer the reviewers and resubmit if anything is flagged.
Updates after launch. Every new version goes through the same process.

The one cost that is yours

Apple and Google charge for a developer account. It is opened in your company's name, so the apps and their listings always belong to you.

Apple App StoreUS$99 a yearApple Developer Program
Google PlayUS$25 onceGoogle Play Console

Submission, listings and reviewIncluded

Store fees are set by Apple and Google and may change.

Tech

What it is built with.

Ordinary tools your next developer will know. Your costed plan names exactly what your store uses.

Payments

Stripe
Razorpay
PayPal
Apple Pay
Cash on delivery

Storefront

React
Next.js
Flutter
Swift
Kotlin

Behind it

Python
FastAPI
PostgreSQL
Redis

Selling elsewhere

Google Merchant Center
Product schema
Point of sale
Your ERP

Price

What sets the price.

There is no price list, because a first store and a store with a till behind it are different projects. Your fixed price comes from the scope in your costed plan.

Get your fixed price

How big the catalogue is
Forty products and forty thousand are different problems, and the import is where that shows first.
How complicated a product is
One price and one button, or variants, options, bundles and made-to-order.
Web, app or both
A responsive store, iOS and Android, or all three from one system.
Whether you sell in person
Point of sale and shared stock is the single biggest addition on this page.
What it connects to
ERP, accounting, couriers and feeds, and whether each has a usable API.
Markets
Languages, currencies, tax rules and the payment methods each country expects.

Why the date holds

We have built a lot of stores.

Your store is designed and built new for your business. What carries over is knowing where these builds go wrong, and it is rarely the checkout. It is stock that disagrees with itself, an order status nobody updates, a search that cannot find a product by the name customers use for it, and a catalogue import that turns four hundred products into four hundred problems. Those are solved problems and none of them is solved on your budget, which is why the scope, the price and the date can be fixed.

See the apps we build

After launch

After launch, we stay.

A store is a shop that is open at three in the morning, and a checkout that fails then fails quietly until somebody looks.

Monitoring
Servers, payments and the checkout watched around the clock, with the funnel itself alerted on rather than raw uptime. A store that is up and taking no orders is the failure that costs money, and it looks fine on a status page.
Fixes
You tell us once and we take it from there. Every issue is logged, fixed, tested and released. Anything touching checkout or stock goes ahead of everything else, because both cost money while they are wrong.
Peak trading
The days that matter are known in advance. We load test before them, watch through them and keep somebody reachable, because a store falling over on the one busy weekend undoes a quarter of work.
Catalogue and content
The first weeks after launch are mostly catalogue: images, descriptions, variants and the lines that imported badly. We stay close to that while it settles rather than handing over a spreadsheet.
New features
Point of sale, subscriptions and integrations are usually later releases, each scoped, priced and dated in writing before work starts, exactly like the first.
Handover
The store is yours and so is everything needed to run it. Your team gets the code, the accounts, the deployment process and written documentation, so you can carry on with us or bring in your own developers whenever you choose.

Clients

What our clients say.

Questions

Asked before most builds.

Not here? The costed plan answers the rest, for your app.

Your idea stays yours. We can sign an NDA before you share the details, and you hear from us within 24 hours.

How much does ecommerce app development cost?

It depends on the size and complexity of the catalogue, whether you need web, apps or both, whether you also sell in a shop, and what it has to connect to. A small first store is a different project from one with a till and an ERP behind it. You get a fixed price in a free costed plan before any work starts, and it does not move unless you change the scope.

How long does it take to build an ecommerce app?

A small store with a catalogue, a cart and one payment method is about two weeks. A full first release with the complete app flow, search, wishlist, tracking and stock management is about 30 days. Point of sale or an ERP integration takes longer, and your costed plan fixes the exact date before we begin.

Headless commerce or traditional, which do we need?

Headless means the store's data sits behind an API and anything can read it, which earns its cost when you have more than one front end: a website, an app and a till, say. If you have one storefront and no plans for another, it is complexity you would be paying for and not using. We will tell you which yours is during scoping rather than selling you the fashionable answer.

What is different about a B2B build?

Almost everything after the product page. Business customers need account pricing rather than one price, volume breaks, purchase orders, credit terms and monthly invoicing rather than a card at checkout. They also reorder the same things constantly, so order history and quick reordering matter more than discovery does. A B2B store that behaves like a retail one is the commonest mistake in this category.

Can the website and our shop till share stock?

Yes, and for a business with a counter it is usually the main reason to build rather than configure. One stock figure means an item sold at the till cannot also be sold online an hour later, the same customer account works in both places, and you get one set of numbers instead of two that need reconciling. Your existing till can often be connected, and where it cannot we will say so.

Can you connect it to our ERP or accounting system?

Where it has an API worth using, yes, and we will look at it before quoting rather than after. Some older systems have no usable interface and the honest answer is a scheduled export rather than a live integration. You will get that answer during scoping instead of discovering it in week three.

Should we build custom or use a platform?

Use a platform if a standard store sells what you sell and you can live with its opinions. Build when the platform charges a percentage of everything you earn, when your pricing or fulfilment does not fit its model, or when you need the shop counter and the website to be one system. We have told people to stay where they are, and we would rather do that than take on a build that a plan would have covered.

Can you migrate our existing store?

Usually. Products, customers, orders and URLs can all come across, and keeping the URLs matters more than most people expect because it is what protects your search rankings. We read what you have first and report back honestly, including when the answer is that your current store is fine.

Who owns the store and the data?

You do. The code is handed over with documentation, the payment gateway and cloud accounts are in your company's name, and every product, customer and order record sits in a database you control.

Related services

Next step

Your first release could be live
next month.

Tell us about the app you want to build. We send back a costed plan with a fixed price and a launch date, free and yours to keep.

Get a free costed plan See case studies