Services · Website development · Pharmacy websites
Codeeo delivers pharmacy website development in Saudi Arabia for national chains, regional groups and independent pharmacies planning to grow. We build Arabic first information and enquiry websites that hold hundreds of branch records accurately, respect SFDA rules on medicine advertising, handle personal data under the PDPL and give patients in any city a quick answer: which branch is near, is it open, what can the pharmacist do and how do I reach them. Your own teams run the content from a CMS with clear approval steps.
This page is about your public website, not online sales. Ordering and paying for medicines online is a separate, licensed project we scope on its own. Our Riyadh office hosts in person workshops; clients in other cities work with us by video call.
200+ companies servedFrom a first store to an ADX listed developer
What the website covers
A pharmacy group with branches in Riyadh, the Makkah region, the Eastern Province and smaller cities such as Buraidah, Abha or Tabuk faces a problem a single store never does: keeping hundreds of addresses, hours and services correct at the same time, in two languages, across the website and every map listing. Add national rules on advertising and personal data, and the website becomes an operational system rather than a brochure.
These are the parts we build for groups operating at national scale. Smaller operators planning expansion get the same structure in a lighter form, so growth does not mean rebuilding the site later. The order below reflects where national groups usually feel the most pain first: inaccurate branch data, slow approvals and patchy compliance evidence. We adjust it after hearing from your regional teams.
One structured record per branch holding region, city, district, coordinates, hours, services, languages and contact routes. The website, branch pages and Google listings all read from it, and regional managers can edit only the branches assigned to them, with changes logged. Bulk imports from spreadsheets help during the first load.
One correction updates every place a branch appears.
Visitors can browse by region and city or let the site locate them and list the nearest open branches. The hierarchy also gives search engines a clear structure, with city pages that describe local branches properly rather than listing addresses. Late night branches are flagged in every list.
Patients anywhere reach a nearby branch in a few taps.
An approval workflow that holds any text mentioning medicines for review by your responsible pharmacist and compliance lead before it publishes, reflecting SFDA rules that restrict promotion of prescription medicines and require approval for many product claims. Approvals are recorded per page. Urgent notices, such as a product recall message, can be fast tracked by named approvers.
Marketing moves quickly without publishing risky claims.
For groups dispensing through Wasfaty, the Ministry of Health e-prescription service, each branch page shows whether it takes part, with a short, accurate explanation of what a patient should bring. Head office updates participation from the branch database as it changes. Wording is checked by your pharmacists before publishing.
Patients with electronic prescriptions choose the right branch.
Enquiry forms that collect only what is needed, store attachments outside the public site and delete them on a schedule. A bilingual privacy notice and consent banner follow the PDPL and SDAIA guidance, and analytics run only after consent. Retention periods are set per form type.
Customer trust is protected as enquiries grow.
Hosting set up under your company, with a Saudi data region where your policy or a client requires it, a web application firewall, role based admin access, backups and monitoring documented to match the NCA controls your IT team follows. Penetration test findings can be tracked against the same documentation.
Security reviews go faster because the evidence is ready.
Right to left layouts designed first, with full English versions that keep the visitor on the matching page when they switch. Medicine and service terms are reviewed by pharmacists, and branch names are written the way local customers actually say them. Arabic typography is chosen for legibility at small sizes.
Saudi families and expatriate residents get the same clarity.
Large tap targets, strong contrast, readable Arabic type and screen reader labels in both languages, tested against WCAG guidance. Older patients and carers searching on behalf of a relative are a large share of pharmacy visitors, and the site has to work for them without help.
Nobody is shut out of basic health information.
A careers area for pharmacists and pharmacy technicians by region, with roles routed to your HR system. It supports recruitment of Saudi professionals in line with Saudisation requirements for pharmacy roles, and shows candidates where branches are and what development you offer. Each posting shows the city and branch type.
Recruitment reaches qualified candidates in every region.
Pharmacy and organisation structured data generated from the branch database, consistent contact details across all listings, and XML sitemaps that update when branches open or close, so search engines always see the current network. A reporting view then shows calls, WhatsApp taps and enquiries by region, city and branch, collected with consent, so leadership sees where demand grows. Exports feed your own BI tools.
Each branch stays eligible to appear in local results.
Who this is for
National scale changes the brief. Accuracy across many branches, governance over what is published, and consistent handling of personal data matter more than visual novelty. Here are the four groups we most often work with in Saudi Arabia, and how the website differs for each. Many groups recognise themselves in two of these at once, and the plan simply combines them.
Growth by acquisition often leaves a group with several websites, inconsistent branding and conflicting branch data. We merge them into one site and one branch database, redirect every old address so search value carries over, align all map listings and retire content that no longer meets current advertising rules. Regional teams keep control of their own stores. Brand guidelines are applied consistently, so a customer moving between regions sees one recognisable group. The result is one brand voice and one place to check that every branch is listed correctly.
One site and one data source replace several partial ones.
A group strong in one province needs a structure that can absorb new cities without redesign. We plan the region and city hierarchy, branch templates and editor roles in advance, so opening in a new city means adding records rather than commissioning pages. Local content is written for each new city, never copied. Reporting by city shows which new areas generate demand online before branches open there. Regional managers in new provinces are trained before their first branch goes live.
Build for the network you plan, not only the one you have.
Groups with branches near the holy cities serve pilgrims from many countries during Hajj and Umrah. Their sites need visitor guidance in several languages, very clear late hours and branch locations described by landmarks, while the rest of the network keeps a standard residential focus. Seasonal hours for Ramadan and the Hajj period are scheduled in advance from head office. Branch staff who speak Urdu, Bahasa Indonesia, Turkish or other visitor languages are shown on the relevant pages, and guidance explains politely that dispensing follows Saudi rules and the pharmacist's judgement.
Visitor features can apply to some regions and not others.
A single store today may run five branches in a few years. We build a compact site now on the same branch data structure a chain would use, so adding locations, languages or a careers section later does not mean starting again. The first release stays small and affordable to maintain. We also help set up an accurate Google listing, which often matters more than the site itself at this stage. As branches open, each one inherits the same templates, approval steps and listing setup.
Start with the right foundations, then add as you open.
How we work
Codeeo has a team of 80+ across Dubai, Riyadh and Karachi and has delivered 200+ projects across the UAE and the US, and we are rated 4.7 from 23 Google reviews. National pharmacy projects get a project lead, a written scope and a staging site shared with head office and regional managers. Workshops can take place at our Riyadh office or yours; teams in other cities join by video call, so every region is heard before decisions are made. Each stage is signed off in writing before the next one begins, and decisions are recorded so regional teams can see why they were made.
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 usually build national pharmacy sites on Next.js with a headless CMS, or WordPress for smaller groups, chosen by branch count, editor numbers and integration needs. Hosting is registered to you, with Saudi data regions available and security documented for your IT team. Pages are built to load quickly on mobile data in smaller cities, and Core Web Vitals are measured before each regional launch.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
Mainly SFDA advertising rules, the PDPL and your own security controls.
Prescription medicines should not be promoted to the public, and claims about non prescription products generally need SFDA approval, so the site centres on branches, services and pharmacist advice. Personal data collected through forms falls under the PDPL, overseen by SDAIA. Many groups also apply NCA controls to their systems. We build approval steps, consent and hosting documentation around these from the start, and your compliance team confirms the final position. We also keep a record of approvals in the CMS, which helps if a regulator or auditor asks who signed off a page.
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