The System Wholesale Runs On.
A Laravel management platform and REST API that owns the catalogue, the customers, the orders and the money rules behind a B2B wholesale operation.
- Role
- Full-Stack Engineer
- Timeline
- Production System
- Industry
- Wholesale Commerce
- Status
- Live
What this system is
Awlad Ragab Wholesale Management System was built to modernise wholesale distribution workflows. A management dashboard sits over a Laravel REST API that owns products, categories, customers, representatives, orders, promotions, loyalty points, permissions and reporting — one scalable source of truth that the business operates from and that every client application reads.
What we needed to solve
Managing wholesale operations manually creates difficulties in handling products, customers, representatives, orders, promotions, inventory visibility, and reporting — and leaves no single source of truth for the applications that need to read any of it.
How we shipped it
A centralised Laravel platform that models the business as data — products, customers, representatives, orders, promotions, points, roles — and exposes it through a versioned REST API, so operations run from one dashboard and every connected client reads the same records.
How the system is wired
A modular architecture separating presentation, application, and data layers with REST contracts between the frontend and backend. Designed for clean scaling, observability, and predictable deployments.
Server-rendered + responsive client UI with reusable components and animation primitives.
Business logic in service classes, validated input, role-aware authorisation, and queueable side-effects.
Relational schema with indexed lookups, soft deletes, and migration-backed evolution.
REST APIs, webhooks, and third-party SDKs surfaced through thin adapters.
Engineering choices
In the wild
Business KPIs, order statistics, sales performance, and operational insights.
Manage wholesale orders, statuses, approvals, and processing workflows.
Centralized management of products, units, categories, and inventory structures.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Control discounts, campaigns, points programs, and customer rewards.
Hard problems, handled
Managing wholesale operations manually creates difficulties in handling products, customers, representatives, orders, promotions, inventory visibility, and reporting — and leaves no single source of truth for the applications that need to read any of it.
A centralised Laravel platform that models the business as data — products, customers, representatives, orders, promotions, points, roles — and exposes it through a versioned REST API, so operations run from one dashboard and every connected client reads the same records.
Maintaining performance under realistic production load.
Indexed queries, paginated lists, image optimisation, and lean client bundles kept the platform responsive end-to-end.
Built to stay fast
Design and interaction
Ready to ship and operate
What it does
Why we chose what we chose
Built on Laravel, PHP, MySQL.
Mature ecosystem, strong typing where applicable, and predictable performance characteristics for the workload.
REST-first integration boundary.
Keeps clients (web, mobile, partner) decoupled and trivially swappable without coupling to a single transport.
Results
The applications this system serves
The catalogue, pricing, orders, promotions and loyalty records administered here are what the Awlad Ragab customer application reads and writes through the same REST API. The mobile side ships as its own case study.
Other case studies
Building something similar?
Let's scope your platform — dashboard, mobile apps, APIs, the full stack.

