Home / Sectors / E-Commerce
Vertical · Enterprise E-Commerce

Commerce that survives
the National Day spike.

Every Saudi e-commerce platform looks fine until the campaign launches. We engineer headless, edge-cached, microservices commerce with ZATCA Phase 2 native, so checkout holds through 12× traffic, e-invoices clear automatically, and the marketing team can actually push the button.

0.6sPage load at National Day peak
12×Peak capacity headroom
+41%Conversion uplift on refit
Order summary
Items3 in cart
Mada / Apple PaySAMA gateway
Step 1Add to cart

A fast storefront with search, variants and real-time stock.

Checkout
PaymentAuthorized
ZATCA invoiceFatoorah e-invoice
Step 2Checkout

Mada and Apple Pay through a SAMA gateway, with ZATCA e-invoicing.

Order confirmed

Paid, invoiced and routed to fulfillment.

Step 3Confirmed & shipped

The order is invoiced and routed to fulfillment automatically.

Swipe to explore
E-commerce, engineered

From cart to ZATCA invoice, checkout that just works.

Storefront, Mada & Apple Pay, ZATCA e-invoicing, inventory and fulfillment, one platform built end to end.

Sneakers320 SAR
Add
Watch890 SAR
Add
Bag540 SAR
Add
Shoes410 SAR
Add
Cap95 SAR
Add
Band180 SAR
Add
Your Cart
Sneakers320
Watch890
Bag540
Total1,750 SAR
MadaApple PayCard
Checkout
ZATCA e-invoice ✓
StorefrontMada & Apple PayZATCA invoiceInventoryFulfillment
The challenge

Where do commerce platforms fail?

The recurring patterns that turn a marketing win into a war room, and the engineering that makes peak day boring.

Checkout collapse

Cart flow degrades, payment timeout cascades, customer chargebacks follow. Recovery cost dwarfs the campaign budget.

ZATCA non-compliance

Manual e-invoice issuance, missed Fatoorah requirements, rejected submissions. Each rejection erodes margin and brand trust.

Slow search & filters

Faceted search times out on a category with 10k SKUs. Bounce rate climbs; the conversion model the deck assumed never materialises.

Vendor data drift

Sellers update price and stock on three systems. The storefront shows fiction; oversells, refunds and disputes pile up.

Payment failures

One gateway, one outage, an entire revenue day lost. No orchestration, no failover, no observability.

Returns logistics

Returns handled by hand, refund posted late, ZATCA credit notes inconsistent. Loyal customers churn quietly.

What we build

What do we engineer?

Production modules across NX Launch and NX Grow engagements for enterprise and multi-vendor commerce.

Headless storefront

Decoupled storefront with edge SSR and atomic deploys. The marketing team ships, engineering doesn't break.

ZATCA Phase 2 invoicing

Cryptographic stamping, real-time clearance, credit/debit notes, invoice flow tested against ZATCA sandbox and production.

Payment orchestration

Multiple gateways behind one abstraction. Routing on success rate, retry on failure, fallback on outage, audit on every attempt.

Multi-vendor onboarding

Self-serve seller onboarding with KYC, ZATCA registration capture, payout flows and dashboards, built for scale, not for the first ten sellers.

Search & recommendation

Indexed search with Arabic + English stemming, personalised ranking and an A/B framework the merchandising team actually uses.

Returns & reverse logistics

Customer self-service returns with automated ZATCA credit notes, refund orchestration and reverse-logistics integration.

0.6sPage load at National Day peak
12×Peak traffic capacity vs baseline
+41%Conversion uplift post re-architecture
0 CLSLayout shift across templates
Common questions

Engineering Saudi e-commerce, answered

Can you migrate from a packaged platform without losing revenue?

Yes, that's typical of an NX Grow engagement. We sequence the migration so storefront, checkout and admin are replaced incrementally behind feature flags, with traffic shifted gradually rather than in a single risky cutover.

Is ZATCA Phase 2 really hard?

It's exacting more than hard. Cryptographic stamping, exact field-level data shapes and live clearance leave little room for ambiguity, we've built it enough times to ship it cleanly the first time.

How do you handle the National Day / White Friday surge?

By load-testing against it months before. Edge caching, autoscaling, async order processing and queued payment authorisation keep the storefront responsive while the back-end works through the volume.

Do you support Arabic-first storefronts properly?

Yes, RTL is engineered into the design system, not retrofitted. Arabic search, currency, address formats and product attributes are handled natively.

Engineer commerce
built for the campaign.

Tell us your next big spike. We'll map the architecture, ZATCA flow and payment orchestration that turns peak day into a measured release.

We usually reply within one business day
Other sectors

Adjacent verticals we engineer