Ijjad's anonymized first-party account of a Jeddah store moving from fewer than 10 to 200+ monthly orders, with a reported 340% conversion-rate lift. Underlying client analytics are private.
How did a Jeddah e-commerce store go from fewer than 10 to 200+ monthly orders?
In Ijjad's anonymized first-party account, a Jeddah store moved from fewer than 10 to 200+ monthly orders within six months after a rebuild. Ijjad also reports a 340% conversion-rate lift and mobile load time moving from 4.2s to 1.1s. The client analytics are private under NDA.
- Outcome: fewer than 10 → 200+ monthly orders within 6 months.
- Conversion: Ijjad-reported +340% lift after the rebuild.
- Speed: Ijjad-reported mobile load time moved from 4.2s to 1.1s.
- Payments: Mada, STC Pay, Apple Pay, Tabby live.
- Investment: similar Saudi e-commerce builds are scoped after a discovery call.
Project Snapshot
In Ijjad's anonymized first-party account, a Jeddah retailer's store moved from fewer than ten to 200+ monthly orders within six months after a rebuild. Ijjad also reports a 340% conversion-rate lift and mobile load time moving from 4.2 seconds to 1.1. The client identity and source analytics are private under NDA, so this page explains the method and reported outcome rather than offering independent verification.
The Challenge: A Store That Looked Live But Wasn't Selling
The original WooCommerce build had every classic problem of a bargain Saudi e-commerce site:
- 4.2-second mobile load time. The recorded mobile experience was slow enough to make performance a priority in the rebuild.
- Broken mobile layout. Navigation, forms, and checkout fields rendered inconsistently on phones — visible bugs on the exact devices where most traffic was coming from.
- No Mada integration. The store accepted only international credit cards, so the rebuild treated Saudi payment-method fit as a checkout requirement to validate.
- Weak SEO foundation. Product pages had no supported product markup, generic metadata, and little internal linking.
- Fewer than 10 orders/month after 6 months live. The owner was scoping to shut the store down.
The lesson here is the one we see most often with Saudi e-commerce: a bad WooCommerce build is worse than no online store at all, because it scopes money to run, ties up the brand, and shapes the team's belief that "e-commerce doesn't work for us."
Old Stack vs Ijjad Rebuild — Side by Side
| What we measured | Old WooCommerce store | Ijjad Next.js rebuild |
|---|---|---|
| Mobile load time | 4.2 s | 1.1 s |
| Mobile UX | Broken / inconsistent | Mobile-first, tested across devices |
| Saudi payments | Credit card only | Mada · STC Pay · Apple Pay · Tabby |
| Product schema | None | Full Product + Offer schema |
| Monthly orders | Fewer than 10 | 200+ |
The Solution: A Five-Move Rebuild
We didn't patch the existing store. We rebuilt it from scratch on Next.js, with a fundamentally different architecture and a completely different relationship to the Saudi customer.
1. Mobile-First Checkout Experience
We designed the entire store mobile-first, around how Saudi shoppers actually buy on their phones. Navigation, filters, breadcrumbs, product descriptions, and the full checkout were built to minimise taps, load fast on mobile data, and surface trust signals (payment logos, return policy, delivery ETA) exactly where buyers hesitate.
2. Saudi Payment Integration
We integrated the payment methods selected for this merchant's account and customer requirements: Mada, STC Pay, Apple Pay, and Tabby. Payment-method availability, onboarding, settlement, and conversion effects depend on the merchant's approved provider configuration and transaction data. The Saudi Central Bank publishes official payment-system and licensed-provider information at sama.gov.sa.
3. Performance Engineering
The new architecture uses Next.js server-side rendering, caching, and an image pipeline. Ijjad's first-party record reports mobile load time moving from 4.2 seconds to 1.1 seconds. That measurement made delivery performance a concrete workstream; it is not presented as the sole cause of the commercial result.
4. Product-Level SEO Built In
Every product page ships with optimized meta tags, full Product + Offer schema (plan, availability, reviews), clean URL slugs, and internal linking to related products and category pages. We targeted long-tail product keywords that the old site and most competitors were ignoring entirely.
5. Catalogue Restructured Around Customer Search Behaviour
We restructured the catalogue based on how Saudi customers actually search and browse — not how the inventory system happened to be organised. Category pages were rebuilt as proper landing pages with unique copy, not just product grids. This is one of those changes that sounds small and pays for itself permanently.
If your store is in this exact spot — live, looking fine, but generating almost no orders — diagnose the catalogue, checkout, delivery, acquisition, and measurement before choosing between a focused repair and a rebuild. See how Ijjad approaches Saudi e-commerce builds.
The Conversion Funnel Workstreams
The reported conversion change coincided with several workstreams. The private source data does not support assigning a fixed share of the outcome to any one stage:
Landing and navigation
Faster delivery, clearer categories, and mobile-first navigation.
Validate with: Review field performance, landing-page engagement, and product discovery.
Product decision
Clearer product information, delivery expectations, and trust evidence.
Validate with: Review product-view, add-to-cart, and support-question patterns.
Cart and checkout
Reduced friction and surfaced shipping information before payment.
Validate with: Review cart-to-checkout movement and abandonment reasons.
Payment
Configured the approved methods selected for the merchant account.
Validate with: Review provider acceptance, failures, settlement, and completed orders.
The Results — Six Months In
Measurement note: these are Ijjad-reported, first-party figures from an anonymized client engagement. The client identity, commerce analytics, and payment data are private under NDA, so the figures are not independently auditable from this page and are not a forecast for another store.
Project Timeline
| Week | Milestone |
|---|---|
| Week 1 | Audit, UX research, architecture planning |
| Weeks 2–3 | Mobile-first UI design and component library build-out |
| Weeks 4–5 | Payment gateway integration (Mada, STC Pay, Apple Pay, Tabby) |
| Week 6 | SEO setup, product data migration, QA testing |
| Week 7 | Launch, analytics, monitoring |
| Months 2–6 | Ongoing SEO, conversion optimisation, scaling to 200+ orders/month |
Our online store went from barely making sales to processing 200+ orders per month after Ijjad rebuilt it. The storefront, Mada integration, and mobile experience are exactly what our customers wanted.
— Anonymized first-party client testimonial, e-commerce manager in Jeddah; identity withheld under NDA
What This Project Says About Selling Online in Saudi Arabia
This rebuild is useful as a method, not a guaranteed outcome. The workstreams below can be evaluated for another Saudi store only after checking its own demand, catalog, payments, operations, traffic, and baseline:
- Mobile UX is not a checkbox. It's a discipline. Customers can feel the difference between "designed for mobile" and "shrunk to fit" instantly.
- Performance needs a measured budget. Test the rendered store on representative devices and networks, then compare field and conversion data after launch.
- Payment methods must match the merchant and customer. Verify Mada, STC Pay, Apple Pay, and BNPL eligibility with the chosen provider instead of assuming one universal stack.
- Product information must be discoverable. Useful catalog copy, internal links, and supported Product markup work together; schema alone is not a ranking shortcut.
- Choose rebuild or repair from evidence. Architecture, maintenance burden, migration risk, and the cost of current workarounds determine the right path.
From understanding to selling
You now know the workstreams used in this anonymized rebuild. A new store still needs its own demand, catalog, checkout, fulfillment, and measurement baseline before anyone can judge which changes are justified.
Talk to Ijjad about your storeFAQ
How did Ijjad approach this e-commerce rebuild?
The work combined a faster mobile storefront, a shorter checkout, relevant Saudi payment methods, product-level search foundations, and post-launch iteration. Several business and acquisition inputs changed together, so this first-party case does not assign the reported order or conversion change to one feature.
How is an e-commerce store like this scoped?
A similar store with mobile-first UX, Saudi payment integration, and product-level search requirements is scoped after discovery. Catalog size, ERP or warehouse integrations, fulfillment, content, and review cycles change the proposal. This case study does not establish a universal payback window or profit forecast.
Can Ijjad replicate these results for my business?
No specific multiplier can be promised. Mobile performance, checkout clarity, relevant payment methods, and product discoverability are reusable workstreams, but results depend on demand, assortment, pricing, operations, traffic, and competition. Ijjad starts by establishing the store's own baseline and constraints.
Why does Mada matter so much in Saudi Arabia?
Mada is Saudi Arabia's national payment network and is a relevant checkout option for many Saudi merchants. Whether it changes conversion for a specific store depends on the gateway, customer mix, transaction data, and the rest of the checkout. Ijjad verifies payment requirements during discovery rather than assigning one universal conversion effect.
How long did the rebuild take?
Seven weeks from kick-off to launch: 1 week of audit and UX research, 2 weeks of design and component work, 2 weeks of payment integration, 1 week of SEO and migration, then 1 week of launch and monitoring. The 200+ monthly orders milestone was reached around month 6 — it took ongoing SEO and conversion optimisation work, not just the initial rebuild.
Does Ijjad build bilingual Arabic/English Saudi e-commerce stores?
Yes. Ijjad can scope Arabic-English storefronts with RTL layouts, Arabic typography, localized product content, and Arabic search structure. Language coverage is confirmed from the audience and content plan; no universal conversion penalty is assigned to an English-only store without that store's data.
Want results like this for your online store?
Whether you're launching a new e-commerce store or rebuilding an underperforming one, Ijjad can help. We'll audit your current situation, recommend the right approach, and give you a tailored proposal — Saudi-aware builds scoped after a discovery call.
Keep exploring: Ijjad E-Commerce Services · Discuss Scope · Saudi National Design System Case Study · Riyadh Redesign Case Study
Source note
Market context: Saudi Arabia's digital economy reached 16.0% of GDP in 2024, according to the General Authority for Statistics, published December 31, 2025. This is why Ijjad treats modern websites, SEO, e-commerce, AI MVPs, and mobile experiences as business infrastructure across Saudi Arabia, Jordan, Iraq, and the GCC.
