All work · Launching

Ebda

ابدأ

An Egyptian merchant creates a branded Arabic and English store, adds products and takes an order through self-serve onboarding. Built on the commerce foundation behind Force Website Builder, adapted for EGP and Egyptian delivery.

Whisky 11’s self-serve commerce platform for Egyptian merchants · Egypt

Client
Whisky 11’s self-serve commerce platform for Egyptian merchants
Region
Egypt
Status
Launching
Delivery
Whisky 11

The problem and context

Egyptian merchants need an approachable way to start selling in EGP with local payment and shipping choices. Ebda adapts the existing commerce foundation into a self-serve product for that market.

Who uses it

  • Small Egyptian merchants creating their first branded online store
  • Customers ordering in Arabic or English
  • Platform staff managing merchant onboarding, subscriptions and support

What was built

  • Self-serve store setup, themes, product import and subscription billing flows
  • Storefront, merchant admin, orders app, marketing site, documentation and help
  • EGP pricing in piastres, cash on delivery and manual InstaPay confirmation
  • Paymob, Kashier and Fawry payment adapters; Bosta and Aramex delivery adapters
  • Free-tier WhatsApp ordering through wa.me links

How it works

  1. Merchant signs up, verifies their account and chooses a store identity and theme.
  2. They add or import products, configure payment and shipping, and preview the storefront.
  3. Customers place orders; the built onboarding flow has been exercised through a cash-on-delivery order.
  4. Paid-plan billing and gateway/carrier flows become usable once prices and real provider configuration are approved.

How the system fits together

  • Next.js applications cover storefront, admin, orders, marketing, documentation and help.
  • The Express commerce API has been adapted for Cloudflare Workers with Node compatibility; PostgreSQL/Prisma preserves the shared data model.
  • Egypt-specific modules use EGP piastres, Egyptian area data and payment/carrier adapters.
  • The free WhatsApp path uses wa.me links rather than calling the WhatsApp Business API.

Technology stack

  • Next.js 16
  • Express + TypeScript
  • Cloudflare Workers (OpenNext + node compatibility)
  • PostgreSQL (Neon) + Prisma
  • Redis
  • Inngest

Delivery and current status

  • Applications and self-serve flows are built; the project is listed as launching.
  • Automated onboarding and commerce checks exist for the Workers and Node paths.
  • Payment and shipping adapters have contract tests against stubs; production deployment and real sandbox verification remain pending.

Evidence

  • Signup-to-store-to-COD-order flow exercised in automated end-to-end checks
  • Egyptian gateway and carrier adapters tested against stubs; real sandbox verification pending
  • Built; production deployment and provider credentials pending

Scope and operating limits

  • This case study is not a live merchant checkout demo.
  • Final subscription prices, platform fees and provider credentials still need approval/configuration.
  • Manual InstaPay confirmation differs from an automated gateway settlement.
  • Legal drafts and provider-specific commercial arrangements need review before launch.

← All work · Start a project