Ajza
Multi-platform automotive marketplace — five marketplaces, one backend, web and native.
// By the numbers
- 5
- Revenue streams live
- 6
- Apps shipped
- AR · EN
- Bilingual from day one
- Real-time
- Live order tracking
parts e-commerce, on-demand services and repair-on-wheels — one backend runs them all
every side of the market — customer, supplier, rider, admin — on web and native
full Arabic RTL across every app — no market left waiting
customers watch services and deliveries move on the map
// From the client
We didn't get a prototype — we got a running business. Storefront, the supplier and rider apps, the admin dashboard, payments, live tracking: one backend behind all of it, in Arabic and English from day one. It launched and it stayed up.
Founder
Automotive parts & services marketplace · Saudi Arabia
What the business was up against
Buying a car part or booking a service in the Saudi aftermarket meant working the phone: call a shop, describe the car, hope the part fits, arrange payment separately, and have no record afterwards. Suppliers had no digital storefront and no way to answer a request for a rare part beyond WhatsApp. The business needed all of it — parts commerce, service booking and mobile repair — under one account, in Arabic, with the money and the order history actually traceable.
A multi-sided automotive marketplace for parts e-commerce, on-demand car services, and repair-on-wheels — five distinct transactional flows running on a single backend, delivered across web dashboards and three native mobile apps, fully bilingual Arabic/English.
How it's put together
Customer App
Shop · book · track
Supplier App
Store operations
Rider App
On-demand repair
Admin Console
Operations & analytics
Partner Dashboard
Store management
Marketing Site
Onboarding & signup
Backend API
Real-time gateway · auth · catalog · orders · payments · chat
Relational Database
Audited · soft-delete
Object Storage
Media & uploads
Payments
Card · wallet · cash
Push & SMS
Notifications · OTP
Logistics
Shipping & tracking
One backend serving five marketplaces across web and native.
The calls that shaped it
The handful of decisions that determined how this system behaves — and what each one bought.
- 01
One backend for five marketplaces, not five products
Direct orders, RFQ negotiations, service bookings, on-demand repair and third-party parts differ commercially but share customers, wallets and settlement. Modelling payment and orders polymorphically meant a new revenue stream became a new flow rather than a new platform.
- 02
One ledger settles every flow
Rather than a balance column per feature, every credit, cashback, coupon and refund is an entry against a single wallet ledger. Adding a marketplace never risked the arithmetic of the ones already live.
- 03
Three native apps instead of one with hidden menus
Customers, suppliers and repair representatives got separate Flutter apps against the same API. Each restricts to a single role and redirects users who open the wrong app — clearer store listings and no permission-shaped UI.
- 04
Store access resolved once, at the access layer
Owner-versus-employee and per-employee permissions are decided in one place on every action, instead of re-checked in each endpoint. Multi-branch stores could delegate safely without a per-feature audit.
- 05
Bilingual in the data model, not the view layer
Arabic and English were carried from the schema through API, web, mobile, email and SMS. There was never a translation retrofit, and neither language shipped late.
Signature capabilities
Five marketplaces, one platform
Direct orders, RFQ negotiations, service bookings, on-demand repair, and third-party parts all settle through a single, polymorphic payment and wallet system.
Real-time everything
Live chat across four domains plus on-map tracking for repair representatives, hardened for production at the proxy layer.
Multi-tenant store access
Store owners issue fine-grained, per-employee permissions; one access layer resolves owner-versus-employee on every action.
Role-segregated native apps
Three native apps share one backend; each restricts to a single role and self-corrects users who open the wrong app.
Wallet, coupons & refunds
A unified ledger settles any flow, with credits, cashback, scoped coupons and audited refunds.
Bilingual end-to-end
Arabic (RTL) and English shipped from the data model through API, web, mobile, email and SMS.
Business feature set
The functional scope delivered across every part of the product.
Customers
- Parts catalog & search
- Multi-store cart & checkout
- Card, wallet & cash payments
- Unified orders across all flows
- Order tracking & invoices
- Wallet top-up & transactions
- Car-wash service booking
- On-demand repair with live tracking
- RFQ store requests & chat
- Reviews, favorites & saved addresses
Stores & suppliers
- Store & multi-branch management
- Product catalog with car compatibility
- Incoming orders & fulfilment
- Service menu & scheduling
- Offers & accessories
- Team & per-employee permissions
- Store-request offers & chat
- Finance, invoices & analytics
Representatives
- Job queue by status
- Live customer chat
- Earnings & transaction history
- Push notifications
Admin & platform
- Users & wallet management
- Company / store approval
- Product approval queue
- Orders & status workflows
- Service bookings & shipping
- Coupons & promotions
- Notifications & broadcasts
- Cross-domain analytics
- Bilingual AR / EN with RTL
What changed operationally
Documented outcomes from the delivered system. Where exact figures are confidential, the operational change is stated instead.
- Five distinct transactional flows running on one production backend
- Six shipped surfaces — customer, supplier and rider apps plus admin, partner and marketing web
- Manual phone-and-WhatsApp ordering replaced by traceable in-platform orders
- Full Arabic RTL across every app and notification from launch
- Live map tracking for on-demand repair, visible to the customer
- Wallet, coupon and refund movements auditable end to end
What we had to work within
- Arabic-first market — RTL could not be a later phase
- Cash and wallet still carry a large share of orders alongside cards
- Suppliers range from single shops to multi-branch chains with staff
- Repair representatives work on mobile data with unreliable coverage
- Real-time chat and tracking had to survive the production proxy layer
What I owned
End-to-end on this project — from architecture and data modelling through to a shipped, production product.
- End-to-end architecture across web, native and backend
- Backend services, data modeling & real-time gateway
- Three native mobile apps: customer, supplier, rider
- Web admin & partner dashboards
- Payments, storage, push, SMS and logistics integrations
- Bilingual Arabic/English with full RTL
- Production deployment, reverse-proxy & mobile release automation
Built with
Backend
Web
Mobile
Infrastructure
Integrations
Want something like Ajza?
Boutique software studio — agency-quality systems, shipped by one senior engineer.
// Related work
