Ecommerce Website Design
in Dubai
Web Tactics is a Dubai studio that builds online stores for UAE businesses. Checkout, the payment gateway, delivery zones and the Arabic version are one build rather than things added afterwards — and the scope and the price are agreed in writing before any work starts.
اقرأ هذه الصفحة بالعربيةSelling online here
is a different build
Three things about an online store in the UAE that decide the build before a single screen is designed.
Payments are set up in your name
A store needs a payment provider that works for UAE merchants, and the account has to be in your name rather than the agency's. Get the per-transaction and monthly fees in writing before anyone quotes the integration, because the fees can change which provider is right for you. Providers operating here include N-Genius, Telr, Tap Payments, PayTabs, Amazon Payment Services, Checkout.com and Stripe.
Cash on delivery decides the order system
Cash on delivery is normal here, and it is the one decision that cannot be added quietly later. The order exists before the money does, so it needs its own status flow, a way to reconcile what the courier collected against your records, and a defined path when a delivery fails. Adding it to a store built around prepaid orders means rebuilding the invisible half.
Arabic checkout is where stores lose orders
Checkout is the hardest screen to get right in Arabic: the fields, the validation messages, the address format and phone entry all change direction. A product page that reads awkwardly costs you some confidence. A checkout that reads awkwardly costs you the order.
The plumbing, decided
before the design
- Delivery zones and a free-shipping threshold. Within the emirate, across the UAE and out to the wider Gulf are three different cost structures, so one flat rate loses money on at least one of them.
- Checkout fields that match UAE addresses. Many addresses here are described by a landmark rather than a street number, so a form demanding a postcode in a fixed format gives you abandoned carts or delivery data nobody can use. Phone entry gets a country selector, not a digit count.
- A tax invoice the store issues itself. If you are registered, the store produces the invoice carrying your registration number, stores it and emails it, in both languages. Adding that capability after launch means reissuing documents for orders you have already taken.
- Product data built around how you actually sell. Variants, what happens when something runs out, and what a customer sees instead of an empty page. These are decisions to make, not defaults to leave alone.
- English and Arabic as two built versions. Not a translation layer over one, and the checkout is built in both rather than translated once it is finished.
- The files, on handover. The store, its theme and its data are yours.
What we do not do: run your payments through an account of ours, name a launch date before the scope is agreed, or build a store for a catalogue that does not exist yet — we will tell you to build the catalogue first.
What a store costs
and why it varies
Our minimum engagement is ~$3,000 (11,010 AED), and an online store sits above it — a store is a website plus a catalogue, a checkout, a payment integration and an order system. Where it lands depends on how many products and variants you carry, whether you take cash on delivery, where you ship, and whether checkout has to work in both languages.
The final scope and its price are confirmed in writing after a scope review. If a store is not the right product yet — no catalogue, no supplier, no stock — we will say so rather than build one and invoice for it.
Straight answers
Tell us what you sell,
and where it ships
Five answers make a store quotable: products and variants, prepaid or cash on delivery, where you ship, one language or two, and whether you issue tax invoices. Send those and you get a personal reply within 24 hours — with a number attached.