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.
Can the store accept Mada and STC Pay, offer Tabby and Tamara installments, and issue ZATCA-compliant invoices?
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?
Whether a store offers wallets, cards, cash on delivery or a mix of them depends on buyer demand, merchant eligibility, provider availability, settlement requirements and courier operations. A named provider or real-time automation is included only after we confirm its current coverage, its API, and the credentials plus test access it needs.
How long does an e-commerce build take?
Timeline depends on the size of the catalog and any migration work, on which checkout and payment providers are involved, and on the shipping rules of each market together with its tax and invoicing requirements. Integrations and additional languages add time. So do late content, the test cycle and the approvals. Rather than promising a date from SKU count alone, the proposal should set out milestones, preview cadence, who owns staging, the named dependencies and the acceptance checks.
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 and order routing, along with catalog governance, dispute handling and settlement logic. The architecture follows from the catalog, the operating model, the integrations, the risk profile and the ownership requirements.
What about post-launch — cart abandonment, retention, ad campaigns?
Abandoned-cart recovery, email or SMS journeys, and loyalty and retention workflows are added only when they fit the scope, the consent requirements, provider access and the operating plan. Paid media is handled by specialist partners; Ijjad focuses on the storefront and measured on-site journey.
Do you handle inventory, warehouse management and logistics integrations?
Yes, when discovery supports them and the merchant or provider can supply suitable documentation with the credentials, sample data and test access we need. What an ERP, a warehouse system or a courier can actually do varies by account and by geography, so rates, labels, tracking, returns, inventory sync and the manual fallbacks are confirmed before any integration is promised.