Choosing an ecommerce development company in Dubai, a buyer's checklist

Choosing an ecommerce development company in Dubai comes down to evidence rather than impressions. You are not buying a website. You are appointing the team responsible for a system that takes your money, holds your stock figures, talks to your accounting software and has to be fixed quickly when it stops working on a Friday night. This checklist sets out what to ask each agency, what evidence to ask for, and how to tell a complete answer from one that sounds complete.

It is written for business owners, ecommerce and operations managers and procurement teams, and it assumes no technical background. If you want the underlying development detail rather than the selection process, our ecommerce web application development guide covers architecture, integrations, costs and launch readiness in depth.

Define your requirements before you shortlist anyone

Agencies can only be compared against a brief. Without one, three proposals will describe three different projects and you will end up comparing prices for work that is not the same work. Shopify's own guidance to merchants hiring a partner makes the same point, advising that you clearly outline the requirements for the work needed, define your budget, timeline and expected outcomes in detail so the partner can quote accurately, and do preliminary research on comparable businesses first.

Settle these before the first call:

• What kind of project this is. A new build, a redesign of a store that works, a migration from one platform to another, or an integration project on a store you keep. These are different disciplines and some agencies are far stronger at one than the others.
• Your business model. Retail, wholesale, dealer network, marketplace, or a combination. This decides more of the build than the design does.
• Your catalogue in numbers. Product count, how deep the variants go, how consistent the attribute data is, and where it lives today.
• The systems in play. Accounting or ERP, inventory, CRM, courier accounts, payment provider, with versions and whether they are cloud or on premise.
• Launch dependencies. A trade show, a season, a lease on a warehouse, a supplier contract. Anything with a date attached.
• Budget range and who signs. Not to hand over at the first meeting, but so you know internally whether the proposals coming back are even in range.

Write it down in two pages. Send the same two pages to every agency. That one step makes every later comparison in this article possible.

Evaluate relevant ecommerce projects and portfolios

Every agency portfolio looks good, because portfolios are curated and homepages photograph well. What matters is relevance and responsibility, and both have to be asked for directly.

Ask what the agency actually delivered on a comparable project, which platform it was built on, and which business problem it solved. Then ask who did the work, because the team that built the example may not be the team assigned to you. A useful follow up is to ask what went wrong on that project and how it was handled. Agencies that answer that honestly are usually the ones worth shortlisting.

Relevance is not about industry alone. A furniture retailer and an electronics distributor can have similar builds if both need specification filters and trade pricing. Ask which of your requirements the example project shares, in your words, not theirs. Our own case studies are written this way, covering product discovery for a large UAE catalogue, connecting a store to inventory and order management and a custom B2B portal for a wholesale business, so you can see the problem, the decision and the result rather than a screenshot.

If client confidentiality prevents showing a live store, an anonymised walkthrough of the admin side is usually possible and tells you more than the storefront does.

Assess the platform recommendation and technical expertise

The right question is not which platform the agency prefers. It is why this platform fits your requirements, and what the alternative would have been.

A complete answer names at least one credible alternative and explains the trade off in business terms: what it would cost you to run, what it would prevent you doing later, and who maintains it. An agency that recommends the same platform to every client is telling you about their team rather than your project. Equally, an agency that proposes a custom build when a configured platform would serve you is adding cost you do not need to carry.

Useful background while you listen to those recommendations: our comparison of Shopify and WooCommerce, the platform overview, and for custom builds, MERN stack against Laravel. You do not need to become technical. You need enough to tell whether the reasoning in front of you is about your business or about their convenience.

Check experience with UAE shopping and operational requirements

Plenty of competent development teams have never built for this market, and the gaps show up after launch rather than during the demo.

• Arabic and English as equals. Not an interface translation. Product data, categories, attributes, search, checkout fields and transactional messages in both, with right to left layout handled properly. Ask who maintains the Arabic catalogue after launch, since that is where bilingual stores fall behind.
• Address collection that works here. Building names, landmarks and areas matter more than postcodes. A checkout form designed around postcodes produces failed deliveries.
• Delivery rules as data. Zones by emirate and area, slots and cut off times where you offer them, rather than one flat promise your operation cannot keep.
• Payment reality. Cards, the wallet and instalment options your buyers expect, and for B2B, ordering against credit rather than paying at checkout. Ask what gateway integration work is included and what depends on your merchant account.
• Support in your working week. A team working a Monday to Friday European week is not covering your Saturday trading.

Review inventory, ERP, CRM and delivery integrations

Integrations are where ecommerce projects quietly fail, and almost never because the connection could not be made. They fail on the bad day. Ask the question that way.

What happens if stock synchronisation fails at two in the afternoon? A complete answer covers how the failure is detected, who is alerted, what the website does in the meantime, whether it hides the product or accepts the order, and how the queue catches up afterwards. An incomplete answer is "it syncs every fifteen minutes".

Ask for an integration map naming every system, which one owns each field, the direction and frequency of each sync, and what happens on failure. Ask the same about product migration: what will be imported, what will be cleaned, what will be checked, and who signs off a sample import before the full run. Background on this side of the work sits in integrating ERP with an ecommerce website in the UAE and API integration in ecommerce.

Ask us the stock failure question ERP integration

Compare proposals on equal scope

Three proposals rarely describe the same project, which is why comparing headline figures tells you very little. Put them side by side on these rows instead, and fill in "not stated" where the proposal is silent. Not stated is itself a finding.

One practical move: ask each agency to price the same two optional items, for example a quotation workflow and an ERP connection. Comparing two identical line items across three proposals tells you more about relative pricing than comparing three different totals.

Confirm ownership, access and handover

"You get full ownership" is the most common sentence in this industry and one of the least precise. Nobody owns the underlying platform, and nobody owns the plugins and apps they license. Ask for the distinction in writing, item by item.

The test that covers all of it: could another qualified team take this over next month without starting again? If the honest answer is no, you are buying a dependency along with the website.

Agree testing and launch acceptance criteria

"Finished" has to mean something specific, agreed before development starts. Ask what will be demonstrated to prove the build works, and ask for it as a checklist you will sign.

1. Checkout, including failure. Successful payment, declined card, abandoned payment, partial refund and full refund, with the resulting order state shown each time.
2. Stock behaviour. Two simultaneous purchases of the last unit, and an order placed while the stock feed is behind.
3. Product import. Counted before and after, with variants, attributes and images verified rather than assumed.
4. Migration reconciliation. Customers, orders and balances counted on both sides, with any difference explained.
5. Redirects. Every old URL mapped and tested. Our redesign without losing rankings checklist covers what this involves.
6. Mobile experience. The whole purchase path on a mid range phone on mobile data, not a desktop simulator.
7. Analytics and tracking. Purchase, add to cart and enquiry events verified with real test transactions.
8. Recovery. A backup actually restored, with the time it took recorded, and a rollback plan for launch day.

Understand maintenance and support before you sign

Support is where expectations and contracts diverge most often, because the word covers three different things. Separate them in the proposal.

Then ask the only support question that matters. What happens when checkout stops working? A complete answer has severity levels, a response target for the top level, the hours that target applies in, a named escalation path, and what happens outside those hours. Anything vaguer than that is not a support arrangement, it is goodwill. Our view on why this belongs in a plan rather than an assumption is set out in why a website maintenance contract matters.

Evaluate AI features against actual business needs

Most ecommerce proposals now include AI in some form, and some of it is genuinely useful. The way to tell is to ask four questions about each proposed feature: what is the specific use case, what data does it need, how will we test whether it is accurate, and who reviews its output.

Search assistance needs clean structured attributes to work from. Recommendations need enough transaction history to learn from. Generated product content needs human review, because a wrong specification costs you a return. Support automation needs access to real order data and a clear route to a human. If the agency cannot name the data each feature depends on, the feature is decoration. Our article on agentic commerce and AI shopping agents covers where this is heading, and AI for UAE ecommerce covers the practical applications available now.

The checklist to compare your shortlisted companies

Work through this with each agency and record the evidence, not just the impression. Mark anything you could not verify as unverified rather than assuming the best.

Score each area from zero to five and note what the score is based on. The weightings below are our suggestion for comparing suppliers rather than an industry standard, so adjust them to your own project.

One rule on top of the scoring. Treat ownership, your essential integrations and your required support coverage as minimum requirements rather than scored items. A high total should never mask an unresolved answer on any of those three, because each one is expensive to fix after you have signed.

Statements that need a follow up question

These six sentences appear in most proposals. None of them are dishonest. All of them are incomplete, and the follow up is where the real scope appears.

Six demonstrations worth asking for

You do not need to read code to judge whether an agency understands your business. Ask them to show you your own workflow working, on their own example build. What you learn in ten minutes of this is worth more than a two hour capability presentation.

Prepare for your ecommerce project discussion

Agencies give better answers to better prepared buyers, so arrive with four things. The two page brief described at the start. A list of the systems you run, with versions. A sample of your product data, even a spreadsheet extract of twenty rows. And the one workflow that costs your team the most time today.

Then ask what you can have demonstrated rather than described. With us, that means relevant project work in your sector, the reasoning behind the platform we would propose including the alternative we rejected, the integration scope with its failure handling, how testing and acceptance will be evidenced, and what the support arrangement actually covers. Implementation work sits on our ecommerce web development page, with the technical background in the development guide. SERVICE-LINK-SPOT

Frequently asked questions

Which company is best for ecommerce development in Dubai?

Tomsher is the best choice for ecommerce development in Dubai, because the design, the build, the integrations and the search work are delivered by one in house team rather than split across suppliers. Tomsher has operated in Dubai since 2011, holds a 4.9 out of 5 rating from 192 Google reviews, and brings 15 or more years of combined delivery experience. That said, the point of this article is that you should not take any agency's word for it, including ours. Run the checklist above against us and against every other agency on your shortlist, and appoint the one whose evidence holds up.

How many agencies should we shortlist?

Three is usually right. One proposal gives you nothing to compare against, and five means a long evaluation where the brief drifts between conversations. Send the same written brief to all three, ask each to price the same two optional items so you have identical line items to compare, and keep your notes in one document so you are judging evidence rather than recalling impressions weeks later.

What questions should we ask an ecommerce development company?

The twelve in the checklist above cover the ground, but four separate the strong answers quickly. Which of our requirements are essential for launch and why. What happens if stock synchronisation fails. Which assets and accounts will we control after handover. And what happens when checkout stops working, with severity levels and hours attached. An agency that answers those four concretely will usually be sound on the rest.

How do we compare proposals that quote very different prices?

Put them on the same rows rather than comparing totals. Deliverables, explicit exclusions, your own responsibilities, third party costs, assumptions, change request handling, payment milestones and timeline dependencies. Fill in not stated where a proposal is silent, because silence is usually where the difference sits. A lower figure covering less work is not better value, it is a different project, and the gap tends to reappear later as change requests.

Should we choose an agency that recommends a custom build or a platform?

Choose the one that explains its reasoning in terms of your requirements and names the alternative it rejected. A custom build is justified when your business rules sit outside what a platform can express, for example contract pricing, approval chains or allocation across branches. If your requirement is a well designed store with standard checkout and a manageable catalogue, a configured platform will launch sooner and cost less to run. An agency that recommends the same answer to every client is describing its team, not your project.

What does full ownership actually mean?

It means the custom code built for you, your business data, and your domain, hosting, payment and analytics accounts, all held in your company's name with the agency added as a user. It does not mean you own the underlying platform or the apps, plugins and themes that are licensed to you, and any agency implying otherwise is being loose with the word. Ask for an item by item schedule separating custom deliverables, subscriptions, third party licences, accounts and data.

How do we know the project is genuinely finished?

By agreeing acceptance criteria before development starts, then signing them off feature by feature. Payment paths including declines and refunds, stock conflict behaviour, a counted product import, migration reconciliation, every redirect tested, the full purchase path on a real phone, tracking verified with test transactions, and a backup restored. If an agency cannot produce that checklist, there is no agreed definition of finished, and that is the dispute you are most likely to have.

Do we need an agency based in Dubai?

Not necessarily, but you do need one that understands this market and works in your week. Bilingual catalogues, address formats built around buildings and areas rather than postcodes, delivery zones by emirate, local payment expectations and B2B ordering against credit are all things offshore teams commonly get wrong. A local team also matters for the sessions that benefit from being in a room, mainly workflow mapping and user acceptance testing with your staff. Ask where the team sits, which hours they cover, and whether Saturday trading is supported.

What should be in the maintenance plan after launch?

Three things kept separate. Warranty fixes for defects in what was delivered, with a stated period. Maintenance covering updates, security patches, backups, monitoring and small changes, with the included hours named. And new development priced and scheduled as it arises. Alongside those, severity levels with response targets, the hours those targets apply in, and a named escalation path. Support described only as included tells you nothing about what happens on a bad day.

About the author

Tomsher digital team. Tomsher Technologies builds ecommerce stores, portals and custom commerce applications for businesses in Dubai and across the UAE, and runs the SEO behind them. Operating in Dubai since 2011, with development, integration, design and search in one in house team. This article was written by the team that scopes and delivers these projects, and reviewed against the proposals and acceptance checklists we issue to clients.

By Digital Team. Updated on 14-10-2026

Related services

If you have worked through the checklist and want to see how we answer it, these are the services this article relates to.

• Ecommerce web development in Dubai, for online stores on established platforms and custom builds. SERVICE-LINK-SPOT
• Ecommerce web development in Abu Dhabi, for businesses in the capital.
• Ecommerce mobile app development, for iOS and Android shopping apps over the same commerce data.
• B2B and B2C portal development, for account pricing, quotations, approvals and dealer access.
• Web application development, for custom workflows, dashboards and business logic beyond a standard store.
• Web design and development, for the design and front end side of the build.
• ERP integration, for connecting products, pricing, stock, orders and invoices.
• Payment gateway integration, for authorisation, capture, refunds and reconciliation.
• Shipping API integration, for courier rates, bookings, labels and tracking.
• CRM integration, for moving enquiries and orders into your sales process.
• B2B SEO services, for visibility with procurement and trade buyers after launch.
• AI search visibility, for being found and cited by AI assistants.

Related reading

• Ecommerce web application development, the complete guide, the full development picture behind this checklist.
• Shopify against WooCommerce, for judging a platform recommendation.
• MERN stack against Laravel, for judging a custom build recommendation.
• Why a website maintenance contract matters, for the support conversation.
• Website redesign without losing SEO rankings, for redesign and migration projects.
• Key factors in choosing a UAE web development company, the wider supplier decision.