Ghulam Abbas

Mine: the Laravel tenancy and queue pipeline, and the FastAPI RAG + ordering brain.

An AI shop assistant a consumer brand can put on every chat channel — it answers from the brand's own catalog, recommends, and takes real orders. I designed the conversational ordering flow end to end: fuzzy catalog search → variant selection → cart → upsell → validated intake → COD confirmation → order created in WooCommerce, with a local order snapshot so a gateway failure degrades gracefully instead of dropping the sale. The RAG pipeline (LangChain + FAISS over PDF/DOCX/OCR ingestion) keeps answers inside the brand's catalog — product hallucination is the failure mode that destroys trust in retail chat, so it's designed out rather than prompted away.

After a production audit found social-channel bots implying orders that no pipeline could actually create, I enforced a channel capability boundary in the architecture — order emission gated at both the brain and Laravel layers, plus a sanitizer, documented as a project-wide non-negotiable. Public comment replies ship with the same two-layer safety design: an LLM prompt layer plus a deterministic product allowlist, so the bot cannot quote a product not bound to that post.

Mine: identity resolution, segmentation, loyalty, campaign delivery, order sync.

The CRM half of the platform, running over 1,026,113 customers and 2,330,105 orders. Identity resolution links repeat buyers across channels by phone; a segmentation engine drives campaign audiences on behavioural and transactional rules; a points-and-tiers loyalty system sits on live order history. Campaigns go out over WhatsApp and SMS with multi-account routing and delivery-receipt reconciliation — so delivery is measured, not assumed. The WooCommerce order-sync pipeline carries revenue and status attribution into merchant reporting at 26,900+ orders per reconciliation window.

Mine: the consolidation — shared auth, organisations, billing.

Raichu, Latias and Bulma were built separately and had drifted into three divergent auth and tenancy models. I consolidated them onto one shared FastAPI backend providing common authentication, organisations and billing behind three Next.js front ends — five channels of inbound customer messaging (web widget, WhatsApp Cloud API, Messenger, Instagram DM, TikTok DM) landing in one asynchronous Redis pipeline.

Mine: the Laravel admin platform and the REST API. Flutter clients were the team's.

12,000+ completed jobs at 4.9/5. Booking and scheduling, zone-based dispatch, live job tracking, customer/cleaner/driver roles, payroll, cancellation-window rules, Pusher realtime chat and job status, FCM notifications, RBAC, and CMS-driven policy pages. I migrated the payment gateway end to end — Stripe to Ziina, across backend and clients, including refund idempotency.

Mine: the full Laravel platform and the OAuth API behind the mobile clients.

A multi-sided courier marketplace: individual and business senders, drivers and driver companies with vehicle management, booking and package flows, in-order chat, wallets and promo codes, Stripe payments, and a country/state/city address hierarchy with per-domain settings. Realtime over Laravel Reverb; mobile clients authenticate through Passport OAuth.

Mine: the three-sided Laravel platform and the APIs behind each companion app.

Customer ordering and tracking, a merchant management panel for menus and incoming orders, and rider registration with earnings wallets — three roles, three surfaces, one order pipeline.

Operating across Canada, the US and four more countries. Booking with pickup/drop-off and vehicle type, instant estimates, real-time tracking, partner API integration, affiliate and franchise programs, bilingual EN/FR.

Merchandiser management, administrative workflows, and the REST API serving the field mobile app.

The customer designs a door or window and watches the visual and the price update live, then orders. Catalog, e-catalog, project gallery, accounts. It's the same modelling problem as a menu with modifiers — options that change both the render and the total, without a round trip.

Multi-tenant and white-label for SMBs: scan-to-add enrolment, branded SMS over Jazz and Telenor as the outbound channel, and a /c/[token] PWA bridge so a first-contact customer needs no app to enrol.

Filterable property search across type, location, bedrooms and area; listing and detail pages, an exclusive-property carousel, agent and branch content, and enquiry capture.

A Next.js admin panel non-technical clients actually run themselves: product, brand and branch CRUD, logo upload to Supabase Storage, Zod-validated forms, about-page CMS, dashboard counts.

Corporate web platform with a Next.js 16 + React 19 CMS admin.

A Next.js 16 admin reading live Firestore, built alongside the existing production apps and scanner tooling rather than replacing them — no migration, no downtime.

Laravel 12 API with a React 19 front end.