Which e-commerce stack does Ijjad build?
Ijjad only builds custom e-commerce websites and custom e-commerce systems. We do not build or configure Salla, Zid, Shopify, or WooCommerce stores. Hosted platforms can be useful for some merchants, but Ijjad is the fit when performance, ownership, SEO, checkout control, and integrations matter.
Do you integrate Mada, STC Pay, Tabby, Tamara, and ZATCA?
Those payment and invoicing flows can be scoped when they fit the merchant and market. Delivery depends on merchant eligibility, provider coverage, approved accounts, documentation, credentials, sandbox access, and the applicable tax and invoicing requirements. The merchant should validate legal and tax obligations with qualified advisers; Ijjad implements the approved technical requirements.
What about ZainCash, FastPay, COD for Iraqi e-commerce?
Wallet, card, and cash-on-delivery flows are selected from buyer demand, merchant eligibility, provider availability, settlement requirements, and courier operations. A named provider or real-time automation is included only after its current coverage, API, credentials, and test access are confirmed.
How long does an e-commerce build take?
Timeline depends on catalog and migration work, checkout and payment providers, shipping, tax and invoicing requirements, integrations, languages, content readiness, testing, and approvals. The proposal should state milestones, preview cadence, staging ownership, dependencies, and acceptance checks instead of promising a date from SKU count alone.
How does this page differ from the country-specific e-commerce pages?
This page is the multi-market hub. The Saudi page covers local checkout and invoicing dependencies, the Jordan page covers local and regional payment and courier access, and the Iraq page provides a payment-route discovery matrix. Use the country page when the launch is single-market.
Can you build a multi-vendor marketplace?
Yes, when discovery supports a custom marketplace. Scope can include vendor onboarding, commission rules, dashboards, customer-facing vendor pages, order routing, catalog governance, disputes, and settlement logic. The architecture depends on the catalog, operating model, integrations, risk, and ownership requirements.
What about post-launch — cart abandonment, retention, ad campaigns?
Abandoned-cart, email, SMS, loyalty, and retention workflows are added only when they fit the scope, consent requirements, provider access, and operating plan. Paid media is handled by specialist partners; Ijjad focuses on the storefront and measured on-site journey.
Do you handle inventory, warehouse, and logistics integrations?
Yes, when discovery supports them and the merchant or provider can supply suitable documentation, credentials, data, and test access. ERP, warehouse, and courier capabilities vary by account and geography, so rates, labels, tracking, returns, inventory, and manual fallbacks are confirmed before an integration is promised.