Ecommerce website development for the GCC is not the same project as building a store for the US or Europe. The differences that decide whether your store works are local payment methods, Arabic and right to left as a first class version rather than a translation, tax and invoicing rules that differ by country, and delivery expectations shaped by cash on delivery and same city dispatch.
We are WeboTech Studio. 6+ years, 230+ projects shipped. This is what we scope on a GCC store build, and what we tell clients to decide before a single page is designed. It is also the part most international agencies get wrong, because none of it shows up in a generic ecommerce checklist.
What ecommerce website development actually involves
A store is a set of connected systems, not a design. The build covers:
- Catalogue. Products, variants, stock, pricing, categories, and how your team adds new items without a developer.
- Checkout. Cart, shipping options, payment methods, order confirmation, and the failure paths when a payment does not complete.
- Payments. Gateway integration, refunds, and reconciliation with what actually lands in your bank account.
- Tax and invoicing. Correct tax handling for the countries you sell in, and invoices that satisfy local requirements.
- Fulfilment. Shipping rates, courier integration, tracking, returns.
- Operations. The admin your staff use daily, order notifications, and reporting.
Design sits on top of all of that. When a quote is mostly about the look of the homepage, the difficult 80% has not been priced.
Payments in the GCC
This is the most common reason a GCC store underperforms. Offering only international card payments cuts out a large share of buyers in Saudi Arabia.
- Mada. Saudi Arabia's domestic card network. Most debit cards in the Kingdom are Mada cards. If your checkout does not accept Mada, a significant portion of Saudi customers cannot pay you with the card in their pocket. This is not optional for a Saudi facing store.
- International cards. Visa and Mastercard for regional and international buyers, and for corporate cards.
- Apple Pay. Widely used across the region and it measurably reduces checkout friction on iPhone, which is a large share of GCC traffic.
- Wallets. Local wallets such as STC Pay in Saudi Arabia are worth supporting depending on your audience.
- Buy now pay later. Tabby and Tamara are common in Saudi Arabia and the UAE and are frequently requested by customers on higher value carts.
- Cash on delivery. Still expected by a portion of buyers in several GCC markets. It brings its own costs, failed deliveries and cash handling, so decide deliberately rather than by default. Many stores restrict it by order value or by city.
You do not integrate each of these separately. You choose a payment service provider that aggregates them. In this region the names you will encounter include HyperPay, PayTabs, Moyasar, Telr, Checkout.com and Network International, alongside Stripe and PayPal for international coverage. We will not quote fees here because they are negotiated per merchant and change. Get written pricing from 2 providers, and ask specifically about settlement time, refund handling, chargebacks, and which methods are included versus charged separately.
One practical point from experience. Confirm which payment methods your provider supports in your specific country of registration before you build. Support varies by market, and discovering after launch that a method is unavailable in your country is an expensive rework.
Tax and e-invoicing
Tax rules differ across the GCC and they change, so treat this section as a list of what to confirm with your accountant rather than as advice.
VAT applies in Saudi Arabia and the UAE, and registration thresholds and rates are set by each country's tax authority. Your store needs to handle tax correctly at the product level, display prices in the way your market expects, and produce invoices that carry the required details. If you sell across borders within the GCC, the treatment can differ from domestic sales, and that is a question for your accountant before you configure anything.
In Saudi Arabia, e-invoicing is required through ZATCA. In practice this means your invoices must be generated in the compliant electronic format, with the technical elements ZATCA specifies, and your systems need to be able to integrate with ZATCA as required for your business. Some platforms have established solutions for this and some do not, which is why we raise it during platform selection rather than after the build. If a store is already handling this through your accounting system, the website work is about making sure order data flows into it cleanly rather than duplicating the compliance layer.
Two rules we apply on every build. Never invent tax logic in the website when an accounting system already owns it, and never launch without your accountant reviewing a real test invoice produced by the live system.
Arabic and right to left
Arabic is not a language toggle. In a right to left layout the navigation, product grids, form fields, breadcrumbs, progress indicators and directional icons all mirror. Prices, phone numbers and dates need consistent formatting decisions. Fonts chosen for English rarely render Arabic well, so the Arabic version needs its own typeface and line height to look like it was designed rather than converted.
Product content matters as much as layout. Machine translated product descriptions read as careless to Arabic speaking buyers, and product names in particular need a human decision about whether to translate or transliterate. Search inside your store also needs to handle Arabic properly, including different spellings of the same term, or customers will not find products you definitely stock.
Delivery expectations
GCC buyers expect fast delivery within their own city, and they expect to know where the order is. Practical implications for the build: shipping rates by city and emirate or region, a clearly stated dispatch time, courier integration so tracking numbers reach the customer automatically, and an address form that fits how addresses actually work here rather than a form designed for another country. National address formats in Saudi Arabia and area based addressing in the UAE both benefit from map based address selection, which reduces failed deliveries more than any other single change we have made to a checkout.
Returns policy should be written and visible before launch, not improvised after the first dispute.
How long an ecommerce build takes
A store on an established platform, with a clean theme, local payments configured and a modest catalogue, is usually 4 to 8 weeks. A custom store with bilingual content, integrations to your inventory or accounting system, and a tailored checkout is typically 3 to 5 months. The variables that move the timeline most are product data quality, photography, and how many existing systems the store must talk to.
On platform choice, the practical options are Shopify, the regional platforms Salla and Zid which are built around Saudi requirements, WooCommerce, and a custom build in something like Next.js. Each is right for a different situation. Volume, catalogue complexity, integration needs and how much control you want over the checkout decide it. Anyone recommending a platform before asking about your payments, invoicing and fulfilment is recommending the one they always use.
Common questions
Do I have to accept Mada?
If you sell to customers in Saudi Arabia, yes in practical terms. Mada is the domestic card network and most Saudi debit cards run on it. A checkout that accepts only international cards will lose a meaningful share of orders, and the customer usually does not tell you why they left.
Which platform is best for a GCC store?
There is no single best. Salla and Zid are built for the Saudi market and handle a lot of local requirements out of the box. Shopify is strong for design flexibility and app coverage. WooCommerce suits teams who want full control at lower licence cost. A custom build makes sense when your operation is unusual or your catalogue and traffic are large. Choose after you have mapped payments, invoicing and fulfilment, not before.
How do I handle VAT and e-invoicing on the site?
Configure tax at the product level rather than adding it as a line at checkout, confirm the correct treatment with your accountant, and make sure invoices produced by the store meet the requirements of the country you operate in. In Saudi Arabia that includes ZATCA e-invoicing, which is best handled by a platform or accounting integration built for it rather than by custom code written for your store alone.
Should I offer cash on delivery?
It depends on your product and margin. It raises conversion for some audiences and brings failed deliveries, cash handling and reconciliation work. A common middle path is to allow it under a set order value, in specific cities, and to require phone confirmation on larger orders.
Can I start small and add features later?
Yes, and we usually recommend it. Launch with a working catalogue, local payments, correct invoicing and reliable delivery. Add wishlists, loyalty, subscriptions and marketplace integrations once you have real orders telling you what customers want. The one thing that is expensive to retrofit is the data structure, so get the catalogue and order model right at the start.
If you are planning a store for Saudi Arabia, the UAE or the wider GCC, send us your product range and how you handle orders today. We will come back with a platform recommendation, the payment setup we would use, and a scope and timeline in writing. If your existing store is losing orders at checkout, we will look at that instead and tell you where they are going.
