Services · Ecommerce development · Online stores
Codeeo offers ecommerce website development Riyadh retailers, distributors and homegrown labels use to take payment online, in Arabic first with English alongside. We build the storefront, catalogue, checkout and the back office behind it, connected to your stock, your couriers and ZATCA compliant invoicing. Because the capital is where so many Saudi brands keep their head office, the store usually has to serve Riyadh districts on the same day and ship to every other region on a slower, clearly stated promise.
Our team works from an office in Riyadh, so planning sessions, design reviews and launch rehearsals can happen in person with your buyers, marketing and finance staff in the room. That matters when the store touches pricing, stock and tax all at once.
200+ companies servedFrom a first store to an ADX listed developer
What the store includes
Riyadh shoppers are used to quick delivery, instalment options at checkout and stores that read naturally in Arabic. They also compare prices with marketplaces in another tab, so a brand store has to give them a reason to buy direct: accurate stock, honest delivery dates, easy returns and service in their language.
The city brings its own pressures. It spreads out over a very wide area, so a delivery promise that works in Al Olaya may not hold for a customer on the far eastern edge. Big seasonal events, Riyadh Season above all, push traffic far above a normal week, and many Riyadh companies also sell to trade buyers who expect their own prices and payment terms. The capabilities below are the ones we most often build for stores run from the capital, ordered roughly by how early they appear in a project.
Pages are designed right to left from the first wireframe, with English as a full second language rather than a translated copy. Product names, size guides, filters and checkout labels are written by people who know how Riyadh shoppers search, including the colloquial terms they type into Google.
A store that feels local to Arabic speakers and clear to everyone else.
Products, sizes, colours, bundles and kits are structured so your merchandisers can add a range without a developer. Attributes drive filters, comparison tables and structured data, and bulk import keeps a seasonal drop of several hundred lines manageable.
New ranges go live in hours, not weeks.
Arabic words are typed with and without hamza, with different forms of alef and taa marbuta, and often in Latin letters. Site search normalises these variations, handles synonyms your merchandisers add, and falls back to related products instead of an empty page, so a shopper in Riyadh finds the item however they spell it.
More searches end on a product page rather than a dead end.
Checkout reads the Saudi National Address or a map pin and offers delivery options by district: same day where your fleet or courier can reach it, next day for outer areas, and scheduled slots for bulky goods. Outside Riyadh, the store switches to national courier rates and dates.
Customers see a date the operation can keep.
For brands with mall stores or showrooms around the city, shoppers reserve online and collect from the nearest branch. Branch stock is read from the POS, staff confirm the order is ready, and the customer receives a collection message with opening hours.
Online orders bring people into your stores.
A SAMA licensed gateway takes mada, Visa, Mastercard and Apple Pay, with STC Pay where your gateway supports it and Tabby or Tamara for instalments. Cash on delivery can be limited by district, basket value or customer history to reduce failed deliveries.
The payment people expect, with fewer abandoned carts.
Distributors and wholesalers based in Riyadh often sell to shops, clinics, offices and contractors as well as the public. Approved trade accounts see their own price lists, minimum quantities, quick reorder from past orders and payment on account, while the public store stays unchanged.
One store handles retail and trade orders.
Campaign pages, countdowns and limited stock drops are prepared ahead of the season, Ramadan and White Friday. We load test checkout and search, cache what can be cached, and queue order exports so a spike does not freeze your warehouse system.
The store stays fast on the nights that matter most.
Every order produces a VAT compliant tax invoice with the QR code and the fields Fatoora requires, issued through your ERP or invoicing system where it is already integrated with ZATCA. Credit notes follow refunds automatically, and finance gets clean exports by day and channel.
Online sales reconcile with the books without manual work.
Customers start a return from their account, choose a reason and pick collection or branch drop off. The store applies the return rules you publish under the e-commerce law, issues the refund or exchange and keeps a history support staff can see. Return reasons are reported by product, so buyers can spot sizing or quality problems early.
Fewer calls about where a refund has got to.
Who this is for
Most of the online stores we plan in the capital start from one of four positions. The right scope depends less on how many products you sell than on where your stock lives, who your buyers are and how much of the operation already runs on software. These are the starting points we see most, and how the first release usually differs for each. In every case, the first release is deliberately narrow: enough to take real orders and learn from them, with the next features chosen from what customers actually do.
You already sell through stores in Riyadh malls and perhaps through marketplaces, but the brand site is a catalogue without a cart. The first release connects branch and warehouse stock, adds click and collect, and gives your loyalty members one account across shops and the website. Marketplace listings can carry on alongside; the brand store is where your margin and customer data stay with you.
Stock accuracy decides whether this works.
Orders arrive by direct message and payment links, and the founder answers every question personally. We move that into a proper store with variants, delivery rules and payment at checkout, keep the visual identity that built the following, and set up product pages that can rank in Arabic search rather than depending only on paid posts.
Your warehouse sits in one of Riyadh's industrial areas and most revenue still comes from shops and businesses ordering by phone. A combined store gives trade buyers their own pricing and reorder tools while opening a direct channel to consumers. We plan account approval, credit limits and invoice terms with your finance team before any design starts.
The current platform is slow, heavily patched or tied to an agency that has gone quiet. We audit the existing store, keep the URLs and products that earn traffic, migrate customers and order history, and rebuild on a platform your own team can run. Redirects are mapped page by page so rankings carry over.
A migration plan is written before anything is switched off.
How we work together
Most clients begin with a fixed scope first release, agreed after the discovery workshops, then move to a monthly retainer for campaigns, new features and platform updates. Larger retail groups sometimes take a dedicated team of designers and engineers who work alongside their own ecommerce staff for a longer programme. Whichever route you choose, scope, dates and responsibilities are written down before work starts, and you can meet the people building your store at our Riyadh office.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
We build on Shopify, WooCommerce, Salla or Zid when a hosted or managed platform fits, and on a headless Next.js storefront when the catalogue, integrations or traffic peaks call for more control. Hosting, monitoring and backups are set up in your accounts. The choice follows your operation, your budget for running costs and the skills of the team who will look after the store, not our preference.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
It depends on the catalogue, the integrations and the launch date you are working back from.
A store with a clean product file and a single gateway moves faster than one that must sync with several branch POS systems, an ERP and trade price lists. We agree the timing after the discovery workshops, once we have seen your data and systems, and we usually plan backwards from a date that avoids launching in the middle of Riyadh Season or Ramadan trading. Once the scope is signed, each stage has its own written date, so you can plan photography, stock and campaigns around it.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
React
Next.js
TypeScript
Node.js
Laravel
WordPress
Shopify Plus
WooCommerce
BigCommerce
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio