Techbanq

Cost guide · e-commerce

An e-commerce store is priced twice — at launch and every month after

The figure on an e-commerce proposal covers the build, but the store's real economics include platform fees, payment costs, hosting and the constant work of keeping catalogue and content alive. The build figure itself moves with platform choice, catalogue complexity and the integrations behind checkout — and this page walks through each driver so a quote can be read for what it includes.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
Commercial Director, Head of Digital
Decision
Budget an online store across its build and its operation
Languages
EN · AR

Information security for software delivery

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

Before the figure

The decisions an e-commerce quotation has to record to mean anything

Five decisions set the shape of the build. A quote that does not state them has made them for you, and the versions suppliers silently choose are rarely the ones you would.

The platform route

SaaS, open-source and custom split both the build effort and the fees that follow it.

What a blank here hides: A recurring platform bill the proposal never mentioned.

The named integrations

Payments including mada, shipping carriers and any ERP sync are each their own piece of work.

What a blank here hides: A checkout that cannot take the payment your customers hold.

The bilingual storefront

Arabic-first, right-to-left commerce is part of the build, not a translation pass at the end.

What a blank here hides: A store built for a different market, reworked at your expense.

The performance target

A store expected to survive a campaign spike is engineered differently from one that is not.

What a blank here hides: A launch-day sale the site does not survive.

The run-rate line

Platform fees, hosting, maintenance and content work continue for every month the store trades.

What a blank here hides: An operating cost discovered from the first month's invoices.

What moves the build

What separates one e-commerce build from another on price

Six drivers, none of them a number. Two stores with the same design can differ enormously in cost because they answer these differently underneath.

VariableEffect on priceWhy
Platform choiceSaaS, open-source and custom are different economicsA SaaS commerce platform lowers the build and adds recurring fees and platform limits; an open-source platform raises the build and hands you control and hosting duty; a custom build is for the rare case where the commerce model itself is the differentiator. The choice sets the build figure and the operating one at the same time, which is why it comes first.
Catalogue complexityProducts are data work, not just pagesA few dozen simple products and thousands of SKUs with variants, bundles and multi-warehouse stock are different projects wearing the same storefront. Modelling, migrating and validating catalogue data is real work that quotes routinely gloss, and it grows with every attribute your products need to carry.
The integrations behind checkoutWhere the store meets your operationPayment methods your customers actually hold — mada among them — shipping carriers, cash-on-delivery handling and any sync with an ERP or accounting system are each scoped, built and tested separately. This is the part of an e-commerce quote that varies most between suppliers, and the part most worth itemising before you sign.
The Arabic and bilingual requirementA build requirement, not a translation taskA storefront for this market works right-to-left, searches and sells in Arabic, and runs its content workflows in two languages. That touches layout, catalogue structure, search and every email the store sends — which is why it is scoped into the build from the start, and why a "we will translate it later" quote has priced a different store.
Performance targetsSpeed is scoped, not hoped forA store that must stay fast through a campaign spike needs caching, image discipline and load testing designed in; one that has never been tested against its own peak will discover the gap on its most valuable trading day. Name the traffic the store has to survive, and let the quote answer to that number of visitors rather than to optimism.
The post-launch operating costIts own budget line, foreverPlatform fees, hosting, payment processing, security updates, and the human work of products, promotions and content continue for as long as the store trades. A proposal that shows only the build has shown you the ticket price of a running business — treat the monthly line as part of the decision, not a detail for later.

Ask any supplier quoting this

  • Which platform does this figure assume, and what will that platform itself charge us monthly?
  • Does the build include mada and the other payment methods our customers actually use?
  • How many products, variants and languages does the catalogue work assume?
  • Is the Arabic storefront a full right-to-left build or a translated theme?
  • What traffic has this store been priced to survive, and how will that be tested?
  • What will the store cost to operate each month — platform, hosting, maintenance and content?

The second price

The e-commerce budget line that never closes

The build is the price of opening the store; the run-rate is the price of keeping it open, and stores fail on the second far more often than on the first. Platform and hosting fees arrive whether or not anyone buys. Payment processing takes its share of every order. Products need photography, descriptions in two languages and prices kept honest against stock; promotions need building; the platform needs patching. None of this is exotic — it is the ordinary overhead of a trading business — but a budget approved on the build figure alone has funded a shop and forgotten the shopkeeping.

The practical discipline is to approve the store as two numbers from the start: what it costs to launch, and what it costs per month to trade. The second number also happens to be where platform choice earns or loses its keep — a route that looked cheaper to build can carry the heavier monthly line, and only seeing both figures side by side reveals which store you can actually afford.

Our role

What we settle before an e-commerce build carries a figure

  1. 01

    The platform, argued not assumed

    We recommend the platform route from your catalogue, integrations and team's capacity to operate it, and we show the reasoning — because the wrong default here is paid for monthly, for years.

  2. 02

    The integration inventory first

    Payments, shipping, ERP and whatever else the store must talk to are named and scoped before the figure exists, so the checkout that ships is the one your customers can actually pay through.

  3. 03

    Two figures, side by side

    Our proposal shows the launch cost and the monthly run-rate together, because a store is a trading business rather than a website, and approving one number without the other is approving half the decision.

What the store sells, at what margin, and how much monthly overhead the business can carry are commercial calls that stay with you; we make sure both prices of the store are on the table before either is committed to.

Common questions

What buyers ask

Other agencies advertise fixed-price e-commerce packages — why is there no price list here?+

Because a package price is only honest when the store fits the package, and the stores worth building rarely do. A fixed-price package works by fixing everything else: a template design, a small catalogue, the platform the agency prefers, and integrations limited to what plugs in without work. If that describes your store, a package may genuinely serve you. The moment you need mada plus specific carriers, an ERP sync, a real Arabic storefront or a catalogue of any size, the package price stops describing your project — and the difference arrives later as extras. We price after scoping so the first number is also the last one.

Is a SaaS commerce platform always the cheaper route for an online store?+

Cheaper to open, not always cheaper to run. The SaaS route wins on build cost and time to launch, and for many stores that is decisive. But its fees recur for the life of the store and typically scale with sales, its limits define what you can build, and leaving it later means a migration. An open-source or custom route costs more up front, then trades platform fees for hosting and maintenance you control. The honest comparison is the total across the years you expect to trade, at the volumes you expect to reach — and that arithmetic lands differently for a boutique and for a catalogue of thousands.

Does an Arabic-English storefront with mada payments cost much more to build?+

It costs more than leaving them out, and far less than adding them after launch — and for this market, leaving them out is not really an option. A storefront that cannot take the payment methods customers hold, or that treats Arabic as a bolted-on translation, tests a different business from the one you are opening. Scoped from the start, right-to-left layout, bilingual catalogue and content workflows, and the local payment integrations are ordinary build work with a known shape. Retrofitted, they touch layout, data structure and checkout all at once, which is the expensive version. Treat them as the baseline of the build, and read any quote that does not as pricing a store for somewhere else.

Which integrations move an e-commerce quote the most?+

The ones that touch systems behind your own walls. Payment and shipping integrations against documented, widely used services are known work; the quote moves when the store has to stay in sync with an ERP, an accounting system or a warehouse platform whose data model was never designed for a storefront. Stock levels, prices and orders flowing both ways between the store and an internal system is genuinely hard to get right — and it is also where the commercial risk lives, because a store showing wrong stock or wrong prices costs money with every order. If your quote has one line item deserving scrutiny, it is that sync.

A scoping session that fixes the platform route, the named integrations and the bilingual requirement, and puts the launch figure and the monthly run-rate side by side before you commit.

Cost your store with us